Weird eSATA Bug

[Frogg]

I can't get Windows to recognize my external hard drive using the eSATA interface. It's like plug and play doesn't work for it. I have to manually refresh the device manager, and then it picks it up

I have a feeling it's something with SP3, and with something I might have taken out. I always nlite my XP's the same way, so I'm pretty sure it's something weird in SP3.

I have an nvidia 680i sli board. A sata cable running to one of my onboard sata ports, and then an esata bracket for the back so I can use my external hard drive that way.

I have attached my nlite configuration.

Also at first I thought it was a chipset driver issue. I used some modified chipset drivers at first, and then I also tried the official from nvidia, and the same things.

Cheers for the help!

LAST_SESSION.INI

[TranceEnergy]

Check logical disk manager = automatic, check drive optimized for fast removal, alternatively try with ahci disabled/enabled (ahci needs drivers).

Also some drives come with jumpers in place. If so, check into that as well. I dont use any jumpers on drives, all sata.

[Frogg]

Check logical disk manager = automatic, check drive optimized for fast removal, alternatively try with ahci disabled/enabled (ahci needs drivers).

Also some drives come with jumpers in place. If so, check into that as well. I dont use any jumpers on drives, all sata.

Logical Disk Manager is set to Automatic.

The settings for Fast Removal, Performance are greyed out. I can't change them.

I have no option in my Bios to use AHCI. Which I know is for hot swap support.

I've never had jumpers on my drive.

I can't figure it out, but it's definitely something with SP3 + nLite combination.

Anywho back to using USB for now

[TranceEnergy]

The only 2 things in you last session i dont normally do is the duplicate removal and merging of the .cab files.

I can remove pretty much anything on x64 and everything works, stripped to bare internet only (no lan, need 3party tools).

I would try without checking them two options. Or possibly check you have clean xp source for sp slipstream.

It could also be some peripheral you have need integrated xp drivers.