Wednesday, January 06th, 2010 | Author: Jamey

I ordered an unlocked Nexus One yesterday. The free overnight shipping was an unexpected bonus. Mainly I’m looking forward to having a truly responsive UI and the multi-account (and Exchange) synchronization. The biggest annoyance has been that the tracking information still hasn’t been sent eighteen hours after my order. While I was preparing to make this post I got an automated call from FedEx, telling me that they were going to deliver a package that I’d need to sign for by 3 P.M. today and giving me the tracking number! Unexpected to say the least. I looked up the tracking number and confirmed that it will indeed be here soon, it’s in the next town south at the distribution facility.

Don’t get me wrong, I love my G1, but it just isn’t up to the task set before it: to be a always-on, always-running amalgamator of information, and a feature-rich one at that. To get the feature-richness I had to go to CyanogenMod after rooting my phone. For a long time, it made my phone more responsive and useable, but lately it has become slow and quirky.

After my N1 gets here my G1 is going up for sale on Craigslist/eBay with all its accessories to help defray the cost of the new phone.

I’ll make new posts with impressions when the N1 gets here.

Category: Hardware  | Tags: , ,  | Leave a Comment
Friday, December 18th, 2009 | Author: Jamey

A few years ago I won a contest sponsored by F5 Networks and used the winnings to build a new water-cooled PC. Being as it was (and is) my first foray into water cooling I decided to go with an all-in-one unit to simplify matters. After research I decided to buy a Koolance PC3-736BK. A few years of mostly problem-free operation later it started making some gnarly grinding sounds. Looking into them I discovered that the reservoir had, apparently, sprung a mighty leak.

I shut off the system and tried to determine the source of the leak. Finding the inside of the case drenched in (thankfully non-conductive) coolant I saw that the source seemed to be the top of the reservoir. Visual inspection of the top of the system showed evidence of cracks/leaks around the gap where the reservoir mounts into the cooling system and the appearance that the reservoir lid had been disturbed. The system was rather a pain in the ass to disassemble but once that was done and it had drained I could see that the reservoir had indeed failed.

I called Koolance support only to find that replacement reservoirs and pumps for the PC3-7xx series are no longer available. When the subject of warranty was raised I acknowledged that the device was certainly out of warranty – the term is a mere one year. I was also told that the pumps “almost never” fail, so it was probably just a leaky reservoir. My only options were to 1. fix it myself, 2. get a standalone reservoir & pump, or 3. get a completely new drop-in cooling system – the new version of the cooling system from the PC3-736. Option one was cheapest but, with the amount of leakage I saw, least viable. Option two would have significant cash outlay and lose me the use of the power supply and temperature monitoring circuits – a significant part of the benefits of the system. Option three cost over $200.

With those options in front of me, I chose to disassemble the reservoir and see what was what. As I was rinsing the coolant residue out I began to see pieces of plastic floating and swirling around inside, both black and clear. With each rinsing, more residue came out and the problems became more clear. Once the damage inside became obvious I had the opportunity to look at the external damage. The lid of the reservoir was cracked about a third of the way around, mostly around the seam where it was epoxied shut, but in the corner the cracks went through the thick plastic of the lid. That amount of damage took a good amount of force. Internally, both pumps seem to have torn themselves to pieces. One was thrown askew on its mounting pin, leaving serious damage both around the pin and the mounting between itself and the coolant outlet port. The other had blown out the entire pump face where it mounts to the inlet which was connected via hose to the radiator. You can actually see the pump impeller from the face of the pump where it had been blown completely off.
Even More Loose PlasticThe Whole Package, Sans Lid

If you look at the pictures, you can see a number of things. Loose pieces of clear plastic…
Loose PlasticMore Loose Plastic
Broken but attached pieces of clear plastic…
Attached Plastic
Large pieces of black plastic (some of which are curved, likely from where they mounted to the water inlet/outlet), and lots and lots of tiny pieces of black plastic dust.
Plastic Dust
You can also see the broken casings of the pumps themselves.Broken PumpBroken Pump Mount
Those motors must have absolutely destroyed themselves – or at least one did and took the other with it. I would call it explosive failure to have generated enough pressure to crack the lid of the reservoir like it did. The two pictures of the entire thing still mostly-assembled also do a decent job of showing somewhat the leakage that had resulted. Look for the crusty, reddish-brown crud at the bottom of the reservoir and on the clamp.
Cruddy ClampCruddy Reservoir
Believe me, there’s a lot more crap where that came from.

On calling Koolance back to tell them what I’d found, I was essentially told, after being put on hold for a while after they’d heard my story, “huh.” No “mail it to us and we’ll see what we can do for you”, no “let us see if maybe a mechanical fault caused the problem”, just that a piece of debris must have caused it. Well, I agree with them. Since the system has been operating as a closed loop since I bought it with the exception of topping off the coolant every four months or so, the debris must have been in the loop from the start, likely as a functional part of the system. Since the clear plastic is nowhere near as pulverized as the black, I think one of the pumps blew itself up, threw shrapnel around, and indirectly took out the other. Depending on how quickly the entire thing took place, it could have been either or both that generated the pressure that cracked the lid.

All I know is at this point, I need to get a new reservoir and pump to get my desktop back into operation, and it’s bloody unlikely to be Koolance parts I use. I’d suggest anyone else thinking about one of their all-in-one units think long and hard about about my story. Think about the availability of replacement parts in the future should one decide to go nova.

Category: Hardware, Koolance  | One Comment
Monday, April 13th, 2009 | Author: Jamey

I love books. I’m not a bibliophile, I don’t collect them (at least, I try not to). But I do tend to buy a lot of them. In the last month I ordered a ton of new books about topics I’m interested in or actively working on. Most of them are on my bookshelf at work.

Database Books:
Oracle Automatic Storage Management: Under-the-Hood & Practical Deployment Guide
High Performance MySQL: Optimization, Backups, Replication, and More
MySQL (4th Edition) (Developer’s Library)

Systems Books:
Running Xen: A Hands-On Guide to the Art of Virtualization

Ruby Books:
Practical Ruby for System Administration (Expert’s Voice in Open Source)
Enterprise Rails
Ruby Cookbook (Cookbooks (O’Reilly))
Rails Cookbook (Cookbooks (O’Reilly))
Enterprise Integration with Ruby
Rails Recipes (Pragmatic Programmers)
Enterprise Recipes with Ruby and Rails

You might be able to tell that I’m on something of a Ruby/Rails kick right now. Ever since I threw together my first rails site (which has yet to make it to production) I’ve enjoyed both the language and the framework immensely. When an opportunity arose to use Ruby for some scripting I needed to do for work I jumped on it and haven’t looked back. I built a simple monitoring framework for my servers spending just a few hours a day for a few days, and it’s currently in place for most of my non-production systems.

It didn’t take long after I had gotten it up and running that I realized that a front end was what it really needed (and, moreso, that a front end would make it more useful for my coworkers) so I am planning on taking the Modules I developed (which is one of the first thing that Enterprise Integration with Ruby harps on you about, putting everything in Modules) and converting the driver code that I wrote to call those modules into a module itself and dumping it all into a Rails site with my Controllers calling my Modules.

A lot of the technical folks I know these days don’t buy a lot of books. They prefer to google whatever information they need, and that works great – to a point. It’s harder to browse google when you only have a general idea of what you need. It’s also exceedingly difficult to do when one is offline, and I’m not allowed to drop my laptop onto the network at the office. Why work on the laptop at all then? Because I almost always have it with me, and if an idea strikes I want to be able to grab it and at least jot down a few notes, or better yet, sketch out a skeleton. You never know when inspiration will strike. This weekend it hit me while I was taking my son out for a walk (and all I could do then was send myself a calendar entry via my googlephone) as well as while visiting my relatives for Easter.

Plus, I love the feeling of holding a real, dead-tree book in my hands. I’m thinking about ordering a few more books in the near future as well. I’ll try to keep this area updated with any other thoughts about the above titles or books I end up buying.


Category: Uncategorized  | Tags: , , , , , ,  | Leave a Comment
Friday, November 21st, 2008 | Author: Jamey

I have a few more things I’ve discovered about the G1. Firtst and foremost, you can only attach pictures to emails with the gmail client. With the normal web-based Gmail client you can’t attach anything. If I were to speculate, that would be because Google doesn’t have a built-in filesystem browser that one can use to find files to attach. Second, a bug: if you are in the gmail client with a message open and a response to that message comes in the number of unread messages does not increment, but the message is marked read and the number of unread messages decrements. This can cause the number of unread messages in the main message list to display a negative number.

Also, sometimes messages get stuck in “sending” status when they’ve actually sent successfully, and sometimes gmail will create extra, draft copies of a message.

I still love this phone.

Category: Uncategorized  | Tags:  | One Comment
Thursday, November 06th, 2008 | Author: Jamey

I went out on Tuesday and picked up a G1 (the Android-based Googlephone). So far I find it useful, convenient, and fun. It very, very close to what a mininotebook should be. As more apps get released it will only get closer.

That’s not to say it’s without quirks. The rich-text version of this form won’t accept text input. I had to type that last sentence twice because I somehow managed to make it disappear. Facebook is quirky while on wifi (possibly because of weak signal) buit works fine on Edge. When an app starts going nuts there doesn’t seem to be a way to kill it short of a reboot, even when you pull up the alt-tab menu where it would make sense. The tab soft-key (alt-q) does a tab character, never a field-advance.

Even with all that it’s still easily the best phone I’ve ever used. It blows my Windows Mobile device, which I loved, out of the water. There are apps that are so obvious and so wonderful that you can’t help but love them. Even the apps that are obviously missing are bound to show up soon.

It’s a shame I had to pay $23 to get it unlocked for use on AT&T, but that’s T-Mobile’s fault.

The phone is so sexy that Wendy wants one and she just got a new phone two months ago. I’m going to keep playing with it and I’ll post anything neat I find here.

Category: Uncategorized  | Tags:  | Leave a Comment
Friday, October 03rd, 2008 | Author: Jamey

You know, this should mean something.  So I was on the F5 site, trying to find a solution to a problem I’m having, and I’m searching around.  I throw a term into the search box, hit enter, and up pops a list of hits – the last of which, a forum post, looks relevant.  So I start reading it.

I wrote it.  The year before last.  When I was trying to solve the same problem.  How did I end up solving it, you ask?  Good question, and the answer involved me winning an award.

I swear.

Category: Uncategorized  | Tags:  | 2 Comments