🚀 go-pugleaf

I've just had a very bad experience with Quicken 2.0 for Windows, and even
though I am a mild-mannered individual my frustration has driven me to post
this note.

I was a Quicken 5 (DOS-version) user switching to Quicken 2 (Windows), being
guaranteed that the data files were 100% compatible between the two.
Unfortunately, this was not the case.  Quicken 2 crashed with a general 
protection fault immediately upon trying to load the Quicken 5 (DOS) data.

Making a long story short, after paying as much for telephone calls to their
support line as we did for the product, and receiving less help and
troubleshooting than I had already performed myself, I got final brush-off from
Quicken today.  They never even investigated the problem given the detailed
segment/offset information available and the Dr. Watson log information.
They suggested I get my PC checked out, even though it runs dozens of other 
software packages (including Quicken 5, and Quicken 2 with new files)
successfully.  The PC even serves as the development environment for my work,
running the windows SDK and MS C/C++ compiler.

I assume that in most cases Quicken works fine, but this experience was so
negative that I felt compelled to write.  Perhaps it will save someone some
headaches in the future.

Chuck Black    Hewlett-Packard / Roseville Networks    chuckb@hprnd.rose.hp.com