Search options (Page 17 of 99)

something like the HFslip report in bugtracker is something I can not test, because I am like a mom and pop store test person, with a few live machines at best.. No network stuff, no sysprep.

thanks
It sheds a light on the riddle.

What we had in Lan D\L\NV\123 for some reason,
%NVENET.DeviceDesc%  =  NVENET_2k.NDI,  {1a3e09be-1e45-494b-9174-d7385b45bbf5}\NVNET_DEV008C
%NVENET.DeviceDesc%  =  NVENET_2k.NDI,  {1a3e09be-1e45-494b-9174-d7385b45bbf5}\NVNET_DEV00DF

what we have in D\L\NV3

[Nvidia]
%NVENET.DeviceDesc%  =  NVENET_2k.NDI,  {1a3e09be-1e45-494b-9174-d7385b45bbf5}\NVNET_DEV008C
%NVENET.DeviceDesc%  =  NVENET_2k.NDI,  {1a3e09be-1e45-494b-9174-d7385b45bbf5}\NVNET_DEV00DF
%NVENET.DeviceDesc%  =  NVENET_2k.NDI,  {1a3e09be-1e45-494b-9174-d7385b45bbf5}\NVNET_DEV0038
%NVENET.DeviceDesc%  =  NVENET_2k.NDI,  {1a3e09be-1e45-494b-9174-d7385b45bbf5}\NVNET_DEV0057

Do you see the two BOLD lines?
This made me think NV\123 could be removed, and 123 had version 5.10..

Well, who would believe that?
Nvidia can make old drivers win over new..
I have uploaded a file with ALL the Nvidia network drivers, and made it a topic of its own.
(it also has the business driver set.. 50.54 I believe.. which I see we do not have.. but a generic in 8.16 should cover that..)

the topic is there for all interested parties, and I should perhaps also upload Joshua's plugin..

Hi zookeeper
It looks like you already put together your version of graphics B.

Can you upload that?

ventajou?
official sigmatel IDT had a few super generics what will mess up a whole range.
the new DriverPacks sound pack are not released yet, but they have (hopefully) worked around that, and one of our members showed us a sigmatel IDT m$ updated what had not a single bugger generic.

I had hoped another team member would build the pack with that file, and it has not happened yet.
But, I am seriously interested in the work you did, because we recently learned that the scanners we use are not perfect, and you could help?
(for instance, the graphics drivers.. when I use spotlightutility05.exe scan tool on Nvidia, I get zero output. )

Getting people to see what can be done teaches those whom do not yet know what can be done.
My past experience says that we will see more tips and more easy solutions described in a not too distant future, and it all started by getting people like us asking you to help us help you.

for instance, I liked that ruby script a lot, but wished it was vbs.
(and it is not perfect yet, because it cannot yet supplant what we list as replaceifOS.)

Hi abdou
it is a Third Party DriverPack so you can actually add it, test it, and when it works you could then upload it for us to review.

I built a testpack with 3wareDrv.sys from 2008 slimesmile linked to and cannot make it load during txtmode in live runs.
I remember the 2006 update was one of those case sensitive buggers, and this one is always saying it is corrupt. (despite streaming on clean copies, despite changing the INI, despite changing case in the filename itself.. despite the archive showing no error..

The live machine I tested on ran vista x64 setup with good result, and vista tests memory pretty good.
----
OH, I have to tell one thing to slimesmile.
the HWIDS list is NOT the same
There are four HWIDs, and the fourth has a difference.
You are lucky your bartPE runs, and that your machine does not use the fourth.

do not waste your time and do not test 805D (3wareDrv.SYS error during txtmode.. the case sensitivity thing struck again..)

hi,
there are a few drivers which have REPLACE_if_OS.
And those you mention are files that have to be replaced..
http://forum.driverpacks.net/viewtopic. … 095#p19095

(I should also tell you DriverPack MassStorage 804 has a known error.. We have a DriverPack MassStorage 805 testpack in testing. See sticky in DriverPack MassStorage forum.)

People need to realise why positive feedback helps solve issues.
DriverPack LAN had a flurry of posts with failures.
8021/805.1/805a/805b/805c/805d/805e(which is now805.2)

we have a DriverPack LAN 805.2 and it started when a REQ was posted about a missing HWID.
All hands on deck, so to speak.
(we have too few hands.. let me tell you.)
Bâshrat the Sneaky once figured a workaround (let's say in 2006. He combined a few driver sets)
And after that, Nvidia was not easy to make a single change to.

I think Nvidia gave up in 2006 because the last business platform unified driver-set nvidia released was (2007) with 2006 drivers.
One has to think about the efforts Joshua and Bâshrat the Sneaky put in when they worked on DriverPack LAN.
Since then, Nvidia have released quite a few new chips but no new bussiness platform set.

In the LAN forum, I repeated an older list with desciptions of downloads. (it was not even complete)
I have updated my collection of drivers and descriptions privately and a "scratch hairs, have coffee" lan file will be available soon.
The analitic will know when they see the "mess".
When you work on Nvidia you need gumbah to find back good humor, or anal IT and coffee.
(gumbah is a flemish cartoonist. )

>> edit, I forgot to mention SamLab as a hero.
His logs are badly compiled (probably because OS is russian and HWID read tool is not ), but he reports.
He told us DriverPack LAN 8.05.2 is not perfect and showed where it fails. (in humour, he sais another case.. a case for holmes. because I used that.)

We need watsons. Holmes could not do without watson.

I figure we'll find out what HWIDS in VIA SP3 natively supports, compare that to what HWIDS SP2 natively supports, then do some magic.
JakeLD is very good at this, and we have a large reporter group when things are WRONG.

Please folks, we do need pre-release testers..
We know we have many lurkers, we know we have a good many users doing massive rollouts and quite a few more serious pop & mom stores and repair IT folks.
Jeff thinks we see less than 1 percent of our DriverPacks users submit a post.

I think less than 35 percent of the posts are helping us in the first post, and the people who really want to help you want you to help us by submitting more data and logs.