Windows 2000

Started by
25 comments, last by bosjoh 24 years, 2 months ago
There was an article about that a few weeks ago in a german computer magazine.
They wrote that even windows 2k builds up on MS-Dos!

There is no visible Console on startup. But the BootGUI command in MSDOS.SYS still works. After a boot in Console mode Windows shows "Dos-Version 7.1" after typing ver.

I'm going to search that article...

Advertisement
Another one:
DJGPP and WATCOM C++ won't work either...
DOS is just one of the several platforms Watcom compiles for. Don't worry, you'll still be able to use Watcom for a long time to come.
Windows 2000 does not boot DOS, or any thing like it. Windows 98 SE has DOS 7.1 if I remember correctly. In fact, Windows 2000 doesnt even have a Real Command.Com as I understand. Try it out and you will see what I mean when it first starts.

I tried the MSDOS.SYS BootGUI=0, and it does not boot a command prompt, as I expected.

I've heard of people arguing Windows 2000 was based on the 9x kernal instead of NT, too. Infact, someone was arguing with me the other day about it until they looked at the Startup screen and saw "Built on NT Technology".

Its most likely that the article you read this information from was misinformed, or was deeply confused.

-Dan Smith
dans@3dgamedev.com

In the beginning, there was Windows NT 5.0. But harken, Y2K was upon us and the people cried out in celebration as people are wont to do and so everywhere one looked, the number 2000 was appended. Thus was born Windows 2000, from the roots of NT technology, but with a much better compatibility akin to its brother Windows 9x.
But behold! Microsoft did then say, "Wait a sec, we can't make it to the consumer market just yet! Our release predictions are blowing out!" and thus the great plague of not meeting the release date claimed another product. And Microsoft then declared to meet in the middle. Windows 2000 Consumer Edition would be of the 9x core, but with NT enhancements.

In other words, unless you want spend a bit of cash on the real NT, don't worry. On the other hand, if you're like me waiting for the real NT5 to come to consumers, you'd be slightly annoyed.

But then, what do I know? Correct me if I'm wrong.

[This message has been edited by Jeranon (edited October 10, 1999).]

[This message has been edited by Jeranon (edited October 10, 1999).]

All I have to say is:

MICROSOFT SUCKS

so get a real operating system.

DESIGN FANATIC
David Abresch
abre1657@blue.univnorthco.edu
All I have to say Turtle, is that you're obviously attempting to be some kind of troll. Go move off to some AOL chat room where you belong.
From what I know, Windows 2000 has a "safe mode" command prompt on boot up, which brings you into a DOS environment. It doesnt use MSDOS.SYS like Win9x, instead, it works the same as NT4, but with a few new features.
I guess Microsoft her fed up with people installing new devices and having their PC's coming to an almost non-fixable halt all the time (The blue screen of death), so they added a command prompt to manually fix the conflicts easily (<-!FINALLY!->).

I just wish Microsaft would get their act together and develop a STABLE, FAST, SECURE operating system (Linux + MacOS are good examples), instead of adding fifty thousand little "enhancments .. cough, choke" that really only slowwww things down and create even more bugs and incompatability problems !!!

Give me Windows 95 OSR2.5 or Win2000 ANYDAY.
i.e. I LOVE a quick, stable, clean desktop.


ps. IE4-5, Win98, and WinNT4 are very sad.


  Downloads:  ZeroOne Realm

Windows 2000 has a Safe Mode Command Prompt, however, it still boots the GUI (graphical user interface). And if you type in explorer at that prompt, it will seem like the normal Safe-Mode.

Windows 2000 doesnt have any command prompt that doesnt run under the core GUI.

If you have Windows 2000, try what I said and you'll understand what I mean.

-Dan

[This message has been edited by Dan Smith (edited October 17, 1999).]

Windows9x is unstable as compared to WinNT & 2K because of the DOS and 16-bit Windows compatibility.

Windows9x thunks down to 16-bit DLL's, and because the Win3.1 wasn't a preemptively multitasked OS, the entire kernel must be locked with a global mutex during kernel operations (this is the Win16Lock for those of you who have tried debugging over a surface lock and a surface GetDC call.)

So one misbehaved App can lock the entire kernel, freeze up, and the whole system is shot. Win2K doesn't have these problems, because it doesn't have complete 16-bit compatibility is built in. It can just lock selective portions of the kernel at a time.

My opinion: DOS is dead. Win16 is dead. Win2K rocks.

This topic is closed to new replies.

Advertisement