Author: Eugene

Posted on

Stupid airline

Just got an email saying the itinerary for my reunion trip in September has changed so that on the flight back, I’m supposed to be going from Edmonton to Denver to Washington Dulles and finally to Charleston. It’s almost 10 hours of flight time and 13 hours from start to finish (not including the drive to and from airports) and nearly double what it was before. Major suckage. Really, really major suckage.

It’s a far cry from the original Edmonton->Chicago->Charleston that I originally booked. I may have to call and see what can be done about switching it back to the way it was, if it’s even possible.

Posted on

Time for new shoes

It’s definitely past time for a new pair of runners. The ones I have, in addition to not seeing much running over the years, are way overdue for replacement. Come to think of it, I think I’ve had these shoes since Detroit…They’ve seen a lot of walking mileage, but not a whole lot of running.

New shoes will have to wait until after AAPM though.

Posted on

Plantar pain

Bottom of my foot hurts for some reason. Started after that last 45 minute workout, so I wonder if I strained some of those muscles and tendons a bit.

Took it a little bit easy today with a 30 minute Fat burner L5 (4.5 mph max) run. Felt pretty good about it today.

Duration: 30 minutes
Distance: 1.82 miles
Average pace: 16:40
Calories burned: 217

Posted on

Messed up blog DB

Well, it seems after years of schema upgrades, betas and life on MT’s bleeding edge in general, the schema of my MT blog DB is messed up and causes spurious errors with MT4 that nobody else can reproduce.

Update: Ok, managed to get things cleaned up enough for beta 6 to upgrade the database properly. Cleaned out a bunch of old unused and unneeded blogs along with cleaning up old junk out of the mt_templatemap and mt_template tables. Once I did all that, everything worked as expected.

So here’s what I tried.

Created a fresh new MT 3.35 database and used INSERT INTO [table “” not found /]
(...) SELECT ... FROM ... to repopulate the fresh database with the contents of the old one. But when I tried to get MT4 to upgrade the fresh database, I ended up with that same error at just before the end of the DB upgrade process

* Removing unused template maps…
Error during upgrade: Can’t call method “archive_type” on an undefined value at lib/MT/TemplateMap.pm line 99

Further attempts to get into MT just result in a blank error page.

So then I created a fresh MT4 database and use the same INSERT/SELECT method to copy data from the MT3.35 DB into the MT4 DB. This ended up being only partly successful. While everything appears to be intact, the dashboard is broken and the entry listing isn’t sorted by date. Ok, that’s fixed…the entry_authored_on and entry_authored_by fields weren’t populated. Filling them in with appropriate values seems to have done the trick.

Will be interesting to see what happens when I start messing with templates and rebuilding things.

Posted on

Bluetoothing

Well, I’m part way there in my efforts to sync my T3 with my work desktop over Bluetooth. Both of the units can discover the other but when I tap the Hotsync button, the T3 fails with

Error: Serial: timeout. Could be bad cable or faulty Modem. (0x0305)

I can use hcitool to get bits of info from the T3

hcitool scan

Scanning ...
00:07:E0:31:75:D6 Eugene Mah
hcitool info 00:07:e0:31:75:d6

Requesting information ...
BD Address: 00:07:e0:31:75:d6
LMP Version: 1.1 (0x1) LMP Subversion: 0x700
Manufacturer: Broadcom Corporation (15)
Features: 0xff 0xff 0x0d 0x00 0x00 0x00 0x00 0x00
<3-slot packets> <5-slot packets> <encryption> <slot offset>
<timing accuracy> <role switch> <hold mode> <sniff mode>
<park state> <RSSI> <channel quality> <SCO link> <HV2 packets>
<HV3 packets> <u-law log> <A-law log> <CVSD> <power control>
<transparent SCO>

so I know BT is active on both. I just can’t get the T3 to establish a connection for some reason.

I suppose I could just bag the whole thing and go out to get a new cable or cradle to sync and charge with. That would be so un-geeky of me though.