NTLDR is corrupt. The system cannot boot.

hi, as stated on the title topic, that is the error I get when I try boot my livexp. i'm creating a multiboot cd w/ ubcd, puppy and livexp.

hi, as stated on the title topic, that is the error I get when I try boot my livexp. i'm creating a multiboot cd w/ ubcd, puppy and livexp.

Yep, good to know.

I mean, there is NO question in your post, NOR any actual useful report of WHAT you attempted to do, with which tools, with which source, etc., etc. etc.

All you can get right now is "standard reply #32":
http://www.boot-land...topic=2587&st=1

Now be nice , and post some meaningful report of what you did, this may be a good trace:
http://homepages.tes...ard-litany.html

Point #d in the "common sense advice" may also clear the issue at hand (missing data):
http://www.boot-land...?showtopic=9101

Generally speaking, a message like "NTLDR is corrupt. The system cannot boot." actually means:

• that NTLDR is corrupt
• that the system cannot boot

so the point is trying to understand which actions you did, and which of them may have corrupted NTLDR (or a pointer to it).


Wonko

sorry about that.

I used Sardu 1.0.7.2 beta to create a multiboot cd.
I wanted to multiboot UBCD5, puppy linux and livexp (w/c i built).
The build doesn't generate errors and it completed the build. Test the ISO using virtualbox, and everything went smoothly except for the livexp. The error:

NTLDR is corrupt. The system cannot boot.

I already tested my livexp and it booted fine.

I check the iso and there's no ntldr. Check the isolinux.cfg and this is the code:

label Boot from LiveXP

menu label Boot from ^LiveXP

MENU INDENT 1

	  COM32 /chain.c32

APPEND boot ntldr=/LIXP/SETUPLDR.BIN

how to fix this error?

Does the LiveXP that you tested "by itself" use the \I386\ or the \minint\ directory or the \LIXP one?

Which EXACT version of source did you use to create the LiveXP, and particularly which SETUPLDR.BIN was used?

If one from Server 2003 SP1 or later, it needs to be patched:
http://www.msfn.org/...showtopic=58410


Wonko

@ wonko the sane with multipe i hexedit i386 with LIXP
appearance news

@ wonko the sane with multipe i hexedit i386 with LIXP
appearance news

Yep, you change \I386\ to \LIXP\ but do you also check if the SETUPLDR.BIN is one of the "with checksum" versions AND patch it ALSO to avoid checksum?


Wonko

Yep, you change \I386\ to \LIXP\ but do you also check if the SETUPLDR.BIN is one of the "with checksum" versions AND patch it ALSO to avoid checksum?


Wonko

I didn't know there were SETUPLDR.BIN with checksum. In my tests everything worked well ... maybe I was lucky.

Does the LiveXP that you tested "by itself" use the \I386\ or the \minint\ directory or the \LIXP one?

It uses the I386.

Which EXACT version of source did you use to create the LiveXP, and particularly which SETUPLDR.BIN was used?

I used Windows XP SP3 as source.

Tried this.

If one from Server 2003 SP1 or later, it needs to be patched:
http://www.msfn.org/...showtopic=58410

It goes through with the ntldr error but gave me another error.

INF file txtsetup.sif is corrupt or missing, status 18

By the way, I tried this with Sardu 1.0.7.1 and no problem booting with the livexp.

Comeon, vaikz.

Let's be rational, OK?

SARDU automatically changes some occurrences of \I386\ to \LIXP\

The patch (which I have NO idea how it was made) has been tested with the NTLDR of XPSP2, in the words of the Author.

It may NOT work with the NTLDR from XPSP3. (which AFAIK has no checksum)

The NTLDR in the thread I gave a reference to is from Server 2003 SP1, it is a particular version with an internal checksum AND it has been changed as to disable the checksum in order to make it possible to change the \I386\ or \minint\ to WHATEVER, BUT these strings have NOT been changed.
Thus you have now:

• a "patched for path" NTLDR from XP SP3 pointing to LIXP that is invalid <-this file is corrupt and prints "NTLDR is corrupt. The system cannot boot."
• a "patched for checksum" NTLDR from Server 2003 SP1 that points to I386 <- this file points to a location where the files ARE NOT

The solution until davidecosta catches up with the issue is obviously to MANUALLY hexedit the NTLDR of XPSP3 you have to point to LIXP.

READ the given thread.


Wonko

I used Windows XP SP3 as source.

What version you have used Windows XP SP3?
I need to re-create the problem to try to resolve it. I made dozens of evidence ... but not encounter this problem. I found on USB ... and ...These days rewrite it all.

What version you have used Windows XP SP3?

Windows XP Pro SP3.

What version you have used Windows XP SP3?

Windows XP Pro SP3.

your file SETUPLDR.BIN is 298.096 byte
my file SETUPLDR.BIN is 261.312 byte

Your is an official release? Or nlited or modded?

the 298.096 bytes is the one from Server2003 SP1.

Back to square #4:
http://www.boot-land...?...=10998&st=3

Or maybe square #9:
http://www.boot-land...?...=10998&st=8

What is the difficult part?


Wonko

the 298.096 bytes is the one from Server2003 SP1.

Back to square #4:
http://www.boot-land...?...=10998&st=3

Or maybe square #9:
http://www.boot-land...?...=10998&st=8

What is the difficult part?


Wonko

This error only with ISO:

inf file txtsetup.sif is corrupt or missing, status 18

With usb work fine

used code of gsar:

gsar -o  -s:x46:xda:x74:x03 -r:x46:xda:xEB:x1A setupldr.bin

gsar -o  -si386\ -rLIXP\ setupldr.bin

gsar -o  -s\minint\txtsetup.sif -r\minixp\txtsetup.sif setupldr.bin

gsar -o  -s\minint\system32\ -r\minixp\system32\ setupldr.bin

fix

gsar -o  -s:x46:xda:x74:x03 -r:x46:xda:xEB:x1A setupldr.bin

gsar -o -i -si386\ -rLIXP\ setupldr.bin

gsar -o  -s\minint\txtsetup.sif -r\minixp\txtsetup.sif setupldr.bin

gsar -o  -s\minint\system32\ -r\minixp\system32\ setupldr.bin

The error was the case sensitive of i386 / I386

In this days remove xvi32 and replace it with gsar

P.S. Thanks to Wonko

thanks davidecosta and also to you wonko I'll try this now.
I'll give feedback later.

thanks davidecosta and also to you wonko I'll try this now.
I'll give feedback later.

New beta 1.0.7.2 beta 10 with this fix: i've rewrited all code of multiPE

Feedback are welcome