QUOTE (hilander999 @ Apr 14 2006, 09:14 PM)
Try booting the ISO with an emultator..VMware, MS virtual pc, bochs,ect...
This will rule out he build as being the source of errors.
Common problems are..
-bad quality burner (wrong speed settings, some brands are picky- try lower speed burn)
-bad quality media
-bad memory installed in system (run memtest to rule out bad module)
-bad capacitors on system board (leaky, bloated - common problem)
-bad ribbon cable on attached CD drive (even if it works on windows, the cable can still be bad.)
--------PE does not have error-correction durring the txtsetup phase of booting, installed OS does.
-Master\Slave not defined - csel (cable select) can cause trouble with BartPE, use master\slave settings.
Unfortunately, I do not have an emulator to try... kinda wish I did, although I'm not sure I want to spend the time and allocate the HD space for one.
Haven't had any problems with my burner, and the burn speed is low (I think the burn was at 9x, if I recall). I have created other bootable cd's with this cd r/w from the same spindle of cd's, notably the DFsee tool (which is not a WinXP bootable cd, so I did not use BartPE).
Bad media does not seem likely, since I made about 6 attempts at burning this BartPE cd and I doubt all of them would fail with the same symptom (NTLDR not found), and I'm still working off the same spindle of cd's that I used for DFsee. Once in a while I get a bad cd, but it's always been very obvious when that happens, and the burn didn't complete on those occasions.
I will make an attempt to create another DFsee bootable cd, just as a test, since it's been a few months since I've burned a bootable cd, but other cd's I've built seem to be fine.
QUOTE (cdob @ Apr 15 2006, 10:06 AM)
If you get "CDBOOT couldn't find NTLDR" message, then file \I386\SETUPLDR.BIN was not found.
There is no file ntldr at a boot CD.
No errors at CD write dosn't indicate good writing.
There are reliable CD-RW. Of course, you have to use a reliable writer too.
I can see that NTLDR is not in the i386 directory, but SETUPLDR.BIN is there. When I boot, I get a message saying a bootable cd was found, but then the "CDBOOT couldn't find NTLDR" error message.
It appears to me that BartPE reads the cd to verify it after creating it, does it not? No errors were noted there (except on one run, and I discarded that cd), and I am booting from the same cd r/w that I used to build the cd's.
I doubt that a half-dozen attempts to write this cd would have all failed the same way, and I have previously created bootable DFsee tool cd's on the same cd r/w with the same batch of cd's (but not using BartPE, as the bootable DFsee tool is DOS-based, I think... in fact I want this WinXP cd for running a WinXP version of DFsee). As I said above, I will try to build another (dos-based) DFsee bootable cd today as a test of the cd r/w and media.
Thanks for your comments and suggestions,