geitonaki

Recovery console works normally with the cracked setupldr.bin. I have used it many times. Something else must be the cause of your problem.

You need to modify all BTS scripts that use the directory OEM. (e.g. in I386\PRESETUP.CMD change OEM to anything you want)

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

yes

http://www.msfn.org/board/index.php?showtopic=58446

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.

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:"

Check this: http://www.msfn.org/board/index.php?showtopic=58446 it automatically creates the boot folders

I have uploaded a new version, check it out and post how it worked for you, the syntax is now: Usage: create_boot_folder setup_dir aio_dir boot_dir1 boot_dir2 flag_for_using_cracked_setupldr You have to open create_boot_folders.cmd with notepad, modify the included examples and then run it by double clicking the file

Make sure you are running create_boot_folders.cmd and not create_boot_folder.cmd Also read carefully the included help.

Having 150kb limit for each post how could I uploaded here? My only option was to upload to rapidshare.de

No it won't. As I said it works for any version of Windows 2000, XP, 2003

Download the self extracting rar file in the first post, execute it and it will ask where to install. Browse to your AIO-DVD folder. When finished it will create #TOOLS in there, open create_boot_folders.cmd which calls create_boot_folder.cmd, modify it in your needs and execute it. It will create the boot folders, modify setupldr.bin, modify txtsetup.sif, create the boot sector and copy the tag files. Everything described in http://flyakite.msfnhosting.com/ for Windows 2000/XP/2003 is made automatically B). Doesn't this topic deserve to be sticky ? @amd64lover please give us feedback for 64bit version of windows since I don't have an amd64 to test, but I am pretty sure that everything should be fine.

http://www.msfn.org/board/index.php?showtopic=58446

Edit: New version. You can automatically create the multi-boot folders and files using my batch file for any version of Windows 2000, XP, 2003. Everything needed is included in the file I have uploaded. File attached so people don't need to wait for RapidShare's download ticket ~ Alanoll Here I will post only the main batch file: create_boot_folder.cmd @echo off if [%1] == [] goto :usage if [%2] == [] goto :usage if [%3] == [] goto :usage if [%4] == [] goto :usage if [%5] == [] goto :usage if not [%6] == [] goto :usage if not exist "%~f1" ( echo Directory "%~f1" does not exist. goto :usage ) if not exist "%~f2" ( echo Directory "%~f2" does not exist. goto :usage ) if exist "%~f2\%3" ( echo "%~f2\%3" already exists so nothing to do, please delete it manually goto :end ) set pth=%~f1 set aio=%~f2 call set pth=%%pth:%aio%=%% if "%pth%" == "%~f1" ( echo "%~f1" must be under "%~f2". goto :end ) if exist "%1\I386\TXTSETUP.SIF" ( set src_dir=%1\I386 set dest_dir=%2\%3 set archit=I386 ) else if exist "%1\AMD64\TXTSETUP.SIF" ( set src_dir=%1\AMD64 set dest_dir=%2\%4 set archit=AMD64 ) else ( echo Cannot find TXTSETUP.SIF in I386 or AMD64 in %1 ) type "%src_dir%\TXTSETUP.SIF" | findstr /r ",_[1-9] ,[1-9]_" | sed -e s/"=.*"/""/g -e s/" .*"/""/g > out.txt type out.txt | sed -e s/".$"/"_"/g > out_.txt mkdir "%dest_dir%" for /f %%i in ('type out.txt') do copy "%src_dir%\%%i" "%dest_dir%" > nul 2>&1 for /f %%i in ('type out_.txt') do copy "%src_dir%\%%i" "%dest_dir%" > nul 2>&1 copy "%src_dir%\BOOTFONT.BIN" "%dest_dir%" > nul 2>&1 copy "%src_dir%\BOOTFONT.BIN" "%2" > nul 2>&1 mkdir "%dest_dir%\SYSTEM32" copy "%src_dir%\system32\*.*" "%dest_dir%\SYSTEM32" > nul 2>&1 set pth=%pth:\=\\% type "%src_dir%\TXTSETUP.SIF" | sed -e s/"SetupSourcePath = \""/"SetupSourcePath = \"%pth%"/g > "%dest_dir%\TXTSETUP.SIF" unix2dos "%dest_dir%\TXTSETUP.SIF" del "%dest_dir%\NTDLL.DLL" > nul 2>&1 if "%archit%" == "AMD64" ( mkdir "%2\%3" copy "%1\I386\NTDETECT.COM" "%2\%3" > nul 2>&1 ) if "%5" == "1" ( copy SETUPLDR.BIN "%2\%3" > nul 2>&1 ) else ( copy "%1\I386\SETUPLDR.BIN" "%2\%3" > nul 2>&1 ) start /w xvi32.exe "%2\%3\SETUPLDR.BIN" /S=replaceI386.xsc "%3" if "%archit%" == "AMD64" ( start /w xvi32.exe "%2\%3\SETUPLDR.BIN" /S=replaceAMD64.xsc "%4" ) copy BOOT.BIN "%2\%3.bin" > nul 2>&1 start /w xvi32.exe "%2\%3.bin" /S=universalrepl.xsc "I386" "%3" del OUT.txt > nul 2>&1 del OUT_.txt > nul 2>&1 copy "%1\CDROM*.*" "%2"\ > nul 2>&1 copy "%1\WIN51*.*" "%2"\ > nul 2>&1 goto :end :usage echo Usage: %~n0 setup_dir aio_dir boot_dir1 boot_dir2 flag_for_using_cracked_setupldr goto :end :end Edit: New version so that you don't need to subst your aio-dvd dir anymore. File attached ~ Alanoll Create_MultiBoot_Folders_And_Files.zip

The outpout you posted isn't complete. Each file goes to the respective directory from where you will find it. If you find it in I386 then copy it to ABCD, if you find it in AMD64 copy it to EFGHI. 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.

Can someone tell me how to determine which one is which? Or is it just the standalone "amd64" entries that reference the txtsetup.sif? (meaning no preceeding or trailing "\") Exactly what you said!

You can save the output like below: type TXTSETUP.SIF | findstr /r ",_[1-9] ,[1-9]_" > c:\out.txt

I started a new topic: http://www.msfn.org/board/index.php?showtopic=58410 Please reply there. I believe this topic should be unsticked and make the new one sticky. No reason for anyone to read these 18 pages. After all I deserve some glory

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. cracked_SETUPLDR_1_.BIN.zip

Great News !! I've just cracked the new setupldr.bin which has checksum error! So now you can modify it like the old one. Only 2 bytes need to be changed. If the admins let me, I will post here tomorrow the way to do it.

@amd64lover The different files you posted are the pagefile and the system registry, so setupldr.bin from windows 2003 32bit non SP1 works just fine for copying the files to disk. Where seems to be the problem is the partition, the boot record, or the master boot record. I wonder if "fdisk /mbr" from win98 boot disk or "fixmbr", "fixboot" from recovery console could fix the error. @anyone having 64bit processor Please try to download the iso file I have uploaded (it's 6.5 MB) and test if we can use setupldr.bin from windows 2003 32bit non SP1. I made it so that anyone can easily try if it works. http://rapidshare.de/files/6338464/Windows...t_.iso.rar.html readme.txt: Using UltraISO or any other similar program: insert your entire cd of Windows XP Professional x64 Edition to SETUP\XP_PRO_X64 or/and insert your entire cd of Windows Server 2003 Enterprise x64 Edition to SETUP\2003_ENT_X64 save it and test if either of them can install successfully under vmware 5.5 or real pc. Please let us know if it worked.

@amd64lover Please create two virtual pcs with vmware, at the one install windows from the original cd and at the other install from the cd you are playing with. Shutdown both the pcs after the first reboot (after the files have been copied). Then mount the virtual hard disk drives with vmware mount utility (available free from their site) and compare with beyond compare the files that have been copied. Also try to change vmware bios->advanced->large disk access mode or create the partition you are installing with fdisk from a win98 bootable floppy and not with windows setup. These are the most common solutions to the problem 'Error loading operating system' you are having from what i had found. @Alanoll Have you tried installing any version of the cd you have?

What the #$%@? Comparing setupldr.bin in EN6R.rar you posted with non SP1 of Windows Server 2003 32bit I have noticed that two instances of I386 have been replaced with EN64 while the other two with EN6R, which is the name of the folder. In root.txt you had posted earlier there isn't any folder EN64. This is I suppose a mistake of WinBeta's release. Comparing SETUPLDR64.BIN that you had posted earlier, all four instances of I386 are replaced with ST6R. Maybe after all this release doesn't work. If it works then the steps I have posted should be valid. If only my amd64 wasn't broken so I could try it myself...

@amd64lover Here is the SETUPLDR.BIN of Windows 2003 non SP1. But I believe this is the same with your's, since you didn't get the corrupt file error which you would have had if you have modified the SETUPLDR.BIN of SP1. The error you are having I don't believe is related with SETUPLDR.BIN. See the results of google search: http://www.google.com/search?q=%22Error+lo...stem%22+windows Try delete the VMware PC and make a new one trying SCSI or IDE HDD. Also please try it with your original cd of Windows x64.