Re: Virtual Memory Management in Windows NT

Daniel Hamilton wrote:

> J. Clarke wrote:
>>>In 1998 Windows NT 5.0 was renamed to Windows 2000. They did so because
>>>they were trying from a technical as well as a marketing standpoint to
>>>jump from Windows 9x over to the NT code-base in the consumer space.
>>
>>
>> I thought they did so because they were so late in delivering it that
>> they
>> decided to try to make lemonade with the Y2K issue. Let's hope Longhorn
>> doesn't end up renamed "Windows 2100".
>
> Yeah I think they intended for Windows 2000 to succeed Windows 98 on the
> consumer side when they originally changed the name, but realized that
> 2000 wouldn't be compatible enough with old DOS stuff that was still
> around, so they hurriedly put together Windows Me, which I've heard
> noone have nice things to say about. XP supposedly improved DOS
> compatibility a good bit over 2000... although I never had any issues
> myself with it. I think it more applied to old games. :)

I don't think it's DOS compatibility that is the issue (little known
fact--2K and XP have the same compatibility features--they were
incorporated in 2K with service pack 2. But with 2K they were turned off
by default--to turn them on you have to enter "regsvr32
%systemroot%\apppatch\slayerui.dll" at a command prompt.) It's my
understanding that the real problem was the idiot application developers
who implement part of their application as a device driver--NT and 9x use
different driver models so such programs break on 9X. ME also breaks those
apps but since it's part of the "9X" family the developers couldn't point
the finger at NT anymore.

There's still the battle of the idiots who write their code so it _must_ be
installed and/or run from a privileged account. I've gotten to the point
that if I encounter one of those that does so for no good reason and the
dumpster is an option then that is where it goes.

> --Daniel

--
--John
to email, dial "usenet" and validate
(was jclarke at eye bee em dot net)
.

Relevant Pages

  • Re: DOS Compatibility
    ... > which uses Windows XP Professional. ... > estimating program nor one of the other DOS based programs. ... > Compatibility and MemoryTabs, all to no avail. ...
    (microsoft.public.windowsxp.general)
  • Re: DOS problems Fullscreen
    ... This problem can also be with the video card drivers that are NOT VESA ... >> work with DOS in the Window mode. ... > Windows XP does not have true DOS. ... > You can try running the old programs in Compatibility Mode (see XP's ...
    (microsoft.public.windowsxp.general)
  • Re: DOS on PPC 2003?
    ... > title this is as far as the resemblance goes to Windows 95/98 or Windows ... > produce that runs DOS backwards compatibility. ... PocketDOS is an MS-DOS 6.22 compatible DOS for your Microsoft ...
    (microsoft.public.pocketpc)
  • Re: DOS Programs
    ... not run them on Windows 2000 and forget about trying to figure out the ... Re-installation is usually a *very* drastic measure ... > compatibility problem. ... >> XP only provides an emulation of DOS, not DOS, with stricter controls ...
    (microsoft.public.windowsxp.general)
  • ~~~~~~~~~~~~~~ FILE NAME ~~~~~~~~~~~~~~
    ... adapter description file file name extension ... apple script to change file names ... batching file name changes in windows ... change short file names in dos ...
    (sci.misc)