[Veovis]

From Windows 2003 Server, Standard Édition English.
For amd64lover

I have forgot the attachment !
SETUPLDR.BIN

This post has been edited by Veovis: 13 October 2005 - 01:23 PM

[amd64lover]

@veovis
did you mean to attach something? if so, it didnt get attached....

[amd64lover]

@geitonaki

i already installed Windows XP x64 from the cd to VMware (so i could ge the $WIN_NT$.~BT& $WIN_NT$.~LS folders) and it worked fine. I tried using the files from those folders (and copying them into the MW64 and PRO64 folders) and i also tried using the AMD64 & I386 folders from the cd (and copying them into the MW64 and PRO64 folders), but neither one of those worked. same 'Error loading operating system' meesage. i already have read up on that error and it looks like a bios issue. ill try it out on an actual PC (instead of vmware) and see how it works....

[amd64lover]

so i burned the iso image to a DVD and tried installing it on an actual PC and it didnt work. I got an 'A disk read error occured. Press Ctrl + Alt + Del to restart'.... not sure what the problem is or why the error is different. maybe something to do with the bios of the computer on which i am installing it (both are exactly the same). maybe VMware is inheriting the properties of my flawed bios. i read and read and it seems that all the solutions say something about enabling large access mode or LBA, but my motherboard bios doesnt have that option and neither does VMware... what to do now?

[Nakatomi2010]

Last time I got that "Press ctrl+alt+del" message was when I had something fowled up in my 32bit install....


I tell you what though.... But everything you guys have discovered into a single post for me to review and second or third thing I do when I get into work tomorrow will be to attempt to get 64-bit to work multi-boot... I meant to awhile back anyways, just got caught up in fine tuning my DVD....

So, please consolidate as much as you can into a single post for me.. Even files I may need... I've got a A64 system I use regularly as a guinea pig, hell I even use RAID drvers..

[amd64lover]

Well, youll need to read flyakite's guide, its pretty thorough. the link is http://flyakite.msfnhosting.com/ .... that will cover everything from adding windows 98 to server 2003 (non SP1) to a multiboot DVD. and here are a semi-modified version of geitonaki's instructions on how to add Windows XP x64 to that multiboot DVD...

OK so for 64 bit versions of windows we need to do probably these steps:

• Create "AIO-DVD\SETUP\XP64\"
• Copy the entire cd to the XP64 folder
• Create "AIO-DVD\MW64\"
• Create "AIO-DVD\PRO64\"
• Copy all files (or only those needed) from "AIO-DVD\SETUP\ XP64\I386\" to "AIO-DVD\MW64\"
• Copy all files (or only those needed) from "AIO-DVD\SETUP\XP64\AMD64\" to "AIO-DVD\PRO64\"
• Take the original setupldr.bin of win2003 32bit with no sp1, replace all instances of "I386" with "MW64", replace "\AMD64" with "\PRO64" and "AMD64\" with "PRO64\" and save it in "AIO-DVD\MW64\"
• Take the regular boot sector file, replace "I386" with "MW64" and save it as "MW64.BIN" in "AIO-DVD\"
• Copy "WIN51" and "WIN51AP" from "AIO-DVD\SETUP\XP64\" to "AIO-DVD\"
• Edit "AIO-DVD\PRO64\TXTSETUP.SIF" and change SetupSourcePath = "\" to SetupSourcePath = "\SETUP\XP64\"
• Now you can link the boot sector in your boot menu (like cdshell).

Let us know how it works for you.

[Alanoll]

@geitonaki

Here are the two dir listings you wanted. I did them on the EN6R and ENR64 folders, since they're for the 64bit OS Windows 2003 x64 Enterprise.

EN6R = I386 from the original CD, atleast in where it attains it's files (not sure where DISK101 and those came from yet) and the only file altered is SETUPLDR.BIN
ENR64 = AMD64 from the original CD, and the only file altered is TXTSETUP.SIF


I'm attaching the DIR listings, and RAR files of both the folders in question.

Attached File(s)

•  EN6R.txt (112bytes)
  Number of downloads: 20
•  ENR64.txt (2.1K)
  Number of downloads: 17
•  EN6R.rar (151.47K)
  Number of downloads: 15
•  ENR64.rar (5.86MB)
  Number of downloads: 15
•  EN6R_BOOTSECTOR.rar (1.06K)
  Number of downloads: 19

[geitonaki]

What the #$%@? Comparing setupldr.bin in EN6R.rar you posted with non SP1 of Windows Server 2003 32bit I have noticed that two instances of I386 have been replaced with EN64 while the other two with EN6R, which is the name of the folder. In root.txt you had posted earlier there isn't any folder EN64. This is I suppose a mistake of WinBeta's release. Comparing SETUPLDR64.BIN that you had posted earlier, all four instances of I386 are replaced with ST6R. Maybe after all this release doesn't work. If it works then the steps I have posted should be valid. If only my amd64 wasn't broken so I could try it myself...

[Nakatomi2010]

Alright, I've got Windows Server 2003 on my end, which version do I need, and how can I tell if it's pre-SP1...

I've got WS2K3 Standard, Enterprise, Datacenter, both VLM and OEM....

Edit: And Web Release, again both VLM and OEM...

Also, how many instances of AMD64 should I be expecting? The setupldr.bin file I have (Which may or may not be pre-sp1) has 27 reference to it...

This post has been edited by Nakatomi2010: 13 October 2005 - 08:28 AM

[Jazkal]

we are trying to get Win2k3 SP1 (any flavor) working in a multi-boot (x86 and x64) DVD enviroment.

[Nakatomi2010]

Jazkal, on Oct 13 2005, 10:23 AM, said:

we are trying to get Win2k3 SP1 (any flavor) working in a multi-boot (x86 and x64) DVD enviroment.

I'm trying to get x64 edition working using the method listed above...

[Nakatomi2010]

Using the technique you described on the previouis page using your instructions did nothing but a blinking cursor...

It's my belief that we technically need 2 BT directories, one to represent i386 and another to represent AMD64...

[Alanoll]

Nakatomi2010, on Oct 13 2005, 01:16 PM, said:

Using the technique you described on the previouis page using your instructions did nothing but a blinking cursor...

It's my belief that we technically need 2 BT directories, one to represent i386 and another to represent AMD64...

Umm...

All the files I posted last night a couple posts back, are for ONE OS, for teh 64bit version. So...umm...yeah...If you look, there are two seperate folders

[Nakatomi2010]

Figured as much.....

Is there any way to tell which files are ABSOLUTLY necesary for it to work? Because otherwise there needs to be a full I386 and AMD64 directory...

Is the BT we'd get this case the AMD64 directory, and we could just use the i386 directory as a place holder?

*Bare in mind in the creation of my AIO I use 3 BT's, one for complete unattended, with drivers and software, another for attended with software and drivers, and a fully vanilla attended version.. I'd try to do the same with X64*

That being said, say we created XP64 and threw in all of the i386 files into there, we could tell all the boot sectors to look at the same folder, but different AMD64 folders, which are the BT's in this case...

Or am I just totally confusing an otherwise simple to grasp subject...

[Alanoll]

I do believe I posted a DIRECTORY LISTING of the files found in the required boot folders... then edit TXTSETUP.SIF to look for the ROOT like in a normal AIO disc like before.

[Nakatomi2010]

Having the directory structure as...

AIO-DVD\MW64 (Wherein all i386 files ae copied)
AIO-DVD\PRO64 (Wherein all AMD64 files are copied) and using a

setupldr.bin from a Windows Server 2003 STD on my end I got into the setup and as far as formatting, but at that point it said it either couldn't see the drive, or some files were corupted...

This post has been edited by Nakatomi2010: 13 October 2005 - 02:32 PM

[Alanoll]

@Nakatomi2010
why are you copying all the files?

[amd64lover]

he probably copied all of them because he either didnt have access to the BT/LS folders, or didnt read the directory structure list... but that shouldnt be the reason why it isnt working. maybe it has do with the replacing of 27 'AMD64' in the setupldr.bin file. i dont remember replacing that many and i got as far as getting all the files copied and the cpu restarting before it stopped working...

[geitonaki]

@amd64lover
Please create two virtual pcs with vmware, at the one install windows from the original cd and at the other install from the cd you are playing with. Shutdown both the pcs after the first reboot (after the files have been copied). Then mount the virtual hard disk drives with vmware mount utility (available free from their site) and compare with beyond compare the files that have been copied.

Also try to change vmware bios->advanced->large disk access mode or create the partition you are installing with fdisk from a win98 bootable floppy and not with windows setup. These are the most common solutions to the problem 'Error loading operating system' you are having from what i had found.

@Alanoll
Have you tried installing any version of the cd you have?

[Alanoll]

I only have a 32bit processor, so i could only test those, and Windows Enterprise 2003 SP1 installed just fine