Patched Mac QuickBooks Still Deletes Data

HardOCP News

[H] News
Joined
Dec 31, 1969
Messages
0
Intuit fixed that file-deleting-flaw in QuickBooks 2006 for Mac…wait… no they didn’t. If you downloaded the patch on Monday, expect an updated patch sometime soon to completely fix the problem.

Users who apply the patch -- available for manual download since Monday and scheduled to be automatically downloaded to all machines running QuickBooks 2006 for Mac starting Thursday morning -- are still at risk if they run the accounting software while in range of a wireless hot spot, said Ian Vacin, offering leader for Intuit's Mac finance line, in a posting to the product's support forum Monday afternoon.
 
So you're saying it's partially Apple's fault that a third-party program's flawed internal update deletes local files? It's Apple's fault because...the third-party program runs on OS X?
 
So you're saying it's partially Apple's fault that a third-party program's flawed internal update deletes local files? It's Apple's fault because...the third-party program runs on OS X?

Correct

Since it was writen for the OSX platform, They can be blamed. It would be the same with Windows if they had that issue with Intuit and deleting.


Plus, I also like giving you mac zealots shit :D

it's so much fun watching you people get all bent outa shape and pissed off. Cause your famed Mac is getting beat on... You guys crack me up :D
 
That's an unusually weak troll.

HINT: Trolls work better when you don't say "HAI GUYZ DO YOU LIKEZ MY TROLL?" :rolleyes:
 
[RIP]Zeus;1031882072 said:
Correct

Since it was writen for the OSX platform, They can be blamed. It would be the same with Windows if they had that issue with Intuit and deleting.

Plus, I also like giving you mac zealots shit :D

it's so much fun watching you people get all bent outa shape and pissed off. Cause your famed Mac is getting beat on... You guys crack me up :D

You are nothing more than a troll. If this was a windows based version would you bash Microsoft?

Writing shitty software is the fault of the programmer who wrote it, not the OS which they wrote it for.

If I write a crappy program that loops and continuously uses memory for no reason, or deletes temp files, and release it for windows its MS's fault?
 
Actually, yes, had this been on Windows people would be sitting here saying that it is just another example of Windows being crap.

Lets look at Vista for a moment. People like to bitch that old devices don't work under Vista. However that isn't Microsoft's fault, it is the fault of the device makers for not making Vista drivers, however that doesn't stop people from claming that is a Microsoft problem.

People alway like to tie more into the OS than should be.
 
Three businesses that lost data during the update snafu have filed a lawsuit against Intuit and have asked a federal judge to grant the case class-action status. The firms -- Create-A-Card Inc. in New York, AGSJ Inc. in California and Philanthropic Focus LLC in Florida -- charged Intuit with reacting slowly to news from users of the buggy update and said that they each had lost irreplaceable data.

It sucks that business lost data, but why weren't they backing up their data? No computer will last forever and datalose could happen at any time. We had a power outage last week that killed two harddrives at my work. It came without warning, and just happened. No company should be able to lose irreplaceable data. At worse, you should only lose a days worth if you do nightly backups. However there is even software out there now that can do backups on the fly ( Symantecs BackupExec with Contintous Protection for example) that would help give you even more protection.

I think that in addition to this lawsuit, these companies also need to fire their entire IT staff and hire new ones for not backuping up any important company data.
 
And I would be saying its the other companies fault not MS's just like I do in these Apple threads.

I use Vista btw :p
 
You are nothing more than a troll. If this was a windows based version would you bash Microsoft?

Writing shitty software is the fault of the programmer who wrote it, not the OS which they wrote it for.

If I write a crappy program that loops and continuously uses memory for no reason, or deletes temp files, and release it for windows its MS's fault?

Actully yes i would bash windows

Either way it's fun bashing both camps. And i must have gotten under skin. Calling me names a such.. quite sad.
 
Once Intuit went and hopped on the activation bandwagon, a good number of people said goodbye to them anyway.

Of course, this isn't going to win anybody back either, regardless of what preference the users have as far as OS.
 
Stellar. This makes me think twice about having Quicken on my Vista PC.:( Very very lame on the part of quicken, how could they possibly let a glitch this bad out the door.:confused:
 
[RIP]Zeus;1031882672 said:
Actully yes i would bash windows

Either way it's fun bashing both camps. And i must have gotten under skin. Calling me names a such.. quite sad.

So you are just a troll then, since you blindly bash companies for user/programmer errors and things that aren't really their fault.

Oh, and I think you started with the name calling, but do you want a tissue?
 
So you are just a troll then, since you blindly bash companies for user/programmer errors and things that aren't really their fault.

Oh, and I think you started with the name calling, but do you want a tissue?

Thank you.

You have shown me the light. ;)
 
Stellar. This makes me think twice about having Quicken on my Vista PC.:( Very very lame on the part of quicken, how could they possibly let a glitch this bad out the door.:confused:

You are asking the wrong question. The right question is how do you let a bug like this past QA.... TWICE?!?!??!

The second time when the only thing to QA is that it didn't do that anymore. Does intuit even have MAcintosh QA? That's just sad.

And yes, without being a troll, you can blame Apple for this too. As maker of the platform and the OS, it is pretty standard to offer up developer relations services to help third parties ensure quality compatible products. With something this public and egregious, you have them show up on intuits doorsteps saying you WILL let us help you get it right, or we will patch your software out of our OS.
 
You are asking the wrong question. The right question is how do you let a bug like this past QA.... TWICE?!?!??!

The second time when the only thing to QA is that it didn't do that anymore. Does intuit even have MAcintosh QA? That's just sad.

And yes, without being a troll, you can blame Apple for this too. As maker of the platform and the OS, it is pretty standard to offer up developer relations services to help third parties ensure quality compatible products. With something this public and egregious, you have them show up on intuits doorsteps saying you WILL let us help you get it right, or we will patch your software out of our OS.

Actually to be honest they never really fixed it the first time. Assuming I am reading the article correctly. The first "fix" was to make a patch that told your machine to stop trying to update itself. This new case here is that the patch fails to prevent Quickbooks from updating if it is connected to a wireless network. So this is about like Microsoft trying to patch a security flaw by disabling your NIC but them forgetting about you being able to get online with a dialup modem.

Thus instead of how did this get past QA twice, it should be asked, why is this update still out there for people to download?

There is no reason why it should have existed in the first place had they had Mac QA. This should have showed up somewhere in testing had they done any. But then to drop the ball as horribly as they did on solving it is just crazy. There was some breif talk about a few people at my work being switched from PCs to Macs and they all run Quickbooks, this will be my reasoning why that shouldn't be done, as it would appear that they have no testing for their Mac software.


As for Apple helping fix this problem. Yes it is public and pretty major of an issue, but it isn't Apple's place to fix the problem, nor is it the case that them helping is even a possiblity. I'm pretty sure Inituit doesn't want as random person coming in and going through all their code. Since I wouldn't think that a standard minor update would change that much I really don't see why heyt hasn't narrowed down the case of this problem and fixed it yet. If nothing else It should be pretty easy to remove the parts of the code that tells it to delete stuff.
 
Back
Top