Why are you running a server OS as a desktop? Why are you using such old code?
I'm not speaking for the OP, but in my own experience this typically comes up in Citrix / Terminal Server Environments where eventually, if you work on the platform long enough, a director or CIO will
order you to install a 16-bit legacy app even though performance will suffer. Given the current job market any response to the request other than "yessir" denotes brain damage.
Nothing like fighting through NTVDM and WowExec subsystems because some crappy accounting program written in Qbasic keeps polling the keyboard constantly for an interupt and pissing off 75 other users and slagging VMware.
So, while this is a messy example, it's an unfortunate common one and shows not all of you have as much experience with windows server as you think you do. In an ideal world you simply have the code re-written in VB by a bored script monky servant (intern), but it's not always viable. Trust me, I cringe less when I see a Malware thread show up in taskmger on a security scan than NTVDV / WowExec eating up a logical processor.
For the record, Server 2000 makes a killer, blisteringly fast and stable desktop OS *if* you are running 32-bit apps. 2003 doesn't.....matter of fact, I don't like 2003 much for anything other than SBS.
So, what happens when I type 'Sysedit' from a run prompt with Server 2008? Microsoft nurf that too?