Incroyable HULK

For now, only the Removal tool is available... http://www.microsoft.com/downloads/details...&displaylang=en

You should install a Linux in a Virtual Machine...

Let's see...hm.. 1- Medal of Honor Alied Assault (my first online game!) 2- Homeworld 3- Far Cry 4- Half-Life 2 5- Giants Citizen Kabuto

it would have been a better move to pair up with AMD. Far superior processor design... but unfortunatly not good as Intel for Chipsets

How about this one: b a s t a r d I'm not quite sure what we are looking for...

BugS BuGs bUGs I have a ATi Radeon X800XT on a nForce4 chipset and I get some kind of keyboard lag. it takes about 2-8 second before a keypress is executed Not to mention the highest resolution being only 1280x960

Come on Alanoll, let's beat him! I'll go get my stick! Unfortunatly, were back to square one...

Same here... NTLDR is corrupt. The system cannot boot

I'm currently testing too... ... I am re-installing VMware 4.5... the stupid v5 demo has expired

You must be jooking, Alanoll wasn't able to do anything! Could you describe the EXACT step you did

What do you mean it worked? Did you sucessfully modified the setupldr.bin of Win2003 Server SP1 ???

I just got my hand on WinPE 2005 so I added the setupldr.bin in the download area of the first post... Afterall, I wonder if this is exactly the same file for all 3 products. They all have 291KB... does somebody have a tool for comparison?

This can be a workaround but in the long term, we need to find out how to modify setupldr.bin... otherwise multi-booting is dead How do you plan to add another Microsoft Product while keeping this folder? This solution is only good for 1 product per media (CD/DVD)

Have you tried the AutoLogon options in your Winnt.sif? [GuiUnattended] AdminPassword="password" EncryptedAdminPassword=No AutoLogon=Yes AutoLogonCount=3

All you have to do is to remove BOOTFIX.BIN in your i386 folder. But if your BIOS is set to boot from the CD-ROM as first, the installation process of Windows will restart at every reboot!

There is already a guide here: http://flyakite.msfnhosting.com/ you have to use the "optimize" option when generating your ISO so a repeated file is only stored once...

Just noticed a small problem, the filename being called in the "Switches:" line refers to a different hotfix. I copied and pasted and couldn't figure out why this one wasn't being installed. Turns out I was installing an older hotfix twice <{POST_SNAPBACK}> Thanks! It is now corrected

WOhaaaa! Speak about improvement! I can't beleive it now we know why it works alot better then CDIMAGE 2.47

What do you mean by that? I don't see any major difference...

The same goes for the Fujitsu S6210... I beleive it is because the Graphic drivers get installed and then Windows is re-detecting the monitor and asking for some drivers. Of course, you don't have to do anything and everything will go fine...

You can leave a second I386 folder at the root of the CD so you can do your upgrade and even perform component installation if Windows is asking for the CD... using the "optimize" feature of CDIMAGE.

Do you have something in mind? Maybe I can help you find one of theses...

Welcome to the MultiBoot family! Please report to the Multi-boot CD/DVDs section HERE and take a look at the official guide HERE

Please post you full RunOnceEx.cmd file so we can have a look at it

*** UPDATE - 18 OCTOBER 2005 *** A solution has been posted here: http://www.msfn.org/board/index.php?showtopic=58410 Hello all, I've been reading around and I found that most people are having difficulty to modify setupldr.bin in order to multibooot: 1- Windows 2003 Server SP1 (and 64-Bits Editions) 2- Windows XP 64-Bits Edition 3- Windows PE 2005 So I decided to start this thread in order to solve theses problems, all together we are better than alone. Windows 2003 Server SP1 (french edition) 1- the new setupldr.bin (SP1) has 5 occurence of i386 and 2 occurence of I386 (the older one only had a total of 4 occurence) 2- Attempting to edit the new setupldr.bin will render it useless. You'll get a NTDLR corrupt message right at the beginning of the installation. 3- I beleive there is some kind of checksum built in the new setupldr.bin preventing any modifications or maybe the new 64bit code added is interfering... I don't know WORKAROUND Fortunatly, it is possible to use the older setupldr.bin from the original Win2003 Server to work with SP1. I did a test under simulation and everything went fine. ** UPDATE ** for now, you can replace i386 with i683 or 83i6, they don't corrupt the file - The credit goes to TheTruth Windows XP 64-Bits Edition No observation for now... I can't extract the boot folder and I can't go under simulation WORKAROUND From my reading, It doesn't seems to work using a Windows 32-Bits setupldr.bin so we'll have to dig this one... The future of MultiBooting is at stake my friend! DOWNLOAD Here you can grab a copy to work on SETUPLDR.BIN from Windows 2003 Server Standard English SETUPLDR.BIN from Windows XP x64-Bits Edition English SETUPLDR.BIN from WinPE 2005 English