cdorobantu

PELoader

15 posts in this topic

Hello everyone,

I have been trying to find a way to start this peloader application in WinPE and I can't find anywhere instructions on how to do it step-by-step.

If I just try running it from the command prompt I get the following message:

"You need not use a patched Winlogon to break WinPE/BartPE resource limits :). Please make a normal WinPE/BartPE build to make use of PE Loader."

I do not haved a patched Winlogon. The version of PE that I am using was created with WinXP PRO SP2.

Any info would be appreciated.

Thanks.

0

Share this post


Link to post
Share on other sites

No one has any idea on how the 24h limit can be broken? I need to clone defective drives that could last well past the 24h limit.

Any suggestions are welcome.

Thanks.

0

Share this post


Link to post
Share on other sites

This is a screenshot of a script created by holger and will automatically remove all limitations from the PE environment on boot-up.

24h-limitation.PNG

You can find inside the latest 053 version wich be download from here:

http://www.boot-land.net/forums/index.php?...ic=652&st=0

You can also use nu2shell from bartPE or manually use the PEloader from TheTruth,

Site:

http://www.geocities.com/pierremounir/

Manual instructions:

http://www.911cd.net/forums/index.php?showtopic=7049

Hope this helps! :)

0

Share this post


Link to post
Share on other sites

Normally I would recommend trying the version 052 found here:

http://www.boot-land.net/index.php?ind=dow...view&iden=2

It's a ~3.7Mb download wich already includes the script created by holger ("MiscSettings.Script")

At this moment I recommend you to download the latest beta of version 053 mostly because you can use it to download the latest scripts directly from our download server.

From there you'll find the liveXP project wich contains the referred script you need.

Configuration for livexp is simple - Add the path to your windows install CD files and then press the play button to see the results, resulting in a 51Mb ISO wich looks like this:

post-96036-1168275661_thumb.jpg

Better use a retail version of XP SP2 - preferably not slipstreamed on nlited - or use a windows 2003 to enable automated ramboot.

Let me know how this works for your goals..

:)

0

Share this post


Link to post
Share on other sites

@Nuno Brito

I have tried to create a LiveXP ISO using WinBuilder, but I encountered the following problems:

1. After creating the ISO, I used VMware to run the file and I received a message that the BIOSINFO.INF file is missing. I added that file to the ISO using MagicISO

2. After adding that file, I again ran the ISO in VMware and I got another message; this time KDCOM.DLL was missing. I added that.

3. After adding the two missing files, I ran the ISO again and I got a message this time in regards to NTOSKRNL.EXE, that it cannot be loaded. Even if I add another version of that file to the ISO, the error persists.

What am I doing wrong?

Thanks

0

Share this post


Link to post
Share on other sites

I'd guess that it's related to the Windows Install CD you're using..

Just a check: to sucessfully build a liveXP you'll will need set the path to your Windows Install CD files - you find these settings on the tab named "Paths" wich contains three boxes (sourcedir, targetdir and iso filename) - only the first (sourcedir) needs to point to the location where your install files are placed - these can be either a CD, or just a folder where you've placed copied files from this CD (recommended since it's also faster to copy them from disk)

winbuilder-config.PNG

If this error persists then this might be due to your source - is it nlited, multiboot type or something like this?

It would be better to use a unmodified windows XP sp2 copy - preferably not an OEM, just one of those retail versions wich are more common to find.

At this step, if you haven't yet booted - then you should post your log.html file wich reports all the things that were done during the build - you find it inside the log tab - next to the paths tab.

In either case, if you want to try with a fresh source and have a fast web connection - I'd recommend download a windows 2003 R2 trial ISO straight from the microsoft site for your testings:

http://www.microsoft.com/windowsserver2003...al/default.mspx

The errors you've mentioned sure looked like the scripts haven't found any of the files that we're needed so you'd probably get a lot of errors inside your log, in most cases they were certainly related to the Copy & Expand script wich needs to copy these files from %targetdir%\I386 where %targetdir% is the path to your windows install folder.

Hope this helps!! :)

0

Share this post


Link to post
Share on other sites

@Nuno Brito

Thank you very much with your help with this. I managed to get LiveXP going but only up to a point. As soon as I get into Windows, I get two errors that say BROWSEUI.DLL & SHDOCVW.DLL are missing. After I click OK on the dialog box for these two errors, the system reboots. This becomes a continuous loop.

Any suggestions on how to fix this?

Thanks again!

0

Share this post


Link to post
Share on other sites
@Nuno Brito

Thank you very much with your help with this. I managed to get LiveXP going but only up to a point. As soon as I get into Windows, I get two errors that say BROWSEUI.DLL & SHDOCVW.DLL are missing. After I click OK on the dialog box for these two errors, the system reboots. This becomes a continuous loop.

Any suggestions on how to fix this?

Thanks again!

This is a sympton due to the lack of enough RAM - you can solve it disabling the autoUPX script since UPX makes exe's smaller but also very resource hungry - you build will grow to around 60Mb but should be working fine on machines will less RAM..

It was last approached here with more limitations details:

http://www.boot-land.net/forums/from-the-v...aving-t954.html

:)

0

Share this post


Link to post
Share on other sites

I have tried your suggestion to disable autoUPX and I get the same errors.

I have attached a screen shot of the errors that I am getting.

post-117796-1169144231_thumb.jpg

post-117796-1169144251_thumb.jpg

0

Share this post


Link to post
Share on other sites

@Nuno Brito

I got it to work!! It appears that I was getting these errors when I was using RAMDisk. I switched to File Based Write Filter and everything tested ok.

Thanks very much for all your help and sorry to keep bothering you!

YAY!!

0

Share this post


Link to post
Share on other sites

@Nuno Brito

Actually, I do have another question for you. How would I go by enabling WMI in this version of Windows. I need to run some software that gets some information from the WMI repository.

How would I go about making this image bootable from a USB key?

Thanks.

Edited by cdorobantu
0

Share this post


Link to post
Share on other sites

There a few tools available to make USB boot possible, for winbuilder some are already available on the russian discussion site:

http://72.30.186.56/babelfish/translate_ur...6start%3d600#lt

Russian .script developer HighwayStar has published them on his site:

http://highwaystar.boot-land.net/scripts/

This ought help you getting started..

About WMI - perhaps you should ask for more informations from the forums on boot-land.net - I personally haven't yet tried to add it, but I think some developers have already created script support for this task.

:)

0

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.