Not all of them. Many *critical bugs* continue to go unfixed. And the first
service pack 2 that was released *nuked* people's hard drives. *shudder*.
We 'upgraded' to 3.51 and the crashes just got worse, so we backpedaled to
3.5. This is in agreement with postings on comp.os.ms-windows.nt.*.
> >all too often we have the "blue screen" crash and each time Microsoft tech
> >support shrugs their shoulders...
> We've NEVER had a "blue screen" crash. Are you sure you didn't have NT
> improperly configured?
Give me a break. Yes. I'm absolutely positive. We've been working with NT
for over 2 years on multiple machines, each with totally different hardware
configurations -- and the same result. C*R*A*S*H. Weekly, sometimes even
daily. And we find new and wonderful ways to crash NT all the time. Like
the aforementioned Visual C++ linker "nuke NT" bug we found this week.
We're migrating our development away from NT as we get time. It's simply
not stable. At least, we've never managed 100+ days uptime like we have on
Linux (and Linux is used more heavily!)
> >One other note.. a few months ago in boardwatch magazine there was an ISP
> >who was touting how he was "up and running without any Unix knowledge". Too
> >bad he doesn't even know how to configure his SMTP server... mail took *ONE
> >MONTH* to bounce from his machine, and when it finally came back, it was due
> >to an admin config error.
> Of course, this has nothing to do with NT's capabilities as an Internet OS.
Aside from NT's totally broken routing, I'll agree with you.
> >Just because you can click a mouse in program manager doesn't necessarily mean
> >you have a clue, or mean you can administrate an ISP.
> You're absolutely right. But it's nice to be able to hire round-the-clock
> support staff who can keep the system up and running and perform routine
> maintenance. With NT, we don't have to hire a bunch of CS majors to do this.
> Of course we have a CS major / Unix / NT / Internet wizard at our disposal
> (we'd be crazy not to), but we don't need him for day-to-day operations.
> Anyone with a basic knowledge of Windows and the Internet can set up mailing
> lists, configure the mail server, set up virtual Web servers, and perform
> numerous other tasks which would otherwise require an expensive Unix expert.
So when you have a router configuration problem, all the mouse clicking in
the world won't save your ass unless your NT "wizard" knows some CLI admin.
Does NT have gated? Ircd? Named (a full *WORKING* one that supports zone
transfers and round-robin addressing, not that crock that's in the resource
kit)? Can your mail server do programmable header rewriting?
Except for *THE MOST BASIC* ISP setups, NT is unsuitable. The lack of a
RADIUS port simply underscores this point.
-Dan