690G/ SB600 AHCI driver slipstreaming issue
Posted 16 January 2011 - 02:41 PM
So I can't decide which of the following 3 should this thread go into, so I'm posting it here...
1. Software, Hardware, Media and Games - Software Hangout
2. Unattended Windows Discussion & Support - Device Drivers
3. Microsoft Software Products - Windows XP
Ok I'm not flaming but after reading through, you will understand that either of microsoft or AMD has to be blamed for the following.
I read about the reduced wear'n'tear + power consumption (and possible speed increases) that AHCI offers, was excited and started to learn how to integrate AHCI drivers into a winXP setup. After a number of hurdles, i managed to get the device IDs, Dosnet.inf and Txtsetup.inf stuff fixed. The windows would install smoothly until after the setup completion and at the initial boot. It would just BSOD with a stop 0x0000007b error despite everything i could do to fix this boot issue. I even tried changing the SATA drive's port while switching to and from a 'standard' IDE non-ahci port, turning computer on & off while rebooting; also tried fixing the ARC bootloader setting from multi(0) to scsi(0) etc and no luck.
Meanwhile also tried bootlogging & safe modes but couldn't find an ntbtlog... Though after close examination of every text file in the installed folders, i came to know about Bootact and Bootsetup logfiles which showed that during GUI mode setup, windows couldn't copy the AHCI drivers and forces the controller as null device.
I have even tried using all the possible Device and subSystem IDs and forced them into Txtsetup.inf as well as ahcix86.inf but to no avail. I'm using the nLite's method to put them in NLDRV/001 folder under i386. I guess I have read too much on this topic and tried almost everything (i say almost, since someone *might* be able to help)
A purely nLited method did not work for a couple of times - so nLite is no-no. RAID slipstreamer fails to execute - I have multiple boot XPs - clean, fully loaded with softwares, tools, etc...have tried adding the EXE to date execution protection list etc etc
Either microsoft has it wrong somewhere (because customer is always right ) or the AMD's hardware (sb600) or its drivers are at fault somewhere.
I'm at the verge of jumping to a bad conclusion now that i have invested so many days on getting ahci to work. Any further help is greatly appreciated!
Posted 17 January 2011 - 11:05 PM
Driver Packs and the Base are compatible with nLite.
Posted 18 January 2011 - 02:02 PM
Posted 25 January 2011 - 09:38 AM
I'm currently going to use Slackware and Win7 which support the AHCI on my motherboard out of the box. I thank everyone for their inputs Cheers
- ← Driver utility to prepare drivers from PMQ file
- Device Drivers
- Can't Image due to different hdd controller driver →