|
Posted by R. C. White on January 8, 2008, 11:47 pm
Please log in for more thread options Hi, Jerry.
Thanks for the feedback. I don't even use H&B, but it's good to know that
today's Q2008 R6 fixed something.
I wonder what was in it for us Q2008 Deluxe users?
RC
--
R. C. White, CPA
San Marcos, TX
(Retired. No longer licensed to practice public accounting.)
rc@grandecom.net
Microsoft Windows MVP
(Currently running Quicken 2008 Deluxe in Vista Ultimate x64)
>
>> For the last couple of weeks Quicken 2008 H&B has been intermittently
>> gobbling up all my available memory then failing. It usually happens
>> after
>> I've exited Quicken and all Quicken windows have disappeared from the
>> screen; qw.exe keeps running and in a minute or two, after having gobbled
>> up
>> over 1.6G of memory, it aborts. Occasionally it gobbles all memory and
>> apparently terminates normally. Except for Quicken Help (now fixed) I
>> haven't noticed any other problems.
>>
>> I'm running Windows Vista and both Quicken and Windows have all the
>> latest
>> patches.
>>
>> I've run Validate and Super Validate, renamed my Price History file, and
>> tried my 12/5 Quicken backup file (the date I installed Q08) but the
>> problem
>> still occurs. If I don't get any better suggestions, I'll reinstall
>> Quicken
>> tomorrow.
>>
>> It may be unrelated but for some reason I have both AnswerWorks 4.0 and
>> 5.0
>> folders. Perhaps because I previously ran Quicken 2006 H&B on this
>> machine?
>>
>> Any suggestions?
>>
>> Jerry
>
> FWIW this problem wasn't intermittent; it happened every time I exited
> Quicken.
>
> My workaround was to kill the qw.exe process, using Windows Task Manager,
> a
> few seconds after I exited Quicken. Apparently this did no harm to
> anything.
>
> It wasn't a corrupted Quicken DB - the problem occurred with a
> newly-created DB and even if I just launched Quicken then exited without
> even opening a DB.
>
> Nor was it Quicken program corruption - reinstalling Q08 and reapplying
> all
> updates didn't fix it.
>
> However, today's Q08 R6 update did seem to fix the problem. So it looks
> like
> it might have been a Q08 bug.
|