I have a MBP running 10.4.7. I installed XP Home Edition SP2 as a guest OS. No problems installing the OS. I installed Quicken 2004 and all of the updates so that Quicken 2004 is patched to rev. 5. I try to open my Quicken file, but it won't open. I also can't create a new file. The only thing that happens is that the XP CPU spikes to 100% and stays there. The MBP processor also becomes very active and the fan is loud. I've used Quicken natively on Windows for years; including this version of Quicken on XP Home, which makes me think this may be a Parallels issue, but I can't be certain. It could also be a 10.4.7 issue (I imagine). Or somehow a Quicken 2004 issue. Does anyone have Quicken 2004 running successfully? I've seen several posts saying people have Quicken running, but not everyone mentions what version they're using. I'm a brand new "switcher" and it was Parallels that convinced me that it was feasible. Any thoughts to help me troubleshoot this?
It works fine for me. It ended up being "confused" at time, when I used a shared folder for the data file folder. I now keep it on the parallels virtual disk, and it works great.
Uninstalling and then reinstalling Quicken fixed the problem. Although I had to go about it in a round about way. I use Quicken 2004 Home and Business. It was the unlocking of the Business features that was causing the problem. Here's how I solved it. 1. Uninstall Quicken. 2. Install Quicken. 3. Open your existing file or a new one. 4. Update Quicken to latest fix pack from within Quicken. (I imagine downloading the fixes and applying from external from One Step Update would also work.) 5. Restart Quicken. 6. Unlock Business feature. 7. Restart Quicken. At least that's how I got it to work for me.
I'm glad you got it running okay. I also use Quicken 2004 and it was the primary reason I decided to try Parallels VM. Quicken loaded just fine for me and I regularly back up this all important (to me anyway) data using my Cruzen mini 1.0GB USB memory stick. It all works as it should although I had to increase my vm hard drive capactiy due to low disk space errors reported by Windows. Even that went well although I was on pins and needles throughout the process thinking something would go disastrously wrong. It didn't. I even have my USB printer working through the network, an HP Laserjet 1300.
