Black screen of death after BartPE loading in white at bottom of screen, perhaps because original CD is Dell OEM. Inserted FixDell.inf (shown below) as additional file with minor improvement: get Windows banner to flash before BSOD.

Then tried inserting Setupreg.hiv, subinacl.exe and Dellfix.cmd (shown below) in same directory and executing Dellfix.cmd. No joy because setupreg.hiv not altered and got error message (shown below). Tried copying entire I386 subdir (from original CD) to separate location, copying in subinacl.exe and Dellfix.cmd, and re-executing Dellfix.cmd. No joy. Then tried using setupreg.hiv built by BartPe (SP1 slipstreamed). Again no joy: setupreg.hiv unchanged by Dellfix.cmd and same error message re "subinacl can't find" message.

Request help. Is this a setupreg.hiv problem? If so, is there a setupreg.hiv that I can download? If not, what am I doing wrong? If not a setupreg.hiv problem, how do I resolve the BSOD?

Hi zugzwang

Is your Dell XP cd a recovery CD ?
what color is it and what service pack level ?

Dell XP Recovery CD with SP1 or SP1A probably does not need fix but SP2 versions probably do need fix.

XP CD with no service pack would not be accepted by Bart PEbuilder

If setupreg.hiv not modified by dell fix it probably does not need to be fixed

Have you tried your disk on other PC's ?
Have you added plugins and drivers ? if so try with no changes to original pebuilder source
(except changes to plugins on or off required by service pack level)

regards
Mike Barnes

BSOD-s can be caused by many things.
Saying you are experiencing a BSOD is very vague, we need the error message itself to help troubleshoot it.


This appears to be saying that the iastor subkey isn't there, which may have nothing to do with your problem anyway.

d4vr0s : ...we need the error message itself to help troubleshoot it

Good point. BartPe loading msg appears in white at bottom of screen. Then Windows banner shows briefly. Then black (not blue) screen shows and stays. This forces me to reboot. Checked C:\Program Files\pebuilder3110a\pebuilder.log and can find no error message. Given my symptom, how do I determine error message?


mbarnes:

CD is mostly gray, with white portion at top. Reads Reinstallation CD...XP Professional. Contains Setupreg.hiv (256k : 6-25-2002). Verified that CD has no SP included at all, because (as you indicated) Bart PE doesn't accept it (as is). First, I downloaded xpsp1a_en_x86.exe (128,097 kb : 1-25-2003) and then slipstreamed it into Windows XP via the xpsp1a_en_x86.exe -s:d:\winxpsp <et al> command. For my purposes, regard SP2 as unnecessary complication that doesn't slipstream as easily as SP1 does.

Mistake in initial post: was getting Windows banner to flash before BSOD even without Fixdell.inf, so Fixdell.inf had no effect. Experimented by attempting BartPE CD boot-up on a Dell Latitude D810 laptop. No joy, symptom identical as with home PC (aopen ax4c II mobo, internal sata C and D drives). This suggests that it is a software rather than mobo problem.

Then, per your suggestion, experimented by removing all unnecessary plugins, making no changes to setupreg.hiv, and tried this both with and without the Fixdell.inf add-in. Only plugins enabled for experiment were Serial Mouse, Startup Group, and NU2Menu (NU2Menu apparently required to avoid build errors). No joy, still getting BSOD. Why? What is there left for me to try? Don't wish to buy 2nd XP pro CD, just to resolve this.

My apologies, when you said BSOD I was understanding you meant Blue Screen Of Death, which is the most common use.
It sounds like when it's switching from text mode to gui mode it hangs.
I would encourage you to slipstream to sp2, just to test with newer file versions.
It's very easy to do that with Autostreamer.
http://www.neowin.net/forum/index.php?&showtopic=223562
If it were a problem with the iastor, you would probably see a blue screen with the message 'inaccessible boot device' as it's message.
The CD media could also cause problems like that if it's having trouble reading it.

Autostreamer 1.0.33 refuses to recognize my Dell OEM cd as a valid build, so I can't use it to simplify slipstreaming in SP2. I'll look for an alternative. Assuming that problem is hang from text to gui mode, is it plausible that SP1 is insufficient and that SP2 will work? Is there a video plugin that I can try? My video card is an ATI Radeon 9200 SE 128MB AGP (PCI slot) 8X Graphics Card that has no other problems.

It's hard to say what's causing it to hang, but unlikely it's the video driver.
It should fall back to the default vga driver.
Dell seems to like tinkering with their oem cds, so the fact that sp2 isn't slipstreaming easily isn't a good sign.
I'd also be concerned that your sp1 slipstream didn't integrate correctly, or if there is something either missing from or added to the txtsetup.sif

Tried to slipstream SP2 without Autostream. Not suprisingly, given that it is a Dell OEM, failed with msg = "This service pack cannot be integrated into a destination that also has integrated Software Updates." Apparently resolution via SP2 doubtful. It seemed to me that SP1 slipstreaming went ok. Resulting txtsetup.sif is 454,830 bytes (too large to post). Is there a specific section of this file that I could post to the forum for analysis? Is there any other way to check whether SP1 slipstreamed ok. Assuming so, is there anything else that I can try?

Is there a special way of slipstreaming SP2 into my Dell OEM cd, given problems above? Has anybody else experienced my symptoms? If so, how did you resolve it?

How much RAM does the machine have?

Have you tried to slipstream SP2 to the CD you created with SP1?

1 gb ram. Yes, tried to slipstream in SP2, both with and without auto-installer. SP1 slipstreams ok, but can't get SP2 to slipstream. See my previous reply. Am I misunderstanding your question? When I used auto-installer on original CD, it wouldn't recognize the (Dell OEM) cd as valid build. Ditto when I pointed autoinstaller to my WinXP_with_SP1_slipstreamed on my hard disk.

Maybe give nlite a try?
http://www.nliteos.com

Great tip, possible light at the end of the tunnel. nlite actually successfully slipstreamed SP2 by detecting and offering to "remove" "hotfixes" from original CD (while integrating in SP2). Experimenting, I then re-ran BartPE off of the xp+sp2, using only the three plug-ins of Serial Mouse, Startup Group, and NU2Menu.

Result was error message = "The file usbehci.sys is corrupted". I did a Dos file compare (fc command) on the BartPE generated file (BartPE step 2) and the file on the cd created from the iso. The files match.

How do I remedy this? Was it caused by my omitting all the other plug-ins? Do I need to reapply the Dellfix.inf or Setupreg.hiv--subinacl.exe--Dellfix.cmd remedies from earlier post in this thread? Am I deceiving myself that I've made progress?

Is it the same error each time you boot?
Does the file match what you have slipstreamed? (unpacked of course)
The dellfix.cmd isn't going to fix that either.
Pebuilder would give you errors when trying to unload the hives if you had that problem.

Rebooted twice on aopen ax4c II mobo, once on Dell Latitude D810 laptop. Same result all three times. Yes, expanding usbehci.sy_ from SP2 integration creates a file that matches the file (byte by byte) on the resultant BartPE cd that is generating the "...file...corrupted" message.

Lets start at the top...

1) The error you first posted sounds like the ACPI problem where pressing F7 while prompted for F6 allows booting.

2) Creating a valid SOURCE from a recovery CD... http://winfuture.de/xpisobuilder3_en
XP ISO Builder has helped many of our users and is avaible in English and German.

3) SetupReg.hiv.... Does it have the IASTOR Locked registry key?
Are you familiar with regedit? If not, then DO NOT PLAY WITH IT.

If you can use regedit without wiping out your system, then load setupreg.hiv in a temporary registry key and go to CurrentControlSet\Services\IASTOR and click on it. If you key is locked, you will get an error saying that you don't have permission to view or edit that key.

Now, this one was interesting to me.... The other day we had another user witht he same problem using a DELL XP CD that strangely enough had no locked registry keys but still would not work. He simply grabbed a copy of setupreg.hiv from another machine and it actually worked and he had no further problems.

This is not "Cut & Dry" either.

Many things can cause this, conflicting drivers, currupted drivers, bad media, bad hardware and wrong jumper settings can be to blame.

I've had some systems where the CD drives were using the CSEL setting and did exactly what you are describing.
Bartpe can have trouble with this setting on certain computers, but not all of them so you may want to check that also. It's always best to use MASTER/SLAVE instead of CSEL (Cable Select) when settin up a computer, but most OEM systems will come set to CSEL just because its easir for them to not have to know what device is going to be added and at what time.

What media are you using? CD-RW (Regardless of how many people tell you they always work) simply do not work on all systems and should be avioded unless you are certain that your machine DOES in fact work with them.

The TXTSETUP mode at the begining of the boot sequence, does not have any error-correction while winds does.
Just because windows can read data from a cd does not meant that the cd drive is actually working the way it is suposed to. Windows continues to read the CD untill it gets the complete file and also uses the extra error correction blocks that are encoded into the iso at the time of pressing. CD-R(W) does not normally have any extra blocks written to protect the boot files.

PE (Any PE build wethier it's MS PE or Bartpe) only reads a file ONE TIME. If it does not read the file sucessfully then the boot will fail.

Are you using a postprocessing script? Mkisofs.exe supports sorting files to keep the bootloader under 2gig on dvd.
CD does not have this problem, but it's always best to sort the CD anyways. If your using a DVD and the boot files are above 2gb on the disk, then there is no way for any PE build to read them, thus the boot will fail.

Back to bad hardware.... When you pull the cover off your system, please check for bad (leaky) capacitors on the mainboard as this is a very common problem and can be hard to find some times.

BAD MEMORY - Will also cause the "File not found" or "Corrupted" message you are getting so run memtest86 on your system to see if you have a faulty stick of ram in your machine.

I HATE TYPING.

BYE

Thank you Dell (again)
Given the hives and enough free time I think this could be figured out tho.

LOL

Thanks to hilander999 and d4vr0s for recent replies.

Hilander:

1) ...sounds like the ACPI problem where pressing F7 while prompted for F6 allows booting.

Interesting. I don't need SP2, I only used it because slipstreaming with SP1 (instead) yielded a BartPE generated CD that hung (after BartPE loading with msg in white at bottom of screen, screen goes dark). Assume that it is an "ACPI" problem (whatever that means). Is there a remedy?

2) Creating ...winfuture.de/xpisobuilder3_en XP ISO Builder has ...

Ineffective here. My source is OEM-Install, not Recovery cd. I tried anyway, and SP2 wouldn't slipstream "naturally" (from the Winfuture app). The only way that I can slipstream SP2 into my OEM source is to first delete svcpack.inf, winnt.sif, and the OEM and svcpack folders. Then Bart accepts it, but the resulting CD yields the "...usbehci.sys is corrupted" message.

3) SetupReg.hiv.... Does it have the IASTOR Locked registry key? Are you familiar with regedit? If not, then DO NOT PLAY WITH IT.

Already looked at, no joy. See 2nd paragraph of my initial post in this thread. Given that, might it still be a ...hiv problem? How might I more deeply explore the potential hiv problem?

... not "Cut & Dry" either ...
... conflicting drivers ...
... some systems where the CD drives were using the CSEL setting ...
... check for bad (leaky) capacitors ...
... BAD MEMORY ...

See my reply to MBarnes earlier in this thread. Same symptoms when using only minimal plug-ins.

Same error message when trying on both {aopen ax4c II mobo, internal sata C and D drives} and a {Dell Latitude D810 laptop}. Two different machines, same problem, and _coincidentally_ source is Dell OEM re-install cd. This very probably is not a mobo or memory issue. Anyway, memtest86 verified my memory ok.

... What media are you using ...

I built my PC and I'm using a Plexwriter Premium CD-drive which I'm sure reads CD-RW. Also, I byte for byte compared the source/target usbehci.sys files. I've never before had a problem with my CD-RW cd's. If the media is the problem, what diagnostic could I run to investigate/verify.

If I need to, I can burn the image to a CD-R rather than CD-RW. However, given that the source is Dell OEM, I suspect this will be clutching at straws.

... Are you using a postprocessing script? Mkisofs.exe supports ...

BartPE process seems to peripherally involve Mkisofs (somehow). Beyond that, I've seen no documentation/instructions that related Mkisofs to BartPE. Again, because Dell OEM involved, burning time in this direction is a last resort.

-----------

I was surprised by your response. Given recent threads from a variety of forums, problem is almost certainly that I'm using Dell OEM as source. Short of buying a 2nd (non OEM) source CD, how do I attack? If I post specific file (name, size, date) lists from specific directories on my source CD, will anyone be able to pinpoint which files/directories to add/change/delete, and _where_ to get the replacements? Since my source is valid I can get _some_ substitutes from Microsoft (e.g. SP2.cab).

Obviously, converting my source is the "industrial strength" solution. Very surprisingly, I have not seen one forum instance of Dell OEM source with my _specific_ BartPE symptoms where the _original_ poster indicated a _definite_ BartPE cure (as opposed to merely being able to slipstream), with detailed remedy instructions. This does not bode well.

Has _any_ Dell OEM (source CD) owner resolved these symptoms and successfully enjoyed BartPE? If so, please respond. Assuming that the problem _is_ my OEM source, what is left for me to try?

Have found no alternative for BartPE that approaches both convenience of use and functionality. Goal is to include DriveImage XML as Bart plug in, boot from BartPE CD, read cloned C drive data (stored as XML files on external drive), and restore image clone to (new) blank C drive. Home PC uses USB external enclosure that contains removable drive drawers, with the drive drawers housing internal hard disks (btw, see StarTech.com for this cost-effective approach). Laptop use external 250gb USB2 drive (instead of external enclosure).

I may have to buy a 2nd (non OEM) source CD. Any reason why a non OEM (full version) XP Home CD won't solve _my_ BartPE problems? Any (under $60) reliable bargains out there? Don't want to gamble $40 to a download service website without some pretty strong testimonials that _my_ problem will be fixed. Any comments?

YES, PRESS F7 like I posted. If you confirm that that was the problem then you can use my plugin to resolve it.

http://www.911cd.net/forums//index.php?s=&...ost&p=43620

We had one user that simply replaced that file (setupreg.hiv) with the same file from a normal XP SP2 Setup CD. I would imagine that if you looked hard enough you could find that single file somewhere??

This only supports my concern about a hartdware issue, and since your getting the error on more then 1 system I would look at the media and try a CD-R instead of RW. (I don't LIke CD-RW, so we wont argue on that subject again.)

Have you by any chance tried to boot the ISO file in a Virtual Machine to rule out a hardware problem?
This should be something you take a serious look at as we all use different VM's for testing unless were working on driver settings.


Is this optical drive set for MASTER/SLAVE or CSEL (cable select)?

Have you ever BOOTED from that drive with any PE BUILD Before? Remeber there is no error correction in PE.

Search the forum for "Postprocessing" or "Autobuild", you really should be using a building script.

I've been doing this for a long time and have seen a lot of really strange symtoms over the years and was simply trying to help you figure out where the real problem was.

YES, There is a good chance that the DELL source you are using is the problem, but MANY PEOPLE use these OEM setups without any major side effects, but all are different so there is no real way of knowing if your problem can be easily solved.

One option that has been poted about MANY, MANY TIMES, is that MS offers a free trial version of Windows 2003 that DOES WORK WITH PEBUILDER. I have tested it myself and found no side effects from it. Any one that searches for it should be able to find it and not have to buy a new source CD, but then again you end up with a questionable legal issue with using the resulting build and I've no intention of discussing it any further then it alread has.


Concidering what your wanting to do, and your lack uf setting up a building script, you may want to test out UBCD4WIN and see if you have any better results.

We have several beta-testers that use XP HOME as the source and there has been no real problems to date other then a few files that are not there but not required unless you using certain advanced plugin.

Did I mention that I HATE TYPING?

FYI I use XP Home as my source for BartPE. And I use DriveImage XML on it to do backups and restores. The only time I ever ran into an XP Home shortcoming was using the PEinst.cmd.

Check media once more: make a C1 errror scan of written media.

Boot ISO image at virtual machine: Qemu or VMware Player.

MS offers a 160 days trial Windows 2003 for download.

BartPE boot fine from most OEM source file.
But there is one exception: Dell

Thanks to hilander999, ed p, and cdob for the recent replies. I already own Win 2000 Pro (luckily not an OEM). I just booted the bart generated iso from a VMWare host. With the problem persisting (msg: usbehci.sys is corrupted), the CD-Rom and CD media concerns are eliminated. Virtual machining is surprisingly easy and extremely efficient. I'll do more experimentation in a day or two and post again. Probably better to stay on this thread than start a new one, for continuity.

What is the file version of your usbehci.sys?
Does this error still happen in the text mode or is it after the GUI starts?

If it's in the text mode I have a tentative suggestion:
After pebuilder finishes and before you write the cd, go into the \i386 folder it created and edit txtsetup.sif using notepad
Look in there for the lines containing usbehci and put a ; in front of them.
It might get you at least booting into the GUI mode, not sure if it will affect your usb input devices.

Alternatively, you may want to try copying the usbehci.sys from the windows\system32\drivers directory and see if that one works.