Hmm,
That's odd.  We don't modify the nvidia drivers.  We only add another .inf file to support mobility chipsets.  If your card was not supported, it would not be listed in the .inf. 
nvidia was the first (I think) to create a unified driverset back in the '90s to support any current and future cards.  Lately, they've been splintering their driver releases so that older cards use the older drivers and are not supported by the newer driversets.  This is a pain for us.

3,802

(3 replies, posted in Other)

Helmi wrote:

In other words, just wait for CAT 7.6 to be included in DriverPack Graphics A, right? wink

I'm working on it! smile
On hold for mobility cat7.6 release sad

3,803

(226 replies, posted in DriverPack Graphics)

Just a heads-up that I'm working on the new Catalyst 7.6 driverset now.  The problem is that ATI hasn't released their mobility 7.6 drivers yet so I'm on hold for that.  I'll be uploading a Graphics_A test DP with ONLY the ATI drivers when it's done.  I'm not sure how to handle the nvidia disparity.  We may have to create new folders N\1, N\2, N\3, etc to handle the different drivers.

Yes, I ran into this issue as well.  I believe the problem is the website where we get our modified inf files to support geforce go chipsets.  In my case it was the geforce go 420. 
I believe that these older chipsets are only supported by the older package.  I'll have to look into this as well...my weekend is shot now.  sad

3,805

(11 replies, posted in DriverPack Graphics)

Kurt_Aust wrote:

Further investigation reveals that the last working driver version is 78.01, it seems the glitch was introduced in the 8x.xx forceware series.

Make sure to let nvidia QA know about this.  I know from working in QA that reports like this do NOT go un-noticed. 
Although, it's becoming standard 'party-line' politics to let older hardware go unsupported in newer driversets to keep filesizes down and optimize the code.

3,806

(226 replies, posted in DriverPack Graphics)

Please do not use the test DP, instead use the release DP on the main page.

3,807

(19 replies, posted in DriverPack Sound)

JasonACS wrote:
JasonACS wrote:
Helmi wrote:

Either that, or introduce another user choice in the BASE à la ATi CP/CCC.

I would recommend using the Sigmatel CP as the only option.  The installer is less than half the size of the Intel CP, and it's used by many motherboard manufacturers, instead of just Intel.

Forgot about the other part. tongue  I'd consider it important to get both FP options working in the DP.  Other HDA drivers (ie: Realtek) seem to work with both FPs automatically.  If this isn't possible, choosing the HDA FP option would seem to make sense seeing that its an HDA driver.  I can test my DG965RY on both types of FP if needed.

See, that's just the problem.  I have a working DP with just drivers...no CPL options (neither Intel or Sigmatel).
I'm working on getting only one CPL to load but any other option would require a rework to the DPbase (which is 99.99% bug-free).

I'll be going on an extended "business trip" soon so I'll be off-line during that time.  I'll bring my gear with me and I'll continue to work on this while I'm gone.  At the moment, I have very little dev-time available. sad

3,808

(8 replies, posted in DriverPack Graphics)

jtdoom wrote:

hmm, I am stumped by the MSI installer.

I just unpacked the installer to take a look.  I just did this from cmd.

msiexec /a "%path_to_matrox%\PDESKSE.msi"

Pack up the admin install in a sfx .exe pointing to the new .msi file.  Call it with an .ini.

Yes?

3,809

(11 replies, posted in DriverPack Graphics)

We may have to splinter the packs to rebalance.  Graphics_A is already pushing 90MB compressed and doesn't support older Geforce hardware.  We may have to reshuffle and add older nVidia hardware into Graphics_B.  It's possible we may have to create a Graphics_D (for outdated, unsupported hardware) for archival purposes to keep the other DriverPacks managable.  Otherwise, we're looking at 'exceptions overload'.

It's not my pack...it belongs to driverpacks.net and I am fortunate enough to have been allowed to contribute.  smile

Jaak and I will look into it, but Intel driver sets are becoming increasingly difficult to work with.  sad

3,811

(226 replies, posted in DriverPack Graphics)

I'll check my folders when I get home for nvucode.bin.
*Edit
I don't have that file.

The .cmd file in the Dev area is wrong.  You need to add the following lines of code in the appropriate places to uncab the .bi_ files.

ren *.bi_ *.bin

The website we get the NV4_go.inf files may have dropped those HWIDs because they're unsupported (or because they screwed it up).  The drivers in the DP G\N\1 folder don't support GeForce4 cards.  The nVidia site recommends the older drivers (from DP 7.04).

Yes, I can verify that the release DP Graphics_A does not support an older HP notebook with Geforce Go 420 video.

PCI\VEN_10DE&DEV_0176&SUBSYS_006D103C&REV_A3\4&2655A04&0&0058: NVIDIA GeForce4 420 Go 32M

Last night, the installer hangs at T-34 "Installing Devices" with the card listed in the pnplog.txt file as the source of the hang.

3,813

(226 replies, posted in DriverPack Graphics)

D\G\N\1 Updated from 93.71 to 94.24 (mr_smartepants)

OK, I just verified that this update does NOT work on an older HP notebook with GeForce Go 420M. sad
I even downloaded the drivers for "Geforce 4 series" and put in the custom INF file to support it and it didn't work.  Only downloading the drivers from HP (c 2005) worked.
Sigh.

3,814

(4 replies, posted in 3rd Party DriverPacks)

We're very happy with your success! smile

Did you try the 3rd party TV Driverpack?
http://3rdpartydriverpacks.thesneaky.co … -32_702.7z

@Mods, This thread needs to get moved to the "3rd party" area.

3,815

(226 replies, posted in DriverPack Graphics)

Chrysalis wrote:

I tried this pack and for me it didnt work the display device wasnt installed I have a 7600GT card.

Can you try the release DP?  If it still doesn't work, please post your HWIDs, your DPbase ini file and your logfiles.

3,816

(2 replies, posted in DriverPack Sound)

Sounds like a conflict between your M-audio sound card and your Leadtek TV card.  Since you verified that the TV card works fine with your onboard sound, we can only assume your M-audio card is configured incorrectly.  Most TV cards use a 'loop-through' audio cable connection, did you move that over to the M-audio card?  Also, you may need to disable the onboard audio first before adding the new audio card.  Without knowing more about your system, this could turn into "try this...try this..." all day long.

AC97 is just a standard, it means "Audio Codec, 1997".  Every modern sound device supports it.

Make sure your hardware is all detected properly.  Check your device manager for conflicts, and ensure all the factory drivers are loaded.

The Driverpacks themselves will only help you create a slipstreamed Windows source, not resolve hardware conflicts.

3,817

(15 replies, posted in Hardware)

Using the Fujitshi HDD Diagnostic Tool resulted to not finding the HDD (its the only HDD connected, the BIOS was able to detect the HDD).

This is NOT a good sign.  When a vendor's utility won't even recognize it's own device...bad news.  IIRC, Fujitsu haven't updated their utility in a while.

Using the Seagate HDD Diagnostic Tool resulted to a message "HDD FAILS pretest SMART check!!" Does it mean the HDD is broken?

Not necessarily, using another vendor's utility may or may not report accurately.  Although, failing a SMART check does mean the drive is on it's way out.

Using the Seagate HDD Diagnostic Tool resulted to a message "HDD have been overtemp - 100" Does it mean the HDD is very hot?

If this is true, the drive is dead or dying.  Heat will kill a HDD faster than anything else (short of dropping it off a building.)

Using the Seagate HDD Diagnostic Tool resulted to a pass test. Both Short (DST) & Long test.

Well, well, well.  A silver lining to the cloud.

Personally, I would back up all the data worth saving off the drive.  Then sell it to an unlucky sucker.  (just kidding). smile

Thank you for your report.
I'll look into it.

I'm sorry, I don't have rights to that area of the server.
@Bâshrat the Sneaky, can you look into it?

Glad to be of assistance! big_smile

3,820

(9 replies, posted in News)

lieblingsbesuch wrote:

New DP_Chipset has no .ini in it. is this okay though?

This is OK.  The ini is only required in certain driverpacks...the chipset DP is not one of them. smile

3,821

(4 replies, posted in DriverPack Mass Storage)

Wow, quick work Jaak!  smile

KB888111 is getting dynamically loaded by the latest HDA Intel drivers (not in the DP Sound_B pack...yet).  That's something we can learn from by dissecting the Intel drivers.

3,823

(19 replies, posted in DriverPack Sound)

OK, I'm going to need some help here.
I have a DP that's working fine but only loads the drivers, not the control panel (either Intel or Sigmatel).  In order to load the control panel correctly, an ini edit is required.
So far I added an 'I' subfolder to D\S\S\ for "Intel".
I'm thinking something like this (WARNING, untested):

[S-I]
; REQUIRED
exc_count		= 1
; OPTIONAL
exc_1_tagFiles	= 1
exc_1_tagFile1	= "%SystemRoot%\system32\drivers\sthda.sys"
exc_1_+hwids	= 0
exc_1_-hwids	= 0
exc_1_+infFiles	= 1
exc_1_+infFile1	= "%DPSROOT%\D\S\S\I\*.inf"
exc_1_-infFiles	= 0
exc_1_commands	= 11
exc_1_command1	= "cmd.exe /c copy /y %DPSROOT%\D\S\S\I\*.dll %SystemRoot%\system32"
exc_1_command2	= "cmd.exe /c copy /y %DPSROOT%\D\S\S\I\*.sys %SystemRoot%\system32"
exc_1_command3	= "cmd.exe /c copy /y %DPSROOT%\D\S\S\I\*.cpl %SystemRoot%\system32"
exc_1_command4	= "cmd.exe /c copy /y %DPSROOT%\D\S\S\I\*.ax %SystemRoot%\system32"
exc_1_command5	= "cmd.exe /c copy /y %DPSROOT%\D\S\S\I\*.cat %SystemRoot%\system32"
exc_1_command6	= "cmd.exe /c copy /y %DPSROOT%\D\S\S\I\*.drv %SystemRoot%\system32"
exc_1_command7	= "cmd.exe /c md "%ProgramFiles%\Intel\HD Audio\STACGUI""
exc_1_command8	= "cmd.exe /c copy /y %DPSROOT%\D\S\S\I\sttray.exe "%ProgramFiles%\Intel\HD Audio\STACGUI""
exc_1_command9	= "cmd.exe /c copy /y %DPSROOT%\D\S\S\I\stlang.dll "%ProgramFiles%\Intel\HD Audio\STACGUI""
exc_1_command10	= "cmd.exe /c copy /y %DPSROOT%\D\S\S\I\stacgui.cpl "%ProgramFiles%\Intel\HD Audio\STACGUI""
exc_1_command11	= "cmd.exe /c copy /y %DPSROOT%\D\S\S\I\stacsv.exe "%ProgramFiles%\Intel\HD Audio\STACGUI""

Our other option is to pack up the entire "Disk1" folder from the Intel download with the " /s /SMS" switch like the ATI CCC package and call it with the ini that way.  That might actually be the safest option, but I don't have the hardware to test on.

Can you please post your log files for the DPbase 7.05.2.

If your notebook/laptop widescreen monitor resolution is not natively supported in the Graphics DriverPacks, and you don't feel comfortable making the modifications yourself using my tutorial here,  then please post your requests in this thread and I'll try to get them implemented in the next driverpack.  You will be requested to TEST the changes added to the new Driverpack.  If you are unwilling to test the new changes, your requested changes will NOT be added to the main Driverpack.

When making your requests, please provide the following information:
Manufacturer and model #:
Website of manufacturer support page: (so I can verify proper resolution support)
HWID of graphics chipset:
Screen resolution requested:


Example:
Manufacturer/model#: Gateway M505
Website: http://support.gateway.com/s/Mobile/Gat … 64nv.shtml
HWID: PCI\VEN_1002&DEV_4E50&SUBSYS_206117C0&REV_00\4&13B9B28C&0&0008: ATI MOBILITY RADEON 9600/9700 Series
Resolution: 1280x800  60Hz