Recommended Posts

Yeah, I'm using the Nvidia 185.20 Drivers for Windows 7 on my machine, noticeable improvement from the hosted Nvidia drivers that windows update found though not sure what version they would be

Yeah, I'm using the Nvidia 185.20 Drivers for Windows 7 on my machine, noticeable improvement from the hosted Nvidia drivers that windows update found though not sure what version they would be

185.20 are for Windows 7? They are WDDM1.1?

According to this http://www.nvidia.com/object/windows_7.html

the drivers on windowsupdate are the only ones nvidia has for W7. They 179.xx i believe and are WDDM1.1 not 1.0 like Vista drivers.

I'm using the *cough* leaked *cough* ones as seen here, they are 185.20 for Vista 64Bit but when you install it actually knows your on Windows 7 and launches setup for that, must include both.

http://www.2manydownloads.com/index.php?op...7&Itemid=54

Switched over to main OS to really give it a run for stability.

Absolutely no issues so far, and that's with me ripping quite a bit out of it with Vlite before installation.

So happy with the new monitor tuning applications in the control pannel - I can finally ditch Eztune!

185.20 are for Windows 7? They are WDDM1.1?

According to this http://www.nvidia.com/object/windows_7.html

the drivers on windowsupdate are the only ones nvidia has for W7. They 179.xx i believe and are WDDM1.1 not 1.0 like Vista drivers.

The 185.20 drivers are not WDDM1.1, but the 185.20 gave me many less graphics errors and good 15% benchmark increase over the 179's. I'm using a GTX 260.

so for those people who download the beta earlier off torrents, how can they legally activate the beta when MS start giving out the keys? remove the re-arm and then apply the key?

If it was a vanilla (non-modified) installation, you should be able to insert the key and away you go.

Public will only get 2.5Mil downloads then cease the links and keys :) wondering how hammered the servers will get and how will they count this number.

Very hammered I'd imagine, I'm not holding my breath on getting a copy...because of the time difference I'll probally miss out :( oh well, I'll probally try and get a key soon as I can (as I'll be able to get a key while at work but obviously not the beta, as someone might notice me downloading it :p) and work on getting the beta itself by other means ;)

Public will only get 2.5Mil downloads then cease the links and keys :) wondering how hammered the servers will get and how will they count this number.

I am having tough time getting it from MSDN - <200 KB/s. :pinch: Not to mention I still can't get keys from MSDN.

The 185.20 drivers are not WDDM1.1, but the 185.20 gave me many less graphics errors and good 15% benchmark increase over the 179's. I'm using a GTX 260.

Well Counter-Strike: Source works fine with the 179.23 drivers. Since that's the only game I play, I'll stick with them. Using a 8800 GT.

I'm using the *cough* leaked *cough* ones as seen here, they are 185.20 for Vista 64Bit but when you install it actually knows your on Windows 7 and launches setup for that, must include both.

http://www.2manydownloads.com/index.php?op...7&Itemid=54

Try the 181 drivers that were just released today. 185 is an old, alpha driver. I had a noticeable improvement from 185 to 181. The 181s also have the windows 7 installation screen.

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

    • No registered users viewing this page.
  • Posts

    • I think the car analogy is more this: Left hand drive, basic commands on the left side of the infotainment screen. Right hand drive, basic commands on the right side of the infotainment screen. Granted, you're not swapping between the two often so it's doesn't really work. But it's to do with the proximity of you (your mouse, or the driver) to the controls.
    • I mean, the old one was broken and so stupidly complex for many users, so I don't see that as a feasible option. A context menu needs to be simple to use, and for me the Windows 11 style actually worked really well for me, and many others. I used to have to scroll the damn context menu just to get to "file properties" in Windows 10. That was not a good experience, and I'm sure you'd agree. What they're trying to do is make it the best of both worlds, as clearly you'd prefer the Win10 style. I'm curious how they're going to do this.
    • The "Show more options" has its place, as does the simpler context menu, but it should perhaps be a separate fly-out rather than relaunching the entire, old context menu. The old context menu was getting absurd in Windows 10. Often I'd have to make the context menu scroll just to get to "File properties" on my old laptop. Even without much installed, the amount of items was just too much. It's a context menu, not a "do all" menu. Making it configurable is fraught with challenges too, so I'm interested to see how Microsoft tackles this one.
    • I don't hate the new menus, I am not a fan of the lack of features and how they went live when they clearly are not complete. The menu itself presents much better than the previous - but what's lacking (IMO) is: 1) Any kind of automated manipulation such as: "this goes on the new menu because you use this feature more often on this filetype" "this is rarely used and will fall back to the old menu" 2) Any kind of user manipulation such as: "a UI to add/remove/order items to the new menu"
  • Recent Achievements

    • Week One Done
      I2D earned a badge
      Week One Done
    • Week One Done
      Dr Jared Dental Studio earned a badge
      Week One Done
    • Week One Done
      RG INVESTMENT GROUP earned a badge
      Week One Done
    • Very Popular
      The Norwegian Drone Pilot earned a badge
      Very Popular
    • Very Popular
      s0nic69 earned a badge
      Very Popular
  • Popular Contributors

    1. 1
      +primortal
      484
    2. 2
      PsYcHoKiLLa
      262
    3. 3
      Skyfrog
      86
    4. 4
      FloatingFatMan
      64
    5. 5
      Michael Scrip
      63
  • Tell a friend

    Love Neowin? Tell a friend!