Not Just Another Weblog

Unbelievable . A Google search for this returns lots of hits, however the variety of solutions seem to have mixed results. This happened to me most recently in a shiny new Windows XP SP3 Pro virtual machine in VMware Workstation 9.x.  The only item installed was, as many might expect, VMware tools. I am a fan of stopping the windows update service, deleting the c:\windows\softwareupdates folder, and then starting the windows update service.  Does that fix this?  Of course not.  (Actually, my usual screw-up is the clock being horribly off....) I installed Chrome and MBSA 2.2.  MBSA threw an error.  Chrome worked like a charm. Ultimately this forum , this KB article , and THIS DOWNLOAD FIXED IT .  Many reboots. Yes, XP is going EOL very soon. You know what, that Mac Airbook with the ridiculously short screen (both models) is starting to look pretty good.  (I really miss those 4:3 monitors.  Stinking display manufacturers...). This VM was originally plagued with getting a

This reminds me why I switched to Firefox in the first place years ago.  Oi. Isn't it lame when a Google search for what appears to be a commonly-experienced problem does not have a solution which readily presents itself? A search for "whoa google chrome has crashed loop" (or etc.) brings up a variety of results in the Google Product Forums--and kudos to all the good people that took the time to post, and repost, and follow-up, and try to help & collaborate.  Regrettably, I couldn't find something that worked for me. This page says to visit this page , and if that doesn't work... create a new user profile .  Wait, what?  Create a new Windows user profile?  Madness!  Mercifully no, the page is titled "Create a new browser user profile".  Sheesh. While searching to see if Chrome writes a log someplace, one nice person's article ultimately led me to stumble across the solution. Here's what I found that works.  Obvious disclaimer: us

For anyone backing up their Google Drive files, there's good news and bad news.  Legitimate file types such as .doc or .docx (Microsoft Word) files should be fine.  However, if you're backing up those .gdoc filetypes, don't hold your breath.  If you have deleted a .gdoc file within Google Drive and emptied the Google Drive Trash, that's it .  Nothing but a warrantless wiretap from the FBI will get it back, and even then, notsomuch for you and I. More from Google Drive 'help,' such as it is.  One more shortcoming of Google Drive: the file extensions are misleading.  This is crap ! " Anything that has been permanently deleted from Google Drive by the owner, or if the owner's account was deleted, can't be recovered . " If anyone has any suggestions for backing up the .GDOC files, the actual files,  such that they can be restored later, please post in the comments.

I am losing count, having just recovered from the third or fourth Google Drive failure in a month across two PC's.  This latest followed an unexpected shutdown, (a BSOD of an as yet unknown nature), which left a SQLite database in an unusable state: Google Drive needs to be closed. ...unknown error occurred and Google Drive needs to be closed. Error: database disk image is malformed If you continue to see this error, try to disassociate your account [*sigh*] One Google (overlord) Groups thread from 2012 suggests using other services. e.g. EverNote, DropBox, and even (gasp!) Microsoft SkyDrive-- Really ? (Lord) Google searches revealed that virtually anyone with some SQL skills might be able to recover from this.  I am not a DBA.  Having some very skilled DBA's at work has resulted in my leaving that skillset wanting.... Folks working in I.T. and/or with related skills can generally deal with and recover from interruptions/failures like these one way or another.  (I

Huge, huge props to the person that posted this information .  What a lifesaver, since our Google Overlords have been merciful and gracious absolutely useless in responding to this problem.  What a bunch of drones!  Anyhow, here's the fix that worked for me (thanks to Guru ). Start Google Drive Hold the SHIFT key down and click the Google Drive systray icon, which will show the 'Enable diagnostic mode' special menu. Click ' Enable diagnostic mode' menu. Wait until Google Drive crashes and shows the "primary key must be unique" error message. Let the application shutdown. Go to "c:\Users\%username%\AppData\Local\Google\Drive" folder and open " sync_log.log ".  (If it opens slowly with Windows Notepad, I recommend using Notepad++ instead) Search /find (CTRL + F) for this text: " Detected conflict while trying to download file to". After 'to' is the file name associated with the conflict. Rename it. Do this for

No!   Not Google Reader!  Have Mercy! So apparently our Google Overlords, in near-violation of their "Do No Evil " policy, er guideline rubbish mantra have decided to dump a truly useful tool , not far on the heels of dumping Google Labs, which was (from my limited perspective) a mistake. Google News (this is a bad   trend , [my/our over-reliance on Google services]) is reporting that people are flocking in droves of cliche's :) to Feedly --and the good people at Feedly are increasing their infrastructure and welcoming us with open arms.  ( Widely   reported in   the news ). If Feedly offered a premium service that costed a couple of bucks, it would be worth every cent, much like EverNote and Pandora. Would you pay a small fee for a service like Feedly, e.g. advertisement-free, etc.? Google, you guys & gals are seriously screwing up.  (...As I type this on their free blog service).