Roo in Japan

I was in Japan last week for business.  While we had been talking about the possibility of going for a while, I found out less than 24hrs before getting on a plane (Jenn was very understanding).  This was my first time across the Pacific Ocean, and with a 14hr leg (single flight) in my trip, I set a new personal record for being stuck on a plance (in economy no less).  The time delta was 14hrs meaning that at 7am in Japan, it was 5pm the previous day at home.

I was staying in Tokyo, near Shinjuku at the Hyatt Regency.  It turns out this was very close to the Park Hyatt that was featured in the movie Lost in Translation (which if you haven’t seen, is a good movie).  The Hyatt was a nice hotel, certainly meeting western standards for space.

Since I was there for business, I was a little concerned about making the right first impression.  I found a few links that helped me not feel like a total idiot.  Generally the Japanese people feel very polite, the bowing really struck me.  The general care they take presenting you with a bill is quite nice, it is done similar to the business card exchange which is very ritualized.

Thankfully, the company we were visiting is a little less traditional and tends to style itself after a Silicon Valley business.  One thing that I would try to do for another trip is make sure I have a few small token gifts from Canada to share with my hosts.

Since the employees of the company were Japanese, we were using a translator.  While some of them did speak English, there was a varying level of abilty with the language.  Since I don’t speak any Japanese the translator was a huge help.  Anyone who has head me speak knows how quickly I can go – this won’t work with a translator.  It took some getting used to, breaking ideas down into short snippets that could be translated without losing any of the technical content (just because they don’t speak the same language, doesn’t make them simpletons).

On day 3 I noticed that the translator was fixing my errors in naming folk by adding -san,  and I was honoured to hear Andrew-san a number of times.  I’ll go out on a limb a little here as I don’t know, but it also seemed to take a little time to break down some of the trust barriers – this may be a cultural issue, or just the standard technical problem of everyone is an idiot until proven otherwise.  By the afternoon of the 3rd day we were all jamming at the whiteboard discussing issues, and it was clear that there was understanding (both ways) even without translation.

We had dinners out as a group (without the translator) and there were enough folks with both English and Japanese on both the customer and IBM side to help things go smoothly enough, they were also especially helpful in instructing us how to eat dinner as many of the dishes were unfamiliar.  We ate in restaurants with low tables but with a cut-out below for your legs, we also removed our shoes before entering the eating area.  While the food was unfamiliar, it was all good. My best guess after the fact is that the meal was ichijū-sansai style.  The soup was cooked at the table and I couldn’t help but compare it to a DIY meal such as fajitas (which I always want a discount on as I’m doing part of the worK).

It was cool to see that Bunnie was in Japan at the same time, and blogging about both food and some of the neat things to see in Japan.  Unfortunately I didn’t have time to explore some of the things he talked about, but it did help me get my head around the culture a little more.  In the little time I did have free, I did a little souvenier shopping – while I could navigate the subway and the stores, the language barrier was significant. Unfortunately I didn’t manage to find a 100 yen shop (dollar store), but did explore a few of the 10+ story department stores.  I ended up buying a few things at a shop on the 45th floor of the Tokyo Metropolitan Government Offices  which gives an amazing view of the city.  In the elevator ride down it was a pretty tight right with about 8 other people, but none of them were above the level of my shoulder – Japan isn’t built for people who are 6 feet tall.

I had been told that McDonald’s was “the same, but not the same – you have to try it”.  The menu certainly had some unfamiliar selections on it such as Ebi Filet-O (shrimp burgers).  When I got to the airport the food selection was pretty limited but there was a McDonald’s so I figured why not?  The double Big-Mac and fries, tasted the same (or possibly better) than the ones I’m used to.  I did also eat out of one of the ubiquitous vending machines, the ice cream was very good.

While I was there the weather was mostly overcast, but around 10C to 15C.  During the day I’d forego having a jacket which made me stand out in crowds.  Generally the Japanese were bundled up in jackets as it was considered “cold”, but as I was primarily in the office (24C), subways and stores I found it hot if I had a jacket on.  It did cool off in the evenings, and many of the commuters had very long trips (1hr+) which might have required more variation in clothing.  In the evenings I did wear a jacket, I’m Canadian – not crazy.

It was a good trip, but I’m really glad to not be on a plane and staying close to home for a while.

Burned by Chrome

Last night I was adding a new wifi device to my home network.  One of the security features I make use of is MAC address filtering (and yes, I know a motivated attacker can spoof a MAC address easily enough, but there are many easier targets in my neighbourhood).  My primary router is a Linksys WRT54GL running DD-WRT.  If you have one of the Linksys WRT54G* routers, my experience is the stock firmware is terrible – you should either run DD-WRT or Tomato and if you insist on staying stock, at least get the latest version from Linksys.

I’ve been playing with Google Chrome a little bit.  The various “run it under Linux” solutions simply don’t work well enough to bother with.  So until Google gets a Linux version going – I’ve been playing with it under Windows.  There are some things I like about Chrome: the ability to tear off a tab and get a new window; the omnibar; and their process per tab is pretty nifty.  On the downside is plug-in stability (Adobe Reader really sucked in the 1st release, better in the update), general stability (I’ve crashed it a few times) and compatibility (some websites don’t recognize it).  I’m not ready to make it my primary browser, but I do use it regularly.

In order to edit the MAC filter list, I need to navigate some of the DD-WRT administration pages to make some changes.  I was surprised to get an error message from Chrome when trying to save my changes, it turns out I was hitting a bug that was only very recently fixed.  So, no worries – I just switched to Firefox and redid the change.  However, to my dismay – it seems that the partial commit from Chrome caused my router to completely clear my nvram (in all honesty I can’t prove this, but the sequence of events makes sense).

DD-WRT has been very stable for me for quite some time.  I was running v23 SP2 and had looked at the newer v24 version since it had some neat bandwidth monitoring features, but had decided to stall as migrating my configuration would be a bunch of work (and risk if I got it wrong).  Lucky for me I had gotten a dump of the nvram by logging into the router via telnet and issuing a “nvram show” command, having this dump gave me a reference to help move my config over.

Faced with the complete loss of my configuration, I figured it was as good a time as any to upgrade to the latest version (v24 SP1).  The upgrade went smoothly, and the new firmware looks really slick.  In a way I’m sort of glad that I finally got around to doing it.

FrankenPod

This is the follow up posting to my tale of two iPods.  Tonight I used the ‘extra hour‘ to perform the logic board swap on my busted iPod from the ‘used’ one I picked up a week ago.

The first step was to take the used iPod apart.  By starting with the used one, I could learn how to do it before taking mine apart. I knew the used one was a little beat up, but I was still surprised by how dirty it was inside as well (mostly lint).  Below is a picture of it fully disassembled.

I found a pretty good .pdf file on powerbookmedic.com that documented the tear down, but found I had to also refer to the ifixit.com site to get a better idea of how some of the cable clips worked.  Now that I’ve got hands on experience doing it, the process is pretty straight forward.  Even cracking the iPod apart is quite easy now.  I do need to point out how insanely small those 6 screws are.

After taking everything apart – I wanted to verify the donor logic board was working. In the picture below you should be able to see the “Please Wait.  Very Low Battery.” message.  If I tried this with my non-working logic board, the screen did not light up at all.

Once I had both iPods completely disassembled, I performed the logic board swap and began to re-assemble my (hopefully working) iPod.  The reason for going to this extreme is that the used iPod was pretty beat up, and the only part I wanted to take from it was the logic board.  In the picture below, I’ve swapped the logic board and reassembled the click-wheel and screen into the front panel.

From this point it was only a matter of minutes before I had a completely assembled iPod and was able to connect it to my PC.  Again I was greeted by the ‘very low battery’ messaage and a pretty long wait – long enough I was starting to think I had done something wrong.

I was relieved when enough juice had made it into the battery and my Ubuntu system recognized the device.  From this point on things were pretty smooth sailing.  I booted up my vmware image of WindowsXP that I use for iTunes and there were no problems connecting and synchronizing the iPod.  I had wondered if the logic board would be tied into my serial number, but apparently the data on the drive alone defines the iPod.

I then proceeded to reassemble the used iPod using the bad logic board.  While I will likely sell this used one for parts, I figure it may as well be together instead of a jumble of parts.  Once I did this, I was surprised to hear whirring coming from the device (sounded like the hard drive spinning).  It was unresponsive to the reboot sequence (menu + center) and continued to whirr away.  I figured this explains why my iPod had such a flat battery, clearly when the logic board failed – it went into this mode and drained the battery completely.

A few minutes later I realized that the used iPod was getting warm to the touch.  This was a little bit alarming, so I popped the cover off and disconnected the battery.  The battery was quite hot, clearly some unexpected load being drawn by the bogus logic board.

At this point it looks like things went as planned.  I was able to transplant the logic board from the used iPod which was pretty beat up into my “like new” iPod.  I also have pretty good evidence to back up my guess that it was the logic board.  And I was able to do it for less than a refurb nano would cost me.

I may still use the shuffle as it is certainly easy to carry around, but I’ll certainly appreciate the video capability on my next boring plane ride.