 Solution for multibooting Win XP/2k3 64-Bit, Win2k3 SP1, WinPE 2004, cracked setupldr.bin |
  |
 Oct 17 2005, 10:18 AM Post
#1 | |
| Newbie Group: Members Posts: 30 Joined: 17-September 05 Member No.: 73431   |
You can now modify setupldr.bin of the follwing windows:
"NTLDR is corrupt. The system cannot boot." In order to crack it:
File is now attached so people don't have to wait for a download ~ Alanoll Now you can replace:
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: CODE 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. This post has been edited by prathapml: Jan 28 2006, 03:31 PM Attached File(s) |
 |   |
| Oct 17 2005, 11:06 AM Post
#2 | |
| Member  Group: Members Posts: 154 Joined: 8-October 05 Member No.: 76070  |
GREAT JOB!!!... one quick thing, when i go to the cmd prompt and typed in the above command, it lists all the files, but it starts with 'H'... since there are so many, i dont know what files are needed that start with a letter before 'H'.... could you post a .txt file with the needed files? thanks
|
| | |
| Oct 17 2005, 11:24 AM Post
#3 | |
| Newbie Group: Members Posts: 30 Joined: 17-September 05 Member No.: 73431 |
You can save the output like below: CODE type TXTSETUP.SIF | findstr /r ",_[1-9] ,[1-9]_" > c:\out.txt |
| | |
| Oct 17 2005, 11:41 AM Post
#4 | |
| Senior Member Group: Members Posts: 564 Joined: 16-January 04 From: Texas Member No.: 12605 | QUOTE (geitonaki @ Oct 17 2005, 10:18 AM)  Do not replace all occurrences of "amd64" since some of them refer to a section of txtsetup.sif 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 "\") This post has been edited by Jazkal: Oct 17 2005, 11:42 AM |
| | |
| Oct 17 2005, 11:45 AM Post
#5 | |
| Member Group: Members Posts: 154 Joined: 8-October 05 Member No.: 76070 |
replace these, "\AMD64" & "AMD64\" & "\amd64" & "amd64\" (without the "" marks)
This post has been edited by amd64lover: Oct 17 2005, 11:47 AM |
| | |
| Oct 17 2005, 12:01 PM Post
#6 | |
| Advanced Member Group: Members Posts: 381 Joined: 28-June 05 Member No.: 62247 | CODE ksecdd.sys = 1,,,,,,_6,4,0,0,,1,4 ntdll.dll = 1,,,,,,_7,2,0,0,,1,2 kbdus.dll = 1,,,,,,_7,2,0,0,,1,2 drvmain.sdb = 1,,,,,,_3,60,0,0 kbddv.dll = 1,,,,,,_5,2,0,0,,1,2 kbdes.dll = 1,,,,,,_5,2,0,0,,1,2 kbdgae.dll = 1,,,,,,_5,2,0,0,,1,2 kbdgr1.dll = 1,,,,,,_5,2,0,0,,1,2 kbdit142.dll = 1,,,,,,_5,2,0,0,,1,2 kbdusl.dll = 1,,,,,,_5,2,0,0,,1,2 kbdusr.dll = 1,,,,,,_5,2,0,0,,1,2 kbdusx.dll = 1,,,,,,_5,2,0,0,,1,2 ntfs.sys = 1,,,,,,_6,4,0,0,,1,4 setupreg.hiv = 1,,,,,,_3,,3 spcmdcon.sys = 1,,,,,,_7,,3,3,,1,1 biosinfo.inf = 1,,,,,,_1,20,0,0,,1,1 wkbddv.dll=55,,,,,,_5,82,0,0,kbddv.dll,1,2 wkbdes.dll=55,,,,,,_5,82,0,0,kbdes.dll,1,2 wkbdgae.dll=55,,,,,,_5,82,0,0,kbdgae.dll,1,2 wkbdgr1.dll=55,,,,,,_5,82,0,0,kbdgr1.dll,1,2 wkbdit142.dll=55,,,,,,_5,82,0,0,kbdit142.dll,1,2 wkbdus.dll=55,,,,,,_7,82,0,0,kbdus.dll,1,2 wkbdusl.dll=55,,,,,,_5,82,0,0,kbdusl.dll,1,2 wkbdusr.dll=55,,,,,,_5,82,0,0,kbdusr.dll,1,2 wkbdusx.dll=55,,,,,,_5,82,0,0,kbdusx.dll,1,2 wntdll.dll=55,,,,,,_7,82,0,0,ntdll.dll,1,2 biosinfo.inf = 1,,,,,,_1,20,0,0,,1,1 ntdetect.com = 1,,,,,,_1,1,3,,,1,1 biosinfo.inf = 1,,,,,,_1,20,0,0,,1,1 wkbddv.dll=55,,,,,,_5,82,0,0,kbddv.dll,1,2 wkbdes.dll=55,,,,,,_5,82,0,0,kbdes.dll,1,2 wkbdgae.dll=55,,,,,,_5,82,0,0,kbdgae.dll,1,2 wkbdgr1.dll=55,,,,,,_5,82,0,0,kbdgr1.dll,1,2 wkbdit142.dll=55,,,,,,_5,82,0,0,kbdit142.dll,1,2 wkbdus.dll=55,,,,,,_7,82,0,0,kbdus.dll,1,2 wkbdusl.dll=55,,,,,,_5,82,0,0,kbdusl.dll,1,2 wkbdusr.dll=55,,,,,,_5,82,0,0,kbdusr.dll,1,2 wkbdusx.dll=55,,,,,,_5,82,0,0,kbdusx.dll,1,2 wntdll.dll=55,,,,,,_7,82,0,0,ntdll.dll,1,2 This is the output.... Though it doesn't say which filesgo into which directory... |
| | |
| Oct 17 2005, 12:21 PM Post
#7 | |
| Slowly Turning Green...  Group: Super Moderator Posts: 1256 Joined: 5-March 04 From: Quebec City Member No.: 15410 OS: none  |
I guess we can use GOSH's method to obtain our BOOT folder... I did that a while ago and I got the following files from $WIN_NT$.~BT CODE <DIR> system32 1394bus.sy_ acpi.sy_ acpiec.sy_ adpu160m.sy_ adpu320.sy_ aic78u2.sy_ aic78xx.sy_ aliide.sy_ amdide.sy_ arc.sy_ atapi.sy_ biosinfo.inf BOOTSECT.DAT bootvid.dl_ cdfs.sy_ cdrom.sy_ classpnp.sy_ cmdide.sy_ c_1252.nl_ c_437.nl_ dac960nt.sy_ disk.sy_ disk101 disk102 disk103 disk104 dmboot.sy_ dmio.sy_ dmload.sy_ dpti2o.sy_ drvmain.sdb fastfat.sy_ fdc.sy_ flpydisk.sy_ ftdisk.sy_ hal.dl_ hidclass.sy_ hidparse.sy_ hidusb.sy_ i2omgmt.sy_ i2omp.sy_ i8042prt.sy_ iirsp.sy_ intelide.sy_ isapnp.sy_ kbdclass.sy_ kbdhid.sy_ kbdus.dll kd1394.dl_ kdcom.dl_ ksecdd.sys l_intl.nl_ migrate.inf mountmgr.sy_ mraid35x.sy_ ntdetect.com ntfs.sys ntkrnlmp.ex_ ohci1394.sy_ oprghdlr.sy_ partmgr.sy_ pci.sy_ pciide.sy_ pciidex.sy_ pcmcia.sy_ ramdisk.sy_ sbp2port.sy_ scsiport.sy_ serenum.sy_ serial.sy_ setupdd.sy_ setupldr.bin setupreg.hiv sfloppy.sy_ spcmdcon.sys spddlang.sy_ storport.sy_ symc810.sy_ symc8xx.sy_ symmpi.sy_ sym_hi.sy_ sym_u3.sy_ toside.sy_ txtsetup.sif ultra.sy_ usbccgp.sy_ usbd.sy_ usbehci.sy_ usbhub.sy_ usbohci.sy_ usbport.sy_ usbstor.sy_ usbuhci.sy_ vga.sy_ vgaoem.fo_ viaide.sy_ videoprt.sy_ volsnap.sy_ watchdog.sy_ wd.sy_ winnt.sif wmilib.sy_ 102 File(s) 7,213,922 bytes This post has been edited by prathapml: Jan 28 2006, 03:22 PM |
| | |
| Oct 17 2005, 12:26 PM Post
#8 | |
| Newbie Group: Members Posts: 30 Joined: 17-September 05 Member No.: 73431 | QUOTE (Jazkal @ Oct 17 2005, 11:41 AM) QUOTE (geitonaki @ Oct 17 2005, 10:18 AM) Do not replace all occurrences of "amd64" since some of them refer to a section of txtsetup.sif 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! |
| | |
| Oct 17 2005, 12:34 PM Post
#9 | |
| Advanced Member Group: Members Posts: 381 Joined: 28-June 05 Member No.: 62247 | QUOTE (Incroyable HULK @ Oct 17 2005, 02:21 PM) I guess we can use GOSH's method to obtain our BOOT folder... I did that a while ago and I got the following files from $WIN_NT$.~BT QUOTE *snip* But which files go into which directory? We technically need 2 BT's now.... Don't we, or am I not grasping something...? This post has been edited by Nakatomi2010: Oct 17 2005, 12:34 PM |
| | |
| Oct 17 2005, 12:50 PM Post
#10 | |
| Newbie Group: Members Posts: 30 Joined: 17-September 05 Member No.: 73431 | QUOTE (Nakatomi2010 @ Oct 17 2005, 12:01 PM) This is the output.... Though it doesn't say which filesgo into which directory... 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. |
| | |
| Oct 17 2005, 12:54 PM Post
#11 | |
| Advanced Member Group: Members Posts: 381 Joined: 28-June 05 Member No.: 62247 |
How do I get the complete listing?
|
| | |
| Oct 17 2005, 01:07 PM Post
#12 | |
| Member Group: Members Posts: 154 Joined: 8-October 05 Member No.: 76070 |
go to a command prompt and navigate to the directory where the txtsetup.sif file is and copy/paste the following.... 'type TXTSETUP.SIF | findstr /r ",_[1-9] ,[1-9]_" > c:\out.txt' (geitonaki stated this on the first page)
|
| | |
| Oct 17 2005, 01:09 PM Post
#13 | |
| Advanced Member Group: Members Posts: 381 Joined: 28-June 05 Member No.: 62247 |
Nevermind, I must've typed it wrong the first time...
This post has been edited by Nakatomi2010: Oct 17 2005, 01:11 PM |
| | |
| Oct 17 2005, 01:09 PM Post
#14 | |
| Member Group: Members Posts: 154 Joined: 8-October 05 Member No.: 76070 |
open the file 'c:\out.txt'... itll have the complete list in there
|
| | |
| Oct 17 2005, 02:31 PM Post
#15 | |
| Advanced Member Group: Members Posts: 381 Joined: 28-June 05 Member No.: 62247 |
Well, hopefully this utterly and totally simplistic .bat file I made works... I basically put 'copy' infront of everything and '<Directory here> behind everything, changing MOST, but not all, os the last characters to _... I matched it against a BT I got from a previous install.... And the out.txt file I got... VERY simplistic batch file... This post has been edited by Nakatomi2010: Oct 17 2005, 02:37 PM |
| | |
| Oct 17 2005, 06:55 PM Post
#16 | |
| Newbie Group: Members Posts: 30 Joined: 17-September 05 Member No.: 73431 | QUOTE (geitonaki @ Oct 17 2005, 12:50 PM) 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/board/index.php?showtopic=58446 |
| | |
| Oct 18 2005, 01:49 PM Post
#17 | |
| Member Group: Members Posts: 154 Joined: 8-October 05 Member No.: 76070 |
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.
|
| | |
| Oct 18 2005, 08:24 PM Post
#18 | |
| Slowly Turning Green... Group: Super Moderator Posts: 1256 Joined: 5-March 04 From: Quebec City Member No.: 15410 OS: none | QUOTE (amd64lover @ Oct 18 2005, 01:49 PM) 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. How do you edit setupldr.bin in that case? Are you only replacing instances of I386? |
| | |
| Oct 18 2005, 08:29 PM Post
#19 | |
| Member Group: Members Posts: 154 Joined: 8-October 05 Member No.: 76070 |
i just used the same one i had edited earlier (which replaced the 'i386' with 'xp64' and 'amd64' with 'pro64').... it worked fine, i would say since there is no 'amd64' folder, just replacing the 'i386' should work fine.
|
| | |
 Oct 18 2005, 11:04 PM Post
#20 | |
| "You were the chosen one...." Group: Members Posts: 197 Joined: 20-October 04 From: Hawaii Member No.: 34301 |
OK, First I would like to say THANK YOU!!! I am now finally able to use my 2K3 Server (ENT/STD/WEB) SP1. The only problem is that I can’t get my “Unattended” install file to work with any of my windows installs. I used the XP distro install tools (too make winnt.sif files). It worked before, but after I used the boot folder creation tool (thanks Alanoll) it won’t work. Please someone help. |
| | |
|
1 User(s) are reading this topic (1 Guests and 0 Anonymous Users)
0 Members:
| Lo-Fi Version | Time is now: 21st November 2009 - 12:39 PM |
All trademarks mentioned on this page are the property of their respective owners
MSFN is not affiliated with Microsoft
Copyright © 2001-2009 msfn.org
Privacy Policy
MSFN is not affiliated with Microsoft
Copyright © 2001-2009 msfn.org
Privacy Policy