Hi OverFlow
There are Hundreds of duplicate HWIDS has been removed in DP_Sound_B_wnt5_x86-32_71103_nightly, I think all should be remain especially BTW the different manufactory
2 2007-11-14 17:37:16
Re: [REQ] hwid fix (97 replies, posted in DriverPack Sound)
Hi dolivas
You have the same problem now, If just resume the HWID "PCI\VEN_1039&DEV_7012&SUBSYS_810D1043" to D/S/SM/A/3/0 (Sound B) and remove it in (Sound A) D/S/R/1/ (alcxauiz.inf) , The realtek device it's HWID is "PCI\VEN_1039&DEV_7012&SUBSYS_810D1043" will have problem.
3 2007-11-13 16:35:06
Re: [REQ] hwid fix (97 replies, posted in DriverPack Sound)
So how to fix the problem in my example, and there are lots of similar problem in DP_Sound_B_wnt5_x86-32_71103_nightly.
We can share the soure code with DriverPacks to improve the driver’s compatibility. It is the better way to slove the problem in my mind?
4 2007-11-13 14:06:28
Re: [REQ] hwid fix (97 replies, posted in DriverPack Sound)
For example?ECS 845GV-M2 ALC655 with HWID “PCI\VEN_8086&DEV_24C5&SUBSYS_18881019†will install zhe driver of SoundMAX Integrated Digital Audio.
We have done the same job and improve it's not the best way, So we change to use a tool (base on EVEREST) to distinguish the Manufacturer of device and decompression the right driver pack
In this example the tool will decompression the driver pack named realtek.7z, The driver pack soundmax.7z will keep in compressed, So windows will automatically install the right driver of realtek.
5 2007-11-13 01:59:30
Re: [REQ] hwid fix (97 replies, posted in DriverPack Sound)
To delete the duplicate HWIDS is not a good idea which will caused a series of problem:
1. The duplicate of the HWID of different manufacturer. Suppose the HWID of
a soundmax card is dupicated with the HWID of a realtek driver, then if the HWID in the soundmax is deleted, the WINDOWNs may install the realtek driver automally, as both of them are of AC97 standard, which mean they are compatible, while not all of them are compatible, which may cause BSOD.
2. The duplicate of the HWID of same manufacturer. I once came across some soundmax card, special version are required to apply.
Windows possess a function that it will choose proper driver to be installed. It will make comparison among different version of drivers and choose the most suitable one. Althougn this function cannot always find the one we need, at least we wont be too worried that the drivers are installed improperly.
Our method to slove this problem?
First we pack drivers from different manufacturer respectively(e.g.realtek.7z soundmax.7z via.7z c-media.7z), then we use a tool based on EVEREST to tell different manufacturer and then extract the proper driver. In this case, the problem caused by the duplicate of HWIDS will be avoided.
6 2007-11-12 17:58:40
Re: [REQ] hwid fix (97 replies, posted in DriverPack Sound)
To delete the duplicate HWIDS is not a good idea which will caused a series of problem:
1. The duplicate of the HWID of different manufacturer. Suppose the HWID of
a soundmax card is dupicated with the HWID of a realtek driver, then if the HWID in the soundmax is deleted, the WINDOWNs may install the realtek driver automally, as both of them are of AC97 standard, which mean they are compatible, while not all of them are compatible, which may cause BSOD.
2. The duplicate of the HWID of same manufacturer. I once came across some soundmax card, special version are required to apply.
Windows possess a function that it will choose proper driver to be installed. It will make comparison among different version of drivers and choose the most suitable one. Althougn this function cannot always find the one we need, at least we wont be too worried that the drivers are installed improperly.
Our method to slove this problem?
First we pack drivers from different manufacturer respectively(e.g.realtek.7z soundmax.7z via.7z c-media.7z), then we use a tool based on EVEREST to tell different manufacturer and then extract the proper driver. In this case, the problem caused by the duplicate of HWIDS will be avoided.
7 2007-10-13 13:00:09
Re: [Final] Mass Storage 711 (36 replies, posted in DriverPack Mass Storage)
Hi Jaak,
In my test,I did not use the DriverPack_MassStorage_wnt5_x86-32.ini file.
So just edit this ini file will not slove this error in sysprep.
It seems like the ViPrt.inf not support to be used by sysprep.
;[V-4]
PCI\VEN_1106&DEV_3149&CC_0101=C:\sysprep\M\V\4\ViPrt.inf
PCI\VEN_1106&DEV_3349&CC_0101=C:\sysprep\M\V\4\ViPrt.inf
PCI\VEN_1106&DEV_0581&CC_0101=C:\sysprep\M\V\4\ViPrt.inf
PCI\VEN_1106&DEV_0591&CC_0101=C:\sysprep\M\V\4\ViPrt.inf
PCI\VEN_1106&DEV_5287&CC_0101=C:\sysprep\M\V\4\ViPrt.inf
PCI\VEN_1106&DEV_5324&CC_0101=C:\sysprep\M\V\4\ViPrt.inf
PCI\VEN_1106&DEV_5337&CC_0101=C:\sysprep\M\V\4\ViPrt.inf
PCI\VEN_1106&DEV_5372&CC_0101=C:\sysprep\M\V\4\ViPrt.inf
8 2007-10-12 19:19:47
Re: [Final] Mass Storage 711 (36 replies, posted in DriverPack Mass Storage)
V/4 can not be used by sysprep,It han an register error