[Incroyable HULK]

Jazkal, on Aug 8 2005, 06:47 PM, said:

N30M0D, on Aug 8 2005, 06:17 PM, said:

for win 2003 sp1 should i replace 7 occurences (five i386 and two I386) or only i386 occurences?
<{POST_SNAPBACK}>

I replaced all 7, if it was a lowercase "i", then I replaced it with LC, and if it was uppercase, I replaced it with UC. Didn't test if it was really required or not.
<{POST_SNAPBACK}>

Same thing for me...

[TheTruth]

Hello Guys,

@Incroyable HULK
Thanks

@evilvoice
Hello friend , missing you.

@Jazkal
Try to reverse the last 3 chars of AMD64 not the firsr ones, and let me know about your results as I'm unable to test.

Anyway, I'll keep an eye on this thread looking for a better solution form a smarter one.

Best regards,
TheTruth
http://www.geocities.com/pierremounir/

[Jazkal]

TheTruth, on Aug 10 2005, 11:10 AM, said:

@Jazkal
Try to  reverse the last 3 chars of AMD64 not the firsr ones, and let me know about your results as I'm unable to test.

Tried that, didn't work. Same results.

[TheTruth]

@Jazkal
What about reversing 4 chars.

Also, make sure you don't replace "Architecture" entry in txtsetup.sif
I mean replace all ocurrences except in "Architecture" and "Drivers Cache" if exist.

This post has been edited by TheTruth: 10 August 2005 - 11:44 AM

[Jazkal]

changing the entries in txtsetup.sif, didn't seem to matter at all.

When I tried the 4-swap to 6dma4, I recieved the old:

"NTLDR is corupt. The system cannot boot."

[TheTruth]

Oh, bad . Anyway, we're sure that reversing 3 consecutive chars is the right rule.
Are you sure you won't get the error msg of ntkrnlos.exe if you don't make any changes?

anyhow, just let's wait.

[Jazkal]

TheTruth, on Aug 10 2005, 12:22 PM, said:

Are you sure you won't get the error msg of ntkrnlos.exe if you don't make any changes?

Yes, I tested it with and without the changes in the txtsetup.sif file, with the same results.

I have a nice stack of coasters.

I sure wish vmware would come out with a version that supported x64 clients

[TheTruth]

Okay man, that's enough for today.
Thanks for your time.

TheTruth

[Jito463]

You can still test with VMWare, because if it gets to a point where it loads ntldr it will just say that your hardware doesn't support this OS. Otherwise it just gives the current message we're all getting.

[Ausmith1]

The VMware v5.5 beta allows for 64 bit VM clients.

[Historic]

Ok, I too am looking for a real solution to this problem.

Here are some tools to help
Binary File comparer (checks for same file size and stops at first diffrence) Very useful to confirn if both of setldr.bin are same or different.
http://www.trombettw...ileComparer.zip

16/32 bit disassembler
ftp://ftp.sac.sk/pub...og/qdasm100.zip

Edit:
Q: If I wanted to create a 3 in 1 for Server 2003, ent/std/web, Sp1
can I use the original setupldr.bin and replace all 7 occurances with these folder names??

1. I386/I386 -- Enterprise; no change in setupldr.bin, change path setupsourcepath=\I386\
2. I683/I386 -- Standard; change setupldr to I683, change path to \I683\
3. 83I6/I386 -- Web; change setupldr to 83I6, change path to \83I6\

and follow multi-boot dvd tutorial. Or do I need to do anything else?

This post has been edited by Historic: 30 August 2005 - 04:24 AM

[Historic]

Ok, people, test this.

Quote

Deleted

Edit: My mistake, seems I got all of my setupldr files mixed up. This look like the same as the one from without sevice pack.

This post has been edited by Historic: 06 September 2005 - 01:57 AM

[geek42]

I was wondering something:

Over at Tom's Hardware there is a article about putting BartPE on a USB stick.

The linked page above discusses using the 2K3 SP1 setupldr.bin file along with ramdisk.sys.

Now from my understanding, the older bootloaders used the "emulate floppy" mode to load the kernel and then go into the install, but recently they ran into size issues with the 1.44 meg limitation for floppys, even most emulated ones(I know about 2.88...). I have this sneaking feeling that the major change in the boot process is to start using an initial ram disk for the startup.

So, could we maybe get this working with a modification of the ramdisk.sys method?

Just some ideas, I've yet to really try getting this to work, and have much to learn about how this all works.

Anyway...

JC

[qzmicro]

geek42, on Sep 10 2005, 07:10 PM, said:

I was wondering something:

Over at Tom's Hardware there is a article about putting BartPE on a USB stick.

The linked page above discusses using the 2K3 SP1 setupldr.bin file along with ramdisk.sys.

Now from my understanding, the older bootloaders used the "emulate floppy" mode to load the kernel and then go into the install, but recently they ran into size issues with the 1.44 meg limitation for floppys, even most emulated ones(I know about 2.88...). I have this sneaking feeling that the major change in the boot process is to start using an initial ram disk for the startup.

So, could we maybe get this working with a modification of the ramdisk.sys method?

Just some ideas, I've yet to really try getting this to work, and have much to learn about how this all works.

Anyway...

JC
<{POST_SNAPBACK}>

Sounds pheasable but I sure don't know enough to test on my own. I'm willing to help if anyone has any suggestions though.

Qz

[Jazkal]

it was probably deleted because it is a "warez" release, and as such, is always deleted.

This post has been edited by Jazkal: 18 September 2005 - 07:55 PM

[geitonaki]

Posting this for 3rd time since my previous posts were deleted.

Posting that WinBeta has found a solution to the problem you are discussing and just giving the link to their nfo for their release at their site violates the forum rules?

The rule says: "Links/Requests to warez and/or illegal material (porn, cracks, serials, etc..) will not be tolerated."

I hope that only the link to their nfo was the problem and that this post will not be deleted as it hasn't any link now.

So WinBeta has managed to put in one dvd various versions of Win XP x64, Win 2003 x64, Win 2003 32bit SP1. Anyone who can find how they have done it please tells us so we can do it in our copies of windows.

P.S. Sorry I just saw that the nfo contains serials.

[Alanoll]

Quote

P.S. Sorry  I just saw that the nfo contains serials.

That would be the primary reason I personally deleted your posts.

[thegafferazzasatz]

can somebody post the nfo on the forum so we can see what oses are on the disc (assume that it is dvd) and what versions etc. and dont forget get rid of the serials off it lollol

[geitonaki]

thegafferazzasatz, on Sep 19 2005, 10:33 AM, said:

can somebody post the nfo on the forum so we can see what oses are on the disc (assume that it is dvd) and what versions etc. and dont forget get rid of the serials off it lollol
<{POST_SNAPBACK}>

 | | |Win XP   x64 retail                    | | | |
 | | |Win XP   x64 vol -                      | | | |
 | | |Win 2003 x64 std srv retail -         | | | |
 | | |Win 2003 x64 std srv vol -          | | | |
 | | |Win 2003 x64 ent srv retail -         | | | |
 | | |Win 2003 x64 ent srv vol -               | | | |
 | | |Win 2003 32Bit ent srv retail -         | | | |
 | | |Win 2003 32Bit ent srv vol -            | | | |
 | | |Win 2003 32bit std srv retail -          | | | |
 | | |Win 2003 32bit std srv vol -           | | | |
 | | |Win 2003 32bit web srv retail -         | | | |
 | | |Win 2003 32bit web srv vol -             | | | |

[Alanoll]

Please don't post the NFO again...