SkyBeam

Unfortunately DH Mobility Modder for nVidia drivers does not work any more for latest nVidia drivers (186.18 at time of writing). There are several reasons for it:

The driver is now installed into a different location. It has moved from:
c:\NVIDIA\WinVista64
to
c:\NVIDIA\DisplayDriver
(NOTE: On Vista 64 - on others the old location looked different)

Then I noticed that the nv_disp.inf file name has no changed to uppercase: NV_DISP.INF. However this usually does not matter on Windows.

The most important change seems to be within nv_disp.inf/NV_DISP.INF. The devices section name has been changed from
[NVIDIA.Mfg.NTamd64.6.0]
to
[NVIDIA_SetB_Devices.NTamd64.6.0]

And it has two [Manufacturer] section entries now:
%NVIDIA_A% = NVIDIA_SetA_Devices,NTamd64.6.0,NTamd64.6.1
%NVIDIA_B% = NVIDIA_SetB_Devices,NTamd64.6.0

Therefore DH Mobility Modder does not find the section (I guess) and reports 0 files modified.

To verfiy this I manually copied the modified section-content to the new NV_DISP.INF and it still worked.

I also tried to modify Settings.xml and change my <Vista64 /> section within <DriverMfg /> at no avail.

Thanks for this great tool! Keep up the great work!

maxmuser

Hello, just downloaded the new Release - it takes very, very long to modify a single file of the new driver 186.03. I killed the process after 5+ mins while modifying the 4th file.
What time is expected to run and modify all files?

The old release modified the old driver 179.28 in less then 1 min.

Jet B

I'm also trying to run the modder tool on 186.03 and it is taking forever. It is constantly giving me the "Not Responding" message.

I will just let it buck for a while and hope it works through the kinks on it's own.

I just modded a new version of the ATI catalyst drivers for my wife's old laptop and it worked great.

Here's hoping...

god_paul

Hi all, actually, I found the similar problem like you encoutered now, the DH tools no longer support the latest nv driver starting from 185.85, Yesterday, I was excited to find the DH tools has been updated to 1.0.0.0 beta, however, after I used it to modified the latest nv driver-190.38, the nv setup said "setup did not install any fiile on your computer, pleas run it at later time", It seem even the 1.0.0 cannot tackle the latest nv drivers, nv was bound to have changed the structure of INF file....

maxmuser

Did the tool finish correctly? Any news?

Jet B

Actually, it never did complete. I just cancelled the process.

Mad props to the creator of the modder tool though, I used the ATI one to put a new Catalyst driver on my wife's old Inspiron laptop and it worked flawlessly.

If someone wants the 186.03 driver on their laptop that isn't one of the ones supported by it, the folks at laptopvideo2go have a modded INF file that will work. (Sorry if mentioning other websites is a no no, I just thought the information would be handy since the modder tool isn't working yet.)

And by the way, I have a Toshiba X200 with the Nvidia 8700M GT and the 186.03 drivers work great.

If you do download the driver from that site, the INF link was broken yesterday. Just download the driver they have and you will find another zipped folder inside the package containing all the other INF files you need. Just unzip it and take them out and put them back in the driver folder and it will install.

Spike

The modding of the files take indeed longer in the new version and if there are a lot of inf files in the folder then it can take long. This is because the program needs to check for the lines and the sections, because nVidia changes that often.

__________________

remmun

I have the same problem... I use Windows 7 x64 and the installer tell me that the system is not modified... I tried to use the driver from laptopvideo2go. I installed them but the problem is that their drivers are not HDCP compliant and I can't play bluray anymore with them. DriverHeaven mod tool was working until driver 182.50 with HDCP for me but not after this release... Nvidia must have changed something in their drivers.

Baldclimber

Longer indeed!

Tooks only seconds to mod nvaa.inf, has an unhandled exception when it next starts to mod nvam.inf, and now has been stuck for two hours displaying "Modifying nvam.inf started".

See error message:

See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.
************** Exception Text **************
System.UnauthorizedAccessException: Access to the path 'C:\Program Files (x86)\MobilityDotNETnV\Log\25-07-2009_Error.log' is denied.
at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
at System.IO.FileStream.Init(String path, FileMode mode, FileAccess access, Int32 rights, Boolean useRights, FileShare share, Int32 bufferSize, FileOptions options, SECURITY_ATTRIBUTES secAttrs, String msgPath, Boolean bFromProxy)
at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize, FileOptions options, String msgPath, Boolean bFromProxy)
at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize, FileOptions options)
at System.IO.StreamWriter..ctor(String path, Boolean append, Encoding encoding, Int32 bufferSize)
at System.IO.StreamWriter..ctor(String path, Boolean append)
at System.IO.File.AppendText(String path)
at msZPMhxeHRdRXfOiaw.N2CoHtTeGiaWblBYZ7.EBTBKEePh(St ring , String , String , String , String )
at MobilityDotNET.frmMain.p8oeRDTtu(Int32 )
at MobilityDotNET.frmMain.ewtcpUZLT(Object , EventArgs )
at System.Windows.Forms.Control.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnMouseUp(MouseEventAr gs mevent)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ButtonBase.WndProc(Message& m)
at System.Windows.Forms.Button.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.W ndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

************** Loaded Assemblies **************
mscorlib
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.4016 (NetFxQFE.050727-4000)
CodeBase: file:///C:/Windows/Microsoft.NET/Fra...7/mscorlib.dll
----------------------------------------
MobilityDotNET
Assembly Version: 2.0.3486.20355
Win32 Version: 1.0.0.0
CodeBase: file:///C:/Program%20Files%20(x86)/M...lityDotNET.exe
----------------------------------------
Microsoft.VisualBasic
Assembly Version: 8.0.0.0
Win32 Version: 8.0.50727.4016 (NetFxQFE.050727-4000)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL...isualBasic.dll
----------------------------------------
System
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.4016 (NetFxQFE.050727-4000)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL...089/System.dll
----------------------------------------
System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.4016 (NetFxQFE.050727-4000)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL...dows.Forms.dll
----------------------------------------
System.Drawing
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.4016 (NetFxQFE.050727-4000)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL...em.Drawing.dll
----------------------------------------
System.Runtime.Remoting
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.4016 (NetFxQFE.050727-4000)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL...e.Remoting.dll
----------------------------------------
System.Xml
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.4016 (NetFxQFE.050727-4000)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL...System.Xml.dll
----------------------------------------
************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.
For example:
<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>
When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.

tRiBUN

Hello, i have also a Problem with the new driver (190.38 WHQL + final 1.0.0.0 Modtool on WinVista 32 with GeForce 9800 GT). When i look to the inf file it was modified by the modtool. But when i start the installation it is only saying "nothing was changed" and this is the truth no driver was installed. I got no error or any other message. But only one file was modified.
Which other files need to be modified maybe i can do the rest by myself.

OffTopic:
For information, this driver version didn't extract like the older drivers. It is extracting, but when the installation is started an error message appears and the extraction folder will be emptied. So i simply extracted the driver with UniExtract.

chadwick21

Has anyone figured out how to get this going? I have been running the modder on 186.03 for 45 minutes and it has barely made any progress.

Spike

Are you using the official drivers from nVidia.com? I tried some of these drivers and it goes good, will look more into it.

__________________