Linked by Eugenia Loli on Wed 22nd May 2002 04:45 UTC
OSNews, Generic OSes Some days ago we hosted a head to head review of Bochs, VMWare Workstation and VirtualPC. I received a number of emails asking why I haven't included Netraverse's Win4Lin in the article. The main reason was because Win4Lin is not an emulator in the "traditional" sense of the word; neither it runs under Windows XP, where our previous test were conducted. In fact, Win4Lin can only run Dos and Win9x/ME, under Linux. We got hold of the brand new version of Win4Lin, version 4.0, and here is our review accompanied by some screenshots we grabbed for you.
Permalink for comment
To read all comments associated with this story, please click here.
by Speed on Tue 28th May 2002 04:54 UTC

It's obvious that you never bothered to do any test, ddj. If you had (and if you're honest), you wouldn't be repeating the rubbish that you are.

You have failed to show that Windows 9x uses DOS "underneath" it. That was your claim.

It's no secret that Windows 9x has a "DOS mode" and includes a full set of DOS utilities. That was the whole point of having another 32-bit Windows -- to provide full compatibility with legacy DOS programs. But you jumped to the conclusion that 16-bit DOS is active at the same time that 32-bit Windows is. And now you're in over your head.

Let's do a real test. You want DOS to be gone? Let's do it! Someone mentioned that the DOS directory was moved to a directory called "COMMAND" under the Windows directory. Go ahead and delete it -- delete it all! Not enough for you? Well we know that without COMMAND.COM you don't have DOS, so delete any COMMAND.COM file you find. Get rid of CONFIG.SYS and AUTOEXEC.BAT too, if there are any.

Now, try booting to DOS mode. Can't do it, can you? DOS is gone! Now boot into Windows...and eat crow.

Of course you might say "but wait, there's still IO.SYS and MSDOS.SYS!" That's true, but as Antarius pointed out they're not the same as any other MS-DOS files. MSDOS.SYS is nothing but a text file. IO.SYS is what loads the Windows kernel, so we can't remove it any more than you could remove NTLDR, NTDETECT.COM or any of the other files that NT uses to boot. So as it stands, 2/3 of what makes up the bare minimum of a DOS installation is gone, and therefore DOS is inoperable. But Windows still runs.

You'll find many things that look familiar to the DOS user. Why? Because Windows 95 was designed to provide full compatibility with legacy DOS programs. Those old programs look for certain files, and refuse to work if they don't find them. Naming files the same names is an elegant solution to a bothersome problem.

If you like, you can rename the files, for example to NTLDR and BOOT.INI, just like in NT. You'll have to alter the boot sector so it points to the new NTLDR file, and alter NTLDR so it looks for BOOT.INI, which shouldn't be much trouble for bigshot engineers like yourselves. You can also build your own bootloader that sets up the initial environment, switches modes so the OS kernel can be loaded into high memory and executes the Windows kernel.

Or I can be lazy and ask you to explain why on a NT/2000/XP box I can bring up a DOS prompt. And why when I enter "MEM /P" (a DOS command) that it shows that MSDOS is running? Now you're sunk, fool!

You're right, I think of you as an ignorant fool -- "daft", as you put it. You give me good reason to think so. You could have learned something useful, but instead you chose to be a jackass. The joke's on you, kid.