Originally posted by: bsobel
I was actually thinking new machine with the 98 code running in a vm. The reason for them to do it is to actually have a backup of that environment. When that eventually crashes they might have more trouble getting it back running than booting up a backup vm image.... (IMHO)
Either that, or use Ghost 2003 regularly to make backup images of a working install.
A couple of other bonuses with Win98: 1) no "activation" hassle. 2) Much easier to move a complete working installation between motherboards/computers. Can always drop down to using Int13h extensions for the HDs (aka "MS-DOS mode"), without fear of a BSOD from not having the proper IDE controller driver loaded as in W2K/XP.
The downside, and probably the strongest reason for running Win98 in a VM - the code is old and crufty, and tends to have strange issues from modern machines. (CPU too fast, too much RAM installed, etc.) Running it in a perhaps more-compatible VM could help with those limitations.
I really wish that MS would release the full set of QFEs for Win98(se), even the non-public ones, once they drop official support for it.
I kind of like MS's VirtualPC myself, haven't tried VMWare yet.