I don’t know what’s sadder, the fact that I still have to go through this workaround to get my NVIDIA graphics card to display the correct color range to my HDTV over HDMI, or that this page of essential instructions has been lost to the internet. I have grabbed the text from The Wayback Machine and am reposting it in case others could use the help.
The following text originally appeared on the following webpage (I will gladly give attribution if the proper owner is identified):
How to fix NVIDIA blurry or fuzzy screen or text caused by driver installation
You install the NVIDIA drivers and your screen or text becomes kind of “fuzzy” or “blury”.
Kind of “washed-out”, but not quite.
It might look almost as if it was not displaying in 32-bit color, even though it is.
If you put your mouse cursor over a blue background, you see a ghosted image of your mouse pointer next to it.
This “ghosting” happens, not when moving fast like LCD screen ghosting, but just when the mouse is sitting still.
The ghosting occurs with all objects, not just the mouse — including window borders, etc, and it’s mostly in the vertical orientation.
When you UNINSTALL the drivers, it returns to normal. When you INSTALL the drivers, the problem re-appears.
The problem can occur on many different hardware and software platforms, including WinXP, WinVista, Win7, Linux;
… including many different NVIDIA GeForce cards;
… including many different monitors (both LCD and CRT & both 4:3 and widescreen aspect ratios).
This is nothing new. NVIDIA has been aware of this problem for YEARS, and has done nothing. They do not officially recognize this as a problem. Yet search in google for “nvidia blurry screen” or “nvidia blurry text” and you will clearly see hundreds of people asking for help with this problem. If you havn’t experienced it yet, consider yourself one of the lucky majority. But do not doubt that it is a real annoying problem for many many others.
The problem is simply that a registry key is missing from the NVIDIA installer .inf file. We must find that file and add the appropriate line of text, before running the setup. Here is the step-by-step instructions to do it:
Part I – Get the drivers
- If you have not done so, go to nvidia.com and download the drivers for your card.
- Run the driver executable. A wizard will come up, asking you where it should extract the files, and you will have to click a checkbox that says something on the order of “I agree” and click next a few times.
- Eventually, it will pop up a different wizard — a NVIDIA-decorated one that looks like the following screenshot. When you see it, cancel the wizard, and of course tell it that “you’re sure” that you want to cancel, etc.
- Ok, now navigate to the folder that you told it to extract to in the above wizard. There is a file in there called nv_disp.inf or it could be something else (depending on your driver version), like nv4_disp.inf ornv_disp_win7.inf. The path should look something like this:c:\NVIDIA\<your OS>\<your driver version number>\<your language>\nv_disp.inf
- Open that file up with notepad.
- Ok minimize this file. We’re going to set it off to the side for now, but we will come back to it in a minute and add a line or two of text in it.
Part II – Find your monitor’s unique EDID
The EDID is different for every type of monitor. You need to find it by doing this:
- First, you need to use an EDID editor to find your monitor’s unique line. To do that, download this utility, unzip, and run it.
http://www.tucows.com/preview/329441 (Alternate download: Phoenix_1_3.zip)
- Ok when it’s open, click New.
- Click Extract Registry EDID.
- This box will pop up. Make sure you click on the row, before clicking the Extract EDID button.
- Now all the info will be filled in the boxes. Click the Byte Viewer button.
- This screen with all the numbers will appear. The numbers you need are in Row 00, Columns 08 thru 0B
Part III – Prepare the line that we will need to stick in the .inf file
As I said previously, the problem is the lack of a registry key in the installer .inf file. Basically, when it installs without this registry key, it doesn’t know the details about your monitor that it needs to make a sharp picture. So all we have to do is supply it with the right info in the form of this line.
- Most of the line is the same for everyone:HKR,,OverrideEdidFlags0,%REG_BINARY%,XX,XX,XX,XX,00,00,FF,FF,04,00,00,00,7E,01,00
- The XX,XX,XX,XX is the four bytes you got from the EDID in the previous part (circled in red in the screenshot above). Again, they are different for each monitor.
Part IV – Putting the line you made into the right spots within the .inf file
- Go into the .inf file that you set aside in Part I.
- Hit CTRL+F to pull up the Find box and look for any or all of the following sections:[nv_SoftwareDeviceSettings]
Or something else similar. I can’t be too much more specific because depending on what driver you download for whichever graphics card series you have, will determine what sections there are.
- For my specific system, I added it (the bold line) to these two sections:[nv_commonBase_addreg]
- After you added your unique line to the proper places, save the .inf file and close it. Proceed to Part V.
Part V – Finishing
- Go to control panel & uninstall your current video drivers.
- Go to the folder and click setup.exe to install the drivers with the modified .inf file.
- There will be a message asking if you’re sure you want to install the driver b/c its not trusted or something like that. That’s just b/c you modified the .inf file and the checksum didn’t add up. Click OK to install anyway.
- Everything should be good now, if you did it right. If not, then you did all this for nothing b/c you obviously had some other problem from the one I am talking about in this How-To. Good luck!
A modern remix of audio from Mr. Rogers, a great American (and Presbyterian minister)!
“A few suggestions for breaking through event boundaries, on behalf of NewsFeed: mentally repeat the decision or action as you enter the room, announce what you’re about to do, or move to a one-room apartment.”
Originally posted on NewsFeed:
“I know I came in here for something, but I can’t remember what it is …”
If you’ve ever said something like this, you’ve probably experienced an “event boundary.” Many, if not all, of us have had the experience of walking into a room and forgetting exactly what it is we came in there to do.
The University of Notre Dame in Indiana recently conducted a study on this phenomenon, concluding that walking through doorways causes memory to lapse. As researcher Gabriel Radvansky explained: “Entering or exiting through a doorway serves as an ‘event boundary’ in the mind, which separates episodes of activity and files them away.”
That means that by the time you’re staring blankly at the kitchen counter, your brain has already moved on from the thought that led you in there, and you can’t…
View original 66 more words
In addition, MLS has given up on relying on the better angels of players’ nature to stop the diving and simulation American audiences so abhor. If a player tumbles to the ground without contact or feigns injury without being touched, he’ll be forced to write a check. If that action results in a goal or card that shows up in the box score, a suspension is likely as well.
Major League Soccer in the United States is taking a hard stance on diving. This is wonderful.
Here’s the Video and PDF I used to build my homemade HDTV antenna. Still works great.
Originally posted on MAKE:
Digital converter box? Check! Great reception? Not so much. John Park shows how to take a fistful of wire coat hangers and make a TV antenna that gives great digital reception. While he’s at it, he also makes a video camera stabilizer using metal piping and counterbalance weight; great for at-home moviemaking.
This is a little long, but it is brilliant. Bret Victor gives a presentation that not only demos some insanely cool software development tools, but with a worthwhile underlying message. If you have the time, take a look (and make sure to hit that full screen button).
(Via Coding Horror)
I’m not a logo designer, but I play one on the internet. I’ll just leave this here.
From last night’s tornado in Dexter, Michigan, this amazing tidbit buried in a AnnArbor.com story.
Washtenaw County Sheriff’s Deputy Ray Yee was the first officer on the scene in Dexter.
Yee approached one destroyed home Thursday, and saw a hand sticking out of the rubble. He pulled out an elderly man, who was shaken but walked away.
“That’s the best part,” Yee said. “Every place I went to, I would have thought I would have found somebody laying there — deceased or whatever. But, knock on wood, everybody was OK.”
Great to see the community coming together and the cleanup starting in earnest so quickly.