DriverPacks.net Forum - need help in integrating sata ahci drivers on nforce630i

Re: need help in integrating sata ahci drivers on nforce630i

2008-02-11T03:18:44Z

i've tried this with a fresh copy. but it still can't detect my sata drive during install.

Re: need help in integrating sata ahci drivers on nforce630i

2008-02-09T02:58:46Z

please read this
(Rightclick, open in new window)
http://forum.driverpacks.net/viewtopic.php?id=2374

Jeff is coding Base at the moment, and we had many sessions in MSN where we banged sherlock's and watson's heads together.
One of the reasons some people have a messed up an install source is that many users were led to believe that Base cleans up previous slipstreams quite nicely.
Well, that is NOT a fact. To the contrary. It left files behind from the old slipstream which can mess up the new slipstream and most often this is undetected because it still works.
The people reporting issues and many (if not all) experienced testers would start fresh when they felt that they needed a clean fresh source, and I assume all experienced users know that it is not a good idea to repeatedly slipstream different packs to a previously slipstreamed source.

Base is not bad when it is used with prudence.
Mass storage has seen drastic changes, and we all learned.
What I learned yesterday has had me make new test files.
The latest I have was extensively tested in method 2.
The advisory post I linked to tells you what not to do.
The Tut in my signature will soon get updated.

fixes in this new testpack are like this.
I removed &CC_0101 (and 104) mode tags where they would cause a BSOD.
(YEP... I thank the poster whom proved to us that mode-tagging cannot be done after subsys_*)

Note to Frequenzy; One of the affected HWIDs was a Nvidia.
Note to myself, I probably did that to avoid a duplicate.. I have to again CHECK dupes.

Via drivers have issue too.
Hey, they usually had. It worked fairly well until we had updates available..
I have to get to bed.
I will upload a 8029 tomorrow.

Re: need help in integrating sata ahci drivers on nforce630i

2008-02-09T01:26:40Z

thanks for the response. yes textmode is checked.

here's the log file

2008-02-09 08:55:16 :  DriverPacks BASE 7.05.2 initialized.
2008-02-09 08:55:16 :  Host environment: WIN_XP Service Pack 2 on X86 CPU.
2008-02-09 08:55:16 :  Created temporary working directory.
2008-02-09 08:55:16 :  Imported proxy settings from Internet Explorer.
2008-02-09 08:55:16 :  Start scanning for DriverPacks for the wnt5_x86-32 platform.
2008-02-09 08:55:16 :  	Detected DriverPack Chipset 7.10.1!
2008-02-09 08:55:16 :  	Detected DriverPack MassStorage 8.01!
2008-02-09 08:55:16 :  	Could not detect any 3rd party DriverPacks.
2008-02-09 08:55:16 :  	Finished scanning.
2008-02-09 08:55:16 :  Detected settings file "D:\Utilities\DpackBase\DPs_BASE.ini".
2008-02-09 08:55:16 :  Windows XP Professional -  Retail SP2 detected.
2008-02-09 08:55:16 :  The platform wnt5_x86-32_disc will be used (which is the 'disc' installation platform for the OS family 'wnt5_x86-32').
2008-02-09 08:55:16 :  Imported settings from settings file.
2008-02-09 08:55:16 :   Initialized GUI.
2008-02-09 08:55:16 :   Created a list of all available language files.
2008-02-09 08:55:16 :   Set the last used language, English, as the GUI language.
2008-02-09 08:55:54 :   Saved settings!
2008-02-09 08:55:54 :   Closed GUI.
2008-02-09 08:55:54 :   Selected module: mod_slip_wxp_x86-32_disc_m2.
2008-02-09 08:55:58 :  Extracted DriverPack MassStorage to a temporary working directory.
2008-02-09 08:55:58 :  Removed all attributes from \I386.
2008-02-09 08:55:58 :  Deleted old DriverPacks.
2008-02-09 08:55:58 :  Deleted old method 2 related files.
2008-02-09 08:55:58 :  Restored original mass storage text mode driver DPTI2O.sys.
2008-02-09 08:55:58 :  Restored original mass storage text mode driver adpu160m.sys.
2008-02-09 08:55:58 :  Restored original mass storage text mode driver ALIIDE.sys.
2008-02-09 08:55:58 :  Restored original mass storage text mode driver mraid35x.sys.
2008-02-09 08:55:58 :  Restored original mass storage text mode driver dac2w2k.sys.
2008-02-09 08:55:58 :  Restored original mass storage text mode driver dac960nt.sys.
2008-02-09 08:55:58 :  Restored original mass storage text mode driver ultra.sys.
2008-02-09 08:55:58 :  Restored original mass storage text mode driver ql12160.sys.
2008-02-09 08:55:58 :  Deleted old DriverPack MassStorage text mode drivers.
2008-02-09 08:55:58 :  Restored \I386\winnt.sif.
2008-02-09 08:55:58 :  Restored \I386\txtsetup.sif.
2008-02-09 08:55:58 :  Restored \I386\dosnet.inf.
2008-02-09 08:55:58 :  Restored original setup: method 2 was used previously.
2008-02-09 08:55:58 :  Created necessary directory structure for method 2.
2008-02-09 08:55:59 :  Copied files necessary for method 2.
2008-02-09 08:55:59 :  Extracted files necessary for method 2.
2008-02-09 08:55:59 :  Deleted old presetup.cmd file from \I386.
2008-02-09 08:55:59 :  Created \I386\presetup.cmd file.
2008-02-09 08:55:59 :  Updated \I386\txtsetup.sif to support method 2.
2008-02-09 08:55:59 :  Updated \I386\dosnet.inf to support method 2.
2008-02-09 08:55:59 :  Copied DriverPacks to \OEM.
2008-02-09 08:56:08 :  Created QuickStream Cache for DriverPack MassStorage text mode drivers.
2008-02-09 08:56:08 :  Slipstreamed DP MassStorage text mode drivers using QuickStream Cache.
2008-02-09 08:56:10 :  Removed entries from \I386\txtsetup.sif that will be updated.
2008-02-09 08:56:10 :  Removed entries from \I386\dosnet.inf that will be updated.
2008-02-09 08:56:36 :  Updated \I386\dosnet.inf and \I386\txtsetup.sif to support DP MassStorage text mode drivers.
2008-02-09 08:56:36 :  Updated \I386\winnt.sif to support method 2.
2008-02-09 08:56:36 :  Updated DPsFnshr.ini to disable KTD.
2008-02-09 08:56:36 :  Updated \I386\winnt.sif's GUIRunOnce section.
2008-02-09 08:56:36 :  Slipstream finished in 41 seconds.
2008-02-09 08:56:38 :  Temporary working directory successfully deleted.
2008-02-09 08:56:38 : Program terminated.

hwids

=========== 
PCI Devices 
=========== 
PCI\VEN_10DE&DEV_056A&SUBSYS_1C3A147B&REV_A1\3&2411E6FE&0&21: Standard Enhanced PCI to USB Host Controller
PCI\VEN_10DE&DEV_056C&SUBSYS_1C3A147B&REV_A1\3&2411E6FE&0&40: Standard Dual Channel PCI IDE Controller
PCI\VEN_10DE&DEV_056D&SUBSYS_00000000&REV_A1\3&2411E6FE&0&50: PCI standard PCI-to-PCI bridge
PCI\VEN_10DE&DEV_07C1&SUBSYS_00000000&REV_A2\3&2411E6FE&0&00: PCI standard host CPU bridge
PCI\VEN_10DE&DEV_07C8&SUBSYS_1C3A147B&REV_A1\3&2411E6FE&0&1C: PCI standard RAM Controller
PCI\VEN_10DE&DEV_07CB&SUBSYS_1C3A147B&REV_A2\3&2411E6FE&0&01: PCI standard RAM Controller
PCI\VEN_10DE&DEV_07CD&SUBSYS_1C3A147B&REV_A1\3&2411E6FE&0&08: PCI standard RAM Controller
PCI\VEN_10DE&DEV_07CE&SUBSYS_1C3A147B&REV_A1\3&2411E6FE&0&09: PCI standard RAM Controller
PCI\VEN_10DE&DEV_07CF&SUBSYS_1C3A147B&REV_A1\3&2411E6FE&0&0A: PCI standard RAM Controller
PCI\VEN_10DE&DEV_07D0&SUBSYS_1C3A147B&REV_A1\3&2411E6FE&0&0B: PCI standard RAM Controller
PCI\VEN_10DE&DEV_07D1&SUBSYS_1C3A147B&REV_A1\3&2411E6FE&0&0C: PCI standard RAM Controller
PCI\VEN_10DE&DEV_07D2&SUBSYS_1C3A147B&REV_A1\3&2411E6FE&0&0D: PCI standard RAM Controller
PCI\VEN_10DE&DEV_07D3&SUBSYS_1C3A147B&REV_A1\3&2411E6FE&0&0E: PCI standard RAM Controller
PCI\VEN_10DE&DEV_07D6&SUBSYS_1C3A147B&REV_A1\3&2411E6FE&0&10: PCI standard RAM Controller
PCI\VEN_10DE&DEV_07D7&SUBSYS_00000000&REV_A2\3&2411E6FE&0&18: PCI standard ISA bridge
PCI\VEN_10DE&DEV_07D8&SUBSYS_1C3A147B&REV_A1\3&2411E6FE&0&19: NVIDIA nForce PCI System Management
PCI\VEN_10DE&DEV_07D9&SUBSYS_1C3A147B&REV_A1\3&2411E6FE&0&1A: PCI standard RAM Controller
PCI\VEN_10DE&DEV_07DC&SUBSYS_1C3A147B&REV_A2\3&2411E6FE&0&78: NVIDIA Network Bus Enumerator
PCI\VEN_10DE&DEV_07E1&SUBSYS_1C3A147B&REV_A2\3&2411E6FE&0&80: NVIDIA GeForce 7100 / NVIDIA nForce 630i
PCI\VEN_10DE&DEV_07F0&SUBSYS_1C3A147B&REV_A2\3&2411E6FE&0&70: Standard Dual Channel PCI IDE Controller
PCI\VEN_10DE&DEV_07FC&SUBSYS_1C3A147B&REV_A1\3&2411E6FE&0&48: Microsoft UAA Bus Driver for High Definition Audio
PCI\VEN_10DE&DEV_07FE&SUBSYS_1C3A147B&REV_A1\3&2411E6FE&0&20: Standard OpenHCD USB Host Controller
22 matching device(s) found.
 
=========== 
USB Devices 
=========== 
USB\ROOT_HUB\4&34FDF0F5&0                                   : USB Root Hub
USB\ROOT_HUB20\4&352E6EA5&0                                 : USB Root Hub
USB\VID_3538&PID_0054\00000000000102                        : USB Mass Storage Device
USBSTOR\DISK&VEN_GENERIC&PROD_USB_FLASH_DISK&REV_0.00\00000000000102&0: Generic USB Flash Disk USB Device
4 matching device(s) found.
 
============= 
Input Devices 
============= 
No matching devices found.
 
============ 
ACPI Devices 
============ 
ACPI\FIXEDBUTTON\2&DABA3FF&0                                : ACPI Fixed Feature Button
ACPI\GENUINEINTEL_-_X86_FAMILY_6_MODEL_23\_0                : Intel(R) Core(TM)2 Duo CPU     E8200  @ 2.66GHz
ACPI\GENUINEINTEL_-_X86_FAMILY_6_MODEL_23\_1                : Intel(R) Core(TM)2 Duo CPU     E8200  @ 2.66GHz
ACPI\PNP0000\4&3469FA3D&0                                   : Programmable interrupt controller
ACPI\PNP0100\4&3469FA3D&0                                   : System timer
ACPI\PNP0103\4&3469FA3D&0                                   : High precision event timer
ACPI\PNP0200\4&3469FA3D&0                                   : Direct memory access controller
ACPI\PNP0303\4&3469FA3D&0                                   : Standard 101/102-Key or Microsoft Natural PS/2 Keyboard
ACPI\PNP0800\4&3469FA3D&0                                   : System speaker
ACPI\PNP0A08\1                                              : PCI bus
ACPI\PNP0B00\4&3469FA3D&0                                   : System CMOS/real time clock
ACPI\PNP0C01\2&DABA3FF&0                                    : System board
ACPI\PNP0C02\1                                              : Motherboard resources
ACPI\PNP0C02\4                                              : Motherboard resources
ACPI\PNP0C02\5                                              : Motherboard resources
ACPI\PNP0C04\4&3469FA3D&0                                   : Numeric data processor
ACPI\PNP0C0B\2&DABA3FF&0                                    : ACPI Fan
ACPI\PNP0C0C\2&DABA3FF&0                                    : ACPI Power Button
ACPI\PNP0C14\NVIF                                           : Microsoft Windows Management Interface for ACPI
ACPI\PNP0F13\4&3469FA3D&0                                   : PS/2 Compatible Mouse
ACPI\THERMALZONE\THRM                                       : ACPI Thermal Zone
ACPI_HAL\PNP0C08\0                                          : Microsoft ACPI-Compliant System
ROOT\ACPI_HAL\0000                                          : ACPI Multiprocessor PC
23 matching device(s) found.

Re: need help in integrating sata ahci drivers on nforce630i

2008-02-08T16:03:34Z

Sure do, that was just meant as an FYI post to provide a little more info for the intrigued user

Basically, it's good to use AHCI if you can but not too bad to not use it if you can't

Re: need help in integrating sata ahci drivers on nforce630i

2008-02-08T11:29:06Z

we still have to find out wether frequenzy ticked ON and TXTmode and mass storage when he integrated.

Re: need help in integrating sata ahci drivers on nforce630i

2008-02-08T08:52:38Z

AHCI does not only offer hot-plugability.

Basically, the idea was to create a unified driver architecture for HDDs so you actually wouldn't need to feed a manufaturer-specific driver during installation (just as it was in the good old dasy with standard IDE controllers).

Of course, this requires the OS to supply the unified driver, something which has not been implemented in XP, of course, due to its age (dunno if SP3 would bring such a driver if slipstreamed, haven't tried that myself).

IDK about nVidia in this case, but theoretically, this should solve our driver woes with them.
Seeing as AHCI is an invention by Intel, it may be that nVidia does not support it 100% by the book, though

Also, AHCI will ususally be needed to make NQC work with SATA drives.
Run them on a controller that uses the legacy setting in the BIOS and they will behave just like their IDE brethren so you gain nothing by using SATA (save the fragile plugs maybe...).

All in all, if possible, one should run in AHCI mode for best performance and compatibility (with up-to-date OSs that is), however, if not possible, reverting back to legacy mode in the BIOS is not that huge a loss to the ordinary user.
Just make sure to set the BIOS properly before you commence installation and do not switch it when an OS is installed unless you take precautious measures!
The HWID of the controller will change if you switch so you will have to have the proper drivers already installed on the OS or you get a BSOD.

Re: need help in integrating sata ahci drivers on nforce630i

2008-02-07T20:45:49Z

Hi,
Windows XP does not really support AHCI out of the box.
http://en.wikipedia.org/wiki/Advanced_H … _Interface

NVidia is one of the most difficult driver suppliers because they use same names and re-use HWIDs across different chipsets.
Speed tests I read show no real improvement compared to SATA with sigle drives (Far as I know, the chip is often set to RAID-mode for a single drive.)
With a single drive, why do you need hot-plug capability?

Re: need help in integrating sata ahci drivers on nforce630i

2008-02-07T13:35:25Z

Did you check the option for TextMode support in the BASE?
That is imperative!

Also, please post your HWIDs (see my sig) rather than just the names of your HW.

need help in integrating sata ahci drivers on nforce630i

2008-02-07T05:33:33Z

here's my hardware
- abit i-n73hd (nforce630i)
- 320GB seagate sata
- win xp 32bit

on the bios settings i chose AHCI mode for the sata drive. i've used the latest mass storage drivers and driverpack dbase. integrated it using method 2. but after xp cd loaded the drivers it didn't detect my sata drive :-(

i want to do this because i don't have a floppy drive for the f6 installation. thanks.