Search options (Page 15 of 64)

Sadly, i know how this feels.
  To be truthful, there has been very limited and mostly incomplete public feedback for the NT5 packs.

Unfortunately, i won't have much time over the next six months or so to help.
If i do DISM in some drivers, i will report my results - I love taking notes.

Welcome back Jaak, compstuff, muiz & SamLab!!!     

Thank you, Chief!

That package you list for Realtek(ATi) HDMI doesn't appear to have changed from the listing on the download page.
I did find a new ATi/AMD HDA package in one of the new AMD 7790/R-Series drivers for XP though.
  {DriverVer= 04/23/2013,5.18.0.5515}
    The executable is no longer signed, although the driver appears WHQL'ed.

Now, if only a proper Intel Gen-4 HDA driver could be found (or .Inf modded) and successfully tested to fill that gap....

The MassStorage.ini already uses ..\N\7\nvgts7.sys {quote:  "From nForce 15.56 DriverVer=04/09/2010,11.1.0.43"} for textmode.  nvgts.inf seems to satisfy WHQL requirements.

Is that PCI\VEN_10DE&DEV_0AB9&CC_0106 or PCI\VEN_10DE&DEV_0AB9&CC_0104?

Are you using a clean or updated source?

This project doesn't officially support flash, yet it is a work in-progress. 
Disc install has greatest odds of success due to least variance in BIOS/uEFI support (except disc-USB).

You seem to be saying, in a way, that you are having issues with malware.  Are there problems with pixellation or random restarts, cut-outs, blue or black screens?  Any blown caps?  Is it clean, or clogged with detritus?
Certainly, it seems possible for what might appear to be malware at first could actually have hardware origins, perhaps even making a system more prone to malware.

How old is the coin-cell battery in it?  They get drained down to nothing if they are left with AC removed for many months.  You can only truly test them "under load", with a same coin-cell based accessory, such as a light or WiFi finder.

It is amazing how much of a difference a well-running proven power supply makes, first and foremost (like audio).  Components on the motherboard run much cooler when they have less electric noise in the power to dissipate as heat.
Warranty length (parts AND labour) is a good gauge for consumer.  By previous observation, products seemed engineered to last one and a half times the length of the original warranty.

Search is good, too.  http://forum.driverpacks.net/viewtopic. … 150#p32150

. updatum
DP_Sound_A_wnt5_x86-32_1310251.7z - 154 MB   2264517730c7ee7911b8d27024619edc03d677eb

*  edit:  links removed - updated below

I do not see anywhere on his page where it states "DriverPacks may include my work in their project if they credit me".
But this is beside the point.

mr_smartepants invested a lot of time and effort in at least the nVidia portion of the MassStorage pack.  To include the work of others would likely mean negating at least some of that.

It is a "kettle of fish" that i dare not open.

It works for most boards.  The few that it does not support can be added.  Yet it need be done his way.

I know of no other way.

What particular nVidia chipset is that?

Hello, urbanriot!

Here are a couple of test packs for you.  ICH8 & ICH10D/DO should be fixed now.

  * - edit: link removed - updated near last post in this topic
  Bear in mind that these have not yet gone through rigorous testing.  I will post an updated Sound_A package later.

In some cases, hardware duplicates (such as video, sound or modem cards) can cause blue-screens during an install.  I am uncertain if this is true with PE.

    Also keep in mind the possibility of hardware issues, such as blown capacitors - especially in the "no user servicable parts" power supplies, which are a shock hazard when opened.  It would be rare for this to cause issue in HDD detection ($7B errors).  However; it can and does cause other instabilities.  Every ten degree Celsius drop in temperature doubles their life span.  Conversely, every ten degree Celsius rise in temperature halves their life span.  55°C is a good average.  Use a non-contact infrared thermometer to gauge thermal zones.  Ensure all dust is removed.  Some of it spontaneously emits electrostatic charge.

Please let us know how it works out for you.
  If there are any further changes needed, do not hesitate to reply here.

I thank you for your report.
============================================================

Hello, Outbreaker!

You will need to run mr_smartepants' gamut of nVidia MassStorage testing.
  here -->  http://forum.driverpacks.net/viewtopic.php?id=4742

Note that i cannot include any of Fernando's work without his expressed permit.
  Also, OEM sources are required as a base for any modification.  I require myself to justify where files are sourced, at least to the Testing Team.  Every project should reveal their sources for peer review.  Progress is much slower this way, yet i believe it supports trust and therefore worth every extra bit of time.

Hello!

That is odd.  I've tested on dozens of different machines and have different results from what you have experienced.

Why not give some more detailed information that i may correct this?
Some HWid's, DP_BASE output, and working revision info would be helpful.

Thank you.     

You could use the NT5 driver on Win7, yet you should probably avoid this for possible security reasons.
It is likely best to use drivers specific to the OS.
The Windows 7 driver should be NDIS6.2, while the XP driver will only support NDIS5.1.

PS:  I have not forgotten your request for updated changelogs, just terminally-short of time at this time.
          Like the tortoise, i will get there eventually.

I see the probability of success is high, as long as one is patient and avoids temptations to rush things.

Do keep track of changes in a changelog.

By the way, i do recommend Mitja Perko's free for personal CD Check (30 day eval. for Business users) to generate and compare hashes of each pack after changes are complete, as mouse mis-manipulation (etc.) can and does happen once in a while.  It does assist one in making changelogs too, as a person's memory can lapse once in a while.

Hoping you have DVD+/-RW's; they save making mountains of discs.  Solutions like WinSetupFromUSB are potential time-savers, yet not officially supported by DriverPacks (IIRC).  That should encourage the USB 3.0 drivers to be added to MassStorage (uncertain about 8.x), as originally pioneered by Damnation.

I wish you well!     

The contents of ..\Lang are likely required.  The DisplayAudio folder is likely for HDMI audio.
  That might integrate in with the same folder as the driver, though i am uncertain.

If there are any files with the same name, one would need check their hash values with a program such as Nir Sofer's Hash My Files.
  Nice; he has included support for VirusTotal.   

  To see which files are required by the driver, first double-click the associated Security Catalog (.Cat) file and click the Security Catalog tab.
  Check the Catalog entries by Tag.  It's a little "clunky", yet it get's the job done.
    Confirm OS support by looking for the first occurance of the hex value 4f (8th byte from left).
      It should appear somewhat like the following, as an example:

30 82 01 32 1e 04 00 4f   0..2...O
00 53 02 04 10 01 00 01   .S......
04 82 01 22 32 00 30 00   ..."2.0.
30 00 30 00 2c 00 58 00   0.0.,.X.
50 00 58 00 38 00 36 00   P.X.8.6.
2c 00 58 00 50 00 58 00   ,.X.P.X.
36 00 34 00 2c 00 56 00   6.4.,.V.
69 00 73 00 74 00 61 00   i.s.t.a.
58 00 38 00 36 00 2c 00   X.8.6.,.
56 00 69 00 73 00 74 00   V.i.s.t.
61 00 58 00 36 00 34 00   a.X.6.4.
2c 00 37 00 58 00 38 00   ,.7.X.8.
36 00 2c 00 37 00 58 00   6.,.7.X.
36 00 34 00 2c 00 53 00   6.4.,.S.
65 00 72 00 76 00 65 00   e.r.v.e.
72 00 32 00 30 00 30 00   r.2.0.0.
38 00 52 00 32 00 58 00   8.R.2.X.
36 00 34 00 2c 00 38 00   6.4.,.8.
58 00 38 00 36 00 2c 00   X.8.6.,.
38 00 58 00 36 00 34 00   8.X.6.4.
2c 00 53 00 65 00 72 00   ,.S.e.r.
76 00 65 00 72 00 32 00   v.e.r.2.
30 00 31 00 32 00 58 00   0.1.2.X.
36 00 34 00 2c 00 53 00   6.4.,.S.
65 00 72 00 76 00 65 00   e.r.v.e.
72 00 32 00 30 00 31 00   r.2.0.1.
32 00 58 00 36 00 34 00   2.X.6.4.
2c 00 5f 00 76 00 36 00   ,._.v.6.
33 00 2c 00 5f 00 76 00   3.,._.v.
36 00 33 00 5f 00 58 00   6.3._.X.
36 00 34 00 2c 00 5f 00   6.4.,._.
76 00 36 00 33 00 5f 00   v.6.3._.
53 00 65 00 72 00 76 00   S.e.r.v.
65 00 72 00 5f 00 58 00   e.r._.X.
36 00 34 00 2c 00 5f 00   6.4.,._.
76 00 36 00 33 00 5f 00   v.6.3._.
53 00 65 00 72 00 76 00   S.e.r.v.
65 00 72 00 5f 00 58 00   e.r._.X.
36 00 34 00 00 00         6.4...

Also check the .Inf file withing [SourceDisksFiles], [SourceDisksFiles.x86] , or [SourceDisksFiles.amd64], depending upon CPU architecture.
  All files listed for that particular architecture need be included as well as the .Inf and .Cat file, or installation may fail.
    That is why some NT5 DriverPacks actually have 64bit files included.

Any files not listed within the Security catalog and .Inf file(s) might not need be integrated, and could conceivably be considered for a separate Optional 3rd-Party DriverPack should anyone not want to install MediaSDK, for whatever raisin.

The real hard part is ensuring HWID's don't overlap on incompatible hardware.

The contents of ..\MediaSDK are likely Runtimes for Intel's MediaSDK.
  Here is a link to their forum containing some whitepapers
         --> http://software.intel.com/en-us/forums/topic/311914

Are the OpenCL runtimes are included within either the driver or MediaSDK?

When you do post DriverPacks, create new Topics for each of them.