Hi guys, I Know its been talked about before. But when will Dell catch up with Nvidia drivers? im just not sure i trust the modified drivers from laptopsvideo2go... I know Im being pedantic about it, but will dell produce the same quality of driver?... if they cant i might just try the modded drivers, because starcraft 2 doesnt run on ultra atm with 267 A01 drivers. Any advice?
-
There is no reason not to 'try' a modded driver from LV2Go. As long as you have a basic understanding of how to implement their modified INF file in order to install, its fairly straight forward. You can always uninstall and reinstall the current Dell driver for the 14x.
As for NVIDIA, my understanding from a post here from one of the AW reps, was that the plan was to have NV incorporate the DeviceIDs into their Verde (mobile) driver releases. I was not given an ETA and this was some time back. Be patient, hopefully we'll see this. This was also the plan for AMD.
Once can hope -
Google Safe Browsing diagnostic page for laptopvideo2go.com
Am I being over cautious?
if Dell ID's could be recognised that would be great, just got to wait I guess. -
laptopvideo2go is fine. I've been a member over there for years now and have tried numerous drivers. Never had an issue.
Do read up on using a modified INF (if you try of course) - they have a couple of old tutorial/FAQ threads up. Although they are a bit old, it does explain the process. Worst case, the driver will not install.
I dont have time tonight, but I'll shoot you a PM with a couple of basic tips tomorrow...
--- -
Thanks for the help man.
-
-
Yep, you have nothing to fear from the modified inf file.
The driver isn't modified, it's just that the .inf tells the driver that it's OK to install. If it was a modified driver, like the Omega ones etc, I wouldn't install it either, but I have not had a single problem with the 270 drivers using the modified inf. -
boby / marcy - sorry, haven't had time to put anything together. Will do so this evening. Apologies for the delay.
-
I was going to ask for a copy as well via PM, but thought, would a sticky work?
-
Apologies for the delay folks... Was quite busy today. As promised, below is a rough overview of INF files. I've also included the process I use when updating an NV driver.
Be sure to see the bottom section of this post concerning the M17xR3 NV 460 driver.
---------------------------------------------------
What is a driver INF file?
Think of it as the 'information' file or 'recipe' for a given driver. It contains information on devices, configuration, etc.
Lets say a driver is released by NVIDIA for a desktop or mobile GPU. Because not all NV GPUs may be supported in said release, the community may 'mod' (modify) a driver. Device IDs for other cards are added and other tweaks can be introduced.
Example of a DeviceID line within the INF file (this is the DeviceID line for the M14x):
Code:NVIDIA_DEV.0DCD.01 = "NVIDIA GeForce GT 555M"
Code:%NVIDIA_DEV.0DCD.01% = Section046, PCI\VEN_10DE&DEV_0DCD&SUBSYS_04911028
Code:[Section046] AddReg = nv_DRS_addreg AddReg = nv_commonBase_addreg AddReg = nv_commonDisplayModes_addreg__04 AddReg = nv_controlPanel_addreg AddReg = nv_global_addreg AddReg = nv_miscBase_addreg__14 AddReg = nv_opengl_addreg AddReg = nv_timingRestrictions_addreg CopyFiles = nv_Drs_copyfiles CopyFiles = nv_controlpanel_copyfiles CopyFiles = nv_detoured32_copyfiles CopyFiles = nv_detoured_copyfiles CopyFiles = nv_license_copyfiles CopyFiles = nv_nvsmi_copyfiles CopyFiles = nv_sysDrivers_copyfiles__02 CopyFiles = nv_system32_copyfiles__02 CopyFiles = nv_syswow64_copyfiles__02 DelFiles = nv_sysDrivers_delfiles DelFiles = nv_system32_delfiles DelFiles = nv_system64_delfiles DelReg = nv_clearRegistrySwitches_delreg FeatureScore = E6 NVAllowHDAudioPreStage = 1 NVBusUpperFilter = nvpciflt NVDefaultBPP = 32 NVDefaultHorizontal = 1400 NVDefaultVertical = 1050 NVSupport3DVision = 1 NVSupportDisplayUpdate = 1 NVSupportOptimus = 1 NVSupportPhysx = 1 Reboot RegisterDLLs = nv_common_registerdll__02 [Section046.CoInstallers] AddReg = nv_commonCoinstaller_addreg CopyFiles = nv_coinstaller_copyfiles [Section046.GeneralConfigData] MaximumDeviceMemoryConfiguration = 80 MaximumNumberOfDevices = 2 [Section046.Services] AddService = nvlddmkm, 0x00000002, nv_nvlddmkm_serviceInstall AddService = nvpciflt, , nv_nvpciflt_serviceInstall
---------------------------------------------------
Ok, now that you know what the INF can contain, lets move on to using a modded INF file.
LV2Go and other sites (including a few NBR members), will tweak certain parts of the INF file to allow the driver to be installed on a system which was not originally included in a driver. As I said at the start of this post, this is typically seen with desktop driver releases. LV2Go will 'add-in' the necessary information to their modded INF. Once done, this INF is posted along with the driver on their site. In addition to desktop drivers, if a specific manufacturer releases a driver (Dell, ASUS, HP, etc.), these manufacturer drivers typically only contain info on devices used on their platforms/systems. Here the modded INF again comes into play. Multiple devices are added so the driver can be used.
In order to install the driver, you need to grab the driver from LV2Go and then download the modified INF file for it. LV2Go has the mod INF link right next to the driver download link.
Once you have both, simply extract the driver and then copy the modded INF file over to the Display.Driver directory. If prompted to overwrite the existing file, do so.
Once the modified INF is copied, you can then run the driver installer.
IMPORTANT NOTE: LV2Go may not have the actual DeviceID for your GPU included. Sucks - but it does happen. In this case, you'll need to wait for someone here to tweak an INF for use with the driver.
While putting this together, I checked LV2Go's 270.61 driver. Their modded INF does not contain the necessary info for the M14x. Never fear... I have taken care of this and modded the INF for you. For those brave souls who would like to test, the modded INF is attached to this post. You'll simply need to download the driver from LV2Go, extract it and then copy over the modded INF as I mentioned above (remember, place it in the Display.Driver directory). See bottom section below
---------------------------------------------------
NV driver installs -
Many will suggest using DriverSweeper and other driver cleaning apps. IMO, these are no longer necessary. NVIDIA has a clean install feature now. My process to updating the NV driver:
NOTE: Before doing this, I suggest disabling Windows Automatic Driver Install before updating drivers - reference this LINK.
1. Uninstall existing NVIDIA DISPLAY DRIVER using the Programs & Features Control Panel (Uninstall a Program).
2. Reboot the system into Safe Mode
3. Run CCleaner's Registry Module and 'fix' any registry issues found. You can back them up but not really necessary.
4. Once complete with step 3, reboot the system.
5. Windows may install the generic NVIDIA driver which is fine. If you see a prompt indicating a driver was installed, just reboot the system again.
6. Now its time to run the setup.exe for the new NV driver. Follow the prompts, select Clean Install and let the installer do the work. Reboot when complete.
7. Since the M14x is an Optimus system, dont forget to re-whitelist your game .exe's. For more info on whitelisting, see this video.
8. Enjoy the new driver. If you find performance is impacted, just uninstall and reinstall the last driver you were using.
---------------------------------------------------
Try 270.61 on the M14x today:
So, now that you have a general idea of how an INF file works, lets try one out. Reminder, this is a modified INF file and may not produce the best results. if you find performance is suffering, reinstall the driver you were on previously.
As I mentioned above, checking LV2Go, it appears their modded INF (for 270.61) does not include the deviceID for the M14x GT555M GPU.
Attached you will find a modded INF I put together for 270.61. Grab it, extract it and then just copy the INF over to Display.driver directory within the NVIDIA driver folder. Run the installer once it has been copied over.
NOTE: you will be prompted by a nice red dialog warning stating the driver is not signed. Go ahead and choose to install anyway.
Have fun testing 270.61
Grab 270.61 here:
v270.61 Windows 7/Vista 64bit | OEM Mobile - LaptopVideo2Go Forums
Use the RED Download link to grab the driver.
---------------------------------------------------
I know this may have been confusing and if so, apologies. Its the best I can do on short notice... lol.
Good Luck with using modded drivers!
---------------------------------------------------
M17xR3 NV 460M driver:
Not sure if anyone has tried this yet, but the M17xR3 NV 460 driver INF includes the M14x GT555M info. You can run this installer on your 14x! I don't expect a big difference, but you can give it a test drive if you like.
The 17xR3 driver is v267.64 (M14x is @ 267.21 currently) and can be found HERE. No modded INF needed.
Have fun!
--
EDIT: I just noticed we have a thread on the 270.61 LV2Go driver. Looks like the INF does have the necessary entries. Weird - I didn't notice them. LOL Anyway, the 270.61 thread can be found here:
http://forum.notebookreview.com/alienware-m14x/576365-installing-nvidia-270-61-issue.html
the INF I attached below will still work but you can always give the LV2Go version a try.Attached Files:
-
-
Thanks man, ill give it a go later
thanks for the help.
-
-
I installed the latest driver (using the laptopvideo2go site), and my 3d Mark 11 results showed that I was 10-15 points less than the factory drivers.
Ended up just putting the dell drivers back. Anyone have any stats on if their video card performed better or not with the new drivers? -
3dmark being with in 10-15 points is fine the issue with drivers are you may have a small decrease for one game but large increase for another. In addition it could just be caused by temp or workload. 3dmark11 is a much better comparision, while I know we all like higher numbers the fact of the matter is 15 points out of 15000 in my case is less than a .1% decrease. The 270 graphics fixed an issue with dragon age 2 resulting in anywhere from 60%-200% fps improvement. When it comes to this graphics card I just would go with the 270.
-
Thanks Jetbo. I heard a new 275 beta driver has come out now too, and I may try that.
I had to reinstall my driver last night because I was getting this weird periodic flicker on the display (very quick flicker that lasts about half a second). After uninstalling and reinstalling the intel and the nvidia driver, no more flicker problem.
I thought maybe it was the graphics card switching that would cause that.
I wish there was an easy way to tell which graphics card was being used when running applications. I know you can configure it yourself, but the reason I ask is that I play quakelive sometimes, and i'm wondering whether it uses the Nvidia GPU or the Intel HD when I play. -
Just for the reference of folks on here, the 270.61 drivers with the modded INF file do not work with Battlefield: Bad Company 2. I was getting all kinds of screen flickering issues.
User beware. -
NerdsAreMyBrethren Notebook Enthusiast
That or force it to use the GPU through the manage 3d settings. -
Everyone try the 275 beta driver its amazing i posted a modded inf in the forum.
-
how so... and ill stay away from beta's.... unless i actually have an issue with 270.61
And humjaba I had that too.... You have to manually set your screen response from 40hz to 60hz....... -
It boosted my 3dmark11 score by 100 points and it also fixed bfbc2 flickering issue
-
Will optimus still work with this moddified driver?
-
No reason it shouldn't, that I can think of anyway.
-
Okay cool thanks.
-
Ya it works the purpose of optimus is you do not need combined driver packet for both cards like you did with switchable graphics. you can independently update each card of you choice
Status of GPU Driver updates for the M14x
Discussion in 'Alienware 14 and M14x' started by Boby b, May 12, 2011.