Jito463 Posted June 24, 2005 Share Posted June 24, 2005 Well, I did figure something out. I copied ntldr from the actual i386 directory to the boot directory (1OPX on my disc). It got past the ntldr is corrupt message, but stopped with a NTDETECT failed error. That's a start anyway. Link to comment Share on other sites More sharing options...
Incroyable HULK Posted June 27, 2005 Author Share Posted June 27, 2005 (edited) Well, I did figure something out. I copied ntldr from the actual i386 directory to the boot directory (1OPX on my disc). It got past the ntldr is corrupt message, but stopped with a NTDETECT failed error. That's a start anyway.This observation bring in a 3rd possibility to the equation... maybe the setupldr.bin file isn't the cause of the problem, an other file may be responsible for that... Edited June 27, 2005 by Incroyable HULK Link to comment Share on other sites More sharing options...
Jito463 Posted June 27, 2005 Share Posted June 27, 2005 Another possibility that I didn't think of before is that a multi-boot DVD as we currently know them just will not work with x64. Think about it. When it boots initially it's running in 16-bit mode if I'm not mistaken. It then launches whatever setup files are needed to run the other setup disc on the DVD. However, x64 is not compatible with 16-bit mode. We may have to resort to a WinPE/BartPE method for preinstalls from here on out. Frankly, it's probably a better idea anyway. What do you think? Link to comment Share on other sites More sharing options...
ziteribo Posted June 27, 2005 Share Posted June 27, 2005 Jito463 =>put ntldr in boot folder doesn't work for me, i have ntldr corrupt (have you modified setupldr, how ?)Try to put ntdll.dll and osloader too, maybe it will work ... !I think the WinPE based method is the best to explore now ... B) Good evening all ! Link to comment Share on other sites More sharing options...
Jazkal Posted June 27, 2005 Share Posted June 27, 2005 This observation bring in a 3rd possibility to the equation... maybe the setupldr.bin file isn't the cause of the problem, an other file may be responsible for that...<{POST_SNAPBACK}>I agree. I have modified setupldr.bin files working fine on linux (for WinPE PXE booting). So I think there is some other file (DLL maybe?) doing a checksum on the setupldr.bin file durring boot. Link to comment Share on other sites More sharing options...
djbe Posted June 27, 2005 Share Posted June 27, 2005 Another possibility that I didn't think of before is that a multi-boot DVD as we currently know them just will not work with x64. Think about it. When it boots initially it's running in 16-bit mode if I'm not mistaken. It then launches whatever setup files are needed to run the other setup disc on the DVD. However, x64 is not compatible with 16-bit mode. We may have to resort to a WinPE/BartPE method for preinstalls from here on out. Frankly, it's probably a better idea anyway. What do you think?<{POST_SNAPBACK}>Well, if windows XP x64 is 64bit, then the installation is 64bit too (or else you wouldn't be having any trouble, would you?). So at some point, the installation switches from 16-bit mode to 64-bit mode. (Maybe with 32-bit mode between those) That moment should normally be the same point where a normal windows XP installation (32 bit) switches from 16 bit to 32 bit mode. That last one (16 -> 32) works on multi-boot, so why wouldn't 16->(32)->64 work? Link to comment Share on other sites More sharing options...
Incroyable HULK Posted June 27, 2005 Author Share Posted June 27, 2005 (edited) Another possibility that I didn't think of before is that a multi-boot DVD as we currently know them just will not work with x64 ... x64 is not compatible with 16-bit mode.I would agree with that IF Windows 2003 Server SP1 (32-Bits) would work! Since it has the same issues as 64-Bits, it must be something else. Edited June 27, 2005 by Incroyable HULK Link to comment Share on other sites More sharing options...
soul Posted June 27, 2005 Share Posted June 27, 2005 Are the download links in the first post broken, or is it just me? I'd like to look at the 2003 .bin, but the link isn't cooperating with me. Link to comment Share on other sites More sharing options...
Incroyable HULK Posted June 27, 2005 Author Share Posted June 27, 2005 Are the download links in the first post broken, or is it just me? I'd like to look at the 2003 .bin, but the link isn't cooperating with me.I don't see anything wrong...here is another link:http://66.131.144.223:88/MSFN/Win2K3-STD-SETUPLDR.BIN Link to comment Share on other sites More sharing options...
soul Posted June 27, 2005 Share Posted June 27, 2005 Ahh, that one worked for me, thanks. Link to comment Share on other sites More sharing options...
Merlinbyt Posted June 28, 2005 Share Posted June 28, 2005 sorry i am from Spain,read english well but write very bad..asi que pondre tambien español,si alguien puede interpretar a los demas se agradeceok,the solution for dvd windows 2003 server and server X64 is posible thats:put yours server 2003 carpets ,no chaing the name I386 ,for the X64 put AMD64 and the I386 rename for example I064 and put too in the boot.bin of the X64SETUPLDR.BINBOOTFIX.BINI064AMD64 DVD I386 ; WINDOWS SERVER 2003 AMD64 ; WINDOWS X64 I064 ; WINDOWS X 64 I386 RENAME I064ok,i am too looking that I386 in the X64 only have one file diferent of the I386 in 2003 server ,i am think put all in I386 , Windows 2003 server and X64 Link to comment Share on other sites More sharing options...
Jito463 Posted June 29, 2005 Share Posted June 29, 2005 Has anyone tried hex-editing the setupldr.exe (after unpacking it of course) and changing the references to i386 in there? I ask because when I opened it in the hex editor, it had the exact same i386 references in what appeared to be the same places as setupldr.bin. I probably won't get a chance to play with it until next week. We're closing our store down and moving everything to the other store, so things are a little busy atm. Link to comment Share on other sites More sharing options...
Jazkal Posted June 29, 2005 Share Posted June 29, 2005 Jito463, gave that a try, but didn't see any changes. Sounded good though. Link to comment Share on other sites More sharing options...
ziteribo Posted June 29, 2005 Share Posted June 29, 2005 Jito463, gave that a try, but didn't see any changes. Sounded good though.<{POST_SNAPBACK}>I think this is normal : with the gosh reducing size of source method, there is no setupldr.ex_I think the WinPe boot Method is the solution ... Link to comment Share on other sites More sharing options...
Jazkal Posted July 1, 2005 Share Posted July 1, 2005 my guess is that ntdetect.com or spcmdcon.sys is doing some kind of checksum on setupldr.bin.Anyone know if this can be debuged somehow? Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now