I recently had my first experience with Windows Live OneCare and I have to say that I was less than impressed. Here is what happened. Microsoft, take note!

My clients are an elderly couple who are nervous about using their PC but they’ve gotten by for a while now. So they had Windows XP Home edition with Service Pack 3 (I think) and a few run of the mill software programs installed. They kept having freezing and rebooting problems. I did a repair of Windows XP. That didn’t fix it. I ran all the diagnostics I could think of but no hardware problem would show up.

I finally ran out of options and formatted their computer. It was running perfectly. I reinstalled most of the programs but not Windows Live OneCare. I don’t like Microsoft’s AntiVirus products so I skipped the program entirely. Unfortunately there were functions in OneCare that the clients wanted so without really thinking that it was the problem, I installed it. BAM!!! The same problems were back exactly the way they were before. I attempted a system restore but OneCare was still there. I tried uninstalling it but that didn’t fix the problem either.

My clients needed their computer so they opted to put up with the problems rather than be without their computer for another day. I said “Okay” and left. About a week later, they called me again and asked if I would help them set up their new Apple laptop. Well, they now have a nice new fully functioning Apple MacBook Pro and they love that it works the way it is supposed to. They’re still getting used to the software but since Windows Live OneCare caused such havoc on their PC, they’re glad to have something that works.

So, as you can tell, Windows Live OneCare won’t get my vote for software application of the year.

Tim

Biden PC is a Computer Network Consulting Company.

If you found this post to be informative, consider subscribing to our Biden PC’s RSS feed.

Are you running Quickbooks on Windows PCs while a Linux domain and file server holds the data files? Do you get an error code -6190 -82? Let me tell you how I fixed this problem on a client’s server. I fully admit that I am no Linux expert but I am learning.

The users that were logged in to the server had admin access but only the user that owned the file was able to access it. All others were given the -6190 -82 error code. I tried everything my non-Linux mind could think of. I had them run QuickBooks from a batch file that removed the “Read Only” attribute. I did this, I did that.

What I finally did to fix the issue was going into the server and see what user group the necessary users belonged to. I then changed the owner setting of the QB Data files to that group.

**ADDITION** I had to go back and I saw that the .TLG file permissions had changed on the server. This sent me searching for why they would change and how to stop it… After testing, changing, testing, changing and retesting, I believe I have the complete solution to the problem.

1. Put all users who need QuickBooks access in 1 user group.
2. Make that group the owner of your .QBW and .TLG file with “Read & Write” permissions.
3. On each users desktop (at least the ones who backup the QuickBooks file), set the program NOT to verify the backup data.
4. Viola. The problem has been solved.

So what is the reason for this??? You can set the permissions on the .TLG file but if you verify the backup data in QuickBooks it creates a new .TLG file with the same name. That causes the permissions to be reset. So backing up without verifying saves the permissions and allows everyone to use the files. **END ADDITION**

Intuit says they don’t support Linux unless you pay for their $3000.00 Enterprise Solutions package. Well, this trick might just save you $3000.00. Feel free to send me a check if you find this useful… Just kidding.

Tim Biden

Biden PC is a Computer Network Consulting Company.

If you found this post to be informative, consider subscribing to our Biden PC’s RSS feed.