[Beta] Graphics Pack M x64

Updated Pack
Drivers are dism compatible.

http://www.mediafire.com/?hmwgql5oj5rofh9

Changelog:
12.05 Testing Mar 2013
- Update - (All) Nvidia\1 Nvidia GeForce Mobility DriverVer = 02/09/2013, 9.18.13.1407 (314.07)
- Update - (All) Nvidia\2 Nvidia Quadro Mobility DriverVer = 12/29/2012, 9.18.13.1090 (311.35)

for x86 please...

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.     

Last edited by TechDud (2013-10-07 12:21:36)

Forum Rules & Guidelines   HWID's tool   Unknown Devices (Win7-max) LatencyMon - NT6.x
MemTest86+    Video Memory Stress Test    D-P-C Driver Latency Tester (Win7-max)