They've come out with several newer VMWare releases since then, and I can't imagine that stability has worsened....

A while back, I ran Win2K under VMWare 2.0 on Linux and had problems as I was trying to keep a real multi-boot configuration (with Win2K pre-installed on a separate partition).

This time around, I decided to forego the multi-boot config and am running Win2K (for certain work apps) under VMWare Workstation 3.2 using a virtual disk and all is well. I'm even able to IPSec tunnel from Win2K over the VMWare virtual NAT and then a second (router NAT) to connect to work.

The only problem I can think of is that I don't know of a way right offhand to get it to run on bootup, as I don't know if VMWare will run without a display.

Interesting issue. I'll try it, but I expect you are right.

One problem. The Win2K virtual machine's clock is totally wacko. It will not sync with the Linux host nmachine through VMWare's BIOS. Using NTP from the Win2K guest OS (the workaround suggested by VMWare) does not work, at least for me. VMware says this will be fixed in version 4, but I want to know if I have to pay for an upgrade just for this bug fix! Anyhow, if Win2k clock/timestamps are important to your application, this might be an issue.