Wednesday, October 10, 2007

At nearly the same time as I was complaining about Google Browser Sync hosing up my bookmarks, Omar Shahine wrote a general post about his Firefox use (and conversation-starting Firefox t-shirt). In it he says...

Google Browser Sync allows me to sync all my cookies, saved passwords and favorites between all my computers. This is AWESOME. I cannot stand re-personalizing my web surfing experience on new computers.

Just goes to show you -- your mileage may vary. My experience with Google Browser sync was quick, but painful. In my testing so far, FoxMarks is working great for syncing bookmarks. While it'd be nice to also sync current tabs (I'm not so interested in syncing all settings, cookies, and passwords), handling bookmarks in a way that I can trust is a good start.

Technorati Tags: , ,
posted on Wednesday, October 10, 2007 10:58 PM Mountain Daylight Time  #    Comments [0]

Sara Ford (from the Visual Studio team) has been running an awesome series of daily tips for Visual Studio tweaking. The series started off as the "Visual Studio 2008 Tip of the Day," but many (most?) of her tips apply to VS.NET 2005 as well. Most of the tips explain tweaks that can be made via the Tools->Options dialog.

11pt text and 14pt members! Her tip for today is about increasing the font size in the Statement Completion window... which is the little panel that opens when you invoke Intellisense in the VS.NET code editor (either by hitting "." on a reference to get its members or via CTRL+SPACE or CTRL+J -- another recent tip).

The change is made via the "Show settings for" list in the "Fonts and Colors" portion of the Options dialog. While I'd been in there before to set my Output and Command window preferences (green on black, yo), I'd never noticed Statement Completion (and probably wouldn't have recognized it as the Intellisense members list in any case).

Very slick and I can see this making it a lot easier to find things in the list... it really makes it stand out in front of the code that's being edited.

Nice tip, Sara! Now I need to go back into that portion of Tools->Options and check out some of the other UI elements that can be tweaked in that "Show settings for" list...

posted on Wednesday, October 10, 2007 10:45 PM Mountain Daylight Time  #    Comments [1]
 Tuesday, October 09, 2007

missingbookmarks Lesson learned -- all that comes from Mountain View is not gold. Or stable. Or safe.

While I use del.icio.us for 99.47% of my bookmarking needs on the web, there are always a couple dozen or so URLs that I leave in Firefox's local bookmarks file. Examples are for sites that I want on the browser's toolbar, private or internal URLs that aren't public, and bookmarks that have search keywords assigned.

For a while now, I've wanted to sync up my Firefox bookmarks at home with the bookmarks on my office machine. Most of these get used on either machine and it's a hassle to remember to add those bookmarks and search shortcuts in both places.

So when I came across the Google Browser Sync extension, I thought, "this is PERFECT!"  It would sync up not only bookmarks but also settings and any open tabs. That seemed great for those times when I had something open for reading in the office, but didn't get to it. Shut it down on that machine and it would open up on my home machine later.

I installed the extension on both machines, let it sync up, and then merged the bookmarks in both locations. After that, I went through a process last night of cleaning up and re-organizing those local bookmarks. I spent over an hour getting rid of the ones that were old, cleaning out the dupes, and adding more search keywords.

Today, they're gone. On both machines. A couple of folders are completely missing. Nice, huh?

Thankfully, I found a backup of the bookmarks.html file from before I installed the extension... so while I've lost the cleanup work I did last night, I haven't completely lost the original bookmarks.

Anyway, be warned... if I'd have taken the time to browse through the Google Groups discussions for this extension, I'd have probably avoided it altogether and perhaps tried FoxMarks instead. But I figured Google's stuff is pretty solid... again, lesson learned. Thank goodness I didn't have it sync passwords and all of my other browser settings.

So... back to that cleanup effort (again).

posted on Tuesday, October 09, 2007 10:43 PM Mountain Daylight Time  #    Comments [0]
 Sunday, October 07, 2007

rrod It started several weeks ago. When playing Madden 08, I would occasionally get weird color glitches. It reminded me of the old CRT days when your VGA cable would get loose -- it was as if I was looking at my television through green-colored glasses. "A bug in Madden," I thought, plus a reboot would always fix it. It happened rarely, so no worries.

On Friday, 9/21, a Dashboard Update went out for the 360 and this green-glasses thing happened again. "Uh oh," I thought, "it's not Madden." At the end of the update, the 360 rebooted and I got a black screen. I could hear the startup sound and playing with the controller would result in sounds as I moved around the UI. I just couldn't see anything due to the black screen.

I tried different inputs on the television. No joy. I bought a new video cable to rule that out. No joy. So if it's not the television or the cable -- gotta be the box. What seemed even more bizarre was that I wasn't getting those three red lights -- the Red Ring of Doom.

"That really sucks," I thought, "especially since Halo 3 releases next week... but at least Microsoft extended their warranty." They announced this a while back because so many boxes (especially the initial "launch day" boxes) were having problems due to overheating. Mine was not a launch-day box -- I got it about 4 months after the 360's release. So I'm covered, right?

Poor, naive me. Turns out Microsoft extended the warranty but only if you get the RRoD. In the open letter from Peter Moore (Xbox Head at Microsoft):

...we are announcing  today a three-year warranty that covers any console that displays a three flashing red lights error message.

A box with the symptoms mine was showing -- not covered. Lots of unhappy people on support forums about that issue... including many people who recommend giving the box a thump on the side (reminding me of an old television set we had when I was a kid) or wrapping the box in a towel to overheat it on purpose. I didn't want to do either of those, but I called Xbox Support to see what my options were. No amount of complaining, griping, or asking to speak with a supervisor mattered -- I'd have to pay the $99 repair fee if I wanted it fixed.

So now my Xbox is somewhere between Colorado and Texas in the supplied box that lots of people refer to as "the coffin".

A few things I've learned over the last couple of weeks:

  • The $99 fee covers shipping three times. First, they get a box to me (took 7 business days). Then the console goes in the box and heads to Texas (en route now). Finally, the repaired box comes back.
  • That fee also re-sets my warranty for another year. I plan on using the crap out of it to put that to the test.
  • I may or may not get the same box back, which surprised me. The box I get back may be someone else's refurbished box with a different serial number. As long as it works and doesn't look like a Best Buy floor model, I don't much care either way.
  • There are a TON of people who had problems on or near that fateful Friday, 9/21. Two different .NET bloggers I read (Scott Hanselman and Travis Illig) had it happen within a couple weeks. A Google search turns up a TON of problems occurring in late September. I doubt that Microsoft will ever admit that the Dashboard Update caused a problem or is even related. But checking out this thread makes it hard to claim "coincidence".

On the plus side... one of the guys at work has a 360 and hadn't used it for months (the horror!), so he brought his in for me to borrow. This added a few more things to the list of what I've learned:

  • There are some very nice people in the world. It's great to have a console to use during this season when a LOT of interesting games are being released (Halo 3, PGR4, Call of Duty 4, Guitar Hero 3, FIFA 08, and more).
  • Plugging your hard drive on to the side of someone else's console works like a charm. It was as if I was using my original console, except...
  • His console is much, MUCH quieter than mine. When it's at the dashboard, you can barely tell it's on and even with a disc spinning, it's still much quieter than mine ever was. So much so that my wife is in favor of buying a newer one if the repaired console doesn't come back as quiet as this borrowed one. It's THAT noticeable.
  • The dashboard update doesn't break every Xbox... his wanted the update as soon as it was turned on and before it could continue. Went through like a champ (though not without me sweating a bit!).

So... I'm sure it will be a couple more weeks before my repair console returns and it'll be interesting to see what's changed. Noise? Serial number? Heat dissipation? Stay tuned.

posted on Sunday, October 07, 2007 1:57 PM Mountain Daylight Time  #    Comments [0]