[evilvoice]

no, i mean overwrite mode or insert more...using hexeditors, there are 2 methods for adding...in insert if it says i386, you put the cursor on the i and type 3, it says 3i386...in overwrite mode it says 3386.

[Incroyable HULK]

Oh, I am always using EasyBoot to replace... so simple!

[evilvoice]

hmmm, i trust your instincts...but I would use a hex editor to do this...if it were me...there are free ones out there that work wonders...hhdsoftware has a great one that I use...never caused problems...I just dont see how some combos work and others dont...especially if your keeping the same characters and only 4 of them...just seems weird to me.

[Incroyable HULK]

Well, I've been using this method for almost a year now... never had any problem. The reason why only thoses 2 combination works is because they don't break the CRC check as mentionned by TheTruth...

[evilvoice]

oh wow, TheTruth is here too...well HELLO TheTruth ltns.

[Jito463]

@Hulk
Did you test this with XP Pro x64 or with Server 2k3 SP1? I ask because I tried various combinations (including those two you said were the only ones you got to work) and still got the ntldr is corrupt message. I may need to try copying the AMD64 directory to the root of the drive. Have to wait and see.

[Incroyable HULK]

Only with Windows 2003 Server SP1...

[Jazkal]

I ran my tests using WinPE, trying to make a multi-boot CD with the following:

WinPE x86
WinPE x64
BartPE w\ XPE x86

I used the only two allowed renamed folders of i683 and 83i6 for the x86 versions. Both of these worked great, no problems at all.

On the x64 version however, I renamed AMD64 to DMA64 and I didn't see the corupt NTLDR error message (which in and of itself looks promising). But I did get this error message on boot:

"The entry "ntoskrnl.exe" in the [SourceDisksFiles] section of the INF file is corrupt or missing.

Setup cannot continue. Press any key to exit."

I tried editing the txtsetup.sif file in the dma64 folder, changing the "\amd64" entries under the [SourceDisksNames.amd64] section to "\dma64". But that didn't work.

[N30M0D]

for win 2003 sp1 should i replace 7 occurences (five i386 and two I386) or only i386 occurences?

This post has been edited by N30M0D: 08 August 2005 - 06:18 PM

[Jazkal]

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.

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