>>Sounds like it was indeed some sort of config issue, but who knows? OS's are put on "new" machines using Ghost software so theoretically the 'ghost' containing several software items has been checked to install and operate properly. One thing we have seen here is the discombobulation of the 16-bit subsystem on some NT workstations here due to we do not know what. But whatever causes it, one it happens, ya can't run any 16-bit Windows programs. Which means a lot of Setup routines won't run cause apparently they're full of 16-bit code. :-)
>
>Yes, that is a big concern here. I wasn't the only one worried about our move to NT...we're having the "rollout" admin meeting in a few weeks , and then we'll have the option of moving our offices to NT anytime. But they've pushed back the "drop dead" date for conversion to the end of 2000, since so many are so worried about all our old but critical in-house apps. Most are out of DOS by now, but still a lot of 16-bit 3.1 stuff around...moving to NT is going to be a much bigger deal than Y2K, I'm quite certain. I'm still wondering if they'll just give up on the idea :)
>
>It was amusing to find that LAN's own inhouse user account app (to change passwords, check on expiration, etc., built in an older version of C++, I think) wouldn't run under NT. I had to report it, they forgot to test it :)

FWIW, we've been running NT4 on the desktops here ( >500 ) for two or more years and we really like it. We've had our problems, but (IOO) it is more stable than Win95 and probably Win98 too.