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

geitonaki

Oct 17 2005, 10:18 AM

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:

open it with your favorite hex editor
goto hex address: 0x2060
change "74 03" to "EB 1A"
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:

all occurrences of "i386", "I386" to "ABCD" (where ABCD is anything you want - 4 characters long)
"\amd64", "\AMD64" to "\EFGHI" and
"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.

amd64lover

Oct 17 2005, 11:06 AM

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

geitonaki

Oct 17 2005, 11:24 AM

You can save the output like below:

CODE

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

Jazkal

Oct 17 2005, 11:41 AM

QUOTE (geitonaki @ Oct 17 2005, 10:18 AM)

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 "\")

amd64lover

Oct 17 2005, 11:45 AM

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

Nakatomi2010

Oct 17 2005, 12:01 PM

CODE

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

Incroyable HULK

Oct 17 2005, 12:21 PM

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

CODE

<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

geitonaki

Oct 17 2005, 12:26 PM

QUOTE (Jazkal @ Oct 17 2005, 11:41 AM)

QUOTE (geitonaki @ Oct 17 2005, 10:18 AM)

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!

Nakatomi2010

Oct 17 2005, 12:34 PM

QUOTE (Incroyable HULK @ Oct 17 2005, 02:21 PM)

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

QUOTE

*snip*

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

geitonaki

Oct 17 2005, 12:50 PM

QUOTE (Nakatomi2010 @ Oct 17 2005, 12:01 PM)

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.

Nakatomi2010

Oct 17 2005, 12:54 PM

How do I get the complete listing?

amd64lover

Oct 17 2005, 01:07 PM

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)

Nakatomi2010

Oct 17 2005, 01:09 PM

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

amd64lover

Oct 17 2005, 01:09 PM

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

Nakatomi2010

Oct 17 2005, 02:31 PM

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

geitonaki

Oct 17 2005, 06:55 PM

QUOTE (geitonaki @ Oct 17 2005, 12:50 PM)

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.

http://www.msfn.org/board/index.php?showtopic=58446

amd64lover

Oct 18 2005, 01:49 PM

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.

Incroyable HULK

Oct 18 2005, 08:24 PM

QUOTE (amd64lover @ Oct 18 2005, 01:49 PM)

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?

amd64lover

Oct 18 2005, 08:29 PM

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.

BrandonS_Mil

Oct 18 2005, 11:04 PM

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.

amd64lover

Oct 18 2005, 11:20 PM

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.

Alanoll

Oct 18 2005, 11:38 PM

QUOTE

boot folder creation tool (thanks Alanoll)

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

BrandonS_Mil

Oct 19 2005, 12:33 AM

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.

amd64lover

Oct 19 2005, 08:26 AM

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.

shanssv

Oct 24 2005, 03:15 AM

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

amd64lover

Oct 24 2005, 07:50 AM

well, follow flyakites guide (http://flyakite.msfnhosting.com/) and then edit the files as necessary. the steps are about the same for both the 32 and 64bit versions of windows. be sure to use VMware or something similar to obtain the boot files for xp64. then read this....

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

read through the forums and youll have a lot of questions answered. let me know how it works.

Incroyable HULK

Oct 24 2005, 04:12 PM

QUOTE (amd64lover @ Oct 24 2005, 07:50 AM)

well, follow flyakites guide (http://flyakite.msfnhosting.com/) and then edit the files as necessary. the steps are about the same for both the 32 and 64bit versions of windows. be sure to use VMware or something similar to obtain the boot files for xp64. then read this....

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

read through the forums and youll have a lot of questions answered. let me know how it works.

When you are editing SETUPLDR.BIN, are you changing 5 occurence of i386 and 2 occurence of I386?

I am asking because I did it this way, then I changed the SetupSourcePath of my txtsetup.sif file and when I boot, setup is asking me to insert the Windows XP x64 CD-ROM right away... unless I put the i386 and AMD64 folder at the root of my CD but if I do so, it won't go unattended

amd64lover

Oct 24 2005, 04:55 PM

that sounds like you forgot to copy the WIN51IA to the root of the DVD... yes, there are 7 instances of 'i386' (case insensitive) being matched. as for unattended, be sure to include the winnt.sif file in both the boot folder and the amd64 folder (in the setup directory).

Incroyable HULK

Oct 24 2005, 05:18 PM

QUOTE (amd64lover @ Oct 24 2005, 04:55 PM)

that sounds like you forgot to copy the WIN51IA to the root of the DVD... yes, there are 7 instances of 'i386' (case insensitive) being matched. as for unattended, be sure to include the winnt.sif file in both the boot folder and the amd64 folder (in the setup directory).

I did include the WIN51 and WIN51IA at the root of the CD and at the root where I moved the I386 and AMD64 folder (inside a \SYSTEM\XPX64EN\ folder).

What I am telling is that even if I edited the SetupSourcePath of my txtsetup.sif file inside my boot folder, (to reflect \SYSTEM\XPX64EN\) the installation is still going into the I386 and AMD64 folders at the ROOT of my CD, not the one inside \SYSTEM\XPX64EN\.

On a "regular" 32-bits system, I would do it this way and then throw my winnt.sif file inside my boot folder (no need to add it to the I386 folder).

I suppose this way of doing business is now gone... I'll have to put a bunch of renamed AMD64 & I386 folders at the root of my CD, and keep a bunch of boot folders at the root and throw each of my winnt.sif files inside theses boot folders as well as the I386 folders...

amd64lover

Oct 24 2005, 05:28 PM

you do not need an I386 and AMD64 at the root of your DVD... obtain the boot folder, $WIN_NT$.~BT, rename it, then edit the setupldr.bin/txtsetup.sif files...

Incroyable HULK

Oct 24 2005, 05:41 PM

QUOTE (amd64lover @ Oct 24 2005, 05:28 PM)

you do not need an I386 and AMD64 at the root of your DVD... obtain the boot folder, $WIN_NT$.~BT, rename it, then edit the setupldr.bin/txtsetup.sif files...

this is EXACTLY what I have done!

I renamed the $WIN_NT$.~BT folder to X4E1
I added the original AMD64 and I386 folder inside a \SYSTEM\XPX64EN\ folder
In my X4E1 folder, I ajusted the SetupSourcePath inside the txtsetupsif file to this location (\SYSTEM\XPX64EN\)
In my X4E1 folder, I edited the setupldr.bin to change I386 and i386 to X4E1 (7 occurences)
In my X4E1 folder, I added my winnt.sif file

Am I missing something?

Edit: if your stuff is working, could you make a download of your BOOT folder?

amd64lover

Oct 24 2005, 10:52 PM

well i am not sure if adding both the i386 and amd64 folders in the XPX64EN folder is problematic. try creating an "XP64" folder in your setup folder (or whatever folder contains the installation files for the other OSes) and copying the entire xp64 installation cd to that folder. in addition to the edits you have made above, be sure to edit the boot image. i have uploaded my boot folder (you may want to delete the winnt.sif thats in there). it can be downloaded at http://rapidshare.de/files/6724995/XP64.zip.html

Incroyable HULK

Oct 26 2005, 01:42 PM

QUOTE (amd64lover @ Oct 24 2005, 10:52 PM)

well i am not sure if adding both the i386 and amd64 folders in the XPX64EN folder is problematic. try creating an "XP64" folder in your setup folder (or whatever folder contains the installation files for the other OSes) and copying the entire xp64 installation cd to that folder. in addition to the edits you have made above, be sure to edit the boot image. i have uploaded my boot folder (you may want to delete the winnt.sif thats in there). it can be downloaded at http://rapidshare.de/files/6724995/XP64.zip.html

Have you checked before allowing the download your winnt.sif file?

So if I use this boot folder, I need to put the I386 and AMD64 folders in a \SETUP\XP64\ directory?

amd64lover

Oct 26 2005, 02:30 PM

i forgot to delete it... unless we are running the exact same version of XP64, the winnt.sif file wont work (or at least the cdkey in there wont work). correct, if you use this boot folder, then copy the entire installation cd to the \SETUP\XP64 directory. be sure to edit the XP64.DAT file as well.

Incroyable HULK

Oct 26 2005, 08:20 PM

Well, still no luck... I used your boot folder and your path but it does exactly the same

This is what I get in WMware and on a real computer:

This is to show what files I have...

It's like the SetupSourcePath entry is ignored... I don't know. If I put the I386 and AMD64 folders at root it will work (but not unattended unless I throw my winnt.sif in there)

I am using a VLK CD I got from Microsoft a few months ago...

*** EDIT ***
I don't think this could matter but I am not using the BOOTSECT.DAT file provided by microsoft, I edit the w2ksect.bin (like I always do) provided with EasyBoot... anyway, I get to the setup so I don't think this has any influence...

amd64lover

Oct 26 2005, 08:28 PM

hmmmm.... is the boot folder in the root named 'XP64'? did you copy the entire cd to the \SETUP\XP64\ directory?

Incroyable HULK

Oct 26 2005, 08:30 PM

QUOTE (amd64lover @ Oct 26 2005, 08:28 PM)

hmmmm.... is the boot folder in the root named 'XP64'? did you copy the entire cd to the \SETUP\XP64\ directory?

Affirmative

amd64lover

Oct 26 2005, 08:40 PM

did you edit the XP64.DAT file to point to the XP64 folder?

Incroyable HULK

Oct 26 2005, 08:50 PM

Wohaaa

You won't beleive this! I took a ride into the txtsetup.sif file and I found this:

QUOTE

cdname = "Windows XP Professional x64 Edition CD-ROM"
productname = "Windows XP Professional x64 Edition"

bootname1 = "Windows XP Professional Setup Boot Disk"
bootname2 = "Windows XP Professional Setup Disk #2"
bootname3 = "Windows XP Professional Setup Disk #3"
bootname4 = "Windows XP Professional Setup Disk #4"
bootname5 = "Windows XP Professional Setup Disk #5"
bootname6 = "Windows XP Professional Setup Disk #6"
bootname7 = "Windows XP Professional Setup Disk #7"

cdtagfile = "\win51ap"

cdtagfilei = "\win51ip"

cdtagfilem = "\win51mp"

cdtagfilea = "\win51ap"

So I added a dumb WIN51IP and WIN51MP file at the root of the CD and inside \SETUP\XP64\ folder and guess what?

IT'S WORKING! My WMware simulation is going on... the only thing is that I had to press next after the first reboot (at the GUI) ... I'll keep you updated, it's still running

amd64lover

Oct 26 2005, 08:55 PM

always the simple solutions.....

Incroyable HULK

Oct 26 2005, 09:05 PM

QUOTE (amd64lover @ Oct 26 2005, 08:55 PM)

always the simple solutions.....

I guess you already had the WIN51IP file (from another Windows) at your root so this is why you didn't get this issue...

Anyway, I still have a few problems:
1- I noticed my drivers didn't get uncompressed at the beginning of the GUI part (T-39)
2- I had to manually click next

3- setup get stuck somewhere at T-33 or T-37 stage...

I'll try with a "simpler" winnt.sif file tomorow

Incroyable HULK

Oct 26 2005, 09:21 PM

Ok, nevermind, I had the time to try with a simple winnt.sif file and I am at stage T-24 without a hitch now...

Are you guys able to decompress your drivers at stage T-39 with a 7zip SFX archive like:

QUOTE

[GuiUnattended]DetachedProgram="%systemdrive%\DP.exe"
Arguments="-y /q /r:n"

matt121

Nov 13 2005, 06:38 PM

QUOTE (geitonaki @ Oct 18 2005, 03:18 AM)

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:

open it with your favorite hex editor
goto hex address: 0x2060
change "74 03" to "EB 1A"
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:

all occurrences of "i386", "I386" to "ABCD" (where ABCD is anything you want - 4 characters long)
"\amd64", "\AMD64" to "\EFGHI" and
"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.

To which folder are you modding the setupldr.bin in?

Is it the one in I386 folder or the front boot folders on the Multiboot DVD?

Incroyable HULK

Nov 13 2005, 06:51 PM

front

r3loaded

Jan 3 2006, 04:41 PM

QUOTE (amd64lover @ Oct 18 2005, 07:49 PM)

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.

Ok, I've got that bit. The only problem is that I'm on a 32 bit system and my 64 bit laptop isn't coming for a couple of weeks. I therefore can't get the boot folder as setup won't even start. Anyone got a boot folder I can borrow? plz?

geitonaki

Jan 6 2006, 05:20 AM

QUOTE (r3loaded @ Jan 3 2006, 04:41 PM)

Anyone got a boot folder I can borrow? plz?

Check this:
http://www.msfn.org/board/index.php?showtopic=58446

it automatically creates the boot folders

Jito463

Jan 18 2006, 08:07 PM

I stopped coming by for a while after the last time when we couldn't figure this out. I'm glad to see someone finally did get it working. Tested it at work with x64 and the preinstall worked without a hitch. Now we just need to figure out how to add Vista to the multi-boot DVDs.

@geitonaki
One thing I feel should be pointed out is that you don't need the AMD64 directory for x64. Just the $WIN_NT$.~BT folder that's created when you run the setup from within Windows as Incroyable Hulk posted earlier. You should update your batch files accordingly.

geitonaki

Jan 19 2006, 05:00 AM

QUOTE (Jito463 @ Jan 18 2006, 08:07 PM)

@geitonaki
One thing I feel should be pointed out is that you don't need the AMD64 directory for x64. Just the $WIN_NT$.~BT folder that's created when you run the setup from within Windows as Incroyable Hulk posted earlier. You should update your batch files accordingly.

Having the AMD64 directory and trying to install to a 32bit processor you get the following message:
"Attempting to load an x64 operating system, however this CPU is not compatible with x64 mode. Please install a 32-bit X86 operating system."
Without the AMD64 directory you will get:
"Please insert the disk labeled Windows blah blah x64 Edition CD-ROM into drive A:"

Jito463

Jan 19 2006, 01:23 PM

Well, either way, it won't work.

geitonaki

Jan 19 2006, 05:57 PM

Yes it won't work but at least it tells you what's wrong

This is the reason that it is better to have two boot folders. But if you don't mind you can merge them into one.