NTLDR missing

[ZaForD]

Hi Guys,

This is really starting to drive me nutz now.

I have three UA disks, all OEM Pro and all work prefectly.

I thought i'd get abit flash and have a go at making a Multi-Boot CD of them.

So I followed the Multi-Boot DVD guide and ended up with three working UA disk on one CD. I then started working out where to place my $OEM$ folders, when I first got this error on booting.

CDBOOT: Couldn't find NTLDR

It seemed strange as the files i'd just changed were in the $OEM$ folders, but didn't worry about it and created another ISO. Which also failed, as did the next 5 or 6.

Anyway to cut a long story short:

Over the last two days, i've since scraped the whole thing twice, then I started again on a newly formated PC, and started again on a differnet PC. Using the same Orignal OEM CD for formating, installing and the Multi-Boot CD, again following the guide to the letter. After these failed with the same error, I tried using my Retail CD and downloading all new files from the links in the guide, but I still keep getting this same error.

I've seached through this forum, but most of the threads are about Win2K3 having these problems not XP Pro SP2. Has anyone got any answers ?

As I said earlier its driving me nutz....

[bober]

post your boot menu.

[LiquidSage]

Do you get ntldr errors upon first booting the cd itself or right before install starts from the hd?

What are you using as the boot menu? CDshell, easyboot... etc

Are you trying to tidy up you folder structure by hiding files?

Are you using something like RyanVM's updates or nlite?

If you delete the $OEM$ folder, does the AIO cd boot correctly again?

Are you sure winnt.sif is correct for all options?

Are you making sure to omit ISO 9660 version number when compiling?

Double check all the setupldr.bin's and try replacing ntldr and ntdetect.com with the win2003 or win2003sp1 versions (might as well do it regardless anyways).

[ZaForD]

@ bober,

By boot menu, do you mean the cdshell.ini ?

I've deleted and formated over my orginal.

So i'm using the one from the download section here.

Unedited incase it was my version that was messing up.

@ LiquidSage,

Do you get ntldr errors upon first booting the cd itself or right before install starts from the hd?

The PC boots, shows the splash screen, displays 'Press Enter to boot from DVD'

I press Enter, then at main menu press 1 for XP Pro menu, then which ever option I choose I get the NTDLR error.

What are you using as the boot menu? CDshell, easyboot... etc

I'm using CD Shell 2.1.6

Are you trying to tidy up you folder structure by hiding files?

On this attempt the only tidying i've done is to remove the 'unattended.txt' 'bootfix.bin' 'txtsetup.si_' 'setupldr.bi_' and '.bak' files, as per the guide.

Are you using something like RyanVM's updates or nlite?

My original build had RyanVM's pack included, this one has nothing.

If you delete the $OEM$ folder, does the AIO cd boot correctly again?

Can't check this as the Multi-Boot CD with the $OEM$ folders have been deleted.

Are you sure winnt.sif is correct for all options?

Again, no winnt.sif in this attempt.

Are you making sure to omit ISO 9660 version number when compiling?

I'm not sure what this means, I made a .bat file which has the ISO info copied from the guide.

Double check all the setupldr.bin's

I've double checked my old ones and created new ones.

try replacing ntldr and ntdetect.com with the win2003 or win2003sp1 versions

I'll see if I can get hold of them.

Thanks for the quick replys guys. Its the only good thing thats happened on this Multi-boot all weekend.

[bober]

here's a sample of the one i use:

print "1)  Windows A \n"
print "2)  Windows C \n"
print "3)  Windows D \n"
print "4)  Windows E \n"
MainKey:
getkey 20 boot 0x80
if $lastKey == key[1]; then chain /A.BIN
if $lastKey == key[2]; then chain /C.BIN
if $lastKey == key[3]; then chain /D.BIN
if $lastKey == key[4]; then chain /E.BIN
if $lastKey == key[r]; then reboot
goto menu
end

[ZaForD]

@ bober,

I notice your menu uses bin files not dat files.

Is that just the way they're named ? Or do they work differently ?

I'm begining to think something has changed in the setup between SP1 which the guide covers, and SP2 that i'm using. I'm about to do a little test, by attempting to make two Multi-Boot disks.

1. With an Orignal OEM WinXP Pro SP2 disk.

2. With the same disks files, but updated with RVM's pack first.

I've got a sneaking feeling the second one will work, but the first won't.

[bober]

just differnet names.

[ZaForD]

Hi Guys,

I think this problem might have something to do with the 'txtsetup.sif'

One my last build 'NTLDR' was in all my UA disk folders, but it couldn't be found on install.

In the test I just did, the base SP2 build, kept reporting files missing on install. Files that when i checked were in the i386 folders.

The second RVM build, is still installing and is at T13 now in Virtual PC, without any errors.

I compared the files in each boot folder and the two 'txtsetup.sif' files and there are very different. Apart from the extra files added by the update pack, the layout is very different.

Anyway, back to trying to work out where to put my $OEM$ folders.

Thanks for the help.

Edited July 1, 2006 by ZaForD

[nlitefanatic]

THE ANSWER IS:

DIRECT BURN. Instead of making an ISO, use the option Direct Burn, insert a blank CD and burn your nlited version of Windows. This CD will be BOOTABLE, which is the problem with your current CD, it is not bootable. I'm from Argentina, thanks for your attention.

[nlitefanatic]

Direct Burn is an option that shows when you finish using nLite, along with the other options, in the last phase. The window is called "create a bootable ISO to burn on CD/DVD or for testing". Choose the mode "Direct Burn" instead of "create image"

[kayden75]

Direct Burn is an option that shows when you finish using nLite, along with the other options, in the last phase. The window is called "create a bootable ISO to burn on CD/DVD or for testing". Choose the mode "Direct Burn" instead of "create image"

DirectBurn writes to the CD/DVD but doesn't add the info from the multiboot session - only the session of WinXP that you are modifying for an unattended install...

I am encountering the same issues with the NTLDR missing, & I'm fairly certain all the files are correct.

has a fix been found yet for this?

here's my boot menu code if anyone needs it:

cls

print "\n"

print "Press Enter to boot from DVD... \n"

getkey 5 boot 0x80

if $lastKey == key[enter]; then goto menu

# When no key found...

goto boot

# Printing the Interface

menu:

set textColor= color[white on black]

set boldColor= color[cyan on black]

cls

print c "\cXXÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ \n"

print c "\cXXDave's Multi-Boot DVD \n\n"

print c "\cXXÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ \n\n"

print "1) Windows XP Professional SP2 Corporate \n"

print "2) Dell Branded Windows XP Professional SP2 Corporate \n"

print "3) HP Branded Windows XP Professional SP2 Corporate \n"

print "\n"

print "Q) Quit to Command Prompt \n"

print "R) Reboot \n"

print "ESC) Boot 1st Harddisk \n"

print c "\n"

MainKey:

getkey 20 boot 0x80

if $lastKey == key[1]; then chain /PRO1.DAT

if $lastKey == key[2]; then chain /PRO2.DAT

if $lastKey == key[3]; then chain /PRO3.DAT

if $lastKey == key[q]; then end

if $lastKey == key[r]; then reboot

if $lastKey == key[F1]; then goto Help

if $lastKey == key[esc]; then boot 0x80

Help:

cls

print c "\n\cXXMulti-Boot DVD Help \n"

print c "\cXXÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ \n"

print "\n"

print "Hit the key of your choice in the main menu -> \n"

print "\n"

print "\n"

print "Press any key to return to main menu... \n"

getkey

goto menu

end

[kmaheshkumar]

i want to use bscriptor for that because it is also the best