I know that there in the west of Ireland that we are having severe problems with Fujitsu drives, especially ones beginning with the serial MPG3. The drives seem to have been giving up the ghost in high numbers for the past 6 months. (ie: in September, one site that had 15 PCs suddenly had 3 hard drives go in a period of 5 days...all three were Fujitsu with that serial number.) I seem to be receiving a call about once every two weeks now about a failed drive, and the majority of them have been Fujitsu ones...
Fair enough. If SP2 is working grand, don't bother upgrading (well, the clients at least...I would definitely upgrade servers to SP3 for security's sake). The compatibility packages could be downloaded as a seperate download for both XP and Win2K, but are now included both of their latest service packs.
Did you install Win2K as a fresh install, or did you upgrade from NT4 to Win2K? Doing upgrades with any Windows product is notoriously buggy...try doing a fresh install if you hadn't.
Also, the "30 seconds to 20 minutes" logging in usually means a service failed upon booting. Check your event viewer, and check the System and Application logs to see which service failed. If it's a non-critical one, disable it, or lookup a solution at http://www.eventid.net or http://support.microsoft.com
I have to agree with the above poster and the poster who said that Windows 2000 requires tweaking, just like Linux. I have seen posts on Slashdot saying that they have to reboot Win2K every 30 minutes, and to be honest, these are either blatant trolls, the user doesn't know what they are doing, or it's a hardware problem.
If you are having major trouble with Win2K, do the following:
1) A clean install, formating your partition with NTFS. Don't bother using FAT32 anymore. NTFS will mark any bad sectors on your hard drive as 'unusable', while FAT32 will not.
2) Service Pack 3. I can not stress this enough. Microsoft has made a huge improvement to Win2K with this Service Pack, both security- and stability-wise.
3) Update-to-date hardware drivers. A lot of the time, freezing PCs are due to buggy version 1 hardware drivers. Download the latest up-to-date drivers.
I am an IT contracter for several companies, doing support mainly for Win2K desktops, and in all honestly, Win2K as a desktop is rock solid, not requiring constant reboots like the nightmarish Win9x's did. While WinXP does improve a great deal on security, I'm not really a big fan of it...too much overhead for pretty graphics in my opinion (yes, I know you can tweak it to use less resources, but none the less I'll take Win2K over XP any day).
The thing that sucks about Win2K (and XP) is the new EULA's, which is a legal problem, not a technical one.
Slashdot Mirror
I know that there in the west of Ireland that we are having severe problems with Fujitsu drives, especially ones beginning with the serial MPG3. The drives seem to have been giving up the ghost in high numbers for the past 6 months. (ie: in September, one site that had 15 PCs suddenly had 3 hard drives go in a period of 5 days...all three were Fujitsu with that serial number.) I seem to be receiving a call about once every two weeks now about a failed drive, and the majority of them have been Fujitsu ones...
Fair enough. If SP2 is working grand, don't bother upgrading (well, the clients at least...I would definitely upgrade servers to SP3 for security's sake). The compatibility packages could be downloaded as a seperate download for both XP and Win2K, but are now included both of their latest service packs.
Did you install Win2K as a fresh install, or did you upgrade from NT4 to Win2K? Doing upgrades with any Windows product is notoriously buggy...try doing a fresh install if you hadn't.
Also, the "30 seconds to 20 minutes" logging in usually means a service failed upon booting. Check your event viewer, and check the System and Application logs to see which service failed. If it's a non-critical one, disable it, or lookup a solution at http://www.eventid.net or http://support.microsoft.com
I have to agree with the above poster and the poster who said that Windows 2000 requires tweaking, just like Linux. I have seen posts on Slashdot saying that they have to reboot Win2K every 30 minutes, and to be honest, these are either blatant trolls, the user doesn't know what they are doing, or it's a hardware problem.
If you are having major trouble with Win2K, do the following:
1) A clean install, formating your partition with NTFS. Don't bother using FAT32 anymore. NTFS will mark any bad sectors on your hard drive as 'unusable', while FAT32 will not.
2) Service Pack 3. I can not stress this enough. Microsoft has made a huge improvement to Win2K with this Service Pack, both security- and stability-wise.
3) Update-to-date hardware drivers. A lot of the time, freezing PCs are due to buggy version 1 hardware drivers. Download the latest up-to-date drivers.
I am an IT contracter for several companies, doing support mainly for Win2K desktops, and in all honestly, Win2K as a desktop is rock solid, not requiring constant reboots like the nightmarish Win9x's did. While WinXP does improve a great deal on security, I'm not really a big fan of it...too much overhead for pretty graphics in my opinion (yes, I know you can tweak it to use less resources, but none the less I'll take Win2K over XP any day).
The thing that sucks about Win2K (and XP) is the new EULA's, which is a legal problem, not a technical one.