Q2007 release 4 update?

Anybody know what this new release fixes?

dotcom

Reply to
DotCom
Loading thread data ...

Hi, DotCom.

No, I don't know what R4 fixes. But, considering the trauma that I reported here with trying to install R3 on my Vista Ultimate x64 (RTM) system, I'm very happy to report that the method I finally found for R3 also worked very well for R4. ;

Reply to
R. C. White

< snip >

Hi R.C.,

Could you elaborate a bit on what we should expect?

Which users do you believe "will be getting Vista starting next Tuesday"?

Reply to
John Pollard

Hi, John.

Tuesday, January 30, 2007, is the long-anticipated date for general consumer availability of the Microsoft Windows Vista operating system. Many of us have been beta-testing it since the Summer of 2005 (about the time the codename "Longhorn" was dropped for the client version. The server version is still called Longhorn.) The official Windows Vista web page is here:

formatting link
Millions of users worldwide have participated in testing Vista, and many of us are already using the "Gold" version, which was Released to Manufacturing (RTM) back in November 2006. It has been available to testers, developers and volume users since about 11/30/06, and lots of us have been using it since then. We've been handicapped because many hardware vendors have delayed drivers for their printers, graphics cards, etc., until general release, but those should all be ready by next week.

Microsoft's launch festivities won't match those for Windows 95 a dozen years ago, and I doubt there will be campers outside Best Buy and Office Depot like those for PlayStation 3 a couple of months ago. But there has been a lot of publicity and speculation about what Vista will and won't do.

Quicken users may not all be on the leading edge of computing, but we see the frenzy (?) in this newsgroup every year in about July and August when the NG is jammed with messages asking, "Is it here yet?", and "What new features are in it?" IT, of course, is the next year's version of Quicken. So I expect that at least a few of those eager readers here will be buying and installing Vista next week. And I said that they will be doing that STARTING next Tuesday, not that they all will rush out and get it it on the first day.

I participate in several other newsgroups in addition to this one, including several Vista-related. Based on comments in those NGs, there will be at least a mini-flood of buyers in the first few days. As soon as the first adopters can assure others that the new OS does work, and that drivers are here and do work, many others will be buying Vista, too.

In addition to simply being the newest version of Windows, Vista will bring

64-bit computing into the mainstream. Not immediately; 32-bit Vista (and Windows XP) will dominate for a few years, I expect. But with growing acceptance of 64-bit hardware, Vista x64 will become the default OS, I think, and probably before the end of this decade. The 64-bit version of Windows XP has been available for over 2 years, but was not widely adopted, largely because 64-bit drivers have not been available. But Vista x64 has many drivers built in, and others can be downloaded from hardware vendors' websites today; more will be ready by next Tuesday. And we should see 64-bit software being developed after that as the chicken-and-egg problem resolves itself.

This post should probably have been in a new thread, but it's here because I had troubles installing Quicken 2007 Release 3 on my Vista x64 system, so it relates to DotCom's question and Subject.

Sorry for the long answer to a short question, John, but you know me. And you DID ask. ;^}

RC

Reply to
R. C. White

RC, having had no problem installing Quicken 2007 R3 on 32-bit Vista Ultimate here, R4 failed yesterday with the message "Download error reading update file." When I tried it again this morning, I got the same error, but immediately. It obviously didn't even try to read anything first; it just displayed the error message.

Any advice? Should I try the qwpatch.exe? Is there any risk in running it?

Reply to
Ken Blake

By the way, I just went to the Intuit web site to try to find out what was new or fixed in R4. According to their site R4 doesn't exist and R3 is the latest patch.

Reply to
Ken Blake

Thanks, R.C. I enjoyed it all.

Reply to
John Pollard

Hi, Ken.

Looks like we swapped places this time! When I reported the failure of R3 to install on my 64-bit machine 3 weeks ago (1/5/07), you were the first to response that it had gone just fine on your 32-bit version.

As I reported later in that dismal thread, when I rebooted into 32-bit Vista x86, then installed Q2007 there, it ran the R3 release without complaint. My situation got worse each time I tried something else to fix it in x64. Finally, I found the fix that worked: Run qwpatch.exe from Command Prompt as Administrator. It worked for R3 (finally) and it worked my first try for R4.

That's what I got, too. Same as for R3, as I recall.

It worked for me. But when I tried running qwpatch.exe from Windows Explorer, even As Administrator, it immediately told me it was an "Invalid folder name" - which was obviously an "invalid" error message. :>( And running qwpatch.exe from a non-Administrator Command Prompt window gave me the same spurious message.

I couldn't remember where Vista had stored that qwpatch.exe file, so after opening the CP window, I searched (dir \qwpatch.exe /s/a) and found 4 instances, including the one at C:\ProgramData\Intuit\Quicken\Inet\Common\patch\Update. Rather than try to type all that, I just Marked the folder name and copy'n'pasted it into a CD command, then ran the patch from there.

It's obvious to me that Intuit's programmers are STILL asleep at the switch. I hope they wake up by Tuesday.

RC

Reply to
R. C. White

Strange...as many problems as I have had with this new version, downloading and installing this new patch (R4) was not problem as all! But I can find no info as to what exactly this patch fixes. dotcom

Reply to
DotCom

That was my experience as well Ken.

dotcom

Reply to
DotCom

BeanSmart website is not affiliated with any of the manufacturers or service providers discussed here. All logos and trade names are the property of their respective owners.