v61.71, v61.72, v61.76, v61.77, v61.78 9X/ME, XP 32bit, XP 64bit | NV, eVGA, PNY, HP/COMPAQ, DELL

[Kamika007z]

That what I've been thinking all along, it's got to be some other tweak interfering with it. Pieter, do you have the "My connected TV is not being detected" checked?

John

[mobilenvidia]

Yes that is caused by

HKR,, DevicesConnected,              %REG_DWORD%,    0x10101

I think this sets it ticked.

You could remove this and see what happens, this forces TV and monitor out.

This will require a reinstall though.

also

HKLM,"Software\NVIDIA Corporation\Global\NVTweak", NvCplAllowForceTVDetection,         %REG_DWORD%, 1

enables the setting to be changed in the first place, setting this to zero should remove the option I think.

This can be changed at any time in the registry under nvtweak in HKLM.

Might also have to remove the devicesconnected as well.

have a play with these.

Pieter.

[Kamika007z]

HKLM,"Software\NVIDIA Corporation\Global\NVTweak", NvCplAllowForceTVDetection,         %REG_DWORD%, 1

I set this to 0 and when I restarted the DisableApplyColorsAtStartup stays at 1. Now here's a new problem. Under troubleshooting, there's no checkbox or even an option for "My connected TV is not being detected" AT ALL. There's just an option to remove the checkbox for the "Display the NVIDIA Settings icon in the taskbar" option.

John

[Kamika007z]

Ok, I just got it working. Setting the "NvCplAllowForceTVDetection" to a value of 2 gives you back the checkbox in the Troubleshooting page. It also keeps the "DisableApplyColorsAtStartup" set to 1 and doesn't let it go back to 0. Hope this helps!

John

Edit: I also had DevicesConnected set to 0 from dabbling with the INF before installation as well.

Edit2: When I use RivaTuner I let it disable coolbits, leaving it to a value of 13. So when I restart my computer, I no longer have it flash black of any sort (I don't overclock). However, if you set coolbits to 3 it does flash black upon loading of windows during the welcome/desktop screen momentarily.

[mobilenvidia]

"NvCplAllowForceTVDetection" on my machine with zero = no checkbox, one = checkbox appears.

I havn't tried setting it to 2 yet.

Coolbits really only has two settings 3 for Overclocking page = flashing.

or zero for no overclocking and no flashing.

I'll play with this some more.

Pieter.

[Kamika007z]

Ok, I just redid the 30.23 INF in regards to these places:

-DevicesConnected to a value of 0

-NvCplAllowForceTVDetection to a value of 1

-I also removed the desktop cards from the top of the INF the ID's and the bottom.

-I also removed all aligart specific code, since I know of no notebook cards that use it. In the past when I made inf's with teraphy, I made sure to remove them (I used to also add omega's tweaks as well, but that's a entirely different story :) ). The one part that I haven't really looked into too much are the desktop specific areas where you have written ";Desktop only settings" so I left that alone.

Now that I installed with this INF, the "DisableApplyColorsAtStartup" goes to 0 but my Digital Vibrance does NOT revert. It stays the same!

I'll post the INF here as a downloadable if you would like to test it.

*Note: I set the DisableApplyColorsAtStartup back to 0 in the INF, because if you think about it, why would you want to disable your applyed colors at startup? It reverting back to 0 if set to 1 seems like it IS a bug from the driver. I believe it's a new function added by the 60 series driver and only should be set to 1 in rare cases. (Just a thought)

[christian]

Yea.. The 61.77 crashes the comp.. The watchdog file is below.

This is with pieters inf 30.23

//

// Watchdog Event Log File

//

LogType: Watchdog

Created: 2004-08-05 01:14:34

TimeZone: -60 - W. Europe Standard Time

WindowsVersion: XP

EventType: 0xEA - Thread Stuck in Device Driver

//

// The driver for the display device got stuck in an infinite loop. This

// usually indicates a problem with the device itself or with the device

// driver programming the hardware incorrectly. Please check with your

// display device vendor for any driver updates.

//

EaRecovery: 1

ShutdownCount: 68

Shutdown: 0

EventCount: 3

BreakCount: 3

BugcheckTriggered: 1

DebuggerNotPresent: 1

DriverName: nv4_disp

EventFlag: 1

DeviceClass: Display

DeviceDescription: GeForce FX Go5650

HardwareID: PCI\VEN_10DE&DEV_031B&SUBSYS_019C1028&REV_A1

Manufacturer: NVIDIA

DriverFixedFileInfo: FEEF04BD 00010000 0006000E 000A1821 0006000E 000A1821 0000003F 00000008 00040004 00000003 00000004 00000000 00000000

DriverCompanyName: NVIDIA Corporation

DriverFileDescription: NVIDIA Compatible Windows 2000 Display driver, Version 61.77

DriverFileVersion: 6.14.10.6177

DriverInternalName: nv4_disp.dll

DriverLegalCopyright: © NVIDIA Corporation. All rights reserved.

DriverOriginalFilename: nv4_disp.dll

DriverProductName: NVIDIA Compatible Windows 2000 Display driver, Version 61.77

DriverProductVersion: 6.14.10.6177

[mobilenvidia]

It looks like DevicesConnected might be the problem, I'll dig up my TV-out cable and have a play with this.

Removing the Desktop and ALIGART sectons will have no effect as they arn't called by the Mobile parts of the INF.

I did some expermentation yesterday, I deleted the entire NVTweak directory in the reg to see what would happen.

Everything still works.

DisableApplyColorsAtStartup will come into that directory (ie driver recreates a new dir) and sets it to zero.

Another settings also comes back 'CinematicPageState' depending on what happens inside the 'Color Colerrection' tab this is either zero, 1 or 255.

Once I find this cable I can test with a device attached (the reason why I have devicesconnected so I don't have to attach device first)

I can test some other things at the same time as well.

Pieter.

[mobilenvidia]

DevicesConnected was the problem, INF v30.25 has all the problems fixed.

Went through a marathon effort of tweak finding, and have everything as I'd like ot now.

NO more forced TV/CRT being attached :) which I found very handy for problem solving (no need for cables), but it had to go to solve the above problems.

I'll update other INFs as time allows,

Enjoy,

Pieter.

[Kamika007z]

Hey,

I'm glad you got it working! :) What do you mean when you said "(no need for cables)"?

Thanks,

John

[Bill]

He means he doesn't need to plug a CRT or TV up to test stuff.

[Guest big_gie]

Hi everyone.

Since I include the drivers on my Unattended Windows XP CD, I need all bytes to be compressed as much as possible. I use XP in french so I like having my drivers in french too. But since the international drivers containt ALL languages, there is too much unneeded data in the driver.

Pieter told me the files to delete, but that was for v61.76 and it seems that in v61.77 the files changed (they seems to be compressed now)

So I checked which languages/files it contained and wrote a small script (JScript) that will delete the language files you don't need.

Here it is, hope it will be usefull to someone else! :)

[mobilenvidia]

big_gie,

Repost this in to the utilities section, it will come in handy for anyone with a setup similar to yours.

Good work,

Pieter.

[jabberwalky]

Maybe there is also a Problem with Xp Service Pack 2? After installing the driver my Notebook want start over. After the Start screen the display turns black. After new starting the bluescreen opens and my harddidsk will be scanned. There are a lot of crossconnetions. They will corrected. After this XP starts. Next time of Starting same procedure. :)

Use the Toshiba 5200-903 with FX5600Go

Use this driver for playing Doom. It´s nice. :)

At all I think it's a good Driver. Very Fast. Got good benchmarks.

From other Forum I know the inf should habve a Problem with the Toshibas!

Maybe this guternet Forum inf should work. Try it tonight.

[mobilenvidia]

66.00 is supposed to be a rock solid driver according to 3DChipset as they have been using it for a few weeks now.

Pieter.

[mobilenvidia]

Yes the 'ModeSetBlankDelay' I would say is to blame here. (only setting that differs from my INF (other than resolution force)

As of yesterday, I have been finding out that this setting is making it's present felt.

For me it won't work in 66.00 but does in 65.62.

Adding this line must make it work for 61.77 !!

This is a setting that will vary from machine to machine, just my luck.

Pieter.

[draiken]

Hi, I just downloaded the 61.77 drivers for my Inspiron, and have the following problems:

If I do a TV-Out with a Composite cable, the image comes in Black & White

If I connect the TV with an S-Video cable, the image comes in Color

If I play a movie, selecting the TV as a Secondary Monitor, I just see half he image to the left, cropping half the movie (I tried all options, zooming, moving the screen with no use). If I select the TV as a Primary Monitor it looks good until I play a movie, then it just scrambles everything.

I tried with several video formats in case it was the codec, tried X-Vid, Div-X, Avi, MPGs, with the same results

My TV is NTSC and mostly use composite cable for tv-out, not having S-Video on all my TV's.

If I return to the latest driver in Windows update, everything works fine, but I don't have Dualview capabilities.

Can anybody helpme?

[®®®]

If I return to the latest driver in Windows update, everything works fine, but I don't have Dualview capabilities

Draiken, nobody answererd to your question. I don#t have an instant solution to your half-cropped problem, but an INF compare of the Windows Update version (btw which one do you use?) with the mobile INF from Pieter is the first step to do. Pay attention to the SoftwareDevice settings and ControlPanel settings.

[mobilenvidia]

Dell uses an odd ball TV-encoder on some lappies (not std Chrontel etc), I have a feeling that it's outputting PAL on the Composite TV-out and NTSC on the Svideo.

I could be wrong.

There might be a INF setting that can fix this, but not having the problem my self, I can't diagnose it.

[Guest zamo_x]

i have a toshiba sm30-852 with geforce fx 5200go (64mb). i have installed driver version 61.77 with inf 30.31. the problem is that i don't have any option to enable dualview mode when tv is connected. (the vga port is working)

is there a way to enable it, or i have to go back to my old toshiba drivers?

[Guest rassilon]

Is there any way to mod the nv4_disp.inf file so that the 61.77 drivers believe my monitor supports 60Hz?? Or is this something that can only be done from the OEM?

Check out problems with game crashing for details of the problem.

Perhaps another workaround is getting the drivers to support a 55Hz refresh rate. Anyone have any ideas?

Thanks,

rassilon

[®®®]

I read about your Leisure Suit Larry problem, but didn't put in much effort to really understand what exactly the problem is besides from not getting the 54Hz or 55Hz refresh rate frequency. I don't know about a 6x4 and 8x6 resolution. Do you mean 640x480 and 800x600? You also need to know that LCDs don't have any refresh rate.

Surely the following fact will NOT solve your problem immediately, but it helps understanding the work of the newer nVIDIA drivers:

Hide Modes Check Box Cannot be Cleared

? Background

One of the NVIDIA display property page dialog boxes contains the check

box labelled ?Hide modes that this monitor cannot display?. It is checked by

default, indicating that only the refresh rates supported by the monitor are

listed in the refresh rate drop down list.

The check box appears in the Device Adjustments->Monitor Settings page.

? Problem

If you clear the check box, click Apply, and then close the dialog box, the

check box is still checked when the page is re-opened.

? Explanation

This function is no longer controlled by the NVIDIA driver, but has not been

removed from the control panel in order to maintain consistency with driver

designs that are currently being shipped to OEMs.

And welcome to the Forum, Larry Fan :)

[Guest rassilon]

Hi ®®®,

I've been abbreviating the standard resolutions since the mid 90's, which was often done on the original Matrox Users Mailing List (now defunct, I believe). Much quicker to type as well as speak this way.

640x480 = 6x4

800x600 = 8x6

1024x768 = 10x7

1280x1024 = 12x10

1600x1200 = 16x12

All displays, whether it's a television, crt, lcd or plasma, have a refresh rate. Until recently, most LCD displays only use 6 bits per color, and dither between the adjacent colors of the desired display color. This fact in itself proves that there is a refresh rate for LCDs. Go check out Tom's Hardware for a more in depth look at how an LCD works.

Yes, the hide modes check box I mention is not in the nVidia CPL. It is located in the Monitor tab when accessing the Advanced property sheets from Display Properties. This is the first non-Matrox chip I've owned since '95, so this is my first foray into the nVidia scene and I have no clue as to how prior versions of nVidia drivers worked.

What I'm really interested in are the DCBOverride and OverrideEdidFlags registry entries found in the nv4_disp.inf file. These binary values are obviously meant to change something in the drivers, and are only found in the modded .inf files for LCDs that I've found on the internet.

[®®®]

Rassilon, i'm soory to say that there is few information available on "DCBOverride" and "OverrideEdidFlags". The "OverrideEDIDFlags" values solved the BlackBar problem on Toshiba Laptops. How it is coded is the secret of nVIDIA and Teraphy. I can't contribute here as it is beyond my expertise :)

[Guest maier]

I can't get the 64-bit drivers working on my machine with a geforce4 440go 64m.

The screen is realy bad with this driver and only on one half of the screen. Could somebody knows why?