Acer One D260 system restore

The hard disk in my wife’s Acer One D260 netbook got damaged. A new hard disk is about a quarter the price of a new netbook, so I wanted to install a new drive. Like with most PCs these days there aren’t any Windows install DVDs included.

The netbook came with Windows 7 Starter, which we needed to somehow install on the new hard disk. Fortunately, the damaged hard disk was still limping along enough to use the Acer eRecovery system to create two Recovery DVDs. These should allow restoring the initial system state to a hard disk in the machine, wiping all the data on the drive.

To replace the hard disk, I had to undo seven clips around the edge of the keyboard, lift off the keyboard and disconnect the keyboard ribbon cable to the motherboard connector. Then I needed to undo 4 screws underneath and push through, to pop out the cover on the bottom of the machine. This opened access to the single memory slot and drive cage.

The 1 GB memory module on the motherboard can be replaced with a 2 GB PC3-8500 1066MHZ DDR3 module available for about $20. This is a wortwhile investment and I already have the module on order.

I replaced the damaged 250 GB WD Scorpio Blue drive with a spare 500 GB drive (available new for about $60-$80). Then I closed the cover and reinstalled the screws and then the keyboard.

With the new drive it was possible to boot off the first Recovery DVD using a USB DVD drive. The eRecovery software copied data from both DVDs to the hard disks and then rebooted. However, that reboot failed because the new drive did not yet have a Windows Master Boot record (MBR) on it. You can install an MBR from within Windows, but not from the bootable eRecovery DVD. So I had a chicken and egg problem.

I overcame this hurdle by booting off a Ubuntu Live DVD (32 bit), installing the ‘lilo’ package and telling it to install the Linux equivalent of Microsoft’s MBR code:

sudo apt-get install lilo
sudo lilo -M /dev/sda mbr

At the next attempt to boot off the hard disk, Windows started installing its components and drivers and launched into its initial configuration, just like the first time we had unboxed the machine more than two years ago. So we are back to a working Winmdows 7 machine!

Thank you, Linux — you saved my day again! ๐Ÿ™‚

Too late to revive Flickr?

Yahoo has just given its Flickr photo sharing service a much needed facelift. I have a Flickr account and used to love the service, but switched to Google’s Picasaweb more than 2 years ago. I loved the Flickr user interface, in fact I much preferred it to Picasaweb, yet I moved on.

Admittedly, Flickr’s 100 MB/month traffic limit was inconvenient, but what really killed it for me was that they limited free accounts to a maximum of 200 uploaded pictures. Not per week or per month, but in total. Facebook has no picture limit at all and Picasaweb has none provided you use the default setting in which it resizes uploads such that the width and height does not exceed 2048 pixels, which is more than enough for anyone with a 1920×1280 or smaller monitor. The greatest user interface was worthless without the ability to upload more pictures. Over the past 12 months alone I uploaded 7.3 GB in 107 sets consisting of 3385 pictures and videos to Picasaweb.

It’s great that Flickr will now offer up to 1 TB of storage for full size images. But how many former users will be prepared to give them another try, now that they have become familiar with Facebook and Google’s competing services? On a positive note though, the new Flickr will force Google to be more careful where it moves with Picasaweb / Google Photo. The Flickr facelift may not make it a winner yet, but any misstep by Google could.

My 300 km Mt Fuji brevet ride (BRM518)

BRM519 was my third brevet ride with AJ NishiTokyo this year and my fifth brevet overall (including an unofficial shadow ride in January). It makes May the 9th month in a row for me with a Century ride (over 160 km / 100 miles).

I’d been wanting to ride this brevet again since I did it last year (my first brevet ever). I worried about family or business travel that might conflict, or about foul weather on the day, but none of that came to pass.

Like last year I was the only one attempting the brevet on a small wheeled bike, but while I heard a few skeptical comments last year, as people thought I was attempting something very difficult, the comments I got this year were overwhelmingly positive. I got many compliments on the Bike Friday, my folding road bike.

I left home at 19:20 on Saturday, got back around 20:30 on Sunday and slept all of 20 minutes in between. I rode 360 km (224 miles) altogether, since this time I didn’t pack my Bike Friday into the bicycle bag for a train ride to and from Machida (the starting point), but rode from Tokyo-Setagaya to the west side of Mt Fuji and back. That makes it the longest bike ride for me so far.

At the signup I was greeted by David and William, who I had met through my blog post about the Nichitsu ghost town ride last year. This was the 3rd brevet we rode together. The previous weekend they had completed a 100 km hike for charity. Kudos to them!

Garmin troubles

I’d been training for this event for a year and bought a Garmin 500 with heart rate monitor belt in January, but Sod’s law would have it that the battery of the belt ran out just before the event. I had done a last training ride a week earlier and everything had worked fine, but when I rode out to the start on Saturday night, the Garmin did not pick up data from the HR belt. I suspected the HR sensor battery (I had used the belt for 2500 km over 4 months). A CR2032 button cell was 250 yen ($2.50) at the next convenience store, but I also needed a tiny screw driver (the size used for eye glasses and watches) to change it. A mechanic at the Cherubim bike shop (where the brevet signup takes place) helped me out. Thank you!

With the new battery the Garmin started displaying numbers though it also warned me about the presence of multiple heart rate sensors, hardly surprising in the reception area of a brevet!

Another problem was that near the 298 km mark, the Garmin lost satellite reception, with no tunnel or other obstacle to explain it. Also, the route as plotted by Strava has me swerve out into the Pacific once. Though my Garmin charger cable worked beautifully to extend its battery life beyond 16 hours, I’d say the jury is still out on whether the Garmin 500 will cope with brevets beyond 200 km.

Too fast and too slow

Why do I use a Garmin if I ignore its data? The idea with HR data is to always operate at your maximum sustainable rate for the duration of the event. I didn’t do that, far from it.

On brevets you need to maintain a minimum average speed of 15 km/h (by elapsed time, including all breaks) overall for the course and up to each check point (PC). Since most climbs are such that my speed will drop below 15 km/h and I can’t make up the lost time on faster descents because they are too short for that, I need to build up a time buffer on flat sections. The first third or so of the course was mostly flat, so we could go fast. I also worked hard for the first 50 km of the 200 km West Izu and Kintaro brevets, but foolishly pushed even harder during the first 75 km of the 300 km, when I should have slightly dropped my speed to allow for the longer course. On top of that I felt the effects of riding through the night without sleep.

As a result, the 4 hour climb from sea level at Fujikawa to 1,100 m above Lake Motosu was really slow. Most of the time my heart rate wouldn’t move much beyond 120, when it had been in the high 150s/low 160s on the flat sections. This is where I lost a lot of time.

I only recovered via the long descent from the pass to Fujiyoshida and then down to Tsuru. My banana-raisin-outmeal energy bars also helped. I think they perked me up more than any bread or onigiri (rice balls wrapped in sea weed) I bought in the convenience store.

Before the Tsuru check point I had all but written off my chances of completing within the time limit. I had to take a second brief nap by the road side at R139 before Fujiyoshida. The high speed descent from Fujiyoshida to Tsuru is always fun and by the time I got there, my time buffer didn’t look great, but workable.

In the end I was 17 minutes faster than last year and will receive my brevet medal by mail ๐Ÿ™‚

Teru teru bozu at work

The Fuji brevet two years ago (2011) got rained out. Though the real hard core riders battled it out in their rain gear, from the pictures it didn’t look like a pleasant experience. The weather report had forecast rain for Sunday right up until the last day, when the outlook changed to something more positive and it worked out OK. At the pre-ride briefing one of the organisers showed us the “teru teru bozu” (anti-rain charm usually made by kids) to ward off rain. Of course I don’t believe in this stuff, but it only started drizzling during the last 30 km before the goal, and only on and off. It was so little, I didn’t even put my smartphone away until I had arrived.

I had discussed my concerns about the weather with my friend Jose and he advised to make sure I’d be warm enough if it rained. I had considered wearing either my GS Astuto bib shorts on top of a long base layer or my dhb winter bib tights and finally opted for the latter. As it happened, the first choice would have been better. I only wore my windbreaker between 04:00 and 06:00 for the early morning descent from Gotemba to the coast. The weather and what to wear is always a guessing game on long rides, especially if you want to minimize how much you carry.

What’s next?

Just like after last year’s 300 km brevet, the AJ NishiTokyo organizers asked me if I was going to give the 400 km brevet in June a try. Also, from next year they will have a 600 km event, for which they will do a trial run in September. My main concern about the longer rides is the effects of lack of sleep. I did much better on that front this year. Short naps work well for me and I probably should have tried one sooner this time. Riding to the brevet start was a decision I only made hours earlier and I still brought along the rinko bag, in case I was too tired after the ride to consider cycling home, but as it happened, I never used it (I could leave it with the staff during the ride). 400 km over 27 hours isn’t that much more than the 360 km over 25 hours that I rode for this event. So I would say, I am definitely up for a 400 km brevet in the future.

No, It’s Not Atlantis!

I don’t envy headline writers who have to come up with catchy phrases every day to get people to read articles in their publications. So it’s understandable that some of them mentioned Atlantis when reporting about the recent discovery of granite from a sunken portion of an ancient continent off the coast of Brazil. Talk about Atlantis or UFOs or a couple of other mysterious subjects always gets people’s attention. According to legend, Atlantis was an island located beyond the Straits of Gibraltar whose civilization was destroyed in a day when it sank into the sea some 10,000 years ago.

Lest anybody gets confused, that recently discovered sunken land has nothing whatsoever to do with the legend of Atlantis. If the real Atlantis had a highly developed civilization then that place can’t be it if no human being ever saw it above sea level, let alone ever lived there. And we know that no human ever lived there if it sunk nearly 50 million years ago and thus is almost as old as the last dinosaurs. Modern man (Homo sapiens) only evolved about 200,000 years ago, tens of millions of years after the recently discovered piece of land had sunk to the bottom of the Atlantic ocean. Whatever real events (if any) may have inspired the legend of Atlantis, they certainly did not occur there.

So what is that piece of former land mass? When the ancient supercontinent of Pangea broke apart and South America separated from Africa, along with India, Madagascar, Antarctica and Australia, not everything from it made it into the present day parts of a jigsaw puzzle that still fit together. Small bits broke off along the fault lines and gradually disappeared into the ocean.

A similar find to the current one was reported in February, from an even older breakup of an ancient continent that left another continental fragment at the bottom of the Indian Ocean.



Good, ugly and excellent movies

Normally I skip the movies on planes and instead try to get as much sleep as possible, as it helps me deal with jet lag once I arrive. I broke this rule on my recent trip from Japan to Germany and back, as I spent a total of 35 hours in the air.

On the way to Germany I watched “The Hobbit – an unexpected journey“, which I found well made and entertaining though I felt the target audience was much younger than I am. I still want to see “Lord of the Rings” one day.

During the return flight I watched “Django unchained“, even though I had decided never to watch another Quentin Tarantino movie after his shockingly violent “Pulp Fiction”. Reading reviews of “Inglorious Basterds” had reinforced that decision. On the other hand, the subject of slavery does not often come up in Westerns, a genre I happen to like, so I was curious. I finished watching the movie, but it wasn’t easy. Several times I was close to turning it off. The violence was so extreme and sadistic, it was more like a Western-themed zombie movie. Afterwards I was sorry for having watched this sick garbage. I will never, ever watch another Tarantino movie!

Then the weekend after I got back from Germany I watched “The English Patient” (1996) on DVD. It was the second time I viewed it, as my wife who had not seen it before rented it on DVD after having it recommended to her by a friend. I was as moved by it as I had been the first time. I loved the finely detailed story, the parallel story lines used and the gradual revelation of what had happened. This is one of the 10 best movies I’ve seen so far.