[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

This post has been edited by Tostis: 20 July 2008 - 09:15 AM

[victor888]

updated:

the method doest apply to win2k3 sp2

This post has been edited by victor888: 27 August 2008 - 08:30 AM

[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

Quote

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:

Quote

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]

amd64lover, on Oct 24 2005, 10:55 PM, said:

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.

This post has been edited by LeveL: 06 March 2009 - 11:34 AM

[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
 untitled.JPG (7.76K)
Number of downloads: 12
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?

This post has been edited by meowing: 30 October 2009 - 02:59 AM

[jaclaz]

meowing, on Oct 28 2009, 04:05 PM, said:

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]

meowing, on Oct 28 2009, 10:05 AM, said:

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.

Quote

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-....de/bcdw_e.html
However no idea about XP x64, this may work or not.

Quote

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=&...st&p=814566
You may use \XP_1\$OEM$ and \XP_2\$OEM$

[meowing]

cdob, on Oct 28 2009, 08:17 PM, said:

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.

Quote

This old release dosn't support XP SP2.
BCDW 2.01a support XP SP2 x32. http://www.wolfgang-....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.

Quote

Quote

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..

Quote

A XP x64 example, slightly different to flyakite's guide: http://www.msfn.org/board/index.php?s=&...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..

This post has been edited by meowing: 31 October 2009 - 01:19 PM

[jaclaz]

meowing, on Oct 30 2009, 10:31 AM, said:

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..

If I may , the idea is to "follow flyakite's guide principles" BUT skip over a few of them and follow cdob's tutorial.

The flyakite guide and what Gremo originally did is (basically and at it's core) made of two "main" steps:

• expand/create the \$WIN_NT$.~BT\ and \$WIN_NT$.~LS folders through WINNT32.exe and rename the first to "\PRO1" and move the contents of second to "\I386" and "\AMD64\"
  
• hexedit/patch/modify paths in relevant files

What cdob's suggested/hinted is to NOT expand anything and just rename/move directories and hexedit/patch modify paths in relevant files.

In other words flyakite's original approach is "bring back to CD a HD install", whilst cdob's suggested one is "modify the original CD based install to work from a different path".

jaclaz

[meowing]

jaclaz, on Oct 30 2009, 10:56 AM, said:

In other words flyakite's original approach is "bring back to CD a HD install", whilst cdob's suggested one is "modify the original CD based install to work from a different path".

So if one wants to use cdob's method, what does one use to load the different OS setup folders? He/she forgets to mention that in his 'guide'.

I prefer using EasyBoot, because I once paid for that thing. But it's quite unclear to me which files need to be edited how, even when I read this entire thread. The solution posted here involves flyakite's guide, which I think is way overkill for just a couple of XP x64 isos on one DVD.

[cdob]

meowing, on Nov 11 2009, 03:46 PM, said:

what does one use to load the different OS setup folders? He/she forgets to mention that in his 'guide'.

Use any working multi boot loader, there is no limitation.

Use the classic boot sector file. Edited files, compare flyakite guide.
multi boot loader -> boot sector file -> setupldr.bin

The boot sector file solution is outdated nowadays.
Chainload different (edited) setupldr.bin: multi boot loader -> setupldr.bin

No idea about EasyBoot.

Ask further questions in another thread.

[meowing]

Is replacing all the amd64 entries as in

gsar.exe -i -o "-sAMD64:x5C" "-r%char4%:x5C:x00" %setupldr%
gsar.exe -o "-sAMD64:x00" "-r%char4%:x00:x00" %setupldr%

really safe?
I ask this because of what it says here:
"Do not replace all occurrences of "amd64" since some of them refer to a section of txtsetup.sif"

When I compare the two setupldr.bin files (the one in that post and the one generated by the gsar commands), the one from geitonaki has a lot more amd64 entries left in there.. :-/

Still not clear what to replace in setupldr.bin and what to leave as is... Can someone reassure me the gsar script here is correct for XP x64 SP2 setup/install?

This post has been edited by meowing: 13 November 2009 - 04:33 PM

[cdob]

meowing, on Nov 13 2009, 02:58 PM, said:

Is replacing all the amd64 entries as in

gsar.exe -i -o "-sAMD64:x5C" "-r%char4%:x5C:x00" %setupldr%
gsar.exe -o "-sAMD64:x00" "-r%char4%:x00:x00" %setupldr%

Command does NOT replace all amd64.

Quote

really safe?

Try and report.

Don't compare different setupldr.bin. They goes to different solutions.
Again, you are mixing solutions, ask details at proper thread.

[meowing]

cdob, on Nov 13 2009, 11:04 PM, said:

meowing, on Nov 13 2009, 02:58 PM, said:

Is replacing all the amd64 entries as in

gsar.exe -i -o "-sAMD64:x5C" "-r%char4%:x5C:x00" %setupldr%
gsar.exe -o "-sAMD64:x00" "-r%char4%:x00:x00" %setupldr%

Command does NOT replace all amd64.

That was not my question, nor did I make that statement.
I know you're making 4 chars from 5 by adding x00. By the way, even though setupldr.bin isn't an executable, it might be safer to use x20 before the x00, see here.

cdob, on Nov 13 2009, 11:04 PM, said:

Don't compare different setupldr.bin. They goes to different solutions.
Again, you are mixing solutions, ask details at proper thread.

I don't see how "Do not replace all occurrences of "amd64" since some of them refer to a section of txtsetup.sif" would not apply to both 'solutions', i.e. I'm NOT mixing any.

This post has been edited by meowing: 13 November 2009 - 04:44 PM

[mordicus]

Hi guys, just a word to say thx a lot for your help (and for your cracked steupldr ).

Regards.

NB: i had a problem on my eazyboot dvd (with xp pro sp3 and a BartPE with win 2k3 server sources (the problem was "ntldr is corrupt" from the boot of BartPE))

This post has been edited by mordicus: 11 January 2010 - 06:58 AM

[tonik22]

I just want to say THANK YOU FOR THIS WORK, with all due respect.

[Letting]

I installed window xp pro using USB flash disk on emachine M350 but it failled to boot when setup reboot the system in order to complete intallation but it give the BLUE SCREEN with the error 0x007B, 0xf7a8a524, 0xc034. cant some one help"

[jaclaz]

Letting, on 02 June 2011 - 12:34 PM, said:

I installed window xp pro using USB flash disk on emachine M350 but it failled to boot when setup reboot the system in order to complete intallation but it give the BLUE SCREEN with the error 0x007B, 0xf7a8a524, 0xc034. cant some one help"

Wrong place to ask , it should be here:
http://www.msfn.org/...ndows-from-usb/

WHICH particular (among the ones listed there) solution did you use?

Or you attempted a "plain install from USB" ?

You don't need this modified SETUPLDR.BIN for XP.

In ANY case, start a NEW thread there:
http://www.msfn.org/...ndows-from-usb/

jaclaz

This post has been edited by jaclaz: 03 June 2011 - 02:19 AM