I am finding that downgrading a machine from Vista to XP isn't as simple as FDISK/FORMAT.
Drivers.
Some machines such as the Gateway boxes use proprietary driver combinations for the Intel and iTE chipset combinations. I suppose the same grief exists with the JMicron controllers.
Dell is pretty good about making drivers easily available. HP/Compaq is not, and Gateway is pretty much "yer f*cked".
I just finished an HP Pavilion DV9803NR latop. What a root canal.
The overly-obsequious HP dip shit in Bangalore was completely useless once he figured out I was downgrading Vista to XP.
He was admonishing me for downgrading Vista when I mashed the chat Disconnect button.
Hey dip shit, I've got your Vista right here...
So.... I got the drivers the hard way, by grabbing all the HTML files for every Service Pack from 30000 to current via an FTP copy. On my local machine, I can GREP for all files with DV9000 in the text, and make a copy of those files. I can further filter those files by GREPing for "Vista" and deleting those copies.
Sorted in descending (most recent) order, I open each .HTM and see if it pertains to any of my problem devices. Even though I built the machine with the full complement of DriverPacks.Net files, I still had a number of bad devices. Taking the newest SPs (descending order) fixed all my problems.
As usual, start with Microsoft UAA first, and build from there.
Drivers.

Some machines such as the Gateway boxes use proprietary driver combinations for the Intel and iTE chipset combinations. I suppose the same grief exists with the JMicron controllers.
Dell is pretty good about making drivers easily available. HP/Compaq is not, and Gateway is pretty much "yer f*cked".
I just finished an HP Pavilion DV9803NR latop. What a root canal.
The overly-obsequious HP dip shit in Bangalore was completely useless once he figured out I was downgrading Vista to XP.
He was admonishing me for downgrading Vista when I mashed the chat Disconnect button.
Hey dip shit, I've got your Vista right here...

So.... I got the drivers the hard way, by grabbing all the HTML files for every Service Pack from 30000 to current via an FTP copy. On my local machine, I can GREP for all files with DV9000 in the text, and make a copy of those files. I can further filter those files by GREPing for "Vista" and deleting those copies.
Sorted in descending (most recent) order, I open each .HTM and see if it pertains to any of my problem devices. Even though I built the machine with the full complement of DriverPacks.Net files, I still had a number of bad devices. Taking the newest SPs (descending order) fixed all my problems.
As usual, start with Microsoft UAA first, and build from there.
Comment