You are not logged in. Please login or register.
DriverPacks.net Forum » Posts by 5eraph
windows will report some kind of an error if a mismatch driver installed is found right?
It won't. As far as it knows, the driver is correct because the hardware looks identical.
Plug and Play monitors can transmit their capabilities through the cable; the only thing missing is the ICM profile. Most monitors can do this unless they're really old.
I prefer not to use the driver for my ViewSonic G220fb because the driver prevents the use of 2048x1536, but the monitor is quite capable of displaying it. 
My nVidia nForce4 AMD system also appeared to install fine a few months ago (using nvRAID), but Windows was indeed using the wrong driver for the nVidia LAN.
More nForce drivers have since been added to the DriverPacks and I've not had the opportunity to test again, but nVidia's use of the same HWID across chipsets does seem to necessitate modding the DriverPacks for use with each nForce chipset variety. I haven't tested the workaround for the nF3 LAN issue yet, but it may have been fixed.
Does that version number match what is displayed in the Device Manager Properties for the NVIDIA nForce4 Serial ATA Controller?
You should also verify that the NVIDIA Network Bus Enumerator is using the correct driver. I didn't notice any problems other than the wrong driver version, but I didn't use it long enough to encounter them before forcing Windows to use the correct driver from DP_LAN.
While I find the prospect of Bâshrat giving more to contributors appealing, I also think it's a bit greedy of us to be asking him to do so. Isn't he giving us enough already? Did we not contribute to pay him back for all the time and effort he has already put into this project? [/rant]
An autoupdate feature would be a good idea, but it could also cause problems for those that modify the DriverPacks themselves. In my opinion an autonotify feature with the option to download, an imbedded Terms of Use statement, and Donate button (all in one pane) would be far more attractive.
Check within the MassStorage and LAN DriverPacks and you'll see that those version numbers match for drivers that aren't supposed to work with your motherboard...
The only way to truly be sure the correct drivers are installed for your nForce motherboard from the start is to remove the drivers that shouldn't be used from those two DriverPacks.
Are you using an AMD processor, or an Intel processor?
Folder 4A contains drivers for nForce4 AMD (Ultra, SLI non-X16) not using nvRAID.
Folder 4AR contains drivers for nForce4 AMD (Ultra, SLI non-X16) using nvRAID.
Folder 4I contains drivers for nForce4 Intel (Ultra, SLI non-X16) not using nvRAID.
Folder 4IR contains drivers for nForce4 Intel (Ultra, SLI non-X16) using nvRAID.
Hope that helps.
I don't know if you can integrate a previously integrated source, but you should rename those DriverPacks as follows:
Printer -> DP_Printer_wnt5_x86-32_603.7z
TV -> DP_TV_wnt5_x86-32_181.7z
USB -> DP_USB_wnt5_x86-32_12.7z
I used the DriverPacks back in March (including MassStorage) on an nForce4 AMD system and my USB 2.0 Sabrent 42-in-1 Media Card Reader works in it using the standard Windows driver.
Which card readers are you using? Do they require special drivers?
Thanks to nVidia, Windows gets confused when dealing with nForce chipset drivers. You'll need to modify the MassStorage DriverPack to remove the nForce drivers that you won't use.
The confusion stems from the fact that nVidia, in their infinite wisdom, decided to make the hardware IDs across all nForce chipset lines identical. Only the latest drivers are used, even if they're the wrong ones!
This also applies to DriverPack LAN.
There's nothing Bâshrat can do to fix it at this point. 
DriverPack MassStorage contains those drivers.
This is the driver I received from the Microsoft Update site:
Have you tried renaming those DriverPacks?
Downloads Page: http://w3serv.realtek.com.tw/downloads/ … tware=True
Direct Download Link: ftp://202.65.194.18/pc/ac97/alc650/WDM_A388.zip
I'm just wondering how the beta driver will expire. Will it automatically uninstall the driver or disable the hardware?
Take note of the following:
..
* This beta driver expires on 22 September 2006. When this happens, users should install the latest Sound Blaster X-Fi driver available.
I've been waiting for an update from Creative for quite some time. There's currently a time-limited beta, but I wouldn't include it. The driver in the DriverPack is currently the latest supported version.
I've been having noise issues with it since I purchased the card and apparrently it's pretty common. The next driver release is slated for the end of June as quoted from Creative's Discussion Forum.
I can't find the confirmation email I got from PayPal at the moment, but you would have received it from xxxxxxxxxx@xxxxxxxxxxxxxxxx.
http://www.msfn.org/board/index.php?sho … ntry416605
I still find your DriverPacks extremely useful. Thanks for all your hard work!
Everything looks great! And now you have a real bugtracker. 
DriverPacks.net Forum » Posts by 5eraph
Powered by PunBB, supported by Informer Technologies, Inc.
Currently installed 3 official extensions. Copyright © 2003–2009 PunBB.
[ Generated in 0.012 seconds, 5 queries executed ]