I have put together a new build based around my old Athlon 64 4000+. I was able to pick up an Asus A8V-VM SE board. I am using all the onboard stuff and picked up 2 gigs of OCZ value pc3200. I am using a 320GB Hitachi Deskstar SATA with an HP SATA DVD Burner.
Everything posted perfectly, and Windows seemed to install just fine. I did all of this on the day SP3 came out, so I had the installation file for that. I purchased a brand new oem of XP with SP2 for the machine, so it already has SP2 on it. When I attempted to install SP3, I would get prompts saying it couldn't find such and such file. I was able to find those files fine, but the installer couldn't. I unpacked the service pack in multiple locations, and was able to point it to another directory if it couldn't find the correct files. I was able to get it installed, but once I got back into windows ipconfig and most of the networking stuff wasn't working because of a missing dll file.
At first I figured no big deal, the service pack was recalled. So I formated and tried again, this time sticking with the default SP2. I noticed issues again when Acrobat Reader would not install properly. After rebooting it installed fine. But if I would be running a few other programs, It would load and then crash instantly. Rebooting and running it by itself and it was perfectly happy. I also seem to have the machine randomly tell me the NX part of the processor is shutting down certain processes to protect my computer.
After a trying multiple hard drives and cd drives(both SATA and PATA), I decided I would bring in another hard drive controller. I brought in my Promise TX 2650 SAS/SATA controller along with my Fujitsu SAS drive. Plugging it in, installed, and EVERYTHING worked exactly as it should. Acrobat Reader, SP3, was basically perfect. So I plugged back in the original Hitachi Deskstar in the SAS/SATA controller and installed Windows yet again on this drive. Once I got into Windows I started having the exact some problems I had had before. I changed the SATA cable and tried a Maxtor SATA drive, but same thing.
I am guessing there is some kind of error correction in the SAS/SCSI protocol that SATA/PATA drives do not have? This was the only reason I could explain why the SAS drive was the only one not to give any trouble. Overall this has been a very frustrating troubleshooting session. I am going to swap the motherboard out for another one to see if this alleviates the problems with regular SATA/PATA drives. Has anyone else experience similar issues or have any thoughts on this problem?
Everything posted perfectly, and Windows seemed to install just fine. I did all of this on the day SP3 came out, so I had the installation file for that. I purchased a brand new oem of XP with SP2 for the machine, so it already has SP2 on it. When I attempted to install SP3, I would get prompts saying it couldn't find such and such file. I was able to find those files fine, but the installer couldn't. I unpacked the service pack in multiple locations, and was able to point it to another directory if it couldn't find the correct files. I was able to get it installed, but once I got back into windows ipconfig and most of the networking stuff wasn't working because of a missing dll file.
At first I figured no big deal, the service pack was recalled. So I formated and tried again, this time sticking with the default SP2. I noticed issues again when Acrobat Reader would not install properly. After rebooting it installed fine. But if I would be running a few other programs, It would load and then crash instantly. Rebooting and running it by itself and it was perfectly happy. I also seem to have the machine randomly tell me the NX part of the processor is shutting down certain processes to protect my computer.
After a trying multiple hard drives and cd drives(both SATA and PATA), I decided I would bring in another hard drive controller. I brought in my Promise TX 2650 SAS/SATA controller along with my Fujitsu SAS drive. Plugging it in, installed, and EVERYTHING worked exactly as it should. Acrobat Reader, SP3, was basically perfect. So I plugged back in the original Hitachi Deskstar in the SAS/SATA controller and installed Windows yet again on this drive. Once I got into Windows I started having the exact some problems I had had before. I changed the SATA cable and tried a Maxtor SATA drive, but same thing.
I am guessing there is some kind of error correction in the SAS/SCSI protocol that SATA/PATA drives do not have? This was the only reason I could explain why the SAS drive was the only one not to give any trouble. Overall this has been a very frustrating troubleshooting session. I am going to swap the motherboard out for another one to see if this alleviates the problems with regular SATA/PATA drives. Has anyone else experience similar issues or have any thoughts on this problem?
Facebook
Twitter