CDBOOT: Couldn't find NTLDR, BartPEDVD unable to boot Options

[JohnG]

Hi All!

I created a bootable DVD using BartPE version 3.1.10a and when I boot off that DVD I get the following message:

CDBOOT: Couldn't find NTLDR

The ISO was created using BartPE and the ISO was burned on a DVD using Nero.

I do not have any problems with version 3.1.9.

Any ideas?

Thanks

[Joshua]

did you use BURN AT IMAGE ??

Joshua

[cdob]

Does a file \I386\SETUPLDR.BIN exist?
Case is importand.

Why do you use a DVD?
Do you add a lot of file?

What about a CD?

Do you build ISO image at first PEBuilder run? Do you use F5 at PEBuilder?

[ireneuszp]

You can now modify setupldr.bin of the follwing windows:

* Windows Server 2003 SP1
* Windows XP Professional x64 Edition
* Windows Server 2003 x64 Edition
* Windows PE 2005

The setupldr.bin of the above versions is the same and has a checksum check built-in so when you try to modify it you get:
"NTLDR is corrupt. The system cannot boot."

In order to crack it:

1. open it with your favorite hex editor
2. goto hex address: 0x2060
3. change "74 03" to "EB 1A"
4. save it

[Daemonforce]

You can now modify setupldr.bin of the follwing windows:

* Windows Server 2003 SP1
* Windows XP Professional x64 Edition
* Windows Server 2003 x64 Edition
* Windows PE 2005

There's definitely a pattern here...

The setupldr.bin of the above versions is the same and has a checksum check built-in so when you try to modify it you get:
"NTLDR is corrupt. The system cannot boot."

I really don't know what it is. I don't believe it's a self-check block. It seems more likely that this is an activation switch to ID a 64-Bit OS that has a 32-Bit counterpart but I don't have a decompiler to rip this apart and I don't have a 64-Bit system so I can't check this out for sure. In any case, all my thoughts about it seem to point to the later. A default setupldr.bin on a Windows Server 2003 Enterprise SP2 disc have the same 74 03 at 0x2060. I'm going to do a file check comparison against an earlier LDR. This is confusing.

Ninja Edit: It looks like the real self-check blocks start at 4FC2. This looks like a total mess. That's for sure.

This post has been edited by Daemonforce: Sep 5 2007, 05:56 PM

[hilander999]

Here is the original source for that information...
http://www.msfn.org/board/index.php?showtopic=58410

It's an interesting read from 2005, but the data is still accurate.

[JohnG]

WOW.....I am amazed by the number of responses I got......you guys are awesome......thanks a bunch....


did you use BURN AT IMAGE ?? (Joshua)

--Well, I am not sure what do u mean by BURN AT IMAGE but I am using this command to build the ISO


mkisofs.exe -iso-level 4 -volid "WinXPSP2Image" -b bootsect.bin -no-emul-boot -boot-load-size 4 -hide bootsect.bin -hide boot.catalog -o "D:\Development\pebuilder3110a\ISO\WINXPSP2.iso" "D:\Development\pebuilder3110a\DVD"



Does a file \I386\SETUPLDR.BIN exist? ----------------Yes
Case is importand.----------------------------------------it is lowercase
Why do you use a DVD?----------------------------------the image size is around 4 GB
Do you add a lot of file?----------------------------------Yes, drivers, applications, etc
What about a CD?-----------------------------------------I wish I could
Do you build ISO image at first PEBuilder run?---------No, I use the above command afterwards
Do you use F5 at PEBuilder? -----------------------------No
(cdob)


You can now modify setupldr.bin of the follwing windows:
* Windows Server 2003 SP1
* Windows XP Professional x64 Edition
* Windows Server 2003 x64 Edition
* Windows PE 2005
The setupldr.bin of the above versions is the same and has a checksum check built-in so when you try to modify it you get:
"NTLDR is corrupt. The system cannot boot."
In order to crack it:
1. open it with your favorite hex editor
2. goto hex address: 0x2060
3. change "74 03" to "EB 1A"
4. save it
(ireneuszp )

I have not tried that yet but I will

[cdob]

Does a file \I386\SETUPLDR.BIN exist? ----------------Yes
Case is importand.----------------------------------------it is lowercase

Do you build ISO image at first PEBuilder run?---------No, I use the above command afterwards

Upper case is importand.
Current PEBuilder does uppecase at first run only.
Build a ISO always.

Or add -force-uppercase, run

CODE

mkisofs.exe -force-uppercase -iso-level 4 -volid "WinXPSP2Image" -b bootsect.bin -no-emul-boot -boot-load-size 4 -hide bootsect.bin -hide boot.catalog -o "D:\Development\pebuilder3110a\ISO\WINXPSP2.iso" "D:\Development\pebuilder3110a\DVD"

Don't edit setupldr.bin currently.
That dosn't relate to error message: CDBOOT: Couldn't find NTLDR

[JohnG]

Thanks a bunch

[JohnG]

OK...I added the -force-uppercase in the command but that did not help either. All the files on the DVD are upper case.

So, any other ideads?

[cdob]

Why do you use a DVD?----------------------------------the image size is around 4 GB

Clarify around 4 GB: Which file size does image file use? Name bytes.

OK...I added the -force-uppercase in the command but that did not help either. All the files on the DVD are upper case.

So, any other ideads?

Early boot file location after 4 GB of DVD media.

Run IsoBuster. Name LBA of \I386\SETUPLDR.BIN.

Remove around 4 GB image. Create a new CD. Does BartPE boot from CD?

Which media do you use? Try high qualtiy DVD media.
Try ImgBurn to burn ISO image.

[JohnG]

ISO file size is 4,303,908 KB
Ghost files Size (total 5 files 525 MB each included in the ISO) 2,652,896,141 bytes)

SETUPLDR.BIN LBA is 2072820 (and BTW I manually copied the SETUPLDR from Windows 2003 RC2 CD because the default SETUPLDR gives me the same error)

CD is not an option even if it works

Verbatim DVD+R 8x, DVD Burners (I am using two, one that comes with Latitude D820 and the other is in GX280 and it is SONY)

I am using Nero 7.10.xx for burning the ISO

This post has been edited by Ed_P: Mar 18 2008, 03:20 PM

Reason for edit: Removed needless quote. Please use the ADD REPLY button.

[jaclaz]

It seems like SETUPLDR.BIN is just "beyond reach".

What do you mean by:

(and BTW I manually copied the SETUPLDR from Windows 2003 RC2 CD because the default SETUPLDR gives me the same error)

You mean you edited the .iso or you added it manually in the Pebuilder folder?

Check this thread:
http://www.911cd.net/forums//index.php?showtopic=16802

As far as I know the bootsector cannot go beyond 4 Gb as well.

jaclaz

[JohnG]

I manually added SETUPLDR.bin file in the pebuilder

So does it mean that the toatl size of my ISO has to be <= 4GB?

[jaclaz]

So does it mean that the toatl size of my ISO has to be <= 4GB?

No, it means that SETUPLDR.BIN and a few other system files must be below the 4Gb limit.

Can you post how you built the .iso and a DIR /S D:\>C:\cdlist.txt of the DVD (supposing it has letter D:\, change as needed).

jaclaz

[cdob]

SETUPLDR.BIN LBA is 2072820

That's within first 4 GB of media.

Setupldr.bin acess media up to 4 GB.
However this file is not read at all. Bootsect.bin gives error message: CDBOOT: Couldn't find NTLDR
There maybe a addional BIOS limitation at 2 GB.

So does it mean that the toatl size of my ISO has to be <= 4GB?

No, ISO size is not limited.
If need be, may add big TB files.
Sort early boot files in front of media. Satisfy BIOS and setupldr.bin.

Use a folder name sorted after \I386\ :
add Ghost files at folder \zzz_images\ or \Programs\Ghost\

[JohnG]

Can you post how you built the .iso and a DIR /S D:\>C:\cdlist.txt of the DVD (supposing it has letter D:\, change as needed).
jaclaz

mkisofs.exe -force-uppercase -iso-level 4 -volid "WinXPSP2Image" -b bootsect.bin -no-emul-boot -boot-load-size 4 -hide bootsect.bin -hide boot.catalog -o "D:\Development\pebuilder3110a\ISO\WINXPSP2.iso" "D:\Development\pebuilder3110a\DVD"

File "dvdlist.txt" is over 8000 lines and I do not see the option to attach the file

thanks jaclaz

Sort early boot files in front of media. Satisfy BIOS and setupldr.bin.
Use a folder name sorted after \I386\ :
add Ghost files at folder \zzz_images\ or \Programs\Ghost\
cdbob

Not sure how to "Sort early boot files in front of media. Satisfy BIOS and setupldr.bin"
The gho files are in D:\Ghost folder if that makes any difference

thanks cdbob

[cdob]

The gho files are in D:\Ghost folder if that makes any difference

\Ghost is sorted before \I386. Do NOT use \Ghost.

Add Ghost files at folder \zzz_images\ or \Programs\Ghost\

[Ed_P]

File "dvdlist.txt" is over 8000 lines and I do not see the option to attach the file

Not everyone reading this thread wants to see your 8000 line file. Upload it to a file sharing service like RapidShare and those who want to see it can download it.

Not sure how to "Sort early boot files in front of media. Satisfy BIOS and setupldr.bin"
The gho files are in D:\Ghost folder if that makes any difference

CDs are written in folder name sequence thus all the files in the \Ghost folder are written to the CD before the OS's \I386 folder. You need the OS files closer to the beginning of the CD, simplest solution put the large Ghost files in a folder that gets written AFTER the \I386 folder. \Xtra, \zzz_images, even \Johns_stuff works.

[JohnG]

Thanks for all the help...it worked after I moved the GHOST files and Drivers folder to X:\Programs folder.......although there is one tiny issue (which is not a big deal) ..and that is my customized bitmap file "bartpe.bmp" (I renamed it to nu2.bmp and modified) does not show up as background anymore..I never had this issue before....and like I said it is not a big deal but if some knows a quick fix that would be great.

thanks again for all your help....truly appreciate