NVIDIA to replace dated GeForce 6/7/8 WHQL drivers Next Week


Recommended Posts

The most recent WHQL drivers for the GeForce 6/7/8 series of cards in fact are a bit dated and were released back on December 19 and 20 of last year 2007. As of today, these are the current drivers offered by NVIDIA:

GeForce 6/7/8 Series

32-bit Windows XP: ForceWare Release 169.21, December 19, 2007

32-bit Windows Vista: ForceWare Release 169.25, December 20, 2007

64-bit Windows XP: ForceWare Release 169.21, December 19, 2007

64-bit Windows Vista: ForceWare Release 169.25, December 20, 2007

GeForce 9 Series

32-bit Windows XP: GeForce Release 174.74, April 1st, 2008

32-bit Windows Vista: GeForce Release 174.74, April 1st, 2008

64-bit Windows XP: GeForce Release 174.74, April 1st, 2008

64-bit Windows Vista: GeForce Release 174.74, April 1st, 2008

The 6/7/8 series are in fact already 18 weeks old, which is quite substantial in this industry segment, especially if you consider that ATI releases new driver packages each month.

However, NVIDIA told us that new drivers are on the way: NVIDIA?s Chris Daniel told us that &quothe drivers are going through WHQL as we speak. ETA is sometime next weekb>."

NVIDIA seriously dropped the ball here, but the situation is getting fixed. We wonder why NVIDIA does not step up to the table and offer monthly or at least quarterly driver updates for its products. i>

http://www.tomshardware.com/news/nvidia-ge...ivers,5262.html

I always use modified Forceware sets based on betas - the rate betas come out sometimes, or even most of the time outpaces Catalyst's release schedule. With that said, WHQL certification barely means anything to me amyore, other than an annoying dialog to dismiss for each new driver install.

Wow, people are complaining like it's the most necessary thing in the world. The current ones work just fine. New drivers aren't going to change your experience THAT significantly.

Oh Whoopy-do.

There's not a game I can't play in full settings (other than crisis, which AA is off for) and I have no problems.

Good news for those who do have problems in games, or want more performance, but mine are running great.

The most recent WHQL drivers for the GeForce 6/7/8 series of cards in fact are a bit dated and were released back on December 19 and 20 of last year 2007. As of today, these are the current drivers offered by NVIDIA:

GeForce 6/7/8 Series

32-bit Windows XP: ForceWare Release 169.21, December 19, 2007

32-bit Windows Vista: ForceWare Release 169.25, December 20, 2007

64-bit Windows XP: ForceWare Release 169.21, December 19, 2007

64-bit Windows Vista: ForceWare Release 169.25, December 20, 2007

GeForce 9 Series

32-bit Windows XP: GeForce Release 174.74, April 1st, 2008

32-bit Windows Vista: GeForce Release 174.74, April 1st, 2008

64-bit Windows XP: GeForce Release 174.74, April 1st, 2008

64-bit Windows Vista: GeForce Release 174.74, April 1st, 2008

The 6/7/8 series are in fact already 18 weeks old, which is quite substantial in this industry segment, especially if you consider that ATI releases new driver packages each month.

However, NVIDIA told us that new drivers are on the way: NVIDIA?s Chris Daniel told us that &quothe drivers are going through WHQL as we speak. ETA is sometime next weekb>."

NVIDIA seriously dropped the ball here, but the situation is getting fixed. We wonder why NVIDIA does not step up to the table and offer monthly or at least quarterly driver updates for its products. i>

http://www.tomshardware.com/news/nvidia-ge...ivers,5262.html

Any word on when we'll see that PhysX software for 8x series and newer cards?

Any word on when we'll see that PhysX software for 8x series and newer cards?

Won't they need to build the hardware into the GPU's first?

Honestly, I'm not concerned with Nvidia drivers nearly as much as I am with ATI drivers. ATI release faster but I don't know how many times I come across problems and have to roll back. Either give us stability or don't f***ing release it in my opinion. :hmmm:

If you're going to post the news, post the news. Keep the bitching and crying in the 12 and under section.

Thanks.

So sorry to annoy you with our discussion. Perhaps you don't have to read our "bitching and crying"... Maybe some of us have opinions of our own and like to express our thoughts to other members of the community, isn't that what Neowin is all about?

If you're going to post the news, post the news. Keep the bitching and crying in the 12 and under section.

Thanks.

Then read the first post and ignore the rest, it's really not that difficult =\

What's the point of consistently meeting a monthly release schedule when they're is no real reason to update the drivers that often. It makes sense to release an update when there is something worth adding, after it has been tested - rather than just rolling out minor, buggy updates each month just to meet the schedule.

Saying that your driver version is working fine is besides the point guys. That's not the intent of this news post. Nvidia does in fact need to work on that. I find ATI drivers much more stable generally. Usually, driver updates are great for those with the latest chipsets/gpus. Those with slightly older hardware, well it barely even affects them.

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

    • No registered users viewing this page.
  • Posts

    • Was it too much to ask to show the icon in this article?
    • Frankly, I blame whoever is writing such articles. "A big improvement/update and/or new feature is now available to everyone! Also, use this unofficial tweak tool to enable it because it actually isn't available to you yet officially and might not in fact even be entirely ready or whatever, hence why it is perhaps not enabled for you*. But it's great and you should enable it!" I mean there's nothing wrong with sharing info about some feature you might need to enable via unofficial means, of course. It's just that these articles tend to essentially end up being two news pieces in one, and one of them tends to be a bit misleading. (*Yes, yes, the "it's a controlled rollout!" thing. Not a fan of that one either. The argument, not the actual rollout.)
    • Thank you. Will do. I read in the release notes that editor config might be at play here.
    • Actually, I think even Microsoft doesn't know how to control it
    • OpenAI is making Codex more useful in Chrome and the cloud by Pradeep Viswanathan OpenAI's Codex now has more than 5 million users, up nearly 4x from earlier this year. To further accelerate Codex's growth among developers, OpenAI today announced that it has agreed to acquire Ona, a company that builds secure cloud execution and orchestration technology for developers. Ona will enable developers to run Codex with persistent and controlled cloud infrastructure for long-running agentic workflows. Right now, most Codex execution happens locally on developers' laptops and PCs, and the agents work continuously for hours. Through Ona, OpenAI aims to make Codex agents keep working for days without being tied to a user’s local machine or an active session. This will be an important capability for enterprises that want to deploy AI agents in production while maintaining control over infrastructure, data, security boundaries, credential scope, logging, and review workflows. Like any acquisition, the deal is still subject to customary closing conditions, including regulatory approvals. Until the deal closes, OpenAI and Ona will continue to operate as separate companies. After closing, Ona’s team will join the Codex team to improve developer workflows. Alongside the Ona acquisition announcement, OpenAI today introduced a few Codex updates. Developers can now save Codex rate limit resets and use them later instead of losing them when they are not needed immediately. OpenAI is also adding a referral option where users can invite a friend to Codex and get a saved rate limit reset. OpenAI today also announced a developer mode for browser use in Chrome and the Codex in-app browser. With this mode, Codex can use the Chrome DevTools Protocol to debug web apps, inspect pages, and work more directly with browser-based development workflows. Developers can use this when they want Codex to profile JavaScript, inspect console output and network traffic, examine web page states including the DOM and applied styles, and more.
  • Recent Achievements

    • Week One Done
      davidbazooked earned a badge
      Week One Done
    • One Month Later
      Jamswaz earned a badge
      One Month Later
    • Week One Done
      Jamswaz earned a badge
      Week One Done
    • Rookie
      Marzoid went up a rank
      Rookie
    • Community Regular
      coch went up a rank
      Community Regular
  • Popular Contributors

    1. 1
      +primortal
      509
    2. 2
      PsYcHoKiLLa
      186
    3. 3
      +Edouard
      157
    4. 4
      Steven P.
      83
    5. 5
      ATLien_0
      75
  • Tell a friend

    Love Neowin? Tell a friend!