always the simple solutions.....

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

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:

1. open it with your favorite hex editor
   
2. goto hex address: 0x2060
   
3. change "74 03" to "EB 1A"
   
4. 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:

1. all occurrences of "i386", "I386" to "ABCD" (where ABCD is anything you want - 4 characters long)
   
2. "\amd64", "\AMD64" to "\EFGHI" and
   
3. "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:

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.

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.

Anyone got a boot folder I can borrow? plz?

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

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.

Need this crack to 2003 R2 ?

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.

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