Slashdot Mirror
Windows ME - The End Of UMSDOS And BeOSfs Over Vfat?
Juan Rojo writes: "I recently got a copy of Microsoft Windows Millennium Edition (which
is suppossed to be the next generation of the Windows 9x series, supposed to mantain 'backwards' compatibility with older versions. In them all the ports and memory access are unprotected). I was really surprised that "pure" DOS access was simply removed. You can't enter into pure DOS in any way. No more 'Command Prompt' option when pressing F8 at the startup.. No more 'Shutdown to MSdos' and no more shorcuts to DOS mode. I even tried removing the Windows directory and it crashes at the startup instead of going back to a DOS prompt (like Win98 or 95). The only possible way seems to be booting from a disk with a Win98 DOS kernel installed. This seems to be a serious problem for UMSDOS based unix distros, for the BeOSfs that runs over Vfat and even for using LoadLin, which many users still may need.
I wonder if Microsoft did this on purpose.. or if they have some 'excuse' about it." That doesn't sound very "backwards" compatible to me either. Considering the source, is anyone really surprised?
Consider: many new motherboards have no ISA slots, and soon the ISA bus will be completely removed on all new motherboards. Does this benefit the consumer? What about consumers who have ISA modems? The answer is, yes, it benefits the consumer in the long term, at the expense of a minor inconvenience in the short term. Once everyone has switched completely over to PCI and USB, we can start using motherboards that have no ISA bus (not just no ISA slots, but no PS/2 ports, no floppy drives, and no other devices that still run on the ISA bus). This leads to a more efficient design, which gives us faster, cheaper, more efficient motherboards - and that benefits everyone.
It's sad, really. This is yet another example of Microsoft's technological achievements(successful migration of the PC industry from DOS/Win16 to Win32, excavation and elimination of DOS legacy code) being marred by the relentless drive of their business side to quell competition.
Wait a minute - what? you're saying moving from DOS/Win16 to Win32 is a good thing, and yet removing DOS is a bad thing? Think about this for a moment.
DOS is not just a lower operating system--it's a basic environment that can be entirely overwritten by whatever code happens to run underneath it. Much has been said about the ability to run alternative operating systems being quelled by this design; the faults generated are actually much more devious.
So, DOS doesn't completely control your system; rather, it lets other software do whatever it wants. This quells the ability to run alternative operating systems? That makes absolutely no sense. This design is what makes LOADLIN possible - LOADLIN can completely remove DOS, and replace it with something else, while the system is still running.
DOS lets the user replace anything with everything; under the Windows model, Microsoft holds the final say on what calls you're allowed to issue, what memory you may rewrite, what partitions you may generate.
Wow, that sounds remarkably like UNIX. Applications can't directly muck around in hardware (unless they're running with root permissions, in which case the OS selectively grants them access).
Even the simple requirement to rewrite applications such as Partition Magic in full Win32 code--and that's presuming a hard drive partitioner could be allowed to function through the API--at minimum makes the code much less portable across OS's, and gives Microsoft leverage over yet another critical element of system configurations.
Hmm, making software companies rewrite old applications that require a backwards-compatibility layer so that they're more efficient and work better is a bad thing? Windows NT is 32-bit only, and is much more stable than Win98, so Microsoft wants to migrate everything to NT. The more 16-bit apps that get rewritten as 32-bit apps, the more likely this plan is to succeed.
This isn't just about Microsoft making it harder for their users to run alternative operating systems; it's about Microsoft closing off direct access to a user's own system to the point of forcing the OS to crash before giving the user a command prompt.
Uhhh, who said anything about forcing the OS to crash? Where the hell did that come from? And by the way, someone else pointed out that you can still get to a command prompt by (surprise!) opening a command prompt window.
--
$x='S24;r)>63/* h@<5+oZ)32"5cz';$me='phroggy'x$];
$x=~y+ -xz+\0-Tx+;print$_^chop$me for split'',$x;
I've taken a look at a WinME beta, and command.com is still there, it still runs on top of it, you can still start the ms-dos prompt from inside windows, it's just you can't get the dos prompt by itself. They've gone out of their way to turn that off.
--
It makes sense. I don't LIKE it, but it makes sense. MS has been promising to make DOS a thing of the past since 3.1, they've just finally delivered. No more legacy 8 and 16 bit processes should mean more stability. Would you be the one to say that Windows doesn't need all the stability it can get?
As I said, I don't like it, I prefer to do half my work CLI style, but I've seen it coming for 6 years now.
OHMIGOD, Microsoft has finally lived up to a promise from many years ago and removed support for MSDOS? Those bastards!
</SARCASM>
This is about a non-story if I ever heard one. On the one hand, MS is blasted by the non-MS community for maintaining legacy 16-bit code. Then, when finally cutting it free, the same community suddenly realizes that they've been benefitting from the old 16-bit code and throws a hissy fit. You can't have it both ways.
All this really means is that people will need to keep old boot diskettes around, or perhaps look at creating a boot floppy using FreeDOS. If it doesn't work now with FreeDOS, I suspect that it could certainly be made to given the proper impetus. In any case, it hardly means the End Of UMSDOS And BeOSfs Over Vfat, as the title of the article suggests.
---
---
"Go Metallica. Die RIAA." -- Linus Torvalds
-----------
"You can't shake the Devil's hand and say you're only kidding."
Windows ME will still have DOS compatibility. To get rid of DOS would mean to re-write Windows (ala NT). There was an article in PC Magazine or Smart Computing or something I read that said there was a way (undocumented of course) to get to DOS mode. Microsoft is most likley doing this so they can create an illusion of having DOS gone so they can get people used to the "no dos" design of there upcoming OS that will merge Win 9x and NT (2000).
Of course that is just my opinion
"If ignorance is bliss, why aren't there more happy people in the world?"
Guys, you're being absurd. They announced two years ago that they would be removing DOS mode. In fact, they had planned on doing so for Win98, but needed to maintain it for one more edition.
The entire Win32s for Windows 3.1 and Windows 4.x series (95, 98, 98SE, ME) has existed for one purpose: get all applications replaced by Win32 versions and migrate everyone to NT.
This is not a hidden agenda. Gates talked about this in the EARLY 90s ('92 or '93). Back then WinCE was referred to as modular windows, Chicago was Windows 4.0, etc.
None of this is secret. None of this is aimed at killing Linux. This is aimmed at killing DOS applications that won't run in a NT VDM. Those applications are the enemy, not Linux. They prevent MS from killing the DOS legacy and moving everyone to NT.
Right now, MS is saddled by that compatibility and limits their products ability to work. There is a world of difference between NT 3.51/4.0/5.0(W2K) and Win3.1/95/98 (can't say for me) in terms of stability, etc.
They keep migrating to new driver models that were more similar to the NT ones to improve stability and make the migration easier (more driver support for NT).
This isn't aimed at Linux, it is aimed at helping MS make a better OS.
Alex
"Officially, Microsoft says you can boot to the real-mode command prompt only from the Emergency Boot Disk, which may leave too little memory free for running BIOS-flashing and similar programs that run only from the command prompt. Unofficially, Microsoft insiders told us to create a minimal bootable floppy disk by copying Io.sys and Command.com from the WindowsCommandEBD folder to a blank formatted disk."
=======================
Enlightenment is a Trap
You can still run DOS applications inside Windows ME (ie: as a window or full screen), but you just can't reboot the machine to a "pure" DOS prompt. If you have a boot floppy made with a previous version of DOS/Window9x, then you can get to a real DOS prompt that way. Also keep in mind that your config.sys and autoexec.bat are not parsed anymore either. Windows ME still has the dependence on the DOS underlyings and DOS really have not been completely removed, but the ability to easily access real-mode DOS has simply been made difficult. The primary purpose of doing this is to further enforce the movement of device drivers away from old style config.sys "DEVICE=" lines and various TSRs for supporting hardware and towards natively written 32-bit drivers. Such 32-bit drivers will generally be easier to port forward to future versions of Windows based on NT (Win2k and future) if those manufacturers don't already support NT. A side benefit is that native 32-bit drivers in Windows ME will generally be easier for users to configure and adapt to hardware changes (such as power state or docking changes). For example, being able to use native 32-bit network drivers instead of 16-bit DOS IPXODI/VLM drivers generally will have a tremendous boost in performance and usability. Switching from a 16-bit DOS CDROM SYS driver with MSCDEX to a fully native will generally not only be faster, but will allow access to long filenames. Although it is true that systems with older, no-longer supported hardware may still depend on DOS-mode TSRs or SYS drivers and may not be able to get updated drivers, Windows ME is not intended to be a general purpose upgrade for all older systems. Going forward, the next consumer OS after Windows ME will be based on NT and will have even more dramatic legacy hardware support issues, since many older manufacturers have neglected to support NT at all.
Don't waste those cycles! Put them to use! http://www.distributed.net/
To be fair you are being just a little hard on Microsoft here.
I can see it now, if they had left dos in then the story would read "Microsofts 20th attempt at a graphical OS still relies on the command line".
Surely this is a step in the right direction and surely the linux/BeOS people can find a way round it.
After all winNT hasn't included a true dos for a heck of a long time and ultimately that is the model that the simultaneous windows versions are striving towards (slowly striving that is).
UMSDOS and BeOS over FAT aren't about the COMMAND.COM. I've installed BeOS PE in a blank MSDOS partition more than once. It's about the file system. WinME still uses FAT32 as its file system, and BeOS can install on NTFS. It doesn't matter whether or not they removed COMMAND.COM in WinME, it matters that the file system structure is still valid. Get it?
Free BeOS, runs from a Linux partition