Jump to content

Multiboot WinXP 64-Bits & 2003 Server SP1


Recommended Posts


Does cheating count? Because if it does then I found a bastardized way to add it to the multiboot DVD... It was an EXTREMELY simple solution and appears to work so far, tthough it is very much limited in how it operates... BUT, assuming it works, scripters out there might be able to do something....

But, if cheating doesn't count.....

So far its copying files to the hard drive without any problems....

Edit: Reached the GUI stage of the install....

Alright, it looks like its going to be a success on the install, so I'm giong to say what I did...

Just remember, it's cheating, but it seems to have worked.....

Extract the boot sector, and rename it to whatever it needs to be, in my case, x64.dat, don't bother hex editing it, remember, we're cheating....

Have nlite make the modifications you want to your CD so it'll install how you want it to, then copy everything, minus the usual setup.exe, autorun.inf, etc etc to the root of you AIO-DVD/CD your directory structure will be....

D:\AIO-DVD\AMD64\

D:\AIO-DVD\I386\

D:\AIO-DVD\XPHO\

D:\AIO-DVD\BLAH\

D:\AIO-DVD\ETC, ETC\

And there you go.... Now tell what ever program you use to script the install to use X64.dat, and it'll initiate the setup from the root....

Obviously this is useless to people who want to have unattended and attended install versions (Like me), BUT it's a start to get us to get X64 Edition ONTO the DVD....

It's currently installing my software sute on my end, so I'm going to call this a mild success and a half-assed work around....

Final Edit: It worked, the system is now running X64 edition run from an AIO-DVD, obviously it was to be expected, but its a start... A very, very small one....

Edited by Nakatomi2010
Link to comment
Share on other sites

I'd already considered that and as a quick and dirty method it would work. But it doesn't answer the real question of this post which is how to integrate it truly on a multi-boot disc.

Link to comment
Share on other sites

I'd already considered that and as a quick and dirty method it would work.  But it doesn't answer the real question of this post which is how to integrate it truly on a multi-boot disc.

I know, if anything all I've done is proven that it can be done, so it's not impossible, but at the same time, as a temporary work around, and assuming you're not doing more than one 64-bit OS, then you're all good....

Link to comment
Share on other sites

Well, that's not entirely true. All you've essentially done is added a multi-boot DVD to your x64 CD. You've not really added the x64 CD to your multi-boot DVD as we're trying to figure out here. I understand you're trying to help, and that's great. We need all the help we can get. But at the same time we need to keep our focus on the ultimate goal of this project.

Link to comment
Share on other sites

SETUPLDR.BIN is from two parts. I test "boot" part (first 20080 B in SP1) with SETUPLDR.EXE from SP1 directory and with SETUPLDR.EXE from W2K3 RTM. It always work, but only with unmodified exe file = "boot" check EXE CRC.

SETUPLDR.EXE from SP1 has same size as SETUPLDR.EXE linked to SETUPLDR.BIN (starting byte 20081h)

BUT: same code, but only debug text is different!!

Comparing files setupldr.exe and SETUPLDR_LOADER.EXE

00000120: 50 26 <- CRC?

00000121: 7F 63 <- CRC?

00039210: 25 50 <- ???

0003EEE5: 00 65 e

0003EEE6: 00 5C \

0003EEE7: 00 62 b

0003EEE8: 00 6F o

0003EEE9: 00 6F o

0003EEEA: 00 74 t

0003EEEB: 00 5C \

0003EEEC: 00 73 s

0003EEED: 00 65 e

0003EEEE: 00 74 t

0003EEEF: 00 75 u

0003EEF0: 00 70 p

0003EEF1: 00 5C \

0003EEF2: 00 64 d

0003EEF3: 00 61 a

0003EEF4: 00 79 y

0003EEF5: 00 74 t

0003EEF6: 00 6F o

0003EEF7: 00 6E n

0003EEF8: 00 61 a

0003EEF9: 00 5C \

0003EEFA: 00 6F o

0003EEFB: 00 62 b

0003EEFC: 00 6A j

0003EEFD: 00 5C \

0003EEFE: 00 69 i

0003EEFF: 00 33 3

0003EF00: 00 38 8

0003EF01: 00 36 6

0003EF02: 00 5C \

0003EF03: 00 73 s

0003EF04: 00 65 e

0003EF05: 00 74 t

0003EF06: 00 75 u

0003EF07: 00 70 p

0003EF08: 00 6C l

0003EF09: 00 64 d

0003EF0A: 00 72 r

0003EF0B: 00 2E .

0003EF0C: 00 70 p

0003EF0D: 00 64 d

0003EF0E: 00 62 b

"e\boot\setup\daytona\obj\i386\setupldr.pdb"

same in RTM version of SETUPLDR.EXE / SETUPLDR.BIN exe part

00000128: 42 8E

00000129: BA FF

0000012A: 04 03

00034A10: 25 52

0003ACD1: 00 61

0003ACD2: 00 73

0003ACD3: 00 65

0003ACD4: 00 5C

.....

Link to comment
Share on other sites

Hello Guys,

Actually, I came here while I was searching for a solution (in fact, a more flexible or generic solution) to the problem in regard than the one I have.

But I found out that you're still looking for one, so here is my simple solution.

I f you wanna replace any combination of characters like "i386" with another, the only available replacements (that won't cause the corrupt error) will be the same combination of chars but in a different order, e.g.:

i386 --> i683

or

i386 --> 83i6

You should notice that reording any combination arbitrarly won't work, that is, to form the new replacement combination, you should take any 3 consecutive chars and reverse them as in the examples above, you should notice that I reversed the order of the last 3 chars in the first example and reversed the order of the first 3 chars in the second example.

You should take into account that I tested this solution by editing setupldr.bin of Win2K3 with SP1 to add support for multiple answer files under the "i386" folder as described in this thread. You should test it yourself by editing setupldr.bin in different ways.

Of course, this way of forming the new replacement will limit the number of availble replacements but they are enough in most cases, so I hope anyone can come up with a more flexible idea (based on computed CRC for example).

Best regrads,

TheTruth

http://www.geocities.com/pierremounir/

Edited by TheTruth
Link to comment
Share on other sites

I think he means it either needs to begin with an I or end with a 6, but so long as that condition is met you can rearrange the rest in whatever order you like. So theoretically, the following should all work (need to test though):

i386

i368

i683

i638

i836

i863

38i6

3i86

8i36

83i6

So far as I can tell, based on what he described above, those should all work.

Link to comment
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
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...