Search options (Page 16 of 99)

Hi, when you look at DriverPack Graphics A /b and /C you will see there are NO entries for the nVidia graphics drivers in the INI files.

I never wrote exception rules from the ground up, but there are quite a few examples across the various DriverPacks showing how it is done.
(( DriverPack MassStorage is a SPECIAL case, this is documented.. but right now I am hoping special post install exceptions can be added to DriverPack MassStorage because there is something funny going on with a Jmicron installer I am testing at home..))

Far as I know, a well written DriverPacks INI will get processed.
I hope we will get an academy for the DriverPacks team to help all team work together (with documentation on how exceptions are written and developed), and I hope that is not in a pipedream.

hi debugger
have you tried the Graphics A testpack?

http://forum.driverpacks.net/viewtopic.php?id=2709

a lot of work was done
http://forum.driverpacks.net/viewtopic.php?id=2752

we had six folders with Nvidia and now we have seven.

I have not worked on DriverPack Sound A and b 805 since their release on 12th..
I have been somewhat busy on trying to puzzle together LAN and a couple other things here..

the LAN testpack UPloaded like ten minutes ago...

and that question about removing 100Mb of native windows drivers and then add DriverPacks..
erm, well, that is tossing the baby out along with the tub.
DriverPacks do not replace windows native drivers so you may find yourself looking for drivers what were not needed had you not removed them..

2006 had fourth line as this
PCI\VEN_13C1&DEV_1004&SUBSYS_100513C1

2008 has fourth line as this
PCI\VEN_13C1&DEV_1005&SUBSYS_100513C1

I will try this again, with this

[3]
ms_count=1
ms_1_deviceName="3ware AMMC 9000/9500 Series SATA RAID Controller"
ms_1_tag="3wareDrv"
ms_1_sysFile="3wareDrv.SYS"
ms_1_hwids="PCI\VEN_13C1&DEV_1002&SUBSYS_100213C1,PCI\VEN_13C1&DEV_1003&SUBSYS_100313C1,PCI\VEN_13C1&DEV_1004&SUBSYS_100413C1,PCI\VEN_13C1&DEV_1005&SUBSYS_100513C1,SCSI\Processor__AMCC__SATA_RAID_9500S_,SCSI\Processor__AMCC__SATA_RAID_9550SX,SCSI\Processor__AMCC__SATA_RAID_9650SE,SCSI\Processor__AMCC___SAS_RAID_9690SA"
ms_1_isBusExtender=false

I just noticed that the HWID posted was the fourth?
And PE does not care for that?
The CAT for the 2008 version has DEV_1005&SUBSYS_100513C1 inside, so that new INF file is not wrong..
I've added the SCSI lines to the INI hoping that will work.

@ overflow

I looked and read about the meaning of skipIfOS and got the wrong impression about skip, and I remembered I cannot use disable if XP  (LOL).

Anyway, I needed something to verify what skipif=XP does.
So,I looked at a streamed source
For lsi_sas ms_1_exc_skipIfOS="wxp" is used.
Well.. that file is not in the streamed source, and not referenced in dosnet nor txtsetup.

Most other sections with ms_count= (higher than one) have more than one systemfile, but I convinced myself this may just work..

[V3]
ms_count=2
etcetera

Thanks.
I gues we found the reason PCI\VEN_1106&DEV_0571 was a pain in the butt for so long.

Hi.
I know it was "cutted",
I had pruned all duplicate HWIDs from that nv4_go file..

What I was saying is that the ATICCC.exe file works properly when I manually executed (after extracting it).
But, it seems it was not exectuted when it had to.

And, for the fun of it, I used DriverPacks BASE 7.05.2 to build a DVD with this pack, and it behaved exactly same.
Maybe it is because of SP3? Maybe it is because the Gigabyte mobo acts funny?
(the JMB36x controller gets detected twice.. so there is yet another thing I have to look at..)

I just spent four or five hours on LAN.. I made many notes on this Nvidia riddle..
I think I have found out why there are ((some)) old drivers ((sometimes)) winning over newer ones.

the only thing I can think of is this

[V3]
ms_count=1
ms_1_deviceName="VIA SATA/PATA IDE"
ms_1_tag="VIDEX32"
ms_1_sysFile="VIDEX32.sys"
; (XP and 2003 natively support PCI\VEN_1106&DEV_0571&CC_0101. 2000 has no native VIA at all.)
; this line is for XP and windows2003. Comment it if you uncomment the line for 2000)
ms_1_hwids="PCI\VEN_1106&DEV_3149&CC_0101"
; (uncomment the full line for 2000 if you need the extra HWID.)
; ms_1_hwids="PCI\VEN_1106&DEV_0571&CC_0101,PCI\VEN_1106&DEV_3149&CC_0101"
ms_1_isBusExtender=false

805E is uploaded for tests.
http://forum.driverpacks.net/viewtopic.php?id=2709

good or bad, we want reports on good too.

@ busel,
I've just finished work on NV4_go.inf for mobility support in the 175.16 Nvidia file.
and I downloaded catalyst 8.5.

you can expect to see a new testpack later today
(805D_nightly does yet not have the Nvidia mobility your HWID requires.)

Erik,
it is amazing to see what was dropped by the non-unified..
Eyeballs are eyeballs. We need better scanners.

I had huge respect for Erik, and more now.
He doesn't want his temporary absense stop us dead. He wants us to go on.
But folks, YOU don't want ME as Erik's replacement. We wanted a broad based team. People whom worked together and perhaps shared same passion.
People with the materials to test live and the willingness to provide detail.
Nutters like us.