Vista and 2007

Hi, DJ.

As I've often reported here, I've been using Quicken Basic (2005, 2006 and now 2007) on Vista, both 32-bit and 64-bit, all through the Vista beta and, since November, on Vista Ultimate RTM (mostly x64 but also installed on x86). Also, for several months, I dual-booted the Vista beta builds alongside WinXP Pro (and occasionally WinXP x64) and could access the same Quicken app and data from both (see the next paragraph). Except for a hassle with installing a Quicken update back in February, I've had no problems with the combination. (I'm running only Vista now because an unrelated problem has prevented me from even booting WinXP for several months.)

I've been using Quicken since long before the \Program Files folder was invented, and I still install it into its own E:\QuickenW folder (from back when Intuit added the "W" to distinguish the Windows version of Quicken from the MS-DOS version). By installing the application into this single folder, accessible from both WinXP and Vista, I was able to run it from either OS and access the same data file from either. Both used the same application files and data fileset.

What Unlock code? I've never run into that in my many installs of Quicken on either WinXP or Vista.

I'm not sure what caused your problem. My suggestion would be to first be sure that your data file is safely backed up and accessible. Then delete the qw.exe file. And then install Quicken in WinXP, as outlined in the next paragraph. When Quicken is running properly in WinXP, reboot into Vista, delete (or rename) qw.exe and follow the same steps again, using the same .qdf file.

In each OS in turn, insert the Quicken CD-ROM and run Setup. It SHOULD find the remnants of your prior installation and install Quicken 2007 again into the same location, overwriting the old application files in the process. When you get to the end, just before clicking Finish to "Run Quicken Now", use the X to bail out of the installation program. Then use Windows Explorer to navigate to your .qdf file and click on it. This should start your new Quicken with your data file loaded. You'll still need to make a few minor tweaks to finish the job.

If that doesn't work, please post back and tell us your exact steps (not just "I tried it") and exactly what error messages or other results you saw (not just "It didn't work.")

RC

DJ:

I know this is not of any help to you now. But, I went through a similar situations a few weeks ago with installing Q2007 H&B on Vista Ultimate 32-bit. Fortunately for me, this was on a brand new machine, so I just reverted back to a clean image after I could not remove the failed installation.

I waited till I got Q2008 H&B, that install went without a hitch.

Bob

I'll make this as short as I can. Can one install 2007 on Vista (Ultimate in my case)...? During install my "Next" button remains grayed out after entering the Unlock code. Apparently this is a well known problem with a couple different approaches to work arounds at the Intuit web site, neither of which appear to work.

Actually, the "clean-up utility method", not only makes no difference in the Vista install realm, but rendered my XP install un useable as it deleted the 'qw.exe' from that install (?!)I can't even do a "repair" install there, or remove the program from XP via Control Panel (errors out)to prep for a clean install of the program. Nice, eh? Thanks Intuit. Can someone please help!

Got a link to a downloadable version of 2007 via live chat with Quickem support this morning, which I haven't tried as I'm at work. My goal now is to install it on Vista Ultimate (falling to knees in prayer).

The genesis of the Vista problematic "unlock code" (that doesn't work) was my upgrading in response to the "No more support for 2004" announcement with 2007 CD campaign early this year. You bought at the web site and they sent the UC.

I am intrigued with R.C. White's install technique which I may try...

-=-=-=-=-=-=- "I've been using Quicken since long before the \Program Files folder was invented, and I still install it into its own E:\QuickenW folder (from back when Intuit added the "W" to distinguish the Windows version of Quicken from the MS-DOS version). By installing the application into this single folder, accessible from both WinXP and Vista, I was able to run it from either OS and access the same data file from either. Both used the same application files and data fileset."

-=-=-=-=-=-=-=-=-

A bit off-topic, but perhaps critical for my situation, seeing as Intuit's "Clean-up" utility rendered my 2007 install unuseable, not to mention uninstallable(!). How does one manually uninstall an app under XP? I thought maybe deleting the Quicken directory, restarting and then running a good registry utility might do it...? Maybe I'll try installing the new DL over it. My CD install just bombed with an error I don't recall. Didn't like something. (R.C. just hates it when I do that!) OK R.C. if I can recreate it I'll reveal the error message! ;-)

You can try the Microsoft Windows Installer Cleanup Utility.

I've never needed to deal with the Windows registry when I've done uninstalls, but I have often manually removed all folders and files with Quicken in the name, and done my subsequent install to a *new* directory (one that didn't exist when the previous install was done).

Hi, DJ.

That explains why I never saw an Unlock Code: I never bought Vista for download. Thanks for the explanation.

RC

Nope, I need to clarify. Actually the 2007 CD came in the mail back in January along with the warning about it's support going away. So, I bit, paid on line and got the unlock code via e-mail! ;-)

Unrelenting in their marketing efforts, and a bit ironically given my recent difficulties, I got the 2008 CD yesterday. I did not bite.

Finally, I did chose a generic non-"Program Files" directory for my install under Vista, "D:\Quicken" by name. Things are fine under Vista, but unlike you I cannot seem to access that install under XP. I get the app window but an accompanying "There seems to be a problem with your installation and Quicken must close" message

Hi, DJ.

Aha! That clarifies the unlock code issue.

Did you go through the entire Install rigmarole twice? Once in WinXP and again in Vista?

It's not enough to have qw.exe and all the hundred or more application files in D:\Quicken. We have to run the installation program while in WinXP so that it can make the proper entries in the WinXP Registry. Then we have to reboot into Vista and do it all again so that the proper entries will be in the Vista Registry. (Even if we are dual-booting two installations of WinXP side by side, one cannot see the other's Registry.)

Once we've done that, we can boot into WinXP and click on our QDATA.QDF file, which should start D:\Quicken\qw.exe with the QDATA fileset loaded. If we have entries to make in Quicken, we can do them now. Then we Exit Quicken, letting it update its internal pointers in its housekeeping files in D:\Quicken, then reboot the computer into Vista. Again, we click on QDATA.QDF, which should start D:\Quicken\qw.exe again with the just-updated QDATA fileset, showing the entries that we just made while in WinXP. And now we can make more entries or see reports that include today's entries. Finally, exit Quicken again so that the internal housekeeping can be done.

Now, we should be able to use the Quicken icon that Quicken Setup put on each desktop (WinXP and Vista) to start Quicken with our default data fileset loaded, fully updated with entries that were made from our last session, no matter whether that session was in WinXP or Vista.

Backups? My practice has been to leave my data files in my equivalent of your D:\Quicken. This may appall some users - having data files in the program folder - but I've been doing it this way since Win9x days. Quicken's automatic backups go to the automatically-created D:\Quicken\BACKUP. And I backup at least once each session to a different folder AND often to a folder on a separate hard drive AND occasionally to a CD or USB thumb drive stored separately from my computer. I'll leave the rest of the backup discussion for another time, but my point here is that all the backups go to the same place, no matter which operating system I'm running at the moment.

RC