The CD Forum > PE Builder v3.1.10

Pages: 1, 2

Bart Lagerweij

Feb 13 2006, 02:43 AM

v3.1.10 is available.
http://www.nu2.nu/pebuilder/

Please read the change log below:

CODE

# PE Builder changes (from v3.1.9 until v3.1.10)

Boot BartPE on a system with 64MB
  Did you ever try to boot BartPE on a system with only 64MB of memory? I used
  to keep a separate CD (nickname "SmallPE") for this. This CD did not have a
  ramdrive and some other plugins, so that it would boot on those old 64MB
  systems. Not anymore! Thanks to an updated nu2menu and a little ramdisk
  parameter tuning, you can use the same BartPE CD also for 64MB system. Of
  course this does not include huge and hungry plugins like xpe and so...

Supported languages
  PE Builder currently supports the following languages:
  english*, dutch*, czech*, german*, japanese*, russian*, slovak*, arabic,
  brazilian, chinese_chs, chinese_traditional_bg5, french, greek, italian,
  macedonian, polish, portuguese, romanian, spanish and turkish.
  (*) Help pages are also available.

Pre-Flight check
  This is a first attempt to check if all files required to boot BartPE exist in
  the output location. At current a warning message is printed if a file is
  missing.

See below for more details...

Changes to pebuilder.exe:
- Added an error and warning counter on build dialog.
- Added a value of 8 to SourceDisksFiles attribute. This will rename the
  filename to uppercase.
- Uppercasing windows files is only done, when an ISO image is build.
- Added an option where you can disable uppercasing the windows files.
- The output directory was created in uppercase, while this is not needed. Fixed
  it.
- Added a routine that, after building, checks if files required for booting
  BartPE are missing from the output directory. Prints warning messages if files
  are missing.
- Added a parser variable @Lcid@, which expands to the system default language
  identifier (for example "409").
- Added an option to erase the ISO image and the output folder after succesfull
  CD burn.
- When burning using starburn, only devices capable of writing to CD or DVD are
  shown in the device listbox. Also when no device is selected PE Builder will
  select the best device for you.

Changed items:
+ pebuilder.inf: Removed olethk32.dll from KnownDLLs. W2k3 SP1 will crash if the
  NTVDM.EXE is stored in i386\system32 with the above RegKey. This happens for
  example with the dospe plugin. In W2k3 the olethk32.dll doesn't exist in the
  KnownDll List.
+ pebuilder.inf: bootfont.bin is now also copied. Mainly used in non-english
  languages. It uses the new sourcedisksfiles attribute value of 8 to uppercase
  the file in ISO images.
+ nu2shell.exe: v1.3, the environment variables USERPROFILE and ALLUSERSPROFILE
  where not set correctly (in fact they where erased). Fixed.
+ plugin\stinger: updated to work with new stinger filenames like "stng259.exe".
+ plugin\irfanview: added "files" folder.
+ plugin\ramdisk: updated ramdisk.inf. Now the ramdisk switches to 4MB in size
  when the system is low on memory. Normally systems with 90MB or less will end up
  with a 4MB ramdisk. This enables you to run your normal BartPE CD on system with
  only 64MB of memory.
+ plugin\nu2menu: updated nu2menu.exe to v0.3.52. Nu2menu was running out of
  memory a bit fast on systems with very little memory (<64MB). Fixed memory
  allocation bug.
- plugin\total commander\wincmd.ini, Small83Names=0
- Updated the following languages files:
  lang\english.lng: updated, the following language numbers: 288-293
  lang\dutch.lng
  lang\chinese_chs.lng
  lang\czech.lng
  lang\dutch.lng
  lang\english.lng
  lang\french.lng
  lang\german.lng
  lang\greek.lng
  lang\italian.lng
  lang\macedonian.lng
  lang\polish.lng
  lang\romanian.lng
  lang\slovak.lng
  lang\spanish.lng
- Updated the following help files:
  help\english\pluginformat.htm, added help for SourceDisksFiles attribute value 8.
  help\dutch\pluginformat.htm

Added items:
- Added the following languages:
  lang\arabic.lng
  lang\brazilian.lng
  lang\chinese_traditional_bg5.lng
  lang\japanese.lng
  lang\russian.lng
  lang\portuguese.lng
  lang\russian.lng
  lang\turkish.lng

Regards,
Bart.

Joshua

Feb 13 2006, 03:20 AM

great new functions !!!

thank's

Joshua

techman

Feb 13 2006, 08:14 AM

once again thanks for all the hard work
its a life saver.

stuartr

Feb 13 2006, 12:21 PM

Tested and working well with 63 plugins.

alex qiriazi

Feb 14 2006, 10:17 AM

QUOTE (stuartr @ Feb 13 2006, 05:21 PM)

Tested and working well with 63 plugins.

hello to all
when i downloaded 3.1.9 version and i tried to build computer restarted so i waited for the next version but same thing in 3.1.10.Can someone help me please

Daemonforce

Feb 14 2006, 10:32 AM

You probably have a horrible configuration setting or a bad SP install. Uninstall your current service pack and reinstall.

JonF

Feb 14 2006, 11:46 AM

QUOTE (Bart Lagerweij @ Feb 13 2006, 02:43 AM)

- Uppercasing windows files is only done, when an ISO image is build.

This means that those of us who build the ISO with a CMD file of our own have to put the uppercasing of I386 back in. No problem as long as we understand that

Ed_P

Feb 14 2006, 12:11 PM

QUOTE (JonF @ Feb 14 2006, 11:46 AM)

This means that those of us who build the ISO with a CMD file of our own have to put the uppercasing of I386 back in. No problem as long as we understand that.

oooo Good point JonF. Thanks for pointing it out.

QUOTE (alex qiriazi @ Feb 14 2006, 10:17 AM)

hello to all
when i downloaded 3.1.9 version and i tried to build computer restarted so i waited for the next version but same thing in 3.1.10.Can someone help me please

Start with a basic PEBuilder install and plugin setup. If that works slowly add in other plugins till the problem reoccurs. Then you will know what to debug.

If the basic PEBuilder install and plugin setup has the same problem your slipstreamed folder is most likely messed up and you will need to rebuild it.

hth

GenericSetup

Feb 14 2006, 07:32 PM

Bart - wanted to say thanks for all the hard work on the program. Great work.

Question/Comment though on version numbers.

PE Builder changes (from v3.1.9 until v3.1.10)

3.1.9 is a higher number than 3.1.10
By not listing the 0 or other number after the 9 doesn't change the value. If it were to use 2 places it would be .90 vs .10

Up to you how you version control your work, but thought I'd at least mention it.

Thanks again.

Ed_P

Feb 14 2006, 08:56 PM

QUOTE (GenericSetup @ Feb 14 2006, 07:32 PM)

3.1.9 is a higher number than 3.1.10
By not listing the 0 or other number after the 9 doesn't change the value. If it were to use 2 places it would be .90 vs .10

Not sure what country you are in but in America and most of Europe that I am aware of 10 is considered higher than 9. And it is worth more in terms of money too.

Certain, less sophisticated, (pc) systems sort decendingly 9s before 1s because they don't take into account the number of digits change. If you take the time and rename all the 3.1 versions prior to 10 to be 3.1.0x, ie the 0 BEFORE the digit, your listing will be fine.

Dumb computers.

Bart Lagerweij

Feb 15 2006, 03:17 AM

QUOTE (JonF @ Feb 14 2006, 05:46 PM)

This means that those of us who build the ISO with a CMD file of our own have to put the uppercasing of I386 back in.

Yes,
Bart.

Bart Lagerweij

Feb 15 2006, 06:53 AM

Hi,

When building from server 2003 you will get:

CODE

Checking for missing files
Error: File "c:\BartPE\I386\SYSTEM32\NTOSKRNL.EXE" not found
Builder has stopped because there are 1 build errors

This message should have been a warning message, but as you can see, it is an error messages.

Workaround:
You can close the build screen and press F5 key in the main screen to build ISO/Burn anyway...

Regards,
Bart.

stuartr

Feb 15 2006, 10:14 AM

QUOTE (Bart Lagerweij @ Feb 15 2006, 11:53 AM)

Hi,

When building from server 2003 you will get:

CODE

Checking for missing files
Error: File "c:\BartPE\I386\SYSTEM32\NTOSKRNL.EXE" not found
Builder has stopped because there are 1 build errors

Hmmm, I"m building from Server 2003 and not getting this error message at all.

oscar

Feb 15 2006, 12:08 PM

May somebody remember me why/when uppercasing?

Is it a must uppercasing? I guess not because I have no problem at all with my CD (pebuilder 3.1.10,XPE, XP SP2, 700Mb, ISO created with cdimage.exe) and no file is uppercased

Thanks

hilander999

Feb 15 2006, 12:28 PM

QUOTE (alex qiriazi @ Feb 14 2006, 10:17 AM)

hello to all
when i downloaded 3.1.9 version and i tried to build computer restarted so i waited for the next version but same thing in 3.1.10.Can someone help me please

As strange as this is going to sound, some pc configurations are having trouble with
the newer versions of pebuilder & restarting.

One workaroud is to start the PC in "safe mode" & then run pebuilder, this seems to work
although I have no idea as to what the error is related too.

We tested on several systems of different configurations that had the problem & the only "common ground" between them was some of the anti-virus programs and\or drive overlays (ie..Acronis).

PS: Almost forgot.....
THANK YOU BART.

Bart Lagerweij

Feb 15 2006, 03:34 PM

QUOTE (stuartr @ Feb 15 2006, 04:14 PM)

Hmmm, I"m building from Server 2003 and not getting this error message at all.

I got it building from Server 2003 US (no SP)

Bart.

batchman61

Feb 15 2006, 06:08 PM

my environment since long without any trouble:

Running OS Version: 5.0.2195 (Service Pack 4)
Source product is: Windows XP Professional
CD-Rom name is: Windows XP Professional Service Pack 1-CD

PE Builder 3.1.9 : OK
PE Builder 3.1.10 : Error: File "...\NTOSKRNL.EXE" not found

Daemonforce

Feb 15 2006, 06:45 PM

QUOTE (Bart Lagerweij @ Feb 15 2006, 12:34 PM)

I got it building from Server 2003 US (no SP)

Bart.

This is funny.

You still don't trust service pack 1?

I don't trust it and I don't like what it did to IIS among several other neat tools I like to use. I still need to do several tests with both the gold and slipstreamed builds. That's probably why I haven't built a (working)BartPE from anything outside of Windows XP this year.

QUOTE (batchman61 @ Feb 15 2006, 03:08 PM)

my environment since long without any trouble:

Running OS Version: 5.0.2195 (Service Pack 4)
Source product is: Windows XP Professional
CD-Rom name is: Windows XP Professional Service Pack 1-CD

PE Builder 3.1.9 : OK
PE Builder 3.1.10 : Error: File "...\NTOSKRNL.EXE" not found

Comedy Goldmine!

Didn't Bart drop support for all Windows NT 5.0 builds around the start of PE Builder v3.1 and move straight to NT 5.1 for the minimum, or am I thinking of something else?

Something tells me that WinPE can be made from Windows 2000, but I'm not sure why. Maybe it's my old copy of Disk Commander. Maybe it's because I remember mention of PE Builder and Windows 2000...If it worked then, it should work now. Right?

gely

Feb 16 2006, 05:47 AM

QUOTE

This means that those of us who build the ISO with a CMD file of our own have to put the uppercasing of I386 back in.

QUOTE (Bart Lagerweij @ Feb 15 2006, 09:17 AM)

Yes,
Bart.

This means that who use the sherpya binl python script on linux box for ris booting can use another pebuilder than 3.1.3

thanks for all your work.

---happy admin here :]

Bart Lagerweij

Feb 16 2006, 09:57 AM

QUOTE (Bart Lagerweij @ Feb 15 2006, 12:53 PM)

Hi,

When building from server 2003 you will get:

CODE

Checking for missing files
Error: File "c:\BartPE\I386\SYSTEM32\NTOSKRNL.EXE" not found
Builder has stopped because there are 1 build errors

After more testing it shows that besides server 2003 (no SP) Windows XP (with SP1) also has the same problem...

Regards,
Bart.

Stugpanzer

Feb 16 2006, 09:59 AM

You never cease to amze me! Thanks again Bart!

Bart Lagerweij

Feb 16 2006, 10:11 AM

@all

I need to find out what makes setupldr.bin decide what kernel (and what hal) it is going to load...

Bart.

cdob

Feb 16 2006, 10:27 AM

@Bart

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

XP SP1 setupldr.bin loads file name ntkrnlmp.exe, but that's a renamed ntoskrnl.exe
XP SP2 and 2003 setupldr.bin loads file name ntoskrnl.exe

Ntdetect.com detect machine and setupldr.bin decide hal.
ACPI hal: There are some rules, compare txtsetup.sif and biosinfo.inf: e.g. old machines don't use ACPI.
Another possiblility: boot BartPE, press F5 and select hal youself.

By default uni processor kernel and hal are used, even at a multi processor machine.

GenericSetup

Feb 16 2006, 01:44 PM

QUOTE (Ed_P @ Feb 14 2006, 05:56 PM)

Not sure what country you are in but in America and most of Europe that I am aware of 10 is considered higher than 9. And it is worth more in terms of money too.

Dumb computers.

Math is math regardless of which Country. Simply becuase the second digit is listed does not change the fact that .9?(unknown) is higher than .10(known) If one were to do math on this

1.0
- .9
= .1

1.0
- .10
= .9

I'm new here and not trying to cause any issue, was simply pointing out that the versioning might be done a bit different is all, but also said was okay if he was good with it.

d4vr0s

Feb 16 2006, 04:30 PM

That's only if you're using decimals.
If you consider the "." being only a delimiter, then .9 is smaller than .10

Dangerous

Feb 16 2006, 05:30 PM

QUOTE (Bart Lagerweij @ Feb 15 2006, 11:53 AM)

Hi,

When building from server 2003 you will get:

CODE

Checking for missing files
Error: File "c:\BartPE\I386\SYSTEM32\NTOSKRNL.EXE" not found
Builder has stopped because there are 1 build errors

I have on on my system xpsp2 and 2003sp1 ,Tried to build using xpsp2 got errors tried with 2003sp1 created iso fine ....

error log
Checking for missing files
Error: File "iastor.sys" not found
Error: File "a320raid.sys" not found
Error: File "aac.sys" not found
Error: File "aarich.sys" not found
Builder has stopped because there are 4 build errors

Is the the old uppercasing again ??
Still Excellent work THANK YOU BART

Oops My Bad used the fixdell plugin and it works

but it was slower than the 2003sp1 version( will try later with clean boot not vmware )

mbarnes

Feb 16 2006, 06:20 PM

Hi Bart

I have been trying out V3.1.10 on a old PC with only 64 MB ram.

With no added plugins resulting 4MB ramdisk allows Bart CD to boot up correctly.

With full compliment of plugins 4 MB ramdisk is too large and memory runs out just as start button is about to be put on bottom left corner of screen ( it ends up on top left corner).

With no ramdisk my Bart CD boots up but causes many program errors about missing temporary directory.

Previously with a 1MB ramdisk and V3.1.3 & 3.1.9 and all plugins in UBCD4WIN project Bart CD will boot up.

Please could you make the minimum ramdisk size configureable (ini file or registry) in next release

can nu2menu.exe be patched to set ramdisk in low memory PC's 1MB or 2MB ?

Another enhancement request, can uppercasing files depend on only on tick box and not if build iso selected

regards

Mike Barnes

FileCity

Feb 16 2006, 07:38 PM

On my PEBuilder Source the RAMDisk is at 2MB as boot default. The user can change it at boot with a batch file menu in my autorun sequence.

2MB as default is enough for BGINfo to put his BMP. Anyway, in low memory PCs people needs more a swap file to run large applications, only if the partition on the disk don't needs to be repaired. Putting a swap file can erease data to be restored...

SteelTrepid

Feb 16 2006, 07:45 PM

All the "automatic" stuff is nice.....but I still prefer to use Joshua's PreShell. You can change the size at boot. If you boot on a decent system, select a bigger ram drive. If booting from an old system, select the 2Mb ram drive.

paraglider

Feb 16 2006, 07:52 PM

Sherpya autoramresizer automatically sets the ram disk size depending on the size of the available ram. That's better than having to make a manual choice.

Some people do however have difficulty getting the autoramresizer to work.

SteelTrepid

Feb 16 2006, 07:58 PM

Yes autoramsizer was a nice option...I used to use it for a long time.

However it doesn't work right when you are on a low memory system. The only way you can get a BPE CD to boot on a system with only 48 or 64 Meg of ram is if you specify a 2-4 Meg ram drive. Take any more and you don't have enough memory to run the shell and other applications. Autoramsizer always wants to allocate more of a ram drive on these systems.

Beta builds of UBCD4Win 3.0 using PreShell to setup a 2 Meg ram drive on a system with only 48 meg of ram do boot and are quite functional.

FileCity

Feb 16 2006, 08:18 PM

Personnaly I prefer to set it at 2MB by default and let the user to choice from 32, 64 or 96. Most of the time you don't need a ramdrive. You need one if you plan to use Opera or any RAMDisk application, or a cache for Nero... If you don't want to use these, you don't need...

But it's interesting to put at least a 32MB RamDisk just in case, if the system is recent, no problem anyway...

SteelTrepid

Feb 16 2006, 08:29 PM

QUOTE (FileCity @ Feb 16 2006, 08:18 PM)

You need one if you plan to use Opera or any RAMDisk application, or a cache for Nero..

Man am I a jerk or what!! It appears I keep picking at people but that is honestly not what I'm doing. I don't like to offend people or start fights. I just like to discuss options and other information.

So what I quoted you saying......you don't even need a ram drive for Opera. UBCD4Win 2.6 has an Opera plugin that runs from the CD. I needed that functionality from it for the project, to make it easier to view CHM files, etc.

mbarnes

Feb 17 2006, 09:16 AM

Hi all

With V3.1.10 you can not effectively set a ramdisk less than 4MB. For low ram machines, 1MB or 2MB ramdisk will be upped to 4MB, before being given chance to select ramdisk size

For PC's with few plugins creating registry settings this is probably OK, but after plugins for Explorer, MMC etc are installed the registry becomes too large to fit in memory on PC with 64MB RAM

regards
Mike Barnes

later 23 Feb 2006
my comment above was wrong, possibly due to wrong version of nu2menu.
I set initial ramdisk size at 2MB, on PC with 64MB RAM, it booted up without any 'out of memory' errors, with a 2MB ramdisk, some programs required virtual memory pagefile.sys to work (Atlantis)

FileCity

Feb 17 2006, 05:20 PM

I have these plugins (legally) on a corporate test system and I can boot the BartPE on 48MB of RAM. All these applications are FULLY pre-configured and all parts of their registry is present. You cannot run all of them unless you have a pagefile but the system is bootable, 100% stable and functionnal into 48MB at minimum...

These are only applications, I have also VB, MMC Dial-UP, PPPoe, and all stuff...
So registry is not too large to fit in memory on PC with 64MB RAM or less, not true...

A43 : 2.4.5.0
Acrobat Reader : 4.05b
Acronis Disk Editor : 6.0.0.385
Acronis Drive Cleanser : 6.0.0.383
Acronis Migrate Easy : 7.0.0.614
Acronis Partition Expert : 8.0.292
Acronis Recovery Expert : 1.0.0.139
Adaptec ASPI : 4.71.2
Autorun : 1.0.5
Bart Stuff Test : 5.1.4
BartPE Installer : 2.0.2
BGinfo : 4.7.0.0
Bootable CD Wizard : 2.0a1
CDRWin : 4.0a
Device Manager Clone : 1.0.0.7
ERD Commander : 2003
EventLog Explorer : 1.3.0.155
Explorer XP : 1.0.7
Fab's Autobackup : 2.1.0.0
FlashFXP : 3.2.0.1080
Ghost32 : 8.2.0.1117
Graphic Network Applications : 0.1.3
Hot CPU Tester Pro : 4.2.2.0
HWPnP : 1.0.0.22
MBR Wizard : 1.53
MDAC 2.81 And DAO 3.5 Support : 0.9.9
MoveIt Freely : 3.2.0.1
Nero Burning Rom : 6.6.1.4
Norton SystemWorks CD Utilities : 2005
NU2 Menu : 0.3.5.2
NU2 Shell : 1.0.3.0
Off By One : 3.5.4.0
OpenSSL : 0.9.8a
Opera : 8.51.7712.0
Pablo Commander : 1.4.0.0
Partition Magic : 8.05
PCI32 Devices Report : 1.2.0.0 + 1.4
PeNetCFG : 2.2.0.0
Putty : 0.58
QuickSFV : 2.3.2.0
RegEditPE : 0.9c
Registry Expander : 1.2.0.0
Runtime DiskExplorer FAT : 2.31
Runtime DiskExplorer NTFS : 2.31
Runtime DriveImage XML : 1.11
Runtime GetDataBack FAT : 2.31
Runtime GetDataBack NTFS : 2.31
Runtime RAID Reconstructor : 2.31
Sandra Pro 2005 : 10.50.2005.2
Secure File Eraser : 5.7.0.0
ServicesPE : 0.9
Set PageFile : 1.0.0.8
Tiny Hexer : 1.6.0.4
Total Commander : 6.5.4.0
Unstoppable Copier : 2.11
WinImage : 8.0.0.8000
WinRAR : 3.51.0.0
WinZip 10.0 : 21.0.6685.0
WS_FTP Lite 5.08 : 2000.1.12.1

GenericSetup

Feb 17 2006, 05:50 PM

QUOTE (d4vr0s @ Feb 16 2006, 01:30 PM)

That's only if you're using decimals.
If you consider the "." being only a delimiter, then .9 is smaller than .10

Well since Bart has remained silent on the subject I will accept that he is okay with it.

However I have to disagree with you as it's not a personal choice. Once the file has been tagged with this value in the version field your computer now analyzes that value and deals with it in a binary fashion. ie. mathmatically. Even if in Europe and using the comma as output to the user it still would sort it as I've shown above.

Okay, enough on this minor issue from me - sorry to beleaguer on with it.

Ed_P

Feb 17 2006, 06:20 PM

If you consider .10 as being a decimal what than do you consider the .1 before it? What math system uses numbers with 2 decimals?

d4vr0s said it correctly, the dot is simply a delimiter. And the computer isn't sorting it mathematically, it is sorting it alphabetically.

ncfl_maine

Mar 9 2006, 04:37 PM

Any plans for BartPE x64 ?

Bart Lagerweij

Mar 10 2006, 02:40 AM

QUOTE (ncfl_maine @ Mar 9 2006, 10:37 PM)

Any plans for BartPE x64 ?

Yes, I have puchased new machine (with athlon64) just for that...
But I want to make some other changes first...
Not sure when I can start on x64 support.

Regards,
Bart.

ncfl_maine

Mar 10 2006, 09:30 PM

QUOTE (Bart Lagerweij @ Mar 10 2006, 07:40 AM)

Yes, I have puchased new machine (with athlon64) just for that...
But I want to make some other changes first...
Not sure when I can start on x64 support.

Regards,
Bart.

Most excellent! I've got a couple EMT64 (Intel) CPU's with my Precision 670. Win x64 treated them identical to AMD64 on the installation.

Oom Erik

Mar 11 2006, 10:48 AM

QUOTE (Bart Lagerweij @ Feb 13 2006, 08:43 AM)

...
Changes to pebuilder.exe:
- Added a parser variable @Lcid@, which expands to the system default language
identifier (for example "409").
...

It would be nice to be able to overwrite this variable for system default language (of the building machine, I assume) with a specific language code.

E.g. in PEbuilder options, show default language language code (derived from building machine), plus extra field to overwrite this default with another language code. If extra field is empty, just use derived language code (from building machine).

This would enable e.g. using a Dutch buildig machine for an English BartPE.

Bart: idea for next version ?

Regards,
Erik.

krash_silver

Mar 12 2006, 10:46 PM

If I'm previosly installed my PC using a Ghost image(has some plugins), and I'm using different WinXP SP2 cd as the source.

1 ) Do you think I able to create the Bootable BARTPE file?? Currently I couldnt build the File, It has lot of errors while I'm building it. ANy Idea??

2) Is that I must install the Exact WinXP into the PC and Build it using the SAME CD while locating the Source??

Thank mans..

Oom Erik

Mar 13 2006, 12:20 PM

I use different WinXP SP2 version on build machine and as PEbuilder source, no problem.
Don't know what you mean/do with Ghost images though.

Regards,
Erik.

zoolander

Mar 27 2006, 04:01 PM

QUOTE (Bart Lagerweij @ Feb 16 2006, 08:57 AM)

After more testing it shows that besides server 2003 (no SP) Windows XP (with SP1) also has the same problem...

Regards,
Bart.

I do not receive this error when building but I get a similar error

File "c:\BartPE\I386\SYSTEM32\NTOSKRNL.EXE" could not be loaded

when I try to boat with the disk made using PE Builder

Any Ideas?

Ed_P

Mar 27 2006, 05:47 PM

I believe that is fixed in the 3.1.10a version.

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

ncfl_maine

May 22 2006, 08:22 AM

Any update on a BartPE X64 ?

Kristi

Sep 9 2006, 08:57 PM

"Source file is wrong version. E:\i386\NTdll.dll is 5.1.2600.0 must be 5.1.2600.1045 or higher you must use XP service pack 1 or Server 2003"

This is the error I get when pointing to my CD drive with my XP installation disk in. Nothing came up in search.

rdsok

Sep 9 2006, 09:23 PM

QUOTE (Kristi @ Sep 9 2006, 08:57 PM)

The answer is simple and staring you in the face ( so to speak ).... your source CD must have XP SP1 or newer... apparently yours is an earler version of XP. Slipstream either SP1 or SP2 and create a new CD... instructions for doing this can be found all over the web and also in this forum.

Alber

Oct 27 2006, 06:29 AM

Hi, I am using pebuilder3110a and I have created a copy of XP SP2 CD in a folder called BartPE. I want that my USB pen drive runs XP. I read that I need some files of W2003 in a folder called srsp1 (the files are ramdisk.sys and setupldr.bin)

With this, in command line I put pe2usb.cmd -f drive (my usb) and when I run my laptop (I enabled in the BIOS the USB) the USB does not run XP

What is the problem??

The files in my usb are:

27/10/2006 11:38 158.959.616 bartpe.iso
04/08/2004 03:07 47.564 ntdetect.com
24/03/2005 20:33 298.096 ntldr
27/10/2006 11:30 157 winnt.sif

Ed_P

Oct 27 2006, 10:07 AM

@Alber

Please create a new thread and post your question in the BartPE Troubleshooting section. Thanks.

This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.