[amd64lover]

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]

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]

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]

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]

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]

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]

amd64lover, on Oct 24 2005, 07:50 AM, said:

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

This post has been edited by Incroyable HULK: 24 October 2005 - 04:13 PM

[amd64lover]

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]

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

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

This post has been edited by Incroyable HULK: 24 October 2005 - 05:19 PM

[amd64lover]

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]

amd64lover, on Oct 24 2005, 05:28 PM, said:

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?

This post has been edited by Incroyable HULK: 24 October 2005 - 05:50 PM

[amd64lover]

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...5/XP64.zip.html

This post has been edited by amd64lover: 24 October 2005 - 10:54 PM

[Incroyable HULK]

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

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...5/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?

This post has been edited by Incroyable HULK: 26 October 2005 - 01:43 PM

[amd64lover]

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]

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

This post has been edited by Incroyable HULK: 26 October 2005 - 08:25 PM

[amd64lover]

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

[Incroyable HULK]

amd64lover, on Oct 26 2005, 08:28 PM, said:

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

Affirmative

[amd64lover]

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

[Incroyable HULK]

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

This post has been edited by Incroyable HULK: 26 October 2005 - 08:58 PM

[amd64lover]

always the simple solutions.....

This post has been edited by amd64lover: 26 October 2005 - 08:56 PM