Server 2003 SP2 Multi-Boot

[LeveL]

Now Server 2003 SP2 is finally released, I would like to include it in my

multi-boot DVD as opposed to the now dated SP1 version.

One problem, the same thing that is always the problem - setupldr.bin

Anyone remember all the trouble with SP1 when that came out, you couldn't

just replace the text "I386" with your own folder name like "ENT1" because

it gave you the error: "NTLDR is corrupt". The answer was to either use the

setupldr.bin from SP0 or call your folder something crazy like "83i6" or

"i683".

Then geitonaki found the answer here:

http://www.msfn.org/board/index.php?showtopic=58410&st=0

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

But this hex editing trick does not work on the SP2 version of setupldr.bin

I tried using the hacked SP1 version of setupldr.bin on SP2, it does not work.

I tried using the SP0 version of setupldr.bin on SP2, it does not work.

So we are back to square one again if you want to use Server 2003 SP2 in a multi-boot.

I think what we really need is some tool to crack, not hack but crack the setupldr.bin

so it has the same CRC number even though you have changed the file, of course

only people like James Bond have such tools, although that would fix it.

All I keep getting is either:

"NTLDR is corrupt"

or...

"NTDETECT Failed"

Edited March 25, 2007 by LeveL

[cdob]

Then geitonaki found the answer here:

http://www.msfn.org/board/index.php?showtopic=58410&st=0

Read Post #69

http://www.msfn.org/board/index.php?showto...st&p=580692

Search string "46 da 74 03" does work at 2003 SP2 too.

[LeveL]

Then geitonaki found the answer here:

http://www.msfn.org/board/index.php?showtopic=58410&st=0

Read Post #69

http://www.msfn.org/board/index.php?showto...st&p=580692

Search string "46 da 74 03" does work at 2003 SP2 too.

If its changing "74 03" to "EB 1A" at hex address 0x2060 it doesn't work on SP2, I tried it.

[cdob]

It dosn't care about hex address:

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

setupldr.bin: 1 occurrence changed

gsar -i -o -si386 -rXPRC setupldr.bin

setupldr.bin: 7 occurrences changed

At this example 2003 SP2 files does boot.

I get neither "NTLDR is corrupt" nor "NTDETECT Failed".

Another hardware or name may get different result.

[prathapml]

Thank you cdob !

I had same problem too (WinXP 64-bit SP2), now it works

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

But because of the folder structure (or god knows what), i still get a different error message after load, saying txtsetup.sif corrupted or missing, but thats easier & i think i know the reason, so can be fixed by me (i hope)

Edited March 30, 2007 by prathapml

[Sudarshan]

Hi prathapml,

As you said that you know the solution for

"INF file txtsetup.sif is corrupted or missing".

Can you help me solve this problem?.

[prathapml]

The reason for above, is replacing too many instances of the text-string "AMD64" in setupldr.bin

Using gsar.exe, an almost fail-proof way to search & replace the folder names from I386 & AMD64, to PX01 & PX641 is:

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

gsar -i -o -si386 -rPX01 setupldr.bin
7 occurrences

gsar -i -o -s\AMD64 -r\PX641 setupldr.bin
5 occurrences

gsar -i -o -sAMD64\ -rPX641\ setupldr.bin
setupldr.bin: 1 occurrence changed