TheTruth Posted August 10, 2005 Share Posted August 10, 2005 Oh, bad . Anyway, we're sure that reversing 3 consecutive chars is the right rule.Are you sure you won't get the error msg of ntkrnlos.exe if you don't make any changes?anyhow, just let's wait. Link to comment Share on other sites More sharing options...
Jazkal Posted August 10, 2005 Share Posted August 10, 2005 Are you sure you won't get the error msg of ntkrnlos.exe if you don't make any changes?Yes, I tested it with and without the changes in the txtsetup.sif file, with the same results.I have a nice stack of coasters. I sure wish vmware would come out with a version that supported x64 clients Link to comment Share on other sites More sharing options...
TheTruth Posted August 10, 2005 Share Posted August 10, 2005 Okay man, that's enough for today.Thanks for your time.TheTruth Link to comment Share on other sites More sharing options...
Jito463 Posted August 12, 2005 Share Posted August 12, 2005 You can still test with VMWare, because if it gets to a point where it loads ntldr it will just say that your hardware doesn't support this OS. Otherwise it just gives the current message we're all getting. Link to comment Share on other sites More sharing options...
Ausmith1 Posted August 26, 2005 Share Posted August 26, 2005 The VMware v5.5 beta allows for 64 bit VM clients. Link to comment Share on other sites More sharing options...
Historic Posted August 30, 2005 Share Posted August 30, 2005 (edited) Ok, I too am looking for a real solution to this problem.Here are some tools to helpBinary File comparer (checks for same file size and stops at first diffrence) Very useful to confirn if both of setldr.bin are same or different.http://www.trombettworks.com/FileComparer.zip16/32 bit disassemblerftp://ftp.sac.sk/pub/sac/utilprog/qdasm100.zipEdit: Q: If I wanted to create a 3 in 1 for Server 2003, ent/std/web, Sp1can I use the original setupldr.bin and replace all 7 occurances with these folder names??1. I386/I386 -- Enterprise; no change in setupldr.bin, change path setupsourcepath=\I386\2. I683/I386 -- Standard; change setupldr to I683, change path to \I683\3. 83I6/I386 -- Web; change setupldr to 83I6, change path to \83I6\and follow multi-boot dvd tutorial. Or do I need to do anything else? Edited August 30, 2005 by Historic Link to comment Share on other sites More sharing options...
Historic Posted September 2, 2005 Share Posted September 2, 2005 (edited) Ok, people, test this.DeletedEdit: My mistake, seems I got all of my setupldr files mixed up. This look like the same as the one from without sevice pack. Edited September 6, 2005 by Historic Link to comment Share on other sites More sharing options...
geek42 Posted September 11, 2005 Share Posted September 11, 2005 I was wondering something:Over at Tom's Hardware there is a article about putting BartPE on a USB stick.The linked page above discusses using the 2K3 SP1 setupldr.bin file along with ramdisk.sys.Now from my understanding, the older bootloaders used the "emulate floppy" mode to load the kernel and then go into the install, but recently they ran into size issues with the 1.44 meg limitation for floppys, even most emulated ones(I know about 2.88...). I have this sneaking feeling that the major change in the boot process is to start using an initial ram disk for the startup.So, could we maybe get this working with a modification of the ramdisk.sys method?Just some ideas, I've yet to really try getting this to work, and have much to learn about how this all works.Anyway...JC Link to comment Share on other sites More sharing options...
qzmicro Posted September 12, 2005 Share Posted September 12, 2005 I was wondering something:Over at Tom's Hardware there is a article about putting BartPE on a USB stick.The linked page above discusses using the 2K3 SP1 setupldr.bin file along with ramdisk.sys.Now from my understanding, the older bootloaders used the "emulate floppy" mode to load the kernel and then go into the install, but recently they ran into size issues with the 1.44 meg limitation for floppys, even most emulated ones(I know about 2.88...). I have this sneaking feeling that the major change in the boot process is to start using an initial ram disk for the startup.So, could we maybe get this working with a modification of the ramdisk.sys method?Just some ideas, I've yet to really try getting this to work, and have much to learn about how this all works.Anyway...JC<{POST_SNAPBACK}>Sounds pheasable but I sure don't know enough to test on my own. I'm willing to help if anyone has any suggestions though.Qz Link to comment Share on other sites More sharing options...
Jazkal Posted September 19, 2005 Share Posted September 19, 2005 (edited) it was probably deleted because it is a "warez" release, and as such, is always deleted. Edited September 19, 2005 by Jazkal Link to comment Share on other sites More sharing options...
geitonaki Posted September 19, 2005 Share Posted September 19, 2005 Posting this for 3rd time since my previous posts were deleted.Posting that WinBeta has found a solution to the problem you are discussing and just giving the link to their nfo for their release at their site violates the forum rules?The rule says: "Links/Requests to warez and/or illegal material (porn, cracks, serials, etc..) will not be tolerated."I hope that only the link to their nfo was the problem and that this post will not be deleted as it hasn't any link now.So WinBeta has managed to put in one dvd various versions of Win XP x64, Win 2003 x64, Win 2003 32bit SP1. Anyone who can find how they have done it please tells us so we can do it in our copies of windows.P.S. Sorry I just saw that the nfo contains serials. Link to comment Share on other sites More sharing options...
Alanoll Posted September 19, 2005 Share Posted September 19, 2005 P.S. Sorry I just saw that the nfo contains serials.That would be the primary reason I personally deleted your posts. Link to comment Share on other sites More sharing options...
thegafferazzasatz Posted September 19, 2005 Share Posted September 19, 2005 can somebody post the nfo on the forum so we can see what oses are on the disc (assume that it is dvd) and what versions etc. and dont forget get rid of the serials off it lollol Link to comment Share on other sites More sharing options...
geitonaki Posted September 19, 2005 Share Posted September 19, 2005 can somebody post the nfo on the forum so we can see what oses are on the disc (assume that it is dvd) and what versions etc. and dont forget get rid of the serials off it lollol<{POST_SNAPBACK}> | | |Win XP x64 retail | | | | | | |Win XP x64 vol - | | | | | | |Win 2003 x64 std srv retail - | | | | | | |Win 2003 x64 std srv vol - | | | | | | |Win 2003 x64 ent srv retail - | | | | | | |Win 2003 x64 ent srv vol - | | | | | | |Win 2003 32Bit ent srv retail - | | | | | | |Win 2003 32Bit ent srv vol - | | | | | | |Win 2003 32bit std srv retail - | | | | | | |Win 2003 32bit std srv vol - | | | | | | |Win 2003 32bit web srv retail - | | | | | | |Win 2003 32bit web srv vol - | | | | Link to comment Share on other sites More sharing options...
Alanoll Posted September 19, 2005 Share Posted September 19, 2005 Please don't post the NFO again... 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