awhile back, my laptop was OOC (out of commission) due to a broken dc-in board. jesse, a tech-head friend, was kind enough to fix it in return for some beer and a trout-and-asparagus dinner. for several months, all was well in the world of laloca’s laptop computing.

then, just this week, i noticed the strangest thing. my laptop wouldn’t connect to the house wireless. or rather, it would connect, but it would self-assign an IP address. it was driving me nuts. could verizon’s service really be so bad that the router was konking out at least twice a day?

well, i’m sure it could, but that doesn’t seem to be the case here. because i discovered that my laptop connects just fine as long as there’s another computer in the house actively connected to the router.

strange, ain’t it?

###

other things i won’t have time to properly blog about:

• two problematic windows in the house were replaced, and a whole passel of storm windows were installed today. they’re burgundy, which is going to necessitate a repainting of the house’s trim. the difference on the first floor is amazing. suddenly, there’s no breeze.
• what with g and me working long hours, the dog’s getting more neurotic. i considered giving him a klonopin yesterday, but decided against it.
• i had to take 4 hours off work for a doctor’s appointment today (and managed to make it from south of 66 to walter reed in half an hour). i still put in an 8.5 hour work day.
• i should sleep more.