slowing down hd for win2000
Banned
Joined: Mar 2002
Posts: 6,193
Likes: 0
Re: slowing down hd for win2000
Originally posted by TriniSpeed
I have to reboot about 3 times for my computer to turn on. I just installed win2000. I was told that my hd is to fast for win2000. How do I slow it down to resolve this problem?
I have to reboot about 3 times for my computer to turn on. I just installed win2000. I was told that my hd is to fast for win2000. How do I slow it down to resolve this problem?
Thread Starter
Senior Member
Joined: May 2002
Posts: 347
Likes: 0
I think I may have word it wrong. I believe I have 256mb of mem and a 20 gig western digital hd. When I shut down it takes forever to save settings. I was told that the hardrive is shutting the comp down before saving all settings. So whenI reboot the computer it freezes because it is missing files. I reboot about 3 or 4 times then the hd check comes on after the startup screen. It then runs a test and finds stray files and place them into a found.00 folder in windows explorer.
w00t
Joined: Mar 2000
Posts: 7,749
Likes: 0
Win2000 taking a longer time to shut down is "normal"...in some cases. Though I find it hard to believe that it would have missing files on boot up. I did have a problem like this a while back, turns out I had bad RAM....so the files loading up into the RAM on boot were corrupted...removed the bad RAM chip....reinstalled 2k and I was good to go 
__________________
Jimmy
Team B.O.B.™ - Ballaz on a Budget
R.I.P Huan Vo 11-19-2008
Jimmy
Team B.O.B.™ - Ballaz on a Budget
R.I.P Huan Vo 11-19-2008
Floppy Death! noES!!!
Joined: Oct 2002
Posts: 21,218
Likes: 0
From: Scranton, PA
TriniSpeed, sounds like just a poor installation of windows... or a hardware failure of some sort.
Nothing can be "too fast" for anything else. There are procedues built in telling hardware and software to wait if something is lagging behind. (ok this is just theoretical) So if your harddrive is actually writing faster than your processor and ram can give it info, things might get corrupt. But why? Because it's not possible to have a HD that fast, therefore they probably don't have any failsafes in place to tell the HD to wait for the CPU/RAM.
Even if you were running some insane RAID 0 on fiberchannel SAN it would still be slower than most CPU/RAM setups can "potentially" work.
I'd start with a fresh install of windows.
Nothing can be "too fast" for anything else. There are procedues built in telling hardware and software to wait if something is lagging behind. (ok this is just theoretical) So if your harddrive is actually writing faster than your processor and ram can give it info, things might get corrupt. But why? Because it's not possible to have a HD that fast, therefore they probably don't have any failsafes in place to tell the HD to wait for the CPU/RAM.
Even if you were running some insane RAID 0 on fiberchannel SAN it would still be slower than most CPU/RAM setups can "potentially" work.
I'd start with a fresh install of windows.
Member
Joined: Apr 2003
Posts: 165
Likes: 0
Better yet is your version of W2k a Warez version because ive known some people that put "extra" files in there that will **** up your O/S. If so look for a legit version to copy from some one...or if your willing to spend the cash buy one. And W2K is slow booting up and saving, the only O/S thats fast bootup and shutdown is WinXP because it saves your hardware config so it doesnt require it to check your hardware everytime. But Xp suxxors as far as secuirty issues go so its your choice.
