Horse Hockey (as you help point out)! You don't have to reboot if you use MS's builtin drivers for Tuke (aka Windows 2000, aka Win2K), which are crap. For example, the drivers for the NVidia TNT2 Riva video card. If you want to reinstall the OEM drivers, you need to reboot in order to get a clean and stable system. (I don't remember if it forced me to reboot or not). I admit that Tuke is more stable than NT, and it doesn't automatically swap out an application when it's minimized, but come on, MS! MS: Look at this revolutionary new product we've made. We call it "MS Wheel". It will allow you to reduce friction by ROLLING stuff around, instead of dragging them. THEM: Oooooooooh. I need that! US: We've had that for years. It's called (Unix, VMS, Geos, BeOS, NeXT, Amiga, etc)... Rich Jesse System/Database Administrator [EMAIL PROTECTED] Quad/Tech International, Sussex, WI USA -----Original Message----- Sent: Thursday, February 01, 2001 14:28 To: Multiple recipients of list ORACLE-L >From the URL: http://www.microsoft.com/windows2000/guide/professional/solutions/overview/r eliable/default.asp <http://www.microsoft.com/windows2000/guide/professional/solutions/overview/ reliable/default.asp> PCs Stay Up and Running Memory conflicts and missing or altered system files caused many of the system crashes prior to Windows 2000. To put an end to these problems, we changed Windows 2000 memory management to reduce the chance that software applications will interfere with one another. Applications runing in a seprate memory area...HMMMMMM Unix did that 15 years ago. Fewer Reboots Performing routine maintenance on your system requires significantly fewer reboots, therefore less downtime, with Windows 2000. In addition, with its support for Plug and Play, Windows 2000 automatically recognizes and adapts to hardware changes. This means users can easily add hardware devices such as scanners, DVD players, and speakers without rebooting, and with less potential for user error. Reboots are also reduced-and reliability increased-through the Microsoft hardware device driver certification program. This program helps ensure that hardware drivers are compatible with Windows 2000, and do not require a reboot after installation. Certified drivers are tested and digitally signed by Microsoft. If Windows 2000 detects a driver that Microsoft has not digitally signed, it warns users about the risk before they install it on their system <http://www.microsoft.com/windows2000/guide/professional/solutions/overview/ reliable/default.asp> ----------------------------------------------------------------------- This message has been scanned for viruses with Trend Micro's Interscan VirusWall.
Rich
Jesse
System/Database
Administrator
[EMAIL PROTECTED]
Quad/Tech International, Sussex, WI USA
-----Original Message-----
From: Rocky Welch [mailto:[EMAIL PROTECTED]]
Sent: Thursday, February 01, 2001 14:28
To: Multiple recipients of list ORACLE-L
Subject: RE: OT NT2K vs Unix.From the URL:
http://www.microsoft.com/windows2000/guide/professional/solutions/overview/reliable/default.asp
PCs Stay Up and Running
Memory conflicts and missing or altered system files caused many of the system crashes prior to Windows 2000. To put an end to these problems, we changed Windows 2000 memory management to reduce the chance that software applications will interfere with one another.
Applications runing in a seprate memory area...HMMMMMM Unix did that 15 years ago.
Fewer Reboots
Performing routine maintenance on your system requires significantly fewer reboots, therefore less downtime, with Windows 2000. In addition, with its support for Plug and Play, Windows 2000 automatically recognizes and adapts to hardware changes. This means users can easily add hardware devices such as scanners, DVD players, and speakers without rebooting, and with less potential for user error.
Reboots are also reduced-and reliability increased-through the Microsoft hardware device driver certification program. This program helps ensure that hardware drivers are compatible with Windows 2000, and do not require a reboot after installation. Certified drivers are tested and digitally signed by Microsoft. If Windows 2000 detects a driver that Microsoft has not digitally signed, it warns users about the risk before they install it on their system