[septic]

I took the old c drive (sata) from my cousin's computer and installed it into his new gateway with Vista64bit. Went smooth. Unplugged old c from new motherboard\psu. Then msconfig>unchecked everything>restart. First I knocked out his button to open the dvd drive. That was a IObutton in msconfig. restarted>Fixed that. Then the green light on the case runs non-stop? still doing it today. I checked his purchased Kapersky - wasn't running a virus scan, but was running 20-27,000k>taskmanager>processes. Malwarebytes wasn't running. I couldn't tell in Vista64 if it was actually defragging but proir to the "constant light" we did defrag. Couldn't tell then, either, what defrag was doing. There were 60 processes running origanally then we reduced it to high 40's. I just expected more (faster browsing) from a 64bit OS with amd4x 2.4ghz and 8 gigs ram.

[Mak213]

The problem is the fact that the OS wasnt reinstalled. Windows has a specifc hardware profile setup when installed. It installs the proper drivers for that hardware.

By switching machines, you do not have the proper drivers anymore. Reinstall and you will see a noticeable difference.

[septic]

even though the new gateway noticed the old c as a d drive it still goofed up the drivers? I will check the drivers for currency. ty mak

[Mak213]

The chipset drivers which control the mother board and allow the mobo ans OS to communicate properly are not going to match.

[septic]

The problem seemed to work itself out. The running c drive (constant blinking green light) ended up being a whole lot of services running in msconfig. I took someone with me that knows more than I and he checked the drivers as you suggested. They seemed to be ok. Luckily there were no jumpers on either hard drive installed. He mentioned Kapersky can be set up to run every start-up. Vista64 was using 1.2 gigs of ram. I still would like to know when defrag starts where can a user see what its doing like in 32bit XP. Thanks again Mak for helping us diagnose this.