QUOTE (-I- @ Jul 6 2006, 12:57 PM)

i realy never ever heared of so mutch BS in my life....
i know there are lots of guys and girls who dont have the money for a better computer ....
but thinking that 98 has a better HAL than for example windows 2k xp or vista is like saying that a toad will outrun an antilope or a sail plain wil better manourvre than an F15 tomcat....
For an OS never intended to be ported to other architectures (Alpha, MIPS, etc.),
W98 has a reasonable HAL (hardware abstraction layer) - most hardware
dependencies are isolated to particular VxDs that could be amended or replaced
with relative ease. The same is true for MS-DOS - the traditional design had all
hw-deps in IO.SYS - OEMs were given the source code for customisation to their
hardware (whereas MSDOS.SYS was provided in object form only)... but both
DOS and W3.x/9x were always closely tied to the x86 CPU architecture, largely
written in assembly language (making them more efficient and compact).
The NT designers, however, tried hard to make the OS portable even to
alien architectures (RISCs in particular) - with C++ as the implementation
language, and the famous"HAL" for shielding the rest of the system from
hardware dependencies, and as a matter of fact they went as far as
building a 286-emulator into the system for running DOS/Win16 software
on the other (non-PC) architectures. Such effort was expended in the
hope of seriously competing with Unix in workstation and server markets.
Fortunately Linux and the free BSDs arrived just on time to thwart those
sinister plans, hopefully for ever.
Or perhaps you weren't thinking of "abstraction" but of "virtualisation",
which is actually a specialty of the Win3.x/9x series - no other OS(*),
whether NT/XP/2K or Unix-like, comes close to matching the level of
virtualisation implemented in W9x VxDs. From the trival tasks of routing
keystrokes and mouse movement to the proper VM (one of of which is
the 16-bit shell - known as the desktop), to the rather more impressive
archievements of simulating the display device, sound card and DMA
channels well enough to allow applications written with almost exclusive
access to the machine in mind, to run properly.
(* VMware, Qemu and similar virtual machine applications do exceed the
virtualisation in Win9x, but they are applications dedicated to that task,
rather than general purpose operating systems)
NT/2K/XP falls short, after all the years they've had to get the job done,
and with full access to tried and tested reference implementations (namely
the Win9x source code)! Perhaps we're supposed to view these
deficiencies, whether due to lack of ambition or lack of skill, as reasons
for "upgrading" to one of those systems, just as we're supposed to
regard an ever richer "legacy" as a bad thing.
Not that Win9x or any other OS from Redmond or other sources is
perfect. For example, the limitations of the 16-bit core Win3.x/9x
components are real, bugs are hiding in all layers of the system,
the hardware support is rapidly getting outdated (as others have
mentioned), an additional or reivsed file system is needed, many
parameters that should be configurable are actually fixed, and so on...
but that's still a lot easier to fix than Microsoft's supposed successor
OSes would be - imagine weeding through 7 GB to find the scattered
pieces that might be worth preserving!
QUOTE (-I-)

ever tried multi-treaded aplications (true multi-treading like cad).
I tried Autocad once... whether it was multi-threaded I don't know.
I also wrote my own multi-threading kernel, resulting in an ~820 byte
DOS .COM-file that I successfully verified the proper operation of in a
Win98 DOS box. Vista would certainly crumble under such heavy load.
Furthermore, if you load a kernel debugger, such as Soft-Ice or
WDEB386 (comes with the DDK), you can view system state
information about active threads and VM (each VM contains at
least one thread, in addition to other resources).