Recommended Posts

Ok my WEI score for graphics wenr up from 3.1>3.4, and desktop went up from 3.0>3.1. (7300GS).

I REALLY HATE THE NEW CONTROL PANEL INTERFACE!!!!!

Whats the differences?

Nevermind i'll post them from Guru3D here.

Wait I can't find it...

You're not a gamer and you have an 8800GTX? :blink:

Yah, I guess I have too much money at the moment but not enough time to play any games.

Anyway, this driver is crashing more and more often doing simple things like surfing the web. I think I'm going to have to roll back soon.

EDIT: just found post in Vista Support

please delete

Just had this email from nvidia

NVIDIA Windows Vista Driver News

April 17, 2007

Dear NVIDIA Customer,

On behalf of NVIDIA, the Vista Quality Assurance team would like to thank our user community for participating in the bug report system. The information you provided is valuable and will help us improve the quality and performance of our drivers.

There is a new Windows Vista Beta driver release available to download from NVIDIA, v158.18. This is a new driver which will support GeForce 6, 7 and 8 series graphics boards; it does not support GeForce Go mobile GPUs. Please continue to check with your notebook manufacturer for a new driver for GeForce Go GPUs. GeForce FX users should continue to use the v96.85 driver.

Before installing the new Windows Vista drivers, please make sure to review the installation steps for the v158.18 driver. These instructions will be found after clicking on the 'Download Driver' link on the next page.

Download Windows Vista 32-bit driver

Download Windows Vista 64-bit driver

Here is a summary of new features and bug fixes this new driver addresses:

New Features

Adds support for GeForce 8600 GTS, GeForce 8600 GT, and GeForce 8500 GT, GeForce 8400 GS, and GeForce 8300 GS GPUs.

Increased performance in 3D applications.

PureVideo? HD support.

Add support for forcing Vertical Sync in DirectX applications.

Updated NVIDIA Control Panel with improved user interface (Please see the Release Notes for more details).

Numerous game and application compatibility fixes (see below for some of the top issues).

Key Bug Fixes

Fixed numerous "Display driver has stopped responding" error messages.

"This is not Vista" error message appears when installing Windows Vista 32?bit drivers on a Windows Vista 64?bit operating system. The error message did not indicate which operating system (32?bit or 64?bit) is installed. NVIDIA has fixed the installer error message to better tell the end user which version of Windows Vista drivers and operating system are running.

Warhammer 40k Dawn of War (all versions) has driver error message and does not run.

The gamma and brightness controls in the NVIDIA Control Panel Adjust Desktop Color Settings page do not function or affect the desktop appearance consistently.

GeForce 8800 GTX/GTS, Windows Vista Ultimate Edition: Text in the Ultimate Game:Hold'em flashes at the start of the game.

GeForce 8800 GTX: Elder Scrolls: Oblivion-NVIDIA Control Panel antialiasing does not work when HDR is enabled.

GeForce 8800 GTX: Half Life 2-fog is broken or misapplied. This fix requires the user to update their Valve Source?based games to the latest versions of the game engines.

GeForce 8800 GTX: Splinter Cell Double Agent-there is corruption in the game.

GeForce 8800 SLI: The system does not resume from S3 mode when SLI mode is enabled.

GeForce 8600/GeForce 7900 GTX SLI: "Display driver has stopped responding" error message appears when changing the resolution, or when resuming from Standby\Hibernate.

GeForce 8800 GTX: The Windows Experience Index tool crashes when trying to refresh the system score in Windows Vista 64-bit.

Please view the driver Release Notes for a list of all of the fixed issues in this driver release.

Windows Vista Limitations

In previous drivers, Vertical Sync (vsync) was listed as a Windows Vista limitations. However, NVIDIA has worked around this issue in our drivers.

Please view the driver Release Notes for a list of all Windows Vista limitations.

Application Limitations

NVIDIA has found application limitations and is continuing to document in our driver Release Notes. Please view the driver Release Notes for a list of all application limitations.

NVIDIA Vista Graphics Driver Issues

Please view the driver Release Notes for a list of all of known issues in this driver release.

NVIDIA Features No Longer Supported

Please view the driver Release Notes for a list of all features no longer supported

Edited by Unimatrix Xero

Guys,

I have a samsung lcd connected via dvi/hdmi to a Nvidia 7900 GTO. I just installed vista and these drivers but have the problem that due to overscan i miss out on a big section of my windows screen.

In Windows XP i would just use pan & scan in the Nvidia Control Panel to fix this issue. In Vista it is saddly not possible to just Pan & Scan and thus fix the overscan problem.

Is their any other way to fix the overscan problem? Could I use custom resolutions? How do I do that? Hope you guys can help me out.

Thanks

this is nuts.

I installed the new drivers on my system running two 6600 cards, and have noticed two things:

1. my second monitor has been detected as non-PNP and therefore its max resolution is 1024x768

2. my WEI went down from 3.8 to 3.4 compared with the 97.46 drivers.

looks like going back to the 97.46 drivers.

at least these drivers installed without doing the BSOD like the 100 drivers did.

These drivers haven't fixed the screen corruption bug I was getting from the last drivers (101.something.or.other I think). Basically any Vista UAC prompt and also the login screen is a mess. Virtually unreadable. Everything else seems fine. Haven't had a chance to test gaming performance yet.

BTW, Vista 32bit, 7600GS AGP.

Finally some new drivers for Vista! :) perhaps my 6800GS will run a little better now....still I'm worried about installing them, since your required to uninstall the old drivers...will Vista think your installing new hardware and need to be re-activated?? (updating my m/b drivers de-activated Vista on me) to be honest I preferred XP when is comes to activation, you activate it once and that was it (till you reinstalled the OS) but Vista seems alot more sensitive to system changes...

Finally some new drivers for Vista! :) perhaps my 6800GS will run a little better now....still I'm worried about installing them, since your required to uninstall the old drivers...will Vista think your installing new hardware and need to be re-activated?? (updating my m/b drivers de-activated Vista on me) to be honest I preferred XP when is comes to activation, you activate it once and that was it (till you reinstalled the OS) but Vista seems alot more sensitive to system changes...

Edit post timed out...

EDIT: I installed them anyway, no dramas Vista didn't ask to re-activate so all is good...now to see if anything runs better!

EDIT2: Sadly no :( my games still seem unplayable in Vista...guess my card just can't handle gaming in Vista (it is getting old)...still at least I can still game fine in XP. Probably won't go pure Vista till my next computer, I think this one is just too old to handle the gaming side if things in Vista :p

Edited by Xerxes
That's what I'm wondering. It's a HUGE jump in version number.

Yeah, but read the release notes PDF document in the original post's link... :blink:

Not many fixes and changes in 158.18, but the document also covers 158.14 which was the first documented post-101 release, and wow... :blink:

I think the version number jump is warranted -- there are heaps of very important Vista 64, as well as SLI fixes for one thing, along with "driver has stopped reponding and Vista had to restart" fixes.

my gaming performance went from 4.8 to 4.4 with these drivers i have a 7600gs :(

Look more for actual game performance than at those scores. They're sometimes a bit misleading. What matters is your gaming performance, not those numbers.

The driver is great on my 7800GS, but they still didn't' fix the desktop color settings wont get saved after a reboot, I filled the bug for the third time!

As for people who ask why the big jump in driver version, I have a logical explanation, that older versions (say 101.70), is actually version "7.15.11.0170" on the device manager, and games used to detect the last 4 numbers as the installed ForceWare version, and then adjust game's features accordingly. The Sims 2 for example wont enable AA because it thinks no proper driver is installed, "01.70" in our case.

But when it jumps in "158.18" = "7.15.11.5818", it's now detected as "58.18" which is a decent version for games that aren't series 100 aware. And The Sims 2 now have the AA option back.

Hope I was clear :p

And for the one asked for a screenshot, see below:

post-49195-1176901169_thumb.jpg

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • I don't understand the vision. Do people really want to buy a new computer from Dell with 6 browsers installed? We all keep asking for Microsoft to stop having so much junk on their OS, and adding a bunch of browsers seems to go against that. Ideally, we would just be asked what browser we want during OOBE but Google is just going to pay Dell a bunch of money to include Chrome. Additionally, would you want your phones to start including all the browsers too when you get them? The only thing I ever wanted was to be able to uninstall IE or edge and I believe you are now able to. I do agree that microsoft needs to chill with their "are you sure you don't want to try edge before you install chrome" ads when going to download chrome.
    • The funny thing here is that like 70% or so of the web browser users use 'Google Chrome' as web browser. What I don't understand is that why on earth would ANYONE choose 'Google Chrome' on Windows when 'Microsoft Edge' is not just better in most things, but it's already there right out of the box for the Windows users. Microsoft Edge has less data collection (yes, that's a fact), less RAM usage and is more optimized for Windows (as it's a Microsoft product) right out of the box. I'm sure you will come with the argument of bloat in Microsoft Edge. Sure, but most of that can be fixed with a simple tool (there are many good ones out there for this). Yes, that require a couple of clicks in the same way as it requires several clicks to install 'Google Chrome'. And I'm sure you really love the 4 GB of AI-slop data 'Google Chrome' is downloading for Chrome without you agreeing to it. Fun right? Sure, the way Microsoft is pushing 'Microsoft Edge' on users might not be the best way of doing it and might need to change. But I would never choose 'Google Chrome' over 'Microsoft Edge' today anyways. I'm sure there was a period back in the days when 'Google Chrome' actually was better in most things, but that period is not today.
    • JetBrains rolls out IntelliJ IDEA update with Markdown preview fixes and more by David Uzondu Image via JetBrains IntelliJ 2026.1.3 from JetBrains has landed, bringing several highly requested bug fixes that target common UI glitches and terminal rendering issues. If you run tmux inside the integrated terminal, the IDE no longer renders the cursor above the active line. The Markdown preview bug, which was fixed in this release, had annoyed developers for quite some time, as the preview pane failed to render images saved outside the project directory. Instead of displaying the actual image, the IDE simply showed a broken image icon, a problem that stuck around for two years before this update. Over on Windows, developers running WSL can now use wsl.exe to spin up their environments without losing terminal functionality. In previous builds, launching a terminal shell with something like wsl.exe -d ubuntu inside a Windows-based project broke both shell integration and active process detection. Other bug fixes in this release include: An issue where Gradle sync incorrectly reported success as a failure on WSL when using Gradle 9.5.0. A syntax highlighting bug that flagged valid Java for-loop initialization blocks with multiple statements as incorrect. A warning bug that triggered a false non-null local variable alert when using JSpecify annotations. A database generation bug that hid the option to use a DELETE statement instead of a TRUNCATE checkbox. A Kotlin highlighting failure where an assertion error in the Gradle redundant library inspection broke error highlighting. A UI bug where the ComboBox popup lacked a maximum height restriction. A Snowflake syntax error where DataGrip failed to support the "create temp" command. A Svelte syntax parsing failure that incorrectly flagged quotes inside inline expressions. A VCS repository manager deadlock that triggered thread pool exhaustion. A memory leak where the LazyTree component kept all previous versions of a tree in memory. IntelliJ 2026.1.3 is the third bug fix release for the IntelliJ 2026.1 series. The first one landed back in April with a fix for the WSL Python interpreter freeze, another fix for guest participants using Emmet abbreviations, and corrected WildFly server deployment errors.
    • That stupid annoying Sign in with Google on all these sites now... get the fk outta here
  • Recent Achievements

    • Collaborator
      Asgardi earned a badge
      Collaborator
    • Conversation Starter
      mobandz earned a badge
      Conversation Starter
    • Apprentice
      fernan99 went up a rank
      Apprentice
    • One Month Later
      nothanks earned a badge
      One Month Later
    • One Month Later
      B2Proxy earned a badge
      One Month Later
  • Popular Contributors

    1. 1
      +primortal
      469
    2. 2
      PsYcHoKiLLa
      243
    3. 3
      Skyfrog
      79
    4. 4
      FloatingFatMan
      73
    5. 5
      Michael Scrip
      60
  • Tell a friend

    Love Neowin? Tell a friend!