XP install is going slooooooooowwwwwww...why?

[Tullphan]

I wasn't aware that Raptors came in different flavors, but nevertheless........
This is the first time i've tried implementing a SATA device. It isn't hooked up in a raid array. I installed the appropriate drivers when prompted to during the XP installation & the drive partition (or lack thereof) was recognized. The drive is also recognized upon bootup.
My last try at reinstalling XP (after the 2 hour episode the led to nothing) has me getting the following message during the file copying portion of setup: Section Files.SCSI.Ulsata_NT5 of the INF file is invalid.
I think i'm done with the Raptor. I don't think the performance benefit (if any) is worth the 14 hours i've put in today to figure out driver issues, etc.

 

[ActuaryTm]

Originally posted by: Tullphan
I wasn't aware that Raptors came in different flavors, but nevertheless........

Not certain how that applies to the previous response. The confusing portion was that fact that the known variables were not stated, and thus all the variables were assumed unknown (ie, a machine build from scratch, and never before implemented). Knowing that particular portions of the equation that are known (again, that the system had run prior with a different drive on a different interface) would have most likely limited the conjecture offered earlier as possible steps to proceed with next.

Section Files.SCSI.Ulsata_NT5 of the INF file is invalid.

Driver issue with the SATA controller. Either not loaded correctly, somehow corrupt, etc. Would delete the partitions, reformat and reload the original driver at the appropriate time (F6 immediately after booting to CD/boot disc, then "S"), or perhaps look for an updated driver for the controller. There should be .INFs for both a single drive and RAID implementation, of course - make certain to have the right one. Could still be a faulty drive of some type, but chances are with that type of error message, is most likely driver related.

Good luck.

 

[justinian1978]

You mentioned that you're using the Asus K8V SE Deluxe, right? That board has 2 different SATA controllers on-board--VIA and Promise. Which one are you using?

 

[Tullphan]

I tried them both, but i've now given up & sent the hard drive back. I don't think the slight performance gain for my usage is worth the aggravation. Perhaps i'll try again another time...maybe after medication...hehehe.

 

[DietDrThunder]

Try going into the bios and changing the memory timings back to "Normal" instead of "Fast". Also try disabling the video shadowing. I had a very hard time loading XP Pro last weekend without tweeking the bios.

 

[Submit]

Originally posted by: Tullphan
Have restarted 3 different times since last post. It keeps saying a file can't be found (& don't ask which one because it varied each time).

This usually means that the hard drive is bad, or possibly the cables.


I've used both optical drives & switched the power connector from the SATA adapter to the "regular" power connector.
Each time I restart, it starts out great, till it gets to about 3%, then it goes into "how slow can I go" mode.
Disheartening. 🙁
Has anyone here who owns a K8V SE Deluxe had the same problem?

 

[Tarrant64]

I have a K8VSE with raptors as well. Had a problem during install, tried again. Went by just fine. I have seen other PC's though quit during installation and what I noticed is the cd-rom drive just quit reading. Crazy stuff.

Anyways,
Make sure that you have all the drivers you need installed for that SATA drive. you should be able to copy SATA drivers for either chipset(cause there's two, Via and Promise or something like that) for SATA. Install those before installing windows(F6 at the first windows screen I believe). Then continue with the installation. Also, you coul've rest the bios all together. Sometimes when putting in new Hardware it is good to just clear everything out and let it detect everything from the ground up instead of freaking it out with something missing and something new. Sorry I didn't post sooner. Missed the threat. Also sorry you had to send it back. I personally don't believe it was a CD-ROM issue or a HD issue, besides the SATA drivers part.