3,151

(34 replies, posted in News)

The 'News' forum is not the appropriate place for this direction of conversation. 
Take it to PM.

3,152

(46 replies, posted in News)

Outbreaker wrote:

MassStorage v811r1 is Not working anymore in VirtualBox with STAT Controller enabled.

If you mean the SATA controller, there is no problem on my PC.  Can you post your HWID of your host machine?

Yes, PEBKAC is the term I remember.  And the "Meat Virus" is running rampant in my dept (despite my best efforts).

Tarbaby wrote:

(PS - I assume PABCHAK is understood? Problem Associated Between CHair And Keyboard?

big_smile  Thanks a lot!  I just blew my coffee all over my screen when I read that!  ROFLMAO!

There was a problem with the SimpleCDN links (I think).  Overflow is working on it.

3,155

(46 replies, posted in News)

Nomadturk wrote:

With the new updates, neither Nvidia nor Ati Control Panels are being installed to me. Tried it with Virtual Machine and 2 different desktops. None worked.

You're never going to get those control panels in VM.  They'll only install on real ATI or Nvidia hardware.

Wim Leers wrote:

These are *not* final DriverPacks! They're RC's!

Well, that's news to me. hmm The graphics DriverPacks (lang & PhysX inc.) are solid and cleaned.  The only issue that I see is that I built them with a 1024 dictionary size with 7z.  I'll repackage them with a 256 dictionary size and they'll be good to go.  Unless Overflow has some major changes to DriverPacks BASE up his sleeve we're not aware of.

3,156

(46 replies, posted in News)

Be patient abdou.  It's the holiday season.  We all have better things to do than sit in front of a computer all day.  Like I wrote in the first post, the final DriverPacks can be found here until the main server gets updated.

magon wrote:

7-zip archiver gives better compression on similar files

Yes, by similar they mean .sys .inf .chm etc.  All of which are present in all the DriverPacks wink

I'm sorry, I don't know if I can help you.  It's not my installer.
You could try Nvidia's support forums.

OK, fair enough.  So what would be the ideal dictionary size?  What's the standard XP PC come with?  256Mb?  512MB?
I'm willing to repack and upload, but over the holidays I just don't have the time to do extensive testing.
Once we come up with a figure, this needs to get documented in the DriverPacks team threads.

OK, well it's an .msi based installer.  Executing physx.exe /? will give you the options screen.
This looks helpful:
    /j<u|m> <Product.msi> [/t <Transform List>] [/g <Language ID>]
        Advertises a product - m to all users, u to current user

So this might work:
"physx.exe /v/qb /g 1032"

Or, you could do: "physx.exe /a"
and do an administrative install point to a folder, then rebuild the sfx and use the /qb switch.  Nvidia didn't document the language functions very well (or at all).

I used a 1 GB dictionary size to compress all the graphics DriverPacks.  I haven't read anything that says the dictionary size slows down decompression.  I'll have to reread the doc.

3,162

(2 replies, posted in Other)

The only way this would work is if we had an online database synced to the DriverPacks.  It would only work for releases, not for nightlies or betas. 
Hopefully, when we migrate to the new server/site, Bâshrat the Sneaky would be able to build the Drupal plugin to make this happen.
But that's up to the boss.

Odd.  I don't get that.

Oh, and: http://forum.driverpacks.net/viewtopic. … 023#p27023
No more requests for common drivers please.

3,165

(36 replies, posted in News)

Ha!  Today was the warmest day so far this year! wink
Seriously though, we got as high as 11C.  A white Christmas in the UK...I think not.

Happy Holidays everyone!

3,166

(34 replies, posted in News)

Deployment Image Servicing and Management (DISM) tool was designed for Windows 7, and because Windows 7 is in development and "invitation only" testing, the tools are also not allowed to be distributed until widespread public beta status.  DISM is set to replace WAIK, so it should be a free download once final.
Having said that, I don't see DISM included in the Vista-Tool, so this is not a problem...currently.

Jaak/Muiz, I know you two have personal issues.  But please don't allow them to obstruct progress.  Muiz has been doing the Vista DriverPacks on his own for a while.  If he wants to bring them back to the 'family' so be it.  The prodigal son returns.
Shahed, I don't know you either, but welcome to the team.

Source code should be made available to the "Code team" for peer review.  DriverPacks development should be posted in the "Testing team" threads prior to release.  Our methods are well known and the quality of the DriverPacks show in each release.

It may be possible to use the command line for the language specific options.  I have no idea if this will work, but you can try and report back.
"fullpathto\physx.exe /qb transforms=1041.mst" replace 1041 with your language code.

Helmi wrote:

Maybe you should untick the "silent edit" option so users can actually see when the last edit took place directly in the first post smile

big_smile

bfc_xxx wrote:

I used DP_Graphics_A_PhysX_wnt5_x86-32_810 but when installing windows it promts to select language.
Is it possible to make it automatic without prompting?

Hmm, which language are you using?
First post updated.

Yes, they should get updated with DriverPack Sound A.  Having said that, the last time ATI HDMI was updated was in October, Realtek (manufacturer) updated them in November.  Funny eh?

3,170

(34 replies, posted in News)

Sounds like fun! I'm in!

3,171

(9 replies, posted in DriverPack WLAN)

Ignorance is encouraged, rudeness is not. smile
Admitting your ignorance, you open the door for education. "I don't know how to do this", "well, let me teach you then".

To verify signatures on a RUNNING XP system, click 'Start'->'Run', then type "sigverif" (without quotes) which will launch the signature verification tool, then click 'Start'.
To verify signatures in a FOLDER using SigVerif.exe, launch it as above, then click 'Advanced', 'Browse' to your folder, click 'Include subfolders', then 'OK'.

Enjoy. smile

ChiefZeke wrote:

So, here's my question: when Driver Packs are updated for a new Catalyst Control Center does this also include the HDMI Audio drivers?

No.
DriverPack Graphics A does not include any audio drivers (anymore).
DriverPack Sound A includes the ATI HDMI audio drivers.  There's a conflict between ATI & RealTek audio drivers.  Realtek's reference drivers have many generic HWIDs that may/may not work.  These get pruned out of DriverPack Sound A.
This is something the team discused a while ago, and it was decided at that time to keep all audio in DriverPack Sound A & B and all graphics in DriverPack Graphics A, B & C.
But because HDMI is tightly integrated (video/audio), we might need to rethink that.
What's everybody's thoughts?

3,173

(5 replies, posted in News)

As stated in the tutorial, you integrate DriverPacks LAST!  If you try to integrate ANYTHING after that (with RVMI, Nlite, etc.) you stand a 90% chance of breaking your source (as you discovered).
Your other option would be to:
1) copy your source dvd to your hdd.
2) run DriverPacks BASE and select NONE DriverPacks (this will effectively remove all traces of DriverPacks from your source)
3) integrate whatever you want.
4) build your ISO and test in VM (VirtualBox is my favorite).  This will ensure the integrity of your source.
5) re-integrate DriverPacks by using DriverPacks BASE.
6) repeat step 4 and TEST in VM.

3,174

(353 replies, posted in Software)

I think I found a bug in v3.2.
See this post: http://forum.driverpacks.net/viewtopic. … 029#p27029
The HWIDs listed are getting skipped, but the VEN_x&DEV_x&SUBSYS_x strings are getting picked up correctly from what I can tell.

I used both options for CSV and Excel.

Search in Excel for "DEV_5B63" from DriverPack Graphics A and you only find lines with the SUBSYS, not the bare HWID.

BTW, before anyone else posts about it, I'm well aware of the ATI/Nvidia releases.  No need to ask for them. smile
I'm looking at the ATI hotfix posted here.
And I'm looking at the new dedicated Nvidia notebook drivers here.