Online updates . . stuck again...

I think "what works for me" summaries like this are quite useful as are both "works for me too" and "doesn't work for me" replies.

But the angry posters in this thread are validly complaining that they often have to wade through too many such suggestions, none of which work for them.

I can't comment on the mouse issue but FWIW I have absolutely no flickering problems with my NVIDEA GeForce 8600 GTS.

When I spoke of "frustrating problems" I should have stated that I meant only those for which no known and logically plausible fix will eliminate the problem on the machine of the frustrated user. If there's a known mouse or printer or graphics driver issue and users don't even try the suggested driver fix simply because "only Quicken has the problem" then I agree that

But some of these problems are really nasty and serious. They appear randomly and/or for only some users. Their number seems to be growing with each new Windows and Quicken release and there is often no effective way to isolate their cause. Fixes, even if they exist, work on only some machines or for a limited time until the problem mysteriously reappears. The fact that the problem may not be in the Quicken code is little consolation to angry and frustrated users who don't see the problem in any program but Quicken. And when people get angry and frustrated they often justifiably get a little irrational. That's the other side of the coin.

Both sides have valid issues but there's no need to sling poo at each other - you may wake up Andrew DeFaria :-)

Ditto for my NVIDIA GeForce 8500 GT

"Eric J. Holtman" wrote in news:Xns9C6286731CC4ejhericholtmamcom@216.168.3.30:

I have no idea what the last 3 words have to do with product development. If a fix or workaround works for any appreciable percentage ofusers it is useful for them. It isn't really for those for whom it doesn't help, but that doesn't require Eric's language. As explained elsewhere in this thread, MMS has done damage as have others (Logitech for one). The solution can possibly be achieved by collaboration, not by namecalling, by anyone.

And I have worked in software development for more than twice as long as you. Thanks for proving that you don't have a clue what you are talking about.

John Pollard

"John Pollard" wrote in news:9eKfm.223488$DP1.99777 @attbi_s22:

If ignorance is bliss John, you must be the happiest man in the world.

oh god... what next... "Liar, liar, pants on fire"?

did not! did too! DID NOT! DID TOOOOO!

Neener, neener, neener.

dieHard® wrote in news: snipped-for-privacy@4ax.com:

Well, since he can't really debate the argument using facts, that's pretty much all he's got.

I have seen the same problem with Quicken Deluxe 2007 on an XP Pro machine. After killing quicken with the task manager, I open a cmd prompt and enter:

ipconfig/flushdns

then wait a few minutes and try again. More often then not quicken will complete the update. Marty

Eric J. Holtman wrote:

The problem also occurs with Vista. Two comments:

1. Under Vista you have to run ipconfig as administrator. Either right-click on Command Prompt under All Programs -> Accessories, select Run as Administrator and respond to the UAC prompt or, more simply, type cmd.exe in the Start Search box then hold down Ctrl-Shift and hit Enter.

1. Going into Windows Mail and, if it fails to connect, clicking the Retry button also appears to repair damage to the IP mechanism and allows both Windows Mail and Quicken to start working again. I suspect that other Windows programs also detect and automatically repair this damage.

It's anybody's guess as to what is corrupting the IP mechansim but Quicken, or one of the drivers it uses, is high on my suspect list.