Welcome to MSFN

Register now to gain access to all of our features. Once registered and logged in, you will be able to contribute to this site by submitting your own content or replying to existing content. You'll be able to customize your profile, receive reputation points as a reward for submitting content, while also communicating with other members via your own private inbox, plus much more! This message will be removed once you have signed in.


Sign in to follow this  
Followers 0
geitonaki

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

101 posts in this topic

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:

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.

cracked_SETUPLDR_1_.BIN.zip

Edited by prathapml
0

Share this post


Link to post
Share on other sites

GREAT JOB!!!... one quick thing, when i go to the cmd prompt and typed in the above command, it lists all the files, but it starts with 'H'... since there are so many, i dont know what files are needed that start with a letter before 'H'.... could you post a .txt file with the needed files? thanks

0

Share this post


Link to post
Share on other sites

You can save the output like below:

type TXTSETUP.SIF | findstr /r ",_[1-9] ,[1-9]_" > c:\out.txt

0

Share this post


Link to post
Share on other sites
Do not replace all occurrences of "amd64" since some of them refer to a section of txtsetup.sif

Can someone tell me how to determine which one is which?

Or is it just the standalone "amd64" entries that reference the txtsetup.sif? (meaning no preceeding or trailing "\")

Edited by Jazkal
0

Share this post


Link to post
Share on other sites

replace these, "\AMD64" & "AMD64\" & "\amd64" & "amd64\" (without the "" marks)

Edited by amd64lover
0

Share this post


Link to post
Share on other sites

ksecdd.sys   = 1,,,,,,_6,4,0,0,,1,4
ntdll.dll = 1,,,,,,_7,2,0,0,,1,2
kbdus.dll = 1,,,,,,_7,2,0,0,,1,2
drvmain.sdb = 1,,,,,,_3,60,0,0
kbddv.dll = 1,,,,,,_5,2,0,0,,1,2
kbdes.dll = 1,,,,,,_5,2,0,0,,1,2
kbdgae.dll = 1,,,,,,_5,2,0,0,,1,2
kbdgr1.dll = 1,,,,,,_5,2,0,0,,1,2
kbdit142.dll = 1,,,,,,_5,2,0,0,,1,2
kbdusl.dll = 1,,,,,,_5,2,0,0,,1,2
kbdusr.dll = 1,,,,,,_5,2,0,0,,1,2
kbdusx.dll = 1,,,,,,_5,2,0,0,,1,2
ntfs.sys = 1,,,,,,_6,4,0,0,,1,4
setupreg.hiv = 1,,,,,,_3,,3
spcmdcon.sys = 1,,,,,,_7,,3,3,,1,1
biosinfo.inf = 1,,,,,,_1,20,0,0,,1,1
wkbddv.dll=55,,,,,,_5,82,0,0,kbddv.dll,1,2
wkbdes.dll=55,,,,,,_5,82,0,0,kbdes.dll,1,2
wkbdgae.dll=55,,,,,,_5,82,0,0,kbdgae.dll,1,2
wkbdgr1.dll=55,,,,,,_5,82,0,0,kbdgr1.dll,1,2
wkbdit142.dll=55,,,,,,_5,82,0,0,kbdit142.dll,1,2
wkbdus.dll=55,,,,,,_7,82,0,0,kbdus.dll,1,2
wkbdusl.dll=55,,,,,,_5,82,0,0,kbdusl.dll,1,2
wkbdusr.dll=55,,,,,,_5,82,0,0,kbdusr.dll,1,2
wkbdusx.dll=55,,,,,,_5,82,0,0,kbdusx.dll,1,2
wntdll.dll=55,,,,,,_7,82,0,0,ntdll.dll,1,2
biosinfo.inf = 1,,,,,,_1,20,0,0,,1,1
ntdetect.com = 1,,,,,,_1,1,3,,,1,1
biosinfo.inf = 1,,,,,,_1,20,0,0,,1,1
wkbddv.dll=55,,,,,,_5,82,0,0,kbddv.dll,1,2
wkbdes.dll=55,,,,,,_5,82,0,0,kbdes.dll,1,2
wkbdgae.dll=55,,,,,,_5,82,0,0,kbdgae.dll,1,2
wkbdgr1.dll=55,,,,,,_5,82,0,0,kbdgr1.dll,1,2
wkbdit142.dll=55,,,,,,_5,82,0,0,kbdit142.dll,1,2
wkbdus.dll=55,,,,,,_7,82,0,0,kbdus.dll,1,2
wkbdusl.dll=55,,,,,,_5,82,0,0,kbdusl.dll,1,2
wkbdusr.dll=55,,,,,,_5,82,0,0,kbdusr.dll,1,2
wkbdusx.dll=55,,,,,,_5,82,0,0,kbdusx.dll,1,2
wntdll.dll=55,,,,,,_7,82,0,0,ntdll.dll,1,2

This is the output.... Though it doesn't say which filesgo into which directory...

0

Share this post


Link to post
Share on other sites

I guess we can use GOSH's method to obtain our BOOT folder... I did that a while ago and I got the following files from $WIN_NT$.~BT

<DIR>          system32
1394bus.sy_
acpi.sy_
acpiec.sy_
adpu160m.sy_
adpu320.sy_
aic78u2.sy_
aic78xx.sy_
aliide.sy_
amdide.sy_
arc.sy_
atapi.sy_
biosinfo.inf
BOOTSECT.DAT
bootvid.dl_
cdfs.sy_
cdrom.sy_
classpnp.sy_
cmdide.sy_
c_1252.nl_
c_437.nl_
dac960nt.sy_
disk.sy_
disk101
disk102
disk103
disk104
dmboot.sy_
dmio.sy_
dmload.sy_
dpti2o.sy_
drvmain.sdb
fastfat.sy_
fdc.sy_
flpydisk.sy_
ftdisk.sy_
hal.dl_
hidclass.sy_
hidparse.sy_
hidusb.sy_
i2omgmt.sy_
i2omp.sy_
i8042prt.sy_
iirsp.sy_
intelide.sy_
isapnp.sy_
kbdclass.sy_
kbdhid.sy_
kbdus.dll
kd1394.dl_
kdcom.dl_
ksecdd.sys
l_intl.nl_
migrate.inf
mountmgr.sy_
mraid35x.sy_
ntdetect.com
ntfs.sys
ntkrnlmp.ex_
ohci1394.sy_
oprghdlr.sy_
partmgr.sy_
pci.sy_
pciide.sy_
pciidex.sy_
pcmcia.sy_
ramdisk.sy_
sbp2port.sy_
scsiport.sy_
serenum.sy_
serial.sy_
setupdd.sy_
setupldr.bin
setupreg.hiv
sfloppy.sy_
spcmdcon.sys
spddlang.sy_
storport.sy_
symc810.sy_
symc8xx.sy_
symmpi.sy_
sym_hi.sy_
sym_u3.sy_
toside.sy_
txtsetup.sif
ultra.sy_
usbccgp.sy_
usbd.sy_
usbehci.sy_
usbhub.sy_
usbohci.sy_
usbport.sy_
usbstor.sy_
usbuhci.sy_
vga.sy_
vgaoem.fo_
viaide.sy_
videoprt.sy_
volsnap.sy_
watchdog.sy_
wd.sy_
winnt.sif
wmilib.sy_

102 File(s) 7,213,922 bytes

Edited by prathapml
0

Share this post


Link to post
Share on other sites

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

Can someone tell me how to determine which one is which?

Or is it just the standalone "amd64" entries that reference the txtsetup.sif? (meaning no preceeding or trailing "\")

Exactly what you said!

0

Share this post


Link to post
Share on other sites
I guess we can use GOSH's method to obtain our BOOT folder... I did that a while ago and I got the following files from $WIN_NT$.~BT
*snip*

But which files go into which directory? We technically need 2 BT's now.... Don't we, or am I not grasping something...?

Edited by Nakatomi2010
0

Share this post


Link to post
Share on other sites
This is the output.... Though it doesn't say which filesgo into which directory...

The outpout you posted isn't complete. Each file goes to the respective directory from where you will find it. If you find it in I386 then copy it to ABCD, if you find it in AMD64 copy it to EFGHI.

I will post later if I have time a batch file that I have created which automatically creates the boot folders and modifies the necessary files.

0

Share this post


Link to post
Share on other sites

go to a command prompt and navigate to the directory where the txtsetup.sif file is and copy/paste the following.... 'type TXTSETUP.SIF | findstr /r ",_[1-9] ,[1-9]_" > c:\out.txt' (geitonaki stated this on the first page)

0

Share this post


Link to post
Share on other sites

Nevermind, I must've typed it wrong the first time...

Edited by Nakatomi2010
0

Share this post


Link to post
Share on other sites

open the file 'c:\out.txt'... itll have the complete list in there

0

Share this post


Link to post
Share on other sites

Well, hopefully this utterly and totally simplistic .bat file I made works...

I basically put 'copy' infront of everything and '<Directory here> behind everything, changing MOST, but not all, os the last characters to _... I matched it against a BT I got from a previous install.... And the out.txt file I got...

VERY simplistic batch file...

Edited by Nakatomi2010
0

Share this post


Link to post
Share on other sites

again, your solution work great. i also found that the 'XP64' and 'PRO64' are not necessary. Just take the boot folder ($WIN_NT$.~BT) and rename it to something else (i did mine to XP64) and then edit the setupldr.bin file & replace all instances of "I386" with "XP64", then edit the boot image to show XP64 instead of i386. this is a way to have 1 less folder in your root. i have the x64 boot folder if anyone needs it.

0

Share this post


Link to post
Share on other sites
again, your solution work great. i also found that the 'XP64' and 'PRO64' are not necessary. Just take the boot folder ($WIN_NT$.~BT) and rename it to something else (i did mine to XP64) and then edit the setupldr.bin file & replace all instances of "I386" with "XP64", then edit the boot image to show XP64 instead of i386. this is a way to have 1 less folder in your root. i have the x64 boot folder if anyone needs it.

How do you edit setupldr.bin in that case? Are you only replacing instances of I386?

0

Share this post


Link to post
Share on other sites

i just used the same one i had edited earlier (which replaced the 'i386' with 'xp64' and 'amd64' with 'pro64').... it worked fine, i would say since there is no 'amd64' folder, just replacing the 'i386' should work fine.

0

Share this post


Link to post
Share on other sites

OK, First I would like to say THANK YOU!!! I am now finally able to use my 2K3 Server (ENT/STD/WEB) SP1.

The only problem is that I can’t get my “Unattended” install file to work with any of my windows installs. I used the XP distro install tools (too make winnt.sif files). It worked before, but after I used the boot folder creation tool (thanks Alanoll) it won’t work.

Please someone help.

0

Share this post


Link to post
Share on other sites

the winnt.sif file needs to be both in the boot folder and in the actual i386 folder. if there is already a winnt.sif file in the boot folder, overwrite it with the one you made.

0

Share this post


Link to post
Share on other sites
boot folder creation tool (thanks Alanoll)

That was not me my friend...I only attached for file to the creator's post

0

Share this post


Link to post
Share on other sites

I'm not trying to be rude, i just want people to think first, before they respond.

If someone were to say, i don't know, ask for help saying the the unattended setup worked before they used the nifty program fo fix the server sp1 issue..... I think they would be inteligent enough to have copied the winnt.sif file where it is needed to make windows use it.

P.S. I still need help with my unattended part.

0

Share this post


Link to post
Share on other sites

well i am going to assume that was aimed at me... i am not sure exactly how his batch files work, but when getting the boot folders the 'old fashion' way, the winnt.sif is modified and no longer contains the same info as the one in the i386 folder, which would make it not work. if you have the exact same winnt.sif file in both the boot folder and the i386 folder, then i dont know what to tell you besides to double check by opening the files and making sure the content is what you made. you could also try using nlite to generate the file.

0

Share this post


Link to post
Share on other sites

hi friends,

Could anyone tell me how to use the "setupldr.bin" I am going to use only XP Pro 32 and 64 bit ,only two OS . Please someone tell me how to multiboot ?

Thanx

Shan

0

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now
Sign in to follow this  
Followers 0

  • Recently Browsing   0 members

    No registered users viewing this page.