os2fan2

i do have win 3.51 lying around, and might load it up on a vm box. i have played around with some of the earlier stuff as well, eg 3.1 and 3.5. in practice, one at this time is interested in 32-bit operating systems, of which OS/2 was the example per excellance. One might say in the times of the appearence of the i386: "OS/2, because a 386 is too precious to waste". It is interesting that Windows still talks of i386 and so on, even though we have i486 and i586 chips out. the alpha, mips and ppc chipsets have gone by the wayside. You *could* treat the "consumer windows" = win9x as another kind of win32 architecture. in any case, winnt4 came with one of my hardware things so i use it since then. since this i have gone to win2k, and it seems stable enough. W

/me fesses to using OS/2. Ok. I once really did use a 32-bit system! W

I have seen nt4, 2k, xp, 2k3 workstations. I use win2k, with assorted xp fixes &c. W

Some proggie i found on the net, which loads under NTLDR, and then loads lockhorn's bootmgr. It's called AVLDR.EXE, it comes with some utility i dug up for booting leghorn's winpe from the hard drive. W

This is the original tree for the Win2k SP0 cdrom. D:\ +--BOOTDISK +--DISCOVER ¦ +--AUDIO ¦ +--COMPATBL ¦ ¦ +--ANIMAT ¦ ¦ ¦ +--MULTMON ¦ ¦ +--AUDIO ¦ ¦ +--DRVRSUPP ¦ ¦ +--IMAGES ¦ ¦ +--LGCYSUPP ¦ ¦ +--MULTSUPP ¦ ¦ +--NEWHRDWR ¦ ¦ +--NTWKSUPP ¦ +--EASY2MAN ¦ ¦ +--ADMIN ¦ ¦ ¦ +--IMAGES ¦ ¦ +--ANIMAT ¦ ¦ ¦ +--AUDIO ¦ ¦ ¦ +--JNDOMWIZ ¦ ¦ ¦ +--MNGMTCON ¦ ¦ +--AUDIO ¦ ¦ +--IMAGES ¦ ¦ +--SETUP ¦ ¦ +--SUPPORT ¦ +--EASY2USE ¦ ¦ +--ANIMAT ¦ ¦ ¦ +--ACTIVDIR ¦ ¦ ¦ +--ASSOCIAT ¦ ¦ ¦ +--AUDIO ¦ ¦ ¦ +--AUTIRSUP ¦ ¦ ¦ +--CONSPOWR ¦ ¦ ¦ +--CUSTLBRS ¦ ¦ ¦ +--FILEOPEN ¦ ¦ ¦ +--IMGMANIP ¦ ¦ ¦ +--INETCWIZ ¦ ¦ ¦ +--INTGSRCH ¦ ¦ ¦ +--NTWRKPL ¦ ¦ ¦ +--ONESTOP ¦ ¦ ¦ +--PRSNLSTM ¦ ¦ ¦ +--RECNTFLD ¦ ¦ +--AUDIO ¦ ¦ +--FINDINFO ¦ ¦ +--IMAGES ¦ ¦ +--PERSONAL ¦ ¦ +--WORKREMO ¦ ¦ ¦ +--IMAGES ¦ ¦ +--WRKONWEB ¦ ¦ ¦ +--IMAGES ¦ ¦ +--WRKWFILE ¦ ¦ +--IMAGES ¦ +--IMAGES ¦ +--MISC ¦ +--MUSIC ¦ +--OPEN ¦ +--POWERFUL ¦ +--AUDIO ¦ +--IMAGES ¦ +--PERFORM ¦ +--RELIABTY ¦ +--SECURITY ¦ +--IMAGES +--I386 ¦ +--COMPDATA ¦ +--LANG ¦ ¦ +--ARA ¦ ¦ +--CHS ¦ ¦ +--CHT ¦ ¦ +--HEB ¦ ¦ +--IND ¦ ¦ +--JPN ¦ ¦ +--KOR ¦ ¦ +--THA ¦ +--SYSTEM32 ¦ +--UNIPROC ¦ +--WIN9XMIG ¦ ¦ +--ACROBAT ¦ ¦ ¦ +--FILES ¦ ¦ +--CMMGR ¦ ¦ +--EASTMAN ¦ ¦ +--FAX ¦ ¦ +--HPTOOLS ¦ ¦ +--IBMAV ¦ ¦ +--ICM ¦ ¦ ¦ +--SYMBOLS ¦ ¦ ¦ +--RETAIL ¦ ¦ ¦ +--DLL ¦ ¦ +--IEMIG ¦ ¦ ¦ +--SYMBOLS ¦ ¦ ¦ +--RETAIL ¦ ¦ ¦ +--DLL ¦ ¦ +--INOCULAN ¦ ¦ ¦ +--_INOC ¦ ¦ +--MAPI ¦ ¦ ¦ +--80 ¦ ¦ ¦ +--802 ¦ ¦ ¦ +--803 ¦ ¦ ¦ +--98MAPI ¦ ¦ ¦ +--98OMI ¦ ¦ ¦ +--DLL ¦ ¦ ¦ +--EX40A ¦ ¦ ¦ +--EX50SP2 ¦ ¦ +--MODEMS ¦ ¦ +--MSGQUEUE ¦ ¦ +--MSP ¦ ¦ +--NAV ¦ ¦ +--NECKBD ¦ ¦ +--NECPA ¦ ¦ +--NECWPS ¦ ¦ +--OCTOPUS ¦ ¦ +--OEWAB ¦ ¦ +--PCANYW ¦ ¦ ¦ +--DRIVERS ¦ ¦ ¦ +--V8 ¦ ¦ ¦ +--DRIVERS ¦ ¦ +--PRINT ¦ ¦ +--PWS ¦ ¦ ¦ +--SYMBOLS ¦ ¦ ¦ +--RETAIL ¦ ¦ ¦ +--DLL ¦ ¦ +--RUMBA ¦ ¦ +--SETUP ¦ ¦ +--TRANSACT ¦ +--WIN9XUPG ¦ +--WINNTUPG ¦ +--MS ¦ ¦ +--MODEMSHR ¦ ¦ +--SNA ¦ +--OEM ¦ +--DIGI ¦ ¦ +--ASYNC ¦ ¦ +--ISDN ¦ ¦ ¦ +--BRI ¦ ¦ ¦ +--PRI ¦ ¦ +--REALPORT ¦ +--EICON ¦ +--EQN ¦ +--NOVELL ¦ ¦ +--LIBS32 ¦ ¦ +--NLS ¦ ¦ ¦ +--CHINESES ¦ ¦ ¦ +--CHINESET ¦ ¦ ¦ +--DEUTSCH ¦ ¦ ¦ +--ENGLISH ¦ ¦ ¦ +--ESPANOL ¦ ¦ ¦ +--FRANCAIS ¦ ¦ ¦ +--ITALIANO ¦ ¦ ¦ +--KOREAN ¦ ¦ ¦ +--NIHONGO ¦ ¦ ¦ +--PORTUGUE ¦ ¦ ¦ +--RUSSKI ¦ ¦ +--REDIR ¦ +--SPX ¦ ¦ +--MPS ¦ +--TIGERJET +--SETUPTXT +--SUPPORT ¦ +--TOOLS +--VALUEADD +--3RDPARTY ¦ +--CA_ANTIV ¦ +--LEVEL8 ¦ ¦ +--MQC.QUE ¦ +--MGMT ¦ ¦ +--AGENTS ¦ ¦ +--CITRIX ¦ ¦ ¦ +--ENG ¦ ¦ ¦ +--ICA16 ¦ ¦ ¦ ¦ +--DISK1 ¦ ¦ ¦ ¦ +--DISK2 ¦ ¦ ¦ +--ICA32 ¦ ¦ ¦ ¦ +--DISK1 ¦ ¦ ¦ ¦ +--DISK2 ¦ ¦ ¦ +--ICAHPC ¦ ¦ +--INTELDMI ¦ ¦ ¦ +--CIMOMPRO ¦ ¦ ¦ +--DMISP ¦ ¦ ¦ +--WBEMDMIP ¦ ¦ +--WINSTLE ¦ +--SECURITY ¦ +--SDTI +--MSFT +--FONTS +--MGMT ¦ +--ADC ¦ ¦ +--RES ¦ +--IAS ¦ +--MSTSC_HPC ¦ +--MS_SMS ¦ +--PBA ¦ +--WBEMODBC +--XTRADOCS +--SCRIPT +--SERK

i tried them both out, i could not spot the difs. they're both faster than win2k, though. i now have my nt4 install use the nt4 sp6 on first load, and the sp6 version is modified to be the 2k3 ones. win2k now sets up the win2k3 ones as well. incidently, this is the only reason i suspect you have to install nt4 first. if you're handy at replacing ntldr etc, you pretty can install win2k3 first and work backwards (or in any order you want!) W

Lots of code in programs like io.sys and win.com is simply deactivated, for reasons that if it ain't broken, don't fix it, and so that it could be activated. While the DOS in Windows 9x is meant to be there for compatibility mode, the idea is that the need for it is being progressively being withdrawn. DOS in Windows 9x is primarily a loader for Windows, but it *can* run old DOS stuff with a bit of effort. MS-DOS 7.0 introduced support for long file names. Even so, this is a new direction for DOS, and Windows 95 is intended to co-exist with a previous DOS. This is why it supports dual boot, and its DOS is pretty much compatible with previous releases of DOS. Users at the time would have had many DOS / Win31 stuff. The fat32 driver was drvspace3, included in P!us95. MS-DOS 7.1 introduces support for fat32 partitions, and larger drives. At this time, one might expect patchy support for DOS, and the dual boot mode is less-well supported. None the same, some parts were made into dead code, which *could* be activated by a simple hex edit. I think in practice, the way MS-DOS 7.1 works is that it has to be fed cookies in the right order to activate the DMPI server, and Windows 3.1 does not do that. A simple patch to the files fixes this. MS-DOS 8.0 is more intended to simply load windows, and separate DOS mode is not supported here. In fact, it has two different command.com and io.sys, and most of the utilities are either straight string-edits on the MS-DOS 7.1 stuff, or actually run under 7.1. Since this DOS is intended to support just one application (windows), it is more written to be in essence, a windows driver, rather than a standalone OS. None the same, you can defang this DOS too, but even defanged, it still won't run Windows 3.1. MS-DOS 7.1 will work without doing the 3xStart patch, but you can't run lots of things. And if all you really want to do is run some kind of Win9x, then the MS-DOS 8.0 is the way to go. Yes, MS-DOS 8.0 will load Win95. But if the intent is to have a DOS that can run DOS stuff, and load Windows, then MS-DOS 7.1 is the option to look for. There are several fixes. I use the 3xStart.exe fix, personnally. DOS 8.0 is no more encripted than DOS 7.1. It just does not have the code there. It automatically loads himem functions inside io.sys. The himem.sys is a string-hacked version of the Win98 one, and in WinME is about as useful as a choclate teapot. While DOS 8 is not really good as a general purpose MS-DOS, it makes a much better loader for Win9x than eithe MS-DOS 7.0 or MS-DOS 7.1. If you load to either the command prompt, or use BootGUI=0, you can start windows by the win command. The point of the current exercise is to recreate a modern version of MS-DOS 6.22, which we need the string hack.

When you use NOAUTO, io.sys does not look in the Windows directory to find and load himem.sys, etc. Its main use is to allow you to use different switches etc with HIMEM.SYS, EMM386 &c, although you can use a replacement memory manager. QEMM does not work here, because it is not Win9x compat. If you want to set up a system that either boots DOS or DOS + Windows, you do it something like this. For a floppy-disk or cdrom boot, it is best to have Logo=0 here. ;MS-DOS 7.10 System Configuration File ;(C)Copyright Microsoft Corp 1981-1999 [Options] AutoScan=0 BootDelay=2 BootGUI=0 BootMenu=0 BootMulti=0 BootSafe=0 BootWarn=0 DoubleBuffer=0 Logo=1 SystemReg=0 ; ;For compatiblity with Windows 9x GUI only: [Paths] WinDir=. WinBootDir=. HostWinBootDrv=C ; ;===================================== ;MS-DOS 7.10 System Configuration File ;(C)Copyright Microsoft Corp 1981-1999 ;===================================== ; ;XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX ;XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX ; You then have a config.sys like this. You could stick all the stuff into a DOS directory, but if you are multibooting DOS versions, it is better to split off the drivers (which are version independent). device=c:\msdrv\himem.sys device=c:\msdrv\vide-cdd.sys /d:mscd0001 dos=high,umb,noauto lastdrive z shell=c:\command.com c:\ /p rem INCLUDE THIS IF YOU WANT TO RUN WIN9X rem IFSHLP.SYS from any version of Win9x. device=c:\msdrv\ifshlp.sys You move the drivers into the directory. The Win98SE is the latest version. WinME version just updates the version number. You can run Windows 3.1 and Windows 98 from the same session, although the Win98 exit is a reboot. You could run Win95 from this DOS as well. (Yes, i done all of this). For these, you need a batch file that does something like this. You simply change what gets added to the path, and launch windows from the %windir% directory. @echo off :: Run Windows 3.1 set oldpath=%PATH% path %PATH%;c:\win31;c:\win31\utils; c: cd \win31 win path %OLDPATH% rem this fixes a prompt-bug in MS-DOS 7,1 cd \ For Windows 3.1, you need to apply the W31Start.exe patch, (which patches Windows 9x to run Win3.1 as well), along with this fix to win31\system.ini, to allow Windows to run in machines with lots of memory: In [386Enh], create or set PageOverCommit=2 Wendy

The DOS from microsoft Win98, with assorted fixes etc, should fit onto a floppy disk, prehaps two. Treat the package as if it were MS-DOS 6.22 or something. You can then add what you want. For a minimal install, i suppose someone could write an install batch that simply wrips the stuff out of a Win98 install, and then patches the stuff. W

The XIMAGE program can repackage .WIM files into parts, suitable for install. You could try to install it from a boot cdrom + hard-disk files (say, copied and reassembled from cdroms, eg file-split. I don't know if that should work. Alternately, buy a DVD player, and install it from there. W

DOS in Windows 98 comprises of the stuff in the windows\command, along with command.com, himem.sys, emm386.exe, setver.exe from the windows directory, along with IO.SYS, mscdex.exe You essentially need only IO.SYS, these drivers, your cdrom driver and a command processor. A mouse would be handy. In config.sys, put DOS=HIGH,UMB,NOAUTO . The NOAUTO tells windows to use the paths, and not to autoload the junk. Hunt down a program at powerload: http://oldfiles.org.uk/powerload/download/3xStart.exe This patches the dos7.1 to load windows 3.1, and a few other proggies. They also have an "MS-DOS 7.1" diskette, suitably modified in this way. The rest of the DOS configuration is then straight Windows. EDIT from Windows 2k/XP will work under MS-DOS. It's not hard to find. You can add a bootsector for the MS-DOS partition to the NTLDR Boot Menu, by using something like bootpart.exe at http://www.winimage.com/ The thing would then be useful enough to not only run your game, but run some other utilities, such as partition-magic, ghost, etc. W

I suppose this site http://snakefoot.fateback.com/tweak/winnt/files.html is worth the look. They have links to a defanged version of a gui "at" replacement, and also some stuff on the windows defrag.

The later versions of ntldr and ntdetect.com support all of the older switches and then some more. This is in part due to the fact one might dual boot Windows NT4 and, say Win2k3 or leghorn. The experiment box has this combination, the plan is to introduce some form of XP (prol sp1 or sp2), and Win2k. For example, you can't boot a MININT session from a NT4 or W2K boot loader, you need XP sp1 or better. The later versions do fix up the bugs in it. Note that XP introduces a new debug dll (dbcom.dll) into the kernel, which is why the lockthorn /USENEWLOADER works with these versions [when the %windir%\system32\winload.exe is copied from leghorn to these versions. The older versions (NT4, W2K) do not support this dll, or the new switch. For the moment, i don't reccomend using leghorn's boot loader, but loading it by a back-door hack. W

Worth adding to the pinned Win2003 Server to workstation is this URL. Google for: sala win2003 or head off to... http://www.sala.pri.ee/ The tool has tick-box options for many of the tasks to do in the Win2003 server to workstation conversion, including the install of WinXP games. W

cygwin1.dll comes from the Redhat Cygwin (unix under windosw), and nothing to do with native windows. Even if you don't install the rest of the package, it is still useful, because Linux ports like some mkisofs.exe use it.

What happens when you run it in Win9x compatibility mode, or full screen? Running it through an emulator can make the program rather clunky, as i find with win9x under winnt. You could, i suppose, dual boot. i have an msdos partition on my pc, even with 120 gb hda.

i wonder if it is not possible to use the files fron nt 4.00.1381?

For all of you who still want an NT4 partition going, i hacked together a batch process to fix NT4 installs without using $OEM$ etc. It does a whole lot of stuff in two reboots... You need to do a few mods to the install source to get it to work. Note it has a check for excessive installs, in the form of files. set hfix=\HOTFIX if exist %systemroot%\system32\qhain.exe goto :fix2 if exist %systemroot%\system32\aspichk.exe goto :fix1 :fix0 :: unpacked for speed %hfix%\nt4sp6a\update\update.exe -q -z -n :: need to comment out fp4auth.dll in hotfix.inf in Q299444 %hfix%\Q299444\hotfix.exe -q -z -n %hfix%\Packed\Q304158i.exe -q -z -n :: these produce KERNEL32 errors if packed. %hfix%\Q810833\hotfix.EXE -q -z -n %hfix%\q815021\hotfix.EXE -q -z -n %hfix%\Q817606\hotfix.EXE -q -z -n :: more that work just fine %hfix%\Packed\Q819696i.EXE -q -z -n %hfix%\Packed\Q841373I.exe -q -z -n :: these are server updates modified for workstation. :: insert in hotfix.inf [Version] a line "ExtendedSupport=1" (without quotes) %hfix%\Q873530\hotfix.exe -q -z -n %hfix%\Q891711\hotfix.exe -q -z -n :: redist files. %hfix%\REDIST1\tweakui.exe %hfix%\redist1\aspiinst.exe silent copy %hfix%\REDIST1\*.cpl %SystemRoot%\system32 copy %hfix%\redist1\ntsubst.exe %systemroot%\system32 copy %hfix%\redist1\oeminfo.ini %systemroot%\system32 copy %hfix%\redist1\oemlogo.ini %systemroot%\system32 copy %hfix%\REDIST1\aspichk.exe %systemroot%\system32\aspichk.exe :: we use IE5, but this baby don't go anywhere near the net :) %hfix%\IE50\ie5setup.exe /q /R:N :: qchain makes a full package %hfix%\REDIST1\qchain.exe :: fdv's file :) %hfix%\redist1\reboot.exe set hfix= goto :end :fix1 :: needs SP6 installed %hfix%\redist2\wmi-nt4.exe /q %hfix%\redist2\instmsiw.exe /q :: this msjava86 replaces a couple of survice packs. %hfix%\redist2\msjava86.exe /q %hfix%\redist2\hhupd140.exe /q %hfix%\redist2\jet40-kb837001-ENU.EXE /q %hfix%\redist2\WM320920_64.EXE /q %hfix%\redist1\qchain.exe copy %hfix%\redist1\qchain.exe %systemroot%\system32 goto :end :fix2 :: this is a failsafe :end The whole lot lives in a directory on the cdrom \HOTFIX, i have unpacked some to make the thing run faster (?), and remove some errors. See comments in the code. Then you need to fix some code for modern machines. 1. Copy NTLDR, NTDETECT.COM and ATAPI.SYS from SP6A to I386. 2. Copy NTLDR, NTDETECT.COM from some later Windows to SP6A. (this frees the install-order), 3. You need to comment out the FP4AUTH.DLL in SP6A. It is used for frontpage anyway, which we (a ) don't install, and (b ) provide by other ways. 4. All the stuff from the redist directories is purely optional. The thing has been set up so you can have hfix.cmd anywhere, and point it to the directory HOTFIX. You could, if you have a fat32 partition [zb Whinge98], put in the readonly fat32 from sysintern.

depending on what form of windows you use, it is possible. i even seen this done on a winme bootdisk. it's one of the 'miniwin' distros does this. the idea is to replace one of the files with command.com. something like vmm.vxd or something. you still need a fair few files to do this, but it can be done. reccomended reading on the subject, including how to do it, is found in 'undocumented dos' [i think]. it talks at length on how to defang windows 9x. w addit: for windows 3.1, you replace the device driver [krnl386.exe], with a suitably renamed command.com. That is, you rename krnl386.exe to krnl386.win, and the copy whatever you want to run as krnl386.exe (including command.com, or 4dos.com). WinStart.bat :: winstart.bat command.com another way of effecting this, is to create a 'winstart.bat' under win3.1, and run things from there, especially if this batch contains the single line 'command.com'. this will continue to load windows after the game is done, but you will have a 32-bit dos environment to play with.

More on lockhorn and co. If you have a messed up ntldr / ntdetect.com [ie from different versions of Windows], the leghorn install will bluescreen with a 'corrupt disk' message. i currently have on the testbox 4.00.1381 sp6 and 5.20.3790 sp0 5.20.3790 boots with no trouble, when you try the winload.exe + /USENEWLOADER trick. Win98 appears in the front menu, presumably, it is stabler than Windows XP. [it is purely a commercial decision that Windows XP can be booted using the old boot system, without having to go through a different menu. It could have easily been achieved by using \boot\ntldr and \boot\ntdetect.com without having to go through all the rigmoral of having to select from the legacy menu]. W

@fdv This is something i saw in the HFSLIP documentation, in the FAQ Q. What about services? Which ones can I kill? A1. Windows without services. A2. Win2k is free of most of the ones that make using XP unbearable, so personally, I wouldn't spend much time worrying about it. Here is a useful third answer: there is an excellent resource at http://www.blkviper.com/ on the Win2k and WinXP services, both system and commonly added ones, along with which ones are safe to stop etc, as well as what they do. W

The WIM files are archives like huge zip files. The installation boots a kind of loader, which unzips boot.ini into ram, and then starts that. Win2k3's ramdrv.sys allowed one to load an iso file as a ramdisk, but this is somewhat different, since you can write to the directories as well. All of the stuff needed to boot, and run winpe, lives in this file, even setup (setup.exe is in the root directory) Once this is set up, setup then basically unzips the install.wim folder to the system drive, and then runs a post-install config. You can effectively make a bartpe by adding an extra file (ximage /mountrw), to the boot.wim archive. Add this file as boot.wim\\windows\system32\winpeshl.exe [LaunchApp] AppPath=%SystemRoot%\System32\cmd.exe You then load to a command prompt, to which you can then launch setup, or do any other kind of fix. You can even add your own utilities to the boot.wim file, eg file commander, rexx or an editor.

I put leghorn on a box that already has all of these. Lockcorn will still put boot-sector loads (like Windows 95, MS-DOS, and Linux), on the front menu. Note that both the front and back menus are derived from boot.ini, and entries that have an rdisk() notation, and no /USENEWLOADER switch will be under the legacy menu (along with everything else!)

The XP version of NTLDR boots faster than the 2K version. Also, the XP version supports the F8 switch, which means that you don't have to have a second entry for 'safe mode', as the NT4 version does. If you plan to support BartPE on the hard disk along with some earlier version of Windows NT, you need at least version 5.1 SP1 (which has the /MININT switch. Neither NTLDR nor NTDETECT.COM remain in core once NTOSKRNL is loaded. W

Here is some testing-results i got from testing Winnt 6.00.5112 bootmgr with other Windows. Adding the switch /USENEWLOADER places the program in the front menu. The new bootmgr requires you have the file %WINDIR%\SYSTEM32\WINLOAD.EXE in the target operating system. You can use the one supplied with lockcorn (zb. nt 6.00.5112). Note this does not work with 4.0 or 5.0 versions. Windows 4.00.1381 sp6 must be booted from the "legacy" menu. Windows 5.00.2195 sp4 must be booted from the "legacy" menu Windows 5.10.2600 sp1 can be booted from the main menu or legacy menu. The file %windir%\system32\winload.exe must be copied from lockcorn to 2600 to work. [isn't it wonderful that the last big use of 2600 was Atari 2600! ] Windows 5.20.3790 svr or x64 are not tested here Windows 6.00.5112 must be booted from the main menu. [The beta version of Neptune that circulates is build 5111. Point upgrade?] Windows leghorn uses a new boot sector. If you want to completely eliminate this, it is reccomended to have a c:\ as fat, and a DOS boot disk. Then use the latest version of bootpart.exe [from http://www.winimage.com/ ], and the versions of NTLDR and NTDETECT.COM from Windows 5.20 or earlier. A backed up version of BOOT.INI is handy, but not essential. Restore the WINNT boot sector, and copy the NTLDR and NTDETECT.COM to the hard disk. c:\. Edit the boot.ini file to remove traces of /USENEWLOADER switch. Leghorn is then uninstalled. 4.0 will crash if either kdcom.dll or winload.exe are in system32 5.0 will boot if winload.exe is present, but only if the boot is from the 'legacy' menu. 5.1 requires the winload.exe file, and will boot from both the bootmgr and legacy menus. 6.0 will only boot from the bootmgr menu.