Looks like the blog is staying clean, and the Garmin connect links are working again.
I’m not really sure where today’s run came from. I was feeling pretty beat up after yesterdays weight set and 5k swim, and a serious lack of sleep last night. Grabbed some coffee around 3:00pm and that seemed to help. I finally logged off the work computer and headed out the door at 5:20 for my run. The workout called for an hour, with intervals, but I didn’t want to push it too far hard. I chose to do a my standard 5k loop instead, and just let the run happen. After a bit of a cludgy start, faffing about with HRM strap and wonky HR readings, I was cruising pretty effortlessly through miles 2-3, and ended up with comfortable negative splits (IF = .987).
I think I’m going to be just about ready for some fresh FTP and pace testing next week!
Well, the hacker got back in and left his fingerprint on the site. Whee. So I dumped the site and reinstalled, restored and reconfigured. I took the opportunity to replace some of the Facebook integration tools and remove some underutilized plugins. Time will tell if the site stays clean or not.
Looks like some douche-bag hacked into the blog. Fortunately I think I caught it early enough to limit damage and restore the posts. Don’t people have anything better to do with their time?
Grrr – I hate it when ‘automated’ updates fail. I’m sticking with 3.0 until someone figures out how to get 3.0.1 to deploy without multiple “could not create public_html” or could not copy “theme-editor.dev.css” errors. A quick check of the blogosphere seems to indicate many people are having the same issues.
I’m trying really hard not to become a total Apple Fan-boy, but this post from “the Real Steve Jobs” hits too close to home:
The Secret Diary of Steve Jobs : A not-so-brief chat with Randall Stephenson of AT&T.
I love my iPhone. I hate ATT. My data connections work pretty well, but 30-50% of my phone calls are dropped or don’t even connect in the first place.
Back in the day, my bank wanted to charge me a fee for online banking. Within a couple of years, they wanted to charge me a fee for talking to a human.
Digital Domain – Zero-Liability Policy Protects Bank Customers From Phishing – NYTimes.com.
I’d like to charge our anointed leaders with a dumb-ass fee. Bob Mueller? Falling for a Phishing Scam? and his wife knew was a scam from his verbal description of the event?
And they wonder why a couple of losers sneak in to see the Prez…
I finally got Windows7 to install on my home desktop. What a royal pain in the ass. I purchased the Home Pro upgrade via the student discount option, and chose the 64-bit version. This was my first mistake. I received the update notice in my in-box, and was able to successfully download the package. When I ran the “unpackager” tool I ran into an error:
“We are unable to create or save new files in the folder in which this application was downloaded. Please check the folder properties to make sure that you have security
permission on the folder to write files and that the folder is not read-only”.
A quick Google search revealed that this was a relatively common problem with the student upgrade. I followed the instructions for downloading a tool that allowed me to create an ISO file from the install package, burned the ISO to DVD and begin the upgrade.
Because I was moving from 32bit to 64bit, I had to do a clean install. I deleted the old partition (after backing everything up, of course!). I ran the install and it would proceed through the “expanding files” module. At 91%, the system would hang for 30-45 minutes, then fail. I retried this multiple times with the same results.
So now I have a bricked desktop computer. Several hours of Google-fu, downloads and frustrations, I finally figured out that the DVD image I burned from the Dell desktop was corrupt. After a few more hours of work, I got a procedure to work:
(1) Download the package to a portable hard drive
(2) Run the “unpackaging” tool in a XP session on VirtualBox on my Macbook Pro
(3) Use ocsdimg to create an ISO on the portable hard disk drive in the VirtualBox session
(4) Burn the ISO to DVD using the Disk Utility on the Macbook Pro.
(5) Run the install
(6) Skip the entry of the license key during install, since an upgrade key won’t work for a new install
(7) When the install is complete and all patches are applied, run this process to activate the license.
So the Dell desktop is now successfully upgraded, and I’m working through the slow process of reinstalling all my apps, restoring backups and dealing with incompatibilities (grr.. printer drivers….)
Isn’t being a geek fun?
Gonna be my 1st major Mac OS upgrade. Fingers crossed….