Sigmatel is one of those drivers, which must be pruned at first of all. I have an idea how to do it. Please wait a pair of days!


(2 replies, posted in News)

Wim Leers, no problem! smile

mr_smartepants, add please driver to next release of Graphics C... Download page - … p;lang=eng

Driver works on Windows XP.


(11 replies, posted in DriverPack Mass Storage)

And don't forget the holy war with nVida mass storage drivers in RAID and AHCI modes smile

Download a sav_HWID_HDAmodified.exe - … dified.exe
and post a hwids with hdaudio bus hwid too.

No feedback at all... I had to modify Sav_HWIDS.exe myself... … dified.exe


(6 replies, posted in Software)

Add HDAUDIO devices please. Like here -

Do you can to post hwids of your Acer M1641?

I think we are can't to do something without Adaptec ATA RAID 1200A Controller... Both of them, Adaptec ATA RAID 1200A and HighPoint HPT3xx ATA RAID builded on HPT3xx chip. I think, does support the Adaptec ATA RAID 1200A a driver from the HighPoint HPT3xx ATA RAID Controller or not?..

"get rid of it" - what it means? I can't to translate it to my native language.

Anonim1979, try to erase [AD] section


(76 replies, posted in DriverPack Mass Storage)

I wrote about that solution in my post - I will updating that post and place results of  tests that DP on all nforce mainboards, which I can found.

wolfi221268, that solution works for nvidia only, I think. I didn't work with ATi drivers.

You must do the changes if you want to get workable disc for your Acer Notebooks... Ideally, these changes must be used always when in inf file of driver is string like that:

HKR, "Parameters\PnpInterface", "5", %REG_DWORD%, 0x00000001

What about Base, all depends from Base programmers I guess...

Sound driver -
Modem driver -

I did check, all OK...

Anonim1979, please try this test DP - … 20only).7z
ms_1_deviceName="Adaptec ATA RAID 1200A Controller"
ms_1_deviceName="HighPoint RocketRAID 100/133 ATA RAID (HPT3xx)"

I guess you have one HDD on your controller? Do you can to create RAID with two HDD's with purpose of testing?

wolfi221268, try DP - [url] Pack/DP_MassStorage_wnt5_x86-32_810I (NV tests only).7z[/url]

All [NVx] sections was removed, and created one universal [NV] section:

ms_1_deviceName="NVIDIA NForce Storage Controller"
ms_2_deviceName="NVIDIA nForce RAID Class Controller"

After integrating of driverpacks with BASE, you need to do next changes manually:

1. Extract DP_MassStorage_wnt5_x86-32_810I (NV tests only).7z to temporary folder.
2. Copy NV_PnPinterface.cmd and NV_setupreg.reg to your platform folder (in that folder must be I386 folder).
3. Start NV_PnPinterface.cmd. In in I386 folder will be added next parameter:


It is necessary for correct textmode setup.
4. Open textfile HIVESYS.INF in I386 folder. Add next string to section [AddReg] manually (hint: that string is in NV_hive.txt):


It is necessary for correct graphic mode setup.

Burn a disc and try. Please post all results.

This is test DP works successfully on Asus M2N32-SLI Deluxe (nForce590SLI) and Gigabyte GA-M55plus-S3G v1 (nForce 430 (MCP51) ) in RAID and non-RAID modes.

OverFlow, I think we are integrate nforce drivers unproperly.

I posted continue.

JakeLD, it was an example only smile

Do you try to install drivers for HDA Codec or nForce Ethernet manually? To get access to HDA Codec or Ethernet card directly, we have to install drivers for HDA Bus (by KB888111.exe) or NVIDIA Network Bus Enumerator at first. These devices are Bus Extenders, i.e. some kind of switch. The idea (from some unattended forums) - NVRAIDBUS is Bus Extender too, and we are have to place all Extenders BEFORE all other RAID and AHCI hwids like a "PCI\...". TXTSETUP.OEM from one of randomly taken chipset drivers shows all clearly:


value = parameters\PnpInterface,5,REG_DWORD,1 ;(!)

; A HardwareIds.scsi.Service section specifies the hardware IDs of 
; the devices that a particular mass-storage driver supports. 
; [HardwareIds.scsi.Service]
; id = "deviceID","service"
; HardwareIds.scsi.Service 
;   Service specifies the service to be installed. 
; <deviceId > Specifies the device ID for a mass-storage device. 
; <service > Specifies the service to be installed for the device. 
;The following example excerpt shows a HardwareIds.scsi.Service section for a disk device:

id = "SCSI\NVIDIA__Raid_Disk________","nvrd32"
id = "SCSI\__NVIDIA_______Raid_Disk","nvrd32"
id = "SCSI\NVIDIA__Raid_Disk_20_____","nvrd32"
id = "SCSI\__NVIDIA____Raid_Disk_20","nvrd32"
id = "*_NVRAIDBUS","nvrd32"
id = "*NVRAIDBUS","nvrd32"
id = "*NVRAID20","nvrd32"

id = "PCI\VEN_10DE&DEV_0036", "nvgts" ; MCP04 SATA1
id = "PCI\VEN_10DE&DEV_003E", "nvgts" ; MCP04 SATA2
id = "PCI\VEN_10DE&DEV_0054", "nvgts" ; CK804 SATA1
id = "PCI\VEN_10DE&DEV_0055", "nvgts" ; CK804 SATA2
id = "PCI\VEN_10DE&DEV_0266", "nvgts" ; MCP51 SATA1
id = "PCI\VEN_10DE&DEV_0267", "nvgts" ; MCP51 SATA2
id = "PCI\VEN_10DE&DEV_036F", "nvgts" ; MCP55 OEM
id = "PCI\VEN_10DE&DEV_037E", "nvgts" ; MCP55 CHANNEL
id = "PCI\VEN_10DE&DEV_037F", "nvgts" ; MCP55 UNUSED
id = "PCI\VEN_10DE&DEV_03F6", "nvgts" ; MCP61 OEM
id = "PCI\VEN_10DE&DEV_03F7", "nvgts" ; MCP61 CHANNEL
id = "PCI\VEN_10DE&DEV_03E7", "nvgts" ; MCP61 NSIP
id = "PCI\VEN_10DE&DEV_044C", "nvgts" ; MCP65 RAID
id = "PCI\VEN_10DE&DEV_0558", "nvgts" ; MCP67 RAID, OEM
id = "PCI\VEN_10DE&DEV_0559", "nvgts" ; MCP67 RAID, CHANNEL
id = "PCI\VEN_10DE&DEV_055A", "nvgts" ; MCP67 RAID, NBP
id = "PCI\VEN_10DE&DEV_07B9", "nvgts" ; MCP72 RAID

BTW, pay an attention to value = parameters\PnpInterface,5,REG_DWORD,1. SamLab wrote about it - … 586#p25586. And many mentions about that registry key in forum...

Unfortunately, I can't to tell ALL my thoughts about PROPER integrating nvidia raid drivers to Windows. The language barriers sad. But I'll return to my post very soon, after some research wink. To be continued...

I'll continue... Without PnPInterface registry key Bus Extender will be initialized AFTER loading in memory. With that key it will be initialized AFTER locating appropriate device. All in English:

To support Plug and Play, a SCSI miniport driver must:

Be installed as a service for the HBA.
Have a PnPInterface entry in the registry that indicates the interfaces for that the miniport driver supports Plug and Play.

Installing a miniport driver as a service for a SCSI HBA is customarily done by providing an setup information (INF) file that matches the Plug and Play hardware ID for a given HBA to the correct driver to control that device. For details about setting up an INF file, see Plug and Play.

Unless a miniport driver is installed as a service for an HBA, the PnPInterface registry entry will prevent the miniport driver from initializing. The specified interfaces are initialized only when Plug and Play locates an appropriate HBA. If no service is properly assigned to the HBA, Plug and Play will never determine which driver to notify when it detects the device. This behavior is by design and a miniport driver should not attempt to circumvent it.

The PnPInterface registry entry should be made under the Services key for the miniport driver. For example, the following registry entry enables Plug and Play for a fictitious miniport driver called Twiddle.

5 : REG_DWORD : 1
1 : REG_DWORD : 1
2 : REG_DWORD : 1
8 : REG_DWORD : 1

The values preceding REG_DWORD correspond to the INTERFACE_TYPE enumerated type declared in miniport.h. The values in this example indicate that the Twiddle miniport driver supports Plug and Play for the following interfaces: PCIBus (5), Isa (1), Eisa (2) and PCMCIABus (8). The value following REG_DWORD is a flag that indicates Plug and Play support for the interface. (Currently, this flag can be any value but must be present. In the future, the flag may be optional.)

After the PnPInterface values are set in the registry and the system is restarted, the miniport driver can be initialized as a Plug and Play driver. During initialization, the SCSI port driver checks the registry to determine whether the miniport driver should be run as a Plug and Play or legacy driver. The SCSI port driver checks the registry for each interface type that the miniport driver supports (for example, PCI and ISA). This is intended primarily to simplify debugging for writers of multiple-interface miniport drivers. The miniport driver writer should make sure that a miniport driver is capable of being run as a Plug and Play driver for all interfaces that driver supports.

I suggest to add in code of save_HWIDs.cmd next lines:

ECHO ============ >> %Out%
ECHO  HDA Audio >> %Out%
ECHO ============ >> %Out%
DEVCON find hdaudio* >> %Out%
ECHO. >> %Out%


(12 replies, posted in DriverPack Sound)

SamLab, I have some feedback from my users too. I did SFX archive and .cmd file in it, which start Everest with saving of ferrum configuration of computer, saves setupapi.log file, save hwids (save_hwids tool), all logs of finishers and many other... And users mail results to me. Can you do so tool and do you give us more information in future?


(107 replies, posted in 3rd Party DriverPacks)

RogueSpear, if .inf file contains *PNP0303 or *PNP0213 (or other compatible with PS/2), that driver will install on any keyboard PS/2 or mouse PS/2. But if you'll chop out all standard PS/2 HWIDS, signing will break, and driver not install at all sad