Search options (Page 48 of 99)

Lan updated today.
http://driverpacks.net/DriverPacks/changelog.php?pag=l

Hi
I had to help out friends today, and figure I'll finalise it tomorrow.

hi JakeLD,
please put the update for attansic and realtek to the fragbert nightly, so we won't have to do frequent re-uploads.

I have the supported intel list for that monster. it is HUGE.

we released that file.

Later in the day, Sound B got released.

We'd like you to help us.
Please help test some groundbreaking work.
http://forum.driverpacks.net/viewtopic.php?pid=15110

Hi Fragbert

this Intel update was a pleasant one to do.
at first glance, it did not drop devices, and added some.

You Can be the first to test this update.
(I will not immediately release this update, because JakeLD has an Attansic driver to add, and he said he also wants to do a realtek update.)

http://dev.driverpacks.thesneaky.com/dr … ragbert.7z

hi,

they exist for PnP.
Bâshrat the Sneaky told me Nvidia provide a TM driver to make things easy.
(Their other drivers are a maze.)

Incidentally, in the latest TEST Packs (exerimental in Mass storage forum) we have four new folders in Nvidia, and also three extra Nvidia sections in INI.
One folder got removed.
I removed N-590SLI drivers from the pack (they had no INI section) because the new additions covered it.
(no, they was not an update for 590sli..)

Two driver versions with support for AHCI mode and Raid support got added.
Because of overlap in the INF I could write only three extra INI sections. I chose to use the one with most PCI HWIDs..

Hi, we can always use people to run tests on "non-production" machines.

Yes, it does look like the sysprep crowd come 'from the voodvork out'.
(Sorry, I had to smile. This reminded me of the Shimmelhorn tales.)

I get the feeling that proper documentation of what we did to fix issues is of extreme importance now.
For instance, ExOrt was alarmed when he used a Mass storage version where an intel driver had been updated, and the updated file was given a new name (to wit, iastor70).
When he asked, I immediately knew he had used a test-pack.

The X-files or EXPERIMENTAL mass storage testpacks have unique INF filenames now.
The drivers themselves, most can get a unique filename too, but I have not done that yet.
(It requires we edit filecopy sections in INF for each driver systemfile renamed.).

Anyway, glad to see you guys post.

hi

Nlite can do a few drivers, but is not intended to handle DriverPacks.
Nlite would not process the exceptions we put in INI files.

These exceptions are processed during windows installation, and after that, WPI can be used.
(WPI is , after all, POST install).

Hi,

I do say that tagging CC_010* may not be neccesary in Silicon image.
(the subsys they provide are probably dealing with this.)
I also know that it works on the machine with Sil3132, which had a yellow flag in HW before.

The INI sections have no duplicate subsys in them.
(this was always a no-no..)
And, because of the nature of this problem, the duplicated HWIDs were removed from INF files.
(HWIDs in INF have  not been tagged with CC_010*)

I can quite easily upload a testPack where the CC_010* are not tagged to HWIDs in the silicon INI sections.

I think release is near.

7105 updated the turtle beach in [SC] with missing file, and an INI fix in [T-2]

sound test pack 7104 and 7105 were pulled.
---------------------------------------------------