Hi all, when creating a bootable CD or XP + SP2 slipstreamed CD, how should "Load Segment" be set for ECDC 6 CD/DVD, and what EXACTLY does that mean?
I've created about 10 of the XP + SP2 slipstreamed CD's. Everything went off without a hitch for ALL of them, yet some of them won't boot I later found out when I tested them! I get the "Couldn't find NTLDR" error message. What I can't figure out, is WHY are only some of the CD's doing this???
They were all created the EXACT same way! I even used two different XP Pro PC's and that changed nothing; I'll get the bad CD's on either PC. Media does not matter, nor does the record speed matter. Both CDRW drives are burn proof (Teac 540E 40x24x48 w/8mb buffer & LiteOn 52x32x52 w/2mb buffer). The boot image file used, and method, was the bootfiles.zip mentioned at http://www.informationweek.com...tml?articleID=47212312 (No surprise the download link was bad and I had to search to be able to find it elsewhere).
I came across the page http://bootcd.narod.ru/ntbootbin_e.htm that explained the error, (note the screwup under "If your program does not have this option, you have to use the following bootsectors: NT5BOOTM.BIN and NT5BOOTM.BIN. In this version, the file version option is switched off,that means..." listing the same file TWICE, so that's confusing). So, I tried a different method using the boot image files from there http://bootcd.narod.ru/neecdc_e.htm . It doesn't say whether to use NT5BOOT.bin or NT5BOOTM.bin. I forget which I tried, but the same $#!@@% thing happens on about half the CD's!!! :roll: :disgust: :|
I did some searches on this, and no one seems to agree upon what to put for "Load Segment". Some places state 0x000, some state 0x7c0, and some state 0x00. So, I'm wondering if that has anything to do with the problem. I've tried two of them, but can't recall which now and I got the NTLDR error either way. Should I be using yet another type of "bootable CD" image file to get rid of this error?
I have enough slipstreamed CD's now, but now it's become an issue of just trying to figure out what's causing this error and how I can avoid in the future. (No, Nero is not an option, lacks too many features & complicated drag 'n drop method. So please, no ECDC bashing).
I've created about 10 of the XP + SP2 slipstreamed CD's. Everything went off without a hitch for ALL of them, yet some of them won't boot I later found out when I tested them! I get the "Couldn't find NTLDR" error message. What I can't figure out, is WHY are only some of the CD's doing this???
I came across the page http://bootcd.narod.ru/ntbootbin_e.htm that explained the error, (note the screwup under "If your program does not have this option, you have to use the following bootsectors: NT5BOOTM.BIN and NT5BOOTM.BIN. In this version, the file version option is switched off,that means..." listing the same file TWICE, so that's confusing). So, I tried a different method using the boot image files from there http://bootcd.narod.ru/neecdc_e.htm . It doesn't say whether to use NT5BOOT.bin or NT5BOOTM.bin. I forget which I tried, but the same $#!@@% thing happens on about half the CD's!!! :roll: :disgust: :|
I did some searches on this, and no one seems to agree upon what to put for "Load Segment". Some places state 0x000, some state 0x7c0, and some state 0x00. So, I'm wondering if that has anything to do with the problem. I've tried two of them, but can't recall which now and I got the NTLDR error either way. Should I be using yet another type of "bootable CD" image file to get rid of this error?
I have enough slipstreamed CD's now, but now it's become an issue of just trying to figure out what's causing this error and how I can avoid in the future. (No, Nero is not an option, lacks too many features & complicated drag 'n drop method. So please, no ECDC bashing).
