Troubleshooting Faqs, The common problems > Updated 01-26-2008 Options

[d4vr0s]

I think we should get a FAQ going here, maybe an admin can make it sticky if enough people contribute.
Any additions will be welcome.

Also, please read Bart's official FAQ on the PEBuilder website.
Don't forget about the help files that come with pebuilder under the Help directory.
Paraglider posted a few links for information on how to get started with pebuilder or building plugins Here

If you are going to post a question about a Blue Screen Of Death (BSOD), please post the actual stop message and other information shown in the error.
It's extremely hard to troubleshoot these without that information.

Q.01: Can I use my installed windows for the source to build BartPE?

A: No. You must use an install source such as the OEM CD that came with the system.
You can copy this to a folder on the hard drive to use as the source.

Q.02: What service pack is on my source disk?

A: Look at the root of the disk.

CODE

WIN51       = Both Win XP and Server 2003 have this file (Doesn't appear to be required for booting)
   WIN51IP     = Win XP Pro
   WIN51IP.SP1 = Win XP Pro SP1
   WIN51IP.SP2 = Win XP Pro SP2
   WIN51IC     = Win XP Home
   WIN51IC.SP1 = Win XP Home SP1
   WIN51IC.SP2 = Win XP Home SP2
   WIN51IP2    = Windows XP Media Center and Tablet Edition
   WIN51IL     = Small Business server 2003
   WIN51ID     = Data Center Server 2003
   WIN51IA     = Enterprise Server 2003
   WIN51IS     = Standard Server 2003
   WIN51IB     = Web Server 2003

Future service packs would be .SP3 etc.
Server 2003 follows the same conventions with the filename appended with SP and the service pack #

These files are also required on your boot CD, if they're missing you'll see errors such as:

Please insert the disk labeled XXXXX CD-ROM into Drive A:

You're missing the main identifier file, WIN51IP for example.

Please insert the disk labeled XXXXX Service Pack XXXXX CD into Drive A:

You're missing the service pack identifier file, WIN51IP.SP2 for example.

Q.03: How do I slipstream a service pack?

A: First of all, slipstream means to update the original CD files with a service pack and/or hotfix so you can use that to install with the most current version.
There are different methods of doing this. Microsoft has a knowledge base article for it: 828930
Other popular choices are AutoStreamer and nLite

Q.04: When trying to slipstream I am getting this error:

"This Service Pack cannot be integrated..."

A: mbarnes posted the answer here: Service Pack 2, slipstream error

Q.05: Can I use a BartPE image to recreate the setup directory and/or plugins?

A: No.

Q.06: Can I boot BartPE from a USB drive?

A: Read these threads: !NEW BartPE To USB Flash Stick Utility and XP booting direct from USB

Q.07: Can I write CDs from BartPE and/or remove the BartPE disk after booting?

A: Read this thread: Help with booting .SDI images from CD.

Q.08: Why am I getting

/cygdrive/c/Win PE/pebuilder/mkisofs: No such file or directory. Unable to open disc image file
Returned exitcode 2
Error: ISO builder (mkisofs) returned error code 2
ISO image "C:\Win PE 3\pebuilder.iso" created.
Build process done...

when pebuilder runs?

A: Don't use directory names that have spaces with pebuilder.

Q.09: I'm getting an error during boot "Can't find filename.xxx" but it's on the disk and in the location it's supposed to be?

A: Most likely it's not UPPERCASED.
Make sure you're running the newest PEBuilder which should resolve this in most cases.
If the file does not exist and you're using a Dell CD, read Q.12

Q.10: Why am I getting

Processing INF file "Someplugin.inf"
Section "Append"
Error: Cannot find file "nu2menu.xml"
Error: appendFile() failed

when pebuilder runs?

A: You've probably disabled the nu2menu plugin. If you did this on purpose you need to either edit your plugins and comment out ; the nu2menu.xml line under [Append] section or use Paraglider's suggestion

Q.11: Why am I getting

Cleanup temporarily files
Error: DeleteFile() "C:\pebuilder313\petmphive" failed.
Error: DeleteFile() "C:\pebuilder313\petmphive.log" failed.
Error: DeleteFile() "C:\pebuilder313\setuphiv" failed.
Error: DeleteFile() "C:\pebuilder313\setuphiv.log" failed.
Builder has stopped because there are 4 build errors

on my Dell? (i.e. Using a DELL OEM CD as source)

A: Look here
A2: If you don't have a Dell this can also be caused by malformed registry entries in a plugin.
You need to unload the petmphive from your registry before trying again.
Load regedit and look for any keys that have pebuilder in their key name. They will be immeditately under the HKEY_USERS key. If you find such a key select the key then from the file menu choose unload hive.
Or simply reboot the system.

Q.12: I'm getting

The file XXXXXX could not be found.

errors when booting and my source CD is from a Dell.

A: You probably need the fixdell plugin.
There is one posted here and will be updated when needed.

Read here some related thread to understand the problem and the way it is fixed:
http://www.911cd.net/forums//index.php?s=&...ost&p=82681
http://www.911cd.net/forums//index.php?sho...st=0#entry87988
http://www.911cd.net/forums//index.php?showtopic=23424


Q.13: Why am I getting this message in XPE?

XPELogon
Main shell died with code 0x1 before starting (GetLastError()==126),
there are some problems... I'll start command prompt now

A: You're running XPE on a writable drive.
You need to copy EMPTYREGDB.DAT to the system32 folder.
You can find this file in an installed windows\system32 folder.

Q.14: I'm getting this message with PEBuilder 3.1.9 :

Error: cannot find file "somefile or garbage charachers here"
Error: setValue() failed 0: The operation completed successfully. (Line 0 String "winpeoem.sif,OEMDriverParams,OemDriverRoot,drivers")

A: PEBuilder 3.1.9 doesn't provide file winpeoem.sif anymore. More can be read in this thread.

Q.15: Why can't I see my harddrive?

A: This can happen for different reasons.
1) Do you have a controller for which XP doesn't have built in drivers? IE: Serial ATA, RAID or SCSI?
Look here for possible solutions.
Also, you could try the ubcd4win driver pack, read this Post for details.
2) Do you have GoBack installed on the drive?
This needs to be disabled because it changes the filesystem identifier so BartPE won't recognize it.

Q.16: Why am I getting this error?

Error: SetupIterateCabinet returned 13: The data is invalid.
Error: fileCopy() failed
Processing INF file "C:\pebuilder314-beta\pebuilder.inf"
Section "DelLine"
Error: CreateFile "C:\pebuilder314-beta\BartPE\I386\INF\NETMSCLI.INF" returned error 2: The system cannot find the file specified.
Error: fopen "C:\pebuilder314-beta\BartPE\I386\INF\NETMSCLI.INF" returned error 2: The system cannot find the file specified.
Error: delLine() failed
Error: doInfAppend() file="C:\pebuilder314-beta\pebuilder.inf" failed

A: This can be caused by a corrupt drivers.cab.
If you're using a CD for your source it might be dirty your drive might be having problems reading it.
You might try copying the entire CD to a folder on your harddisk and use that as the source.

Q.17: Why do I have duplicate menu enties in my Nu2Menu?

A: You probably have more than one plugin with the same Menu ID.
Paraglider has a fix for this on his website called Sortmenu.
This can also be caused by malformed entries in your menu, and example of this is here

Q.18: Why Don't I have any desktop icons?

A: You're probably not using an explorer shell.
By default BartPE uses nu2menu as it's shell which is faster and uses less resources.
If you want more windows-like functionality then you probably want to add XPE to your build.
The Reatogo package also uses XPE.

Q.19: How can I get my NForce LAN to work?

A: Read this Thread

Q.20: Can I change the default shell at during bootup?

A: Yes, there are a few methods of doing so, two of which are:
1) Joshua's PreShell
2) The Truth's PE Shell Swapper

Q.21: How can I make a donation or thank Bart for all the hard work he has put into this?

A: Visit his donation page.

Q.22: Why does the time in the PC clock change when I use BartPE?

A: Read this thread

Q.23: How do I get an application to run at startup?

A: This would depend on the shell you are using.
For the default shell (nu2menu) read the documentation located in <pebuilderDir>\plugin\autorun\autorun.htm
For XPE read the xpe.htm in it's folder.
There are also more advanced methods of running programs during the boot process, read this thread for more information.

Q.24: How can I help keep the 911CD forums alive?

A: You can donate to schamber@zeoran.com via paypal.
The source of this address can be found in this Announcements Thread.
Of course sharing experience and knowledge helps as well.

Q.25: My USB Keyboard isn't working after my disk boots.

A: Give the plugin from this Thread a try.

This post has been edited by jaclaz: Dec 2 2009, 03:42 AM

Reason for edit: Updated links to new versions of the DELL fix

[CWorks]

not really Troubleshooting related but these are common questions asked

Q.01: How to add files to an .ISO?

A: Use a program that supports ISO 9660:1999
I prefer UltraIso for this with only these settings checked

• optimize
• Max(221)
• Omit ISO 9660 version number

after adding files i choose save as with a new name (I don't use this method anymore)

this is the way I prefer to do it now:
add files to pebuilder out directory and choose from Builder menu Build ISO/CD or just hit F5

Q.02: How to edit reg hives from pebuilder output?

A:

1. start regedit.exe
2. highlight HKEY_LOCAL_MACHINE or HKEY_USERS
3. from file menu choose Load Hive
4. browse to your output folder and choose the hive to load
   I386\SYSTEM32\CONFIG\SOFTWARE (for HKLM\SOFTWARE)
   I386\SYSTEM32\CONFIG\DEFAULT (for HKCU)
   I386\SYSTEM32\SETUPREG.HIV (for HKLM\SYSTEM)
   
5. choose a name when asked like pe-soft or pe-setup
6. when done editing click on the name you gave it and choose unload hive from file menu
7. rebuild in pebuilder from Builder menu Build ISO/CD or just hit F5

Q.03: How to burn .iso with Nero?
A: From Recorder menu choose Burn Image

Q.04: How to use RegExpander?
A: Posted here

Q.05: How to create shortcuts for XPE?
A: A short detailed explanation of a shortcut

shortcuts aren't that hard to make once you know the format

list of folders to create shortcuts in
* "Sherpya\XPEinit\StartMenu" to place shortcuts on Start Menu Root
* "Sherpya\XPEinit\StartUp" is used for StartUp (autorun programs after explorer.exe)
* "Sherpya\XPEinit\Desktop" to place shortcut on desktop
* "Sherpya\XPEinit\Programs" to place shortcuts on Start Menu Programs folder
* "Sherpya\XPEinit\QuickLaunch" to place shortcuts on QuickLaunch
* "Sherpya\XPEinit\SendTo" to place shortcuts on SendTo Menu

folder under startmenu\programs displayed Name path to program
0x2,"Sherpya\XPEinit\Programs","Sys Tools\Ad-Aware SE","%SystemDrive%\Programs\adaware\Ad-Aware.exe"

for desktop
displayed Name path to program
0x2,"Sherpya\XPEinit\Desktop","Ad-Aware SE","%SystemDrive%\Programs\adaware\Ad-Aware.exe"

and what's with the 2 pipes || , one is for the command but not using it here so it's empty and second is for the icon
this is all on one line it may look like two but when copied it will be one line
displayed Name path to program shortcut icon to use the ,0 at the end is the icon index in the file starting at 0
0x2,"Sherpya\XPEinit\Desktop","Ad-Aware SE","%SystemDrive%\Programs\adaware\adaware.cmd||%SystemDrive%\Programs\adaware\Ad-Aware.exe,0"

And of course if you need to add switches to them
only one | here because it using icon from program
displayed Name path to program Switches
0x2,"Sherpya\XPEinit\Desktop","Ad-Aware SE","%SystemDrive%\Programs\adaware\adaware.exe|+log:%ramdrv%\ad-awarese"

Q.06: How to add things to RunonceEX and what are all the #'s about in XPE
A: A short explanation of RunonceEX

first i'll tell you what the #'s are for
they're used as a way to run them in a certain order and to keep them organized
evrything under 500 key get's run in order and then key 600 etc...

0x1,"Microsoft\Windows\CurrentVersion\RunOnceEx\500","100","shell32.dll|DllInstall|I"
0x1,"Microsoft\Windows\CurrentVersion\RunOnceEx\500","103","browseui.dll|DllInstall|I"

0x1,"Microsoft\Windows\CurrentVersion\RunOnceEx\600","100","||xpeinit.exe"

how they look in registry

[HKEY_LOCAL_MACHINE\Microsoft\Windows\CurrentVersion\RunOnceEx\500]
"100"="shell32.dll|DllInstall|I"
"103"="browseui.dll|DllInstall|I"

[HKEY_LOCAL_MACHINE\Microsoft\Windows\CurrentVersion\RunOnceEx\600]
"100"="||xpeinit.exe"

now i'll tell you what xpeinit.exe is for and how to use it

The syntax is: xpeinit [-s][-f] [-m message] cmdline
-s means don't complain if the launched command fails
-f means force load also if control key is pressed
-m changes the title on xpelogon window while executing the command

you only need to use it if you want it to display in the xpelogon window

0x1,"Microsoft\Windows\CurrentVersion\RunOnceEx\900","101","||xpeinit.exe -m ""Installing Tcp/IP"" bartpe.exe -c p -i ms_tcpip"

otherwise you can just do it like this
0x1,"Microsoft\Windows\CurrentVersion\RunOnceEx\900","113","shnicon.cmd"
btw RunOnceEx gets run before the shell starts unlike RunOnce which runs after the shell
also you should always make sure the #'s you use are not used already because only one will get added

Q.07: How to remove reg entries from XPE without editing the default files
A: here's a few examples

if you wanted to remove this entry from xpe-defaults.inf
0x1,"Microsoft\Windows\CurrentVersion\RunOnceEx\900","101","||xpeinit.exe -m ""Installing Tcp/IP"" bartpe.exe -c p -i ms_tcpip"

you would add this to z_xpe-custom.inf to remove it instead of editing the default file
[Software.DelReg]"Microsoft\Windows\CurrentVersion\RunOnceEx\900","101"

and to remove Command Prompt from desktop
0x2,"Sherpya\XPEinit\Desktop","@shell32.dll,-22022","%comspec%"

you would add this to z_xpe-custom.inf
[Software.DelReg]
"Sherpya\XPEinit\Desktop","@shell32.dll,-22022"

just something i wrote almost a year ago about making plugins
My Thoughts On Plugins

This post has been edited by CWorks: Jun 11 2006, 04:09 AM

[d4vr0s]

Thanks for your additions CWorks
Thanks to whoever pinned it.

[d4vr0s]

Some other information which is nice to have on hand.
Folder list for plugins:

CODE

30000 = Drive Root
1 = i386 aka %SystemRoot%
2 = system32
3 = system32\config
4 = system32\drivers
5 = system
7 = system32\ras
9 = system32\spool
10 = system32\spool\drivers
11 = system32\spool\drivers\w32x86\3
12 = system32\spool\prtprocs
13 = system32\spool\prtprocs\w32x86
14 = system32\wins
15 = system32\dhcp
16 = repair
17 = system32\drivers\etc
18 = system32\spool\drivers\w32x86
19 = system32\drivers\disdn
20 = inf
21 = Help
22 = Fonts
23 = Config
24 = msagent\intl
25 = Cursors
26 = Media
27 = java
28 = java\classes
29 = java\trustlib
30 = system32\ShellExt
31 = Web
32 = system32\Setup
33 = Web\printers
34 = system32\spool\drivers\color
35 = system32\wbem
36 = system32\wbem\Repository
37 = addins
38 = "Connection Wizard"
39 = "Driver Cache\i386"
40 = security
41 = security\templates
42 = system32\npp
43 = system32\ias
44 = system32\dllcache
45 = Temp
46 = Web\printers\images
47 = system32\export
48 = system32\wbem\mof\good
49 = system32\wbem\mof\bad
50 = twain_32
51 = msapps\msinfo
52 = msagent
53 = msagent\chars
54 = security\logs
55 = system32\icsxml
57 = system32\mui
58 = %MUI_PRIMARY_LANG_ID_DIR%
59 = system32\mui\dispspec
60 = AppPatch
61 = Debug
62 = Debug\UserMode
63 = system32\oobe
67 = Help\Tours
68 = Resources\Themes\Luna
69 = Resources\Themes\Luna\Shell\NormalColor
70 = system32\oobe\html\ispsgnup
71 = system32\oobe\html\mouse
72 = system32\oobe\html\oemcust
73 = system32\oobe\html\oemhw
74 = system32\oobe\html\oemreg
75 = system32\oobe\images
76 = system32\oobe\setup
77 = system32\oobe\sample
78 = Resources\Themes\Luna\Shell\Metallic
79 = Resources\Themes\Luna\Shell\Homestead
91 = Help\Tours\mmTour
92 = Help\Tours\htmlTour
100 = system32\1025
101 = system32\1028
102 = system32\1031
103 = system32\1033
104 = system32\1037
105 = system32\1041
106 = system32\1042
107 = system32\1054
108 = system32\2052
109 = system32\3076
110 = system32\wbem\xml
111 = system32\usmt
112 = system32\inetsrv
123 = mui
124 = WinSxS
125 = WinSxS\Manifests
126 = WinSxS\InstallTemp
127 = ime
129 = Resources\Themes
130 = ime
132 = ime\imejp
133 = System32\IME\PINTLGNT
134 = System32\IME\CINTLGNT
135 = System32\IME\TINTLGNT
136 = IME\CHTIME\Applets
137 = ime\imejp98
138 = ime\imejp\applets
180 = system32\3com_dmi

Special folders bug? I believe cdob found this little trick

CODE

%0% = \ (root of pe drive?)
%1% = plugin dir (full path)
%10% = \WINDOWS (%windir%)
%11% = \WINDOWS\system32
%12% = \WINDOWS\system32\drivers
%17% = \WINDOWS\inf
%18% = \WINDOWS\help
%20% = \WINDOWS\fonts
%21% = \WINDOWS\system32\viewers
%23% = \WINDOWS\system32\spool\drivers\color\
%24% = %SystemDrive% ?
%50% = \WINDOWS\SYSTEM
%51% = \WINDOWS\system32\spool\
%52% = \WINDOWS\System32\spool\DRIVERS\W32X86
%53% = %UserProfile%
%55% = \WINDOWS\System32\spool\PRTPROCS\W32X86
%16384% %userprofile%\Desktop
%16386% %userprofile%\Start Menu\Programs
%16389% %userprofile%\My Documents
%16390% %userprofile%\Favorites
%16391% %userprofile%\Start Menu\Programs\Startup
%16392% %userprofile%\Recent
%16393% %userprofile%\SendTo
%16395% %userprofile%\Start Menu
%16397% %userprofile%\My Documents\My Music
%16398% %userprofile%\My Documents\My Videos
%16400% %userprofile%\Desktop
%16403% %userprofile%\NetHood
%16404% \WINDOWS\Fonts
%16405% %userprofile%\Templates
%16406% %allusersprofile%\Start Menu
%16407% %allusersprofile%\Start Menu\Programs
%16408% %allusersprofile%\Start Menu\Programs\Startup
%16409% %allusersprofile%\Desktop
%16410% %userprofile%\Application Data
%16411% %userprofile%\PrintHood
%16412% %userprofile%\Local Settings\Application Data
%16415% %allusersprofile%\Favorites
%16416% %userprofile%\Local Settings\Temporary Internet Files
%16417% %userprofile%\Cookies
%16418% %userprofile%\Local Settings\History
%16419% %allusersprofile%\Application Data
%16420% System Root (C:\WINDOWS)
%16421% \WINDOWS\System32
%16422% Program Files
%16423% %userprofile%\My Documents\My Pictures
%16424% %userprofile%
%16425% \WINDOWS\System32
%16427% \Program Files\Common Files
%16429% %allusersprofile%\Templates
%16430% %allusersprofile%\Documents
%16431% %allusersprofile%\Start Menu\Programs\Administrative Tools
%16432% %userprofile%\Start Menu\Programs\Administrative Tools
%16437% %allusersprofile%\Documents\My Music
%16438% %allusersprofile%\Documents\My Pictures
%16439% %allusersprofile%\Documents\My Videos
%16440% \WINDOWS\resources
%16441% \WINDOWS\resources\0409
%16443% %userprofile%\Local Settings\Application Data\Microsoft\CD Burning

Service/driver parameters and information

Types: 8
0x1 A kernel-mode device driver.
0x2 A file system driver.
0x4 A set of arguments for an adapter.
0x8 A file system driver service, such as a file system recognizer.
0x10 A Win32 program that runs in a process by itself. This type of Win32 service can be started by the service controller.
0x20 A Win32 program that shares a process. This type of Win32 service can be started by the service controller.
0x110 A Win32 program that runs in a process by itself (like Type16) and that can interact with users.
0x120 A Win32 program that shares a process and that can interact with users.

Start: 5
0x0 Boot (loaded by kernel loader). Components of the driver stack for the boot (startup) volume must be loaded by the kernel loader.
0x1 System (loaded by I/O subsystem). Specifies that the driver is loaded at kernel initialization.
0x2 Automatic (loaded by Service Control Manager). Specifies that the service is loaded or started automatically.
0x3 Manual. Specifies that the service does not start until the user starts it manually, such as by using Device Manager.
0x4 Disabled. Specifies that the service should not be started.

Error Control: 4
0x0 Ignore. Startup proceeds with no warning messages.
0x1 Normal. Startup proceeds, but a warning message appears.
0x2 Severe. The system declares that the startup has failed, and it restarts by using the LastKnownGood control set. If startup is already using the LastKnownGood control set, then it continues.
0x3 Critical. The system declares that the startup has failed, and it restarts by using the LastKnownGood control set. If startup is already using the LastKnownGood control set, then the system stops the startup procedures and runs a debugging program.

Tag:
Indicates the order that services need to start within a given group.

Enum:
The Enum subkey in each Services subkey stores information about the hardware associated with that service. The values in the Enum subkey associate the service with the instance of the device it controls.
The Enum subkey appears in subkeys that are in the Services subkey and that store values for drivers and other services controlling or interacting with devices.

Additional Info
Adapter A service for a hardware device that requires its own driver.
FileSystemDriver A file system driver, which is also a Kernel device driver.
InteractiveProcess A service that can communicate with the desktop.
KernelDriver A Kernel device driver such as a hard disk or other low-level hardware device driver.
RecognizerDriver A file system driver used during startup to determine the file systems present on the system.
Win32OwnProcess A Win32 program that can be started by the Service Controller and that obeys the service control protocol. This type of Win32 service runs in a process by itself.
Win32ShareProcess A Win32 service that can share a process with other Win32 services.

ImagePath variants

System32\drivers\filename.ext
%SystemRoot%\System32\drivers\filename.ext
X:\I386\System32\drivers\filename.exe
\SystemRoot\System32\drivers\filename.ext
\??\X:\I386\System32\drivers\filename.ext

Special Variables

%1 The normal parameter.
%~f1 expands %1 to a fully qualified path name. If you only passed a file name from the current directory it would expand to the drive/directory as well
%~d1 extracts the drive letter from %1.
%~p1 extracts the path from %1
%~dp1 extracts (or expands then extracts) the drive letter and path from %1
%~sp1 extracts (or expands then extracts) the short path from %1
%~n1 extracts the file name from %1 without the extension
%~sn1 extracts (or expands then extracts) the short file name, without extension, from %1
%~x1 extracts the file extension from %1
%~nx1 extracts (or expands then extracts) the file name and extension from %1
%~s1 changes the meaning of n and x options to reference the short name.
%~sn1 for the short file name
%~sx1 extracts (or expands then extracts) the short extension from %1

The %0 Replaceable Parameter is for determining filename and where the batch file is running from. This means that a script can use the %0 of the batch file to determine the directory the script is running from, "%0\..\" is the result (see Q121387). The %0 is the complete path, filename, and extension of the file.

Lines that NEVER should be in a plugin:

CODE

[SetupReg.AddReg]
0x0,"CurrentControlSet"
0x1,"CurrentControlSet"
0x3,"CurrentControlSet"
0x4,"CurrentControlSet"
0x7,"CurrentControlSet"

These will result in a STOP 0x00000067: CONFIG_INITIALIZATION_FAILED

This post has been edited by d4vr0s: Mar 5 2006, 10:13 AM

[CWorks]

if you do have CurrentControlSet in your .inf file you need to change it to ControlSet001
most reg to inf converters do this automatically

[d4vr0s]

Here is a new fixdell plugin

Please post results in this thread -> http://www.911cd.net/forums//index.php?showtopic=16042

fixdell.inf

CODE

; Original file from Bart
; Updated 2008-09-11

[Version]
Signature= "$Windows NT$"

[PEBuilder]
Name="Fix Dell Windows XP OEM boot problems"
Enable=1

[SourceDisksFiles]
iastor.sys=4,,4
a320raid.sys=4,,4
aarich.sys=4,,4
aac.sys=4,,4
cercsr6.sys=4,,4
afamgt.sys=4,,4
NvAtaBus.sys=4,,4
nvraid.sys=4,,4
symmpi.sys=4,,4
megasas.sys=4,,4

[paraglider]

If you are having problems burning iso files to a dvd with either cdrecord or starburn then try out imgburn - all it does is burn isos and it does that very well. It is also scriptable from the command line. Its available here:

http://www.imgburn.com/


An example script to burn on drive X: ( assumes the batch file is in the same directory as the pebuilder.iso file):

"c:\Program Files\ImgBurn\ImgBurn.exe" /SRC "%~dp0pebuilder.iso" /DEST X: /START /CLOSESUCCESS /VERIFY YES /ERASE /SPEED MAX /WAITFORMEDIA


Replace the X: with your burner drive letter.

[B34r]

Please pardon my ignorance. Does the fixdell.inf file go in the \I386 directory in the source folder?

[paraglider]

No its a plugin inf file. So you create a directory in the plugin directory of pebuilder and place the inf file in the directory you just created.

[Andy2Long]

BartPE + XPE Disk Management forced reboot issue:

I finally got this one figured out, seems that Microsoft had documented this some time back:

http://support.microsoft.com/kb/884564/en-us

This issue starts with the pebuilder.inf line 574:

0x1, "ControlSet001\Control\ComputerName\ComputerName", "ComputerName", "MININT-JVC"

Notice the MININT-JVC ComputerName.

Next the issue is compounded with the msclient.cmd line 6:

bartpe -pnp -cn bartpe-* -wg workgroup

Notice the bartpe-* dynamic ComputerName.

Next the issue is sealed in z_xpe-custom.inf lines 118 and 119:

0x1,"ControlSet001\Control\ComputerName\ComputerName","ComputerName","WinXPE"
0x1,"ControlSet001\Control\Session Manager\Environment","ComputerName","WinXPE"

As you can see we have effectively named the Computer for a 3rd time, since booting BartPE + XPE. As you may see this is effectively a "catch 22" situtation, as the reboot will just start this issue all over again.

My fix is to change all 3 to a single Computer Name, and this problem using Disk Management is eliminated.

Now if I just get could get all 3 to support a dynamic computer name...

HTH,

Andy

[paraglider]

You don't need to change the one in pebuilder.inf. The one in z_xpe_custom.inf replaces it as its the same registry setting. You may also want to add:

0x1,"ControlSet001\Services\Eventlog","ComputerName","..."

to the xpe custom inf so that the event log is using the same name as everywhere else ( replace ... with whatever static computer name you use ).

[Greyhair]

Hi Paraglider,

This was your reply to a question about the FixDell plugin. Do I call the new folder "FixDell"? Does the exact name matter?

Thanks in advance for helping a newcomer.

Dan

No its a plugin inf file. So you create a directory in the plugin directory of pebuilder and place the inf file in the directory you just created.

[CWorks]

you can name the folder whatever you want or even add it to an existing folder
you can even just put it in the plugin folder since it is just an .inf file

pebuilder will read any .inf file in the plugin folder

[HenWin]

How do I incorporate the "fixdell.inf" into a BartPE so Bart will run on a Dell machine?

[Ed_P]

Create a folder under PEBuilder's plugins folder and call it DellFix. In this folder create a text file named DellFix.inf. Cut & paste the above code into the DellFix.inf.

BTW My BartPE CD & USB run on Dell machines and I don't have this plugin.

[d4vr0s]

That plugin is for people who use Dell disks as their source and experience errors during building.

[d4vr0s]

More troubleshooting tools.
Sometimes it's easier to test the ISO pebuilder created with a virtual machine.
To that end, there are several options.
VirtualBox
Microsoft Virtual PC
Qemu
There is a GUI based front end that makes it easier to use this
Qemu Manager

and finally
VMware

In addition, you may want to run a memory tester on your RAM.
Bad RAM can cause a lot of weird errors.
Memtest86+
or
Memtest-86

This post has been edited by d4vr0s: Mar 9 2007, 04:47 PM

[traveling]

I learn a bit knowledge in this thread.

[twljazz]

I have a Maxtor external drive on my system - why can't I see it when I run my BartPE disk?

[Ed_P]

Q: I have a Maxtor external drive on my system - why can't I see it when I run my BartPE disk?

A: USB drives need to be plugged in before booting BartPE.