|
|
| Post Number: 1
|
Incroyable HULK 
Group: Members
Posts: 197
Joined: Oct. 2004
|
 |
Posted on: Aug. 05 2005,23:24 |
|
   |
Hello all,
Finally, we have found a permanent solution to to the corruption problem of SETUPLDR.BIN with 64-Bits Windows as well as Windows 2003 Server family (since SP1).
You will need a hex editor program to do so...
1- open the SETUPLDR.BIN file with your hex editor
2- Go to the hex address 0x2060
3- replace value 74 03 with EB 1A
4- Save the file
Now you can edit the SETUPLDR.BIN file with EasyBoot (using the Replace Text... feature under the Tools button) and replace
5 occurence of i386 and 2 occurence of I386
that's it
You can download a modified SETUPLDR.BIN file from here:
http://www.encoremedias.com/MSFN/setupldr.bin
This way, you won't need a Hex editor
The credit goes to geitonaki on the MSFN forum
Archived
just to let you know that we have found a "temporary" solution to the corruption problem of SETUPLDR.BIN with 64-Bits Windows as well as Windows 2003 Server family (since SP1).
you can safely replace i386 with i683 or 83i6; they won't break the CRC check.
I successfuly tested theses combinations with Windows 2003 Server SP1
Stay tuned for later developement. Next step is to change the AMD64 entry...
Edited by Incroyable HULK on Nov. 03 2005,18:39
--------------
Get a Quad NIC for your Server (perfect for VMware)
HowTo: VMware Server 1.0.1 on Ubuntu Server 6.10
|
 |
|
|
| Post Number: 2
|
Hannes
Group: Members
Posts: 68
Joined: Dec. 2003
|
|
Posted on: Oct. 13 2005,09:32 |
|
 |
I must be missing something here. i386 works fine for me but for the life of me I cannot get i683 to work. Here's what I'm doing:
Under disk1 I've named the directory i683
In the saved bootfile I replace I386 with I683.
In setupldr.bin I replace i386 with i683
In the txtsetup.sif I change the "SetupSourcePath" from "\" to "i683".
Am I missing something here or do I have the case wrong for "i683" or "I683" in any of these instances?
Hannes
|
|
|
|
| Post Number: 3
|
Incroyable HULK
Group: Members
Posts: 197
Joined: Oct. 2004
|
|
Posted on: Oct. 15 2005,20:36 |
|
|
What you have to indicate in txtsetup.sif is the ROOT were the I386 folder reside. You DON'T rename the I386 folder...
You should try something like:
SetupSourcePath ="\"
and Yes, you have to edit both i386 and I386 in your setupldr.bin file (the important thing is to get 7 occurence replaced if I remember correctly...)
Edited by Incroyable HULK on Oct. 15 2005,20:37
--------------
Get a Quad NIC for your Server (perfect for VMware)
HowTo: VMware Server 1.0.1 on Ubuntu Server 6.10
|
|
|
|
| Post Number: 4
|
Hannes
Group: Members
Posts: 68
Joined: Dec. 2003
|
|
Posted on: Oct. 16 2005,17:23 |
|
|
Thanks for the response, but actually, do do have to rename i386.
Say you are going to have a multiboot disc with Windows 2000, Windows XP, and Server 2003 on it. In c:\easyboot\disk1 only one of these can use the the subdirectory i386. You have to create different directories for the others. In fact, the point of the original post in this thread was to say that i683 was one of the workable names that didn't kill the new CRC check in Server 2003 SP1.
On my multiboot disc I'm using directory names such as WXP1, WXP2, MCE1, W2K1, W2K2, etc. for Operating Systems including Win XP, Win 2000, and Windows Media Center. These all work fine. However, for Server 2003 SP1 I'm finding that only i386 seems to work. The names provided in the original post don't work for me. That is what led to my question - I was thinking that I was probably missing a very subtle detail such as caps vs. lowercase.
Hannes
|
|
|
|
| Post Number: 5
|
Marsianin
Group: Members
Posts: 8
Joined: Jan. 2006
|
|
Posted on: Jan. 12 2006,02:15 |
|
|
But where to get WinXP x64 setup files ? (boot floppies or which files we need from i386 or amd64)
And another one thing. When I have WinPE, WinXP x32 setup on one DVD and AMD64 folder in the root of CD - these programs are not works.
|
|
|
|
| Post Number: 6
|
|
|
| Post Number: 7
|
Marsianin
Group: Members
Posts: 8
Joined: Jan. 2006
|
|
Posted on: Jan. 12 2006,15:17 |
|
|
All these for 32bit Windows versions.
I need 64 bit. But I will try to start install it to get $WIN_NT$.~BT
|
|
|
|
| Post Number: 8
|
|
|
| Post Number: 9
|
Marsianin
Group: Members
Posts: 8
Joined: Jan. 2006
|
|
Posted on: Mar. 01 2006,22:35 |
|
|
Ok. I got setup files for x64 XP and run ISO under VMWare 32bit processor (I don't know why but it can't emulate 64bit CPU on my Athlon FX-55  )
When I tryed to run from this ISO I got "Cannot load ntkrnlmp.exe" error. Can it be because it's run on 32bit platform ?
And another one.
Where I should place AMD64 folder ? Inside \XP64\ (where installer placed and i386) or in the root ?
|
|
|
|
| Post Number: 10
|
Marsianin
Group: Members
Posts: 8
Joined: Jan. 2006
|
|
Posted on: May 05 2007,06:04 |
|
|
It seems I missing to do something but I still can't get x64 Windows to multiboot.
I have everything except AMD64 folder in XP64 (and changed setupldr.bin for it).
AMD64 folder I have in the root of CD elsewhere it will not work.
When I booting everything works fine until it starts to copy files from AMD64 folder (I think so, because on ~60% installer starts to ask for files which are in AMD64 folder).
Txtsetup.sif exists only in AMD64 folder and setupsource="\".
Please help. What else I need to change to get it work?
|
|
|
|
|
|
