[Incroyable HULK]

amd64lover, on Oct 26 2005, 08:55 PM, said:

always the simple solutions.....

I guess you already had the WIN51IP file (from another Windows) at your root so this is why you didn't get this issue...

Anyway, I still have a few problems:
1- I noticed my drivers didn't get uncompressed at the beginning of the GUI part (T-39)
2- I had to manually click next

3- setup get stuck somewhere at T-33 or T-37 stage...

I'll try with a "simpler" winnt.sif file tomorow

This post has been edited by Incroyable HULK: 26 October 2005 - 09:06 PM

[Incroyable HULK]

Ok, nevermind, I had the time to try with a simple winnt.sif file and I am at stage T-24 without a hitch now...

Are you guys able to decompress your drivers at stage T-39 with a 7zip SFX archive like:

Quote

[GuiUnattended]DetachedProgram="%systemdrive%\DP.exe"
Arguments="-y /q /r:n"

[matt121]

geitonaki, on Oct 18 2005, 03:18 AM, said:

You can now modify setupldr.bin of the follwing windows:

• Windows Server 2003 SP1
  
  
• Windows XP Professional x64 Edition
  
  
• Windows Server 2003 x64 Edition
  
  
• Windows PE 2005

The setupldr.bin of the above versions is the same and has a checksum check built-in so when you try to modify it you get:
"NTLDR is corrupt. The system cannot boot."

In order to crack it:

• open it with your favorite hex editor
  
  
• goto hex address: 0x2060
  
  
• change "74 03" to "EB 1A"
  
  
• save it

I also uploaded it for your convenience at:
File is now attached so people don't have to wait for a download ~ Alanoll

Now you can replace:

• all occurrences of "i386", "I386" to "ABCD" (where ABCD is anything you want - 4 characters long)
  
  
• "\amd64", "\AMD64" to "\EFGHI" and
  
  
• "amd64\", "AMD64\" to "EFGHI\" (where EFGHI is anything you want - 5 characters long)

Do not replace all occurrences of "amd64" since some of them refer to a section of txtsetup.sif

In order to find what files need to be copied to the directories ABCD and EFGHI open command prompt, go to the directory you have txtsetup.sif and enter:

type TXTSETUP.SIF | findstr /r ",_[1-9] ,[1-9]_"

and copy the files listed there from I386 to ABCD and AMD64 to EFGHI.

For anyone curious, open the setupldr.bin with hiew, goto the above hex address and see the surrounding assembly code.

To which folder are you modding the setupldr.bin in?

Is it the one in I386 folder or the front boot folders on the Multiboot DVD?

[Incroyable HULK]

front

[r3loaded]

amd64lover, on Oct 18 2005, 07:49 PM, said:

again, your solution work great. i also found that the 'XP64' and 'PRO64' are not necessary. Just take the boot folder ($WIN_NT$.~BT) and rename it to something else (i did mine to XP64) and then edit the setupldr.bin file & replace all instances of "I386" with "XP64", then edit the boot image to show XP64 instead of i386. this is a way to have 1 less folder in your root. i have the x64 boot folder if anyone needs it.

Ok, I've got that bit. The only problem is that I'm on a 32 bit system and my 64 bit laptop isn't coming for a couple of weeks. I therefore can't get the boot folder as setup won't even start. Anyone got a boot folder I can borrow? plz?

[geitonaki]

r3loaded, on Jan 3 2006, 04:41 PM, said:

Anyone got a boot folder I can borrow? plz?

Check this:
http://www.msfn.org/...showtopic=58446

it automatically creates the boot folders

[Jito463]

I stopped coming by for a while after the last time when we couldn't figure this out. I'm glad to see someone finally did get it working. Tested it at work with x64 and the preinstall worked without a hitch. Now we just need to figure out how to add Vista to the multi-boot DVDs.

@geitonaki
One thing I feel should be pointed out is that you don't need the AMD64 directory for x64. Just the $WIN_NT$.~BT folder that's created when you run the setup from within Windows as Incroyable Hulk posted earlier. You should update your batch files accordingly.

This post has been edited by Jito463: 18 January 2006 - 08:38 PM

[geitonaki]

Jito463, on Jan 18 2006, 08:07 PM, said:

@geitonaki
One thing I feel should be pointed out is that you don't need the AMD64 directory for x64. Just the $WIN_NT$.~BT folder that's created when you run the setup from within Windows as Incroyable Hulk posted earlier. You should update your batch files accordingly.

Having the AMD64 directory and trying to install to a 32bit processor you get the following message:
"Attempting to load an x64 operating system, however this CPU is not compatible with x64 mode. Please install a 32-bit X86 operating system."
Without the AMD64 directory you will get:
"Please insert the disk labeled Windows blah blah x64 Edition CD-ROM into drive A:"

[Jito463]

Well, either way, it won't work.

[geitonaki]

Yes it won't work but at least it tells you what's wrong
This is the reason that it is better to have two boot folders. But if you don't mind you can merge them into one.

[selanec555]

geitonaki, on Oct 17 2005, 12:50 PM, said:

Nakatomi2010, on Oct 17 2005, 12:01 PM, said:

This is the output.... Though it doesn't say which filesgo into which directory...

I will post later if I have time a batch file that I have created which automatically creates the boot folders and modifies the necessary files.

send me please your batch file.

[geitonaki]

geitonaki, on Oct 17 2005, 06:55 PM, said:

geitonaki, on Oct 17 2005, 12:50 PM, said:

I will post later if I have time a batch file that I have created which automatically creates the boot folders and modifies the necessary files.

http://www.msfn.org/...showtopic=58446

[Angelico_Payne]

I'm glad you figured out the procedure for x64 windows, all your hard work is appreciated

[a.kooning]

When i use setupmgr.exe (by step 2 in unattended windows cd) there happended nothing.
I dont now what i do wrong??

Ho an help me??

a.kooning@hccnet.nl

[blacks]

good

[neo_01]

Need this crack to 2003 R2 ?

[geitonaki]

neo_01, on Apr 3 2006, 10:00 AM, said:

Need this crack to 2003 R2 ?

Yes, 2003 R2 is 2003 SP1 plus some extras on a second cd. (First cd is exactly the same with 2003 SP1)

[Angelico_Payne]

amd64lover, on Oct 18 2005, 11:20 PM, said:

the winnt.sif file needs to be both in the boot folder and in the actual i386 folder. if there is already a winnt.sif file in the boot folder, overwrite it with the one you made.

This is acctualy not true, I have mine placed in boot folder only (in my case PRO1)

Also I went to crack my setupldr.bin, and found no reference as to hex code suggested here, I just renamed i386 to PRO1 or PRO[any numer or letter] and it works, could it be possible that we dont have same setupldr.bin, i use WinXP pro SP2 corp edition.

Incroyable HULK, on Oct 26 2005, 08:50 PM, said:

You won't beleive this! I took a ride into the txtsetup.sif file and I found this:

name = "Windows XP Professional x64 Edition CD-ROM"
productname = "Windows XP Professional x64 Edition"


bootname1 = "Windows XP Professional Setup Boot Disk"
bootname2 = "Windows XP Professional Setup Disk #2"
bootname3 = "Windows XP Professional Setup Disk #3"
bootname4 = "Windows XP Professional Setup Disk #4"
bootname5 = "Windows XP Professional Setup Disk #5"
bootname6 = "Windows XP Professional Setup Disk #6"
bootname7 = "Windows XP Professional Setup Disk #7"



cdtagfile = "\win51ap"

cdtagfilei = "\win51ip"

cdtagfilem = "\win51mp"

cdtagfilea = "\win51ap"


So I added a dumb WIN51IP and WIN51MP file at the root of the CD and inside \SETUP\XP64\ folder and guess what?

IT'S WORKING! My WMware simulation is going on... the only thing is that I had to press next after the first reboot (at the GUI) ... I'll keep you updated, it's still running

So how can i remove thoose files from the root,
i try the suggestion of one user here to edit txtsetup.sif, nad change path, but it gives me the same error just like when they are not placed in the root..?

[overdream]

Helo, help me.
After having to carry out this handling and to have same use the cracked_SETUPLDR_1_.BIN.zip.
I obtain “Ntkrnlmp.exe Could Not Be Loaded. The Error Codes Is 4”.
what do I have to make?

[chris9999]

Does anyone know why the Multi-Boot DVD introduction link appears to be broken?

http://flyakite.msfnhosting.com/ has been down for a couple of days

Is it hosted anywhere else?