Originally posted by: BikeDude
Originally posted by: Genx87
Win98 for all the crap it went through wasnt terribly bad for stability if you took the extra time and money and bought quality hardware.
You are confusing dumb luck with quality.
The difference is staggering! I can crash any Win98 installation with less than a minute's keyboard work (open a command line, DEBUG, o 21 ff, or f 0:0 L ffff 00 will do nicely).
XP can be crashed too, but you need either faulty hardware or code running in kernel mode. The latter can only be achieved by installing a bad device driver. As a software developer writing application code there's precious little (i.e. nothing!) I can do to crash the system if the user isn't an administrator (can't install a device driver then, see?).
Show me user-mode code that crashes XP, and I'll bet MS will release a patch before long. That was never an option with Win98, because Win9x's whole purpose was provide backward compatibility thus giving the industry an upgrade path to a clean operating system: Windows NT (which eventually became XP, or NT 5.1 according to the GetVersion() API function). Win98 MUST remain easy to crash because of backward compatibility with 16-bit device drivers. There's no way for anyone to fix that. Other than upgrading to a NT class OS. All the quality hardware in the world can't disguise that.
There are other issues as well. E.g. Win98 impose some 16-bitish limitations on GDI and USER resources. Modern applications just won't run as smooth. Where I work we stopped testing for Win98 a while back. We still have some Win98 users, but it's just dumb luck that keeps our app humming along and it is noticably more limited than it would be running under NT. (our app really isn't a resource hog, but the users will want to set it up to display _a lot_ of information and eventually this eats into resources big time)