No, our systems are ghosted and identical and just don't crash often. Users are instructed to call the helpdesk when they crashed (EVERY time). They're plain-jane IBM machines running Windows 95 (standard installs, policied so they can't install other apps that can cause crashes). Most of the crashes are due to hardware and the machines are promptly fixed.
Maybe we're just lucky, but this is how I thought a network is supposed to be run.
The OS itself doesn't have memory leaks, that's just plain wrong. The OS used to, and they were patched. Poorly written applications do. Run away processes are easily killed with the "kill" application that can even kill system services.
Slashdotters often lament the intelligence of NT administrators as a whole, and I really don't fault them. I've seen what most are capable of, and that isn't much. I like to put myself above them in terms of capability, as I've admin'd everything from WFWG 3.11 to MacOS to FreeBSD. My machines don't crash, and if they do, I fix them. Isn't that what being an Administrator is about? If you can't do that job effectively...then look into another profession.
1) The ODBC vulernability doesn't affect you if you're current on MDAC components. MDAC 2.1 or 2.5 beta avoid this issue completely.
2) "30 odd flaws"? Care to list them all? I'm running NT 4.0 SP5 on an IBM laptop of all things, and it has never crashed once. And it's even running Novell Client32. Stay current on patches and drivers (just as you would in any other NOS) and there isn't a problem.
3) A real administrator would fix machines that have to be rebooted weekly. The quality of a NOS is only as good as the administrator and the hardware.
4) I have a home-built PII 450 sitting on my desk that's been running NT 4.0 ever since I put it together almost a year ago. It's crashed twice. Both times, I was running Unreal (yes, Unreal) in a window. And for some reason, I suspect that Unreal is the culprit in that one:)
I'm not advocating. I'm simply setting you straight.
Slashdot Mirror
How do you know there aren't any in Linux? Or UX? Or FreeBSD? Or any other OS? You only know what's documented.
Who said I lost 600 files a year? We do backups, the files are RESTORED.
No, our systems are ghosted and identical and just don't crash often. Users are instructed to call the helpdesk when they crashed (EVERY time). They're plain-jane IBM machines running Windows 95 (standard installs, policied so they can't install other apps that can cause crashes). Most of the crashes are due to hardware and the machines are promptly fixed.
Maybe we're just lucky, but this is how I thought a network is supposed to be run.
The OS itself doesn't have memory leaks, that's just plain wrong. The OS used to, and they were patched. Poorly written applications do. Run away processes are easily killed with the "kill" application that can even kill system services.
When a good admin implements it with solid hardware, NT is very stable. How's that?
-witz0r
And no one uses Quattro Pro.
I handle about 1500 users here in our LAN. I get two requests a day to restore a file. Two.
-witz0r
I've seen NT administrators set NT servers to run openGL screen savers. Then they wonder why they peg out and eat it.
Slashdotters often lament the intelligence of NT administrators as a whole, and I really don't fault them. I've seen what most are capable of, and that isn't much. I like to put myself above them in terms of capability, as I've admin'd everything from WFWG 3.11 to MacOS to FreeBSD. My machines don't crash, and if they do, I fix them. Isn't that what being an Administrator is about? If you can't do that job effectively...then look into another profession.
-witz0r
1) The ODBC vulernability doesn't affect you if you're current on MDAC components. MDAC 2.1 or 2.5 beta avoid this issue completely.
:)
2) "30 odd flaws"? Care to list them all? I'm running NT 4.0 SP5 on an IBM laptop of all things, and it has never crashed once. And it's even running Novell Client32. Stay current on patches and drivers (just as you would in any other NOS) and there isn't a problem.
3) A real administrator would fix machines that have to be rebooted weekly. The quality of a NOS is only as good as the administrator and the hardware.
4) I have a home-built PII 450 sitting on my desk that's been running NT 4.0 ever since I put it together almost a year ago. It's crashed twice. Both times, I was running Unreal (yes, Unreal) in a window. And for some reason, I suspect that Unreal is the culprit in that one
I'm not advocating. I'm simply setting you straight.