*Edit
The above folder/file structure does NOT solve the problem for the new drivers.
Samlab, if you can put together the new nvidia x86/x64 files together so that they work, upload them somewhere and I'll test them.  If they don't blow up, and if they work, I'll include them in the next release.
Otherwise, I'll be sticking with 270.61.

The original arrangement of files doesn't work, also as well as an arrangement of all files in one folder without subdirectories + setup-files should be in a root where also driver files

NB: This files from xp-release, but in the win7-release similarly

My fix was to unpack the nvidia 280.26 driver and place it alongside this driverpack in my "drivers path" used for auto-installation. Then it worked!

So it seems that upgrading the nvidia driver in the driverpack would fix the problem...

No.  I can't get the 280.26 driver to install.  Not even the manual method works.  Integrating 280.26 into the install.wim will cause a BSOD at first boot.  275.33 isn't any better.  (Code 28) error.
I'm reverting the packs back to 270.61 because those are stable.

We are using Matrox for multi-screen digital signage players with many screens... We use them for many customers, and currently I just include the driver in addition to the driverpacks downloaded here... That works fine for me, and often we need more current gfx-drivers than included in DP anyways.

But I was under the impression that the goal of this project was to supply drivers for ALL hardware:-) (judging from the sound-DP, there are many rare products supported)

Agreed, all drivers included is our goal...

If you find outdated or not included drivers then report them... that is how they get added .
Be sure to include the HWIDs of the device(s) and a link to the updated driver (on an OEM site).

mr_smartepants Just said the issue was no testers available... R U willing to test and report?

Walk into any computer store ask for a Matrox product: "Who?" will be your response.

Nothing a merger or acquisition with/by nV or Chipzilla wouldn't solve.

But I was under the impression that the goal of this project was to supply drivers for ALL hardware:-) (judging from the sound-DP, there are many rare products supported)

XDDM WHQL drivers here --> http://www.matrox.com/graphics/en/suppo … ad/?id=449
                 64bit here --> http://www.matrox.com/graphics/en/suppo … ad/?id=450

WDDM WHQL drivers for M series 7_x86 here --> http://www.matrox.com/graphics/en/suppo … ad/?id=455  as previously noted by atlesj
                                   release notes --> ftp://ftp.matrox.com/pub/mga/archive/w7 … es.401.pdf
                                        7_x64 here --> http://www.matrox.com/graphics/en/suppo … ad/?id=456

DisplayPort, HDMI support & stereoscopic support included where applicable.  Not noted elsewhere; the XPDDM drivers add WHQL support for Win2k & since they are WHQL'ed for Vista, the WHQL will be valid for Win7, too.

Curious, on an install of xp on a nforce500 board, i had a "Matrox Extio PCI Standard PCI-to-PCI Bridge" installed.  Until now i thought it may have been licensed IP, now i wonder if it is related to other problems with Matrox drivers.

I sure love Nirsoft's "Hash my files" for comparing packs with many files.

The M-series gfx cards are supported http://www.matrox.com/graphics/en/suppo … ad/?id=455

PS: I assume the matrox driver fit better in the GFX B package, as not many are using Matrox anymore

First it reports missing driver signature, and when I select "install anyways", the driver is not installed (it seems to install, but is missing after reboot).

My fix was to unpack the nvidia 280.26 driver and place it alongside this driverpack in my "drivers path" used for auto-installation. Then it worked!

So it seems that upgrading the nvidia driver in the driverpack would fix the problem...