Solution for multibooting Win XP/2k3 64-Bit, Win2k3 SP1, WinPE 2004

[Crazysky]

I'm looking for a solution for Windows 2003 server R2 SP2 (sp2 applied after Win Installation, 2CD)

I've tried "crack" the setupldr.bin but i have this error :

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

Setup cannont continue , ...

If anyone have seen it please tell me how to resolve this error.

thanks

[xenon2050]

1 - I got the (original, from my own CD) setupldr.bin file from Server 2003 SP2.

2 - I opened the file in Hex Workshop and at the address 00002060 I hex

edited the value "7403" so it said "EB1A"

3 - I got the message "NTDETECT Failed"

Any one have a answer to this? I'm getting the NTLDR corrupt problem trying to use the 2003 SP2 version...

Edited April 16, 2008 by xenon2050

[Siginet]

OK... I can say that this method DOES still work for Win2k3 SP2. I edited my setupldr.bin at hex address: 0x2060 and changed: "74 03" to "EB 1A". It isworking now. I don't know why others are having an issue. I know I use a slightly different method for my multiboot disks then the method most people use. But I don't see why it would work for me uding my method instead of the normal method.

[xenon2050]

Are you using 2003 or 2003 R2? Maybe my problem is using the R2 edition... I'll try it with the standard and get back to you.

[jojo2005]

@BrandonS_Mil,

where did you take your winnt.sif file ?

Boot Directory ?

or

Setup Directory ?

It must be placed in the Boot Directory, then should be work.

greetz

jojo2005

Edited June 27, 2008 by jojo2005

[723novy723]

Thank you very much. I cannot create bootable Windows 2003 server. Thaks for Cracked SETUPLDR.BIN. This fix solve my problem. Once again Thank you. Who make up this crack? Really clever master.

Bye

Majkl Czech Republic

[Tostis]

i applied the crack tor setupldr.bin of windows 2003 sp2 but it doesn't work. does anyone managed to work?

UPDATE:

solved putting boot folder at the beginning of dvd

Edited July 20, 2008 by Tostis

[victor888]

updated:

the method doest apply to win2k3 sp2

Edited August 27, 2008 by victor888

[GreenMark909]

Hi guys,

I'm new to this whole Multi-Boot DVD. I have two versions of XP x64 and would want to have them in one Bootable DVD. I google-d up and i found this http://flyakite.msfn.org/ very helpful but its mainly for 32Bit Windows

And then i found this

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

I also uploaded it for your convenience at:

File is now attached so people don't have to wait for a download ~ Alanoll

Now you can replace:

1. all occurrences of "i386", "I386" to "ABCD" (where ABCD is anything you want - 4 characters long)

2. "\amd64", "\AMD64" to "\EFGHI" and

3. "amd64\", "AMD64\" to "EFGHI\" (where EFGHI is anything you want - 5 characters long)

Do not replace all occurrences of "amd64" since some of them refer to a section of txtsetup.sif

In order to find what files need to be copied to the directories ABCD and EFGHI open command prompt, go to the directory you have txtsetup.sif and enter:

CODE

type TXTSETUP.SIF | findstr /r ",_[1-9] ,[1-9]_"

and copy the files listed there from I386 to ABCD and AMD64 to EFGHI.

For anyone curious, open the setupldr.bin with hiew, goto the above hex address and see the surrounding assembly code.

From where do I exactly start to compile this. My understand is that because both of my Windows XP x64 has the same folder names "I368" & "AMD64", I would have to copy and rename first Disk folder "I368 to PRO1" & "AMD64 to XPro1" and respectively 2nd disk "I368 to PRO2" & "AMD64 to XPro2"

Well that is my understanding, but I don't know how to execute the portion below:

Now you can replace:

1. all occurrences of "i386", "I386" to "ABCD" (where ABCD is anything you want - 4 characters long)

2. "\amd64", "\AMD64" to "\EFGHI" and

3. "amd64\", "AMD64\" to "EFGHI\" (where EFGHI is anything you want - 5 characters long)

Do not replace all occurrences of "amd64" since some of them refer to a section of txtsetup.sif

In order to find what files need to be copied to the directories ABCD and EFGHI open command prompt, go to the directory you have txtsetup.sif and enter:

CODE

type TXTSETUP.SIF | findstr /r ",_[1-9] ,[1-9]_"

and copy the files listed there from I386 to ABCD and AMD64 to EFGHI.

Please, if someone could write and step-by-step walk thru. Where do I do the "all occurrences" and where do I perform this command "type TXTSETUP.SIF | findstr /r ",_[1-9] ,[1-9]_"

Thank You

[LeveL]

that sounds like you forgot to copy the WIN51IA to the root of the DVD

Holy cow I have been trying to get it working all day and only just realized this is why!

Replying to it from 4 years ago, hehehehe.

Edited March 6, 2009 by LeveL

[SXiPRATEEK]

i have merged win xpsp3 & bartpe

then i have edited bartpe disk in which i have renamed i386 to bart

"i386 is also in xpsp3 so"

edit setupldr.bin with hex edit to replace i386 with bart

edit textsetup.sif with notepad & change i386 to bart

then i extrat boot.img using isobuster & rename it to "bart.dat"

similarly extract boot.img from xpsp3 & rename it to "xpsp3.dat"

then i extrat files from xpsp3 & bartpe in same folder

three files have same name i keep xpsp3 xpsp3 version

then i use magic iso to creat multiboot cd with multiboot wizard

cd boots well

then xpsp3 works well

bartpe loads well it shows booting screen then login screen of pe & then login & then suddenly it gives error " lsass.exe"

& restart

how to overcome this

[meowing]

What's the best way to dual-boot two OS-installs of XP x64 Edition SP2, while using only one $OEM$ precopy folder?

I'd also like to maintain the original CD folder structure of both OS-isos, because I require the official volume-name (at work) in tact,

I just need the 2 choice dialog at boot, no fancy stuff, so cdshell looks like overkill to me.

Tried employing the reanimato tool (http://bootcd.narod.ru/index_e.htm) but it errors out everytime it starts setup on each of the two.

As I understand, I at least need to copy ntdetect.com and setupldr.bin from both the i386 folders one folder higher up, so they are in their respective install-root folders, but I have no clue how they need to be hexed. Let's say my iso-root folders are called \XP_1 and \XP_2 and I also have the \$OEM$ in the root of the dual-boot-installer; What is the best way to go about creating a dual-boot menu and switch for that?

Edited October 30, 2009 by meowing

[jaclaz]

What's the best way to dual-boot two OS-installs of XP x64 Edition SP2, while using only one $OEM$ precopy folder?

I'd also like to maintain the original CD folder structure of both OS-isos, because I require the official volume-name (at work) in tact,

I just need the 2 choice dialog at boot, no fancy stuff, so cdshell looks like overkill to me.

Tried employing the reanimato tool (http://bootcd.narod.ru/index_e.htm) but it errors out everytime it starts setup on each of the two.

As I understand, I at least need to copy ntdetect.com and setupldr.bin from both the i386 folders one folder higher up, so they are in tehir respective install-root folders, but I have no clue how they need to be hexed. Let's say my iso-root folders are called \XP_1 and \XP_2 and I also have the \$OEM$ in the root of the dual-boot-installer; What is the best way to go about creating a dual-boot menu and switch for that?

Read flyakite's guide:

http://flyakite.msfn.org/

http://flyakite.msfn.org/xpprosp1.htm

Editing "setupldr.bin"

Alternative:

grub4dos

or

grub4dos+floppy images:

http://www.msfn.org/board/please-help-w-du...sp2-t127900.htm

Cannot say if everything that applies on 32 bit also works exactly the same on x64.

jaclaz

[cdob]

dual-boot two OS-installs of XP x64 Edition SP2

I'd also like to maintain the original CD folder structure of both OS-isos, because I require the official volume-name (at work) in tact

Windwos support one volume-name at CD. Do you need different volume names?

To maintain the original CD folder structure is possible, if there are tiny differences: different winnt.sif or similar.

You have to use another folder structure, if two OS contains major differences.

Tried employing the reanimato tool (http://bootcd.narod.ru/index_e.htm)

This old release dosn't support XP SP2.

BCDW 2.01a support XP SP2 x32. http://www.wolfgang-brinkmann.de/bcdw_e.html

However no idea about XP x64, this may work or not.

I also have the \$OEM$ in the root of the dual-boot-installer

To clarify, that's two $OEM$ folders. The root of the dual-boot-installer is not the root of CD.

A XP x64 example, slightly different to flyakite's guide: http://www.msfn.org/board/index.php?s=&amp...st&p=814566

You may use \XP_1\$OEM$ and \XP_2\$OEM$

[meowing]

Windows supports one volume-name at CD. Do you need different volume names?

No, I'm using one base core volume for both install isos, so the volume name of the dual-boot DVD should be the same as the original volume-name. I've done this before, it's more efficient to auto find proper drivers and such with the proper volume lable.

This old release dosn't support XP SP2.

BCDW 2.01a support XP SP2 x32. http://www.wolfgang-brinkmann.de/bcdw_e.html

However no idea about XP x64, this may work or not.

Thanks for that. I hope it does work with x64, I'll let you know how it works out.

I also have the \$OEM$ in the root of the dual-boot-installer

To clarify, that's two $OEM$ folders. The root of the dual-boot-installer is not the root of CD.

No I mean my $OEM$ folders have the exact same content for both, so I was wondering if I could put only one on the disk, in the root of the DVD, and then somehow point to them from each separate installer. Do you know where the location for that precopy $OEM$ folder is read from during the installation process? I could hexedit if necessary..

A XP x64 example, slightly different to flyakite's guide: http://www.msfn.org/board/index.php?s=&amp...st&p=814566

You may use \XP_1\$OEM$ and \XP_2\$OEM$

OK thank you. You wrote there:

"Follow flyakite's tutorial and ignore flyakite's tutorial."

so.. which one is it? ;-) What part should I follow from flyakite's tutorial? I prefer using just BCDW. Pity its original developer has disappeared..

Edited October 31, 2009 by meowing