As of the rush hour this morning (and “rush” is just a word today), WMATA has yet to adjust their system clocks to account for the early switch to DST. I’m not sure if they didn’t feel like paying the average $4000 to Microsoft for the corporate fix (which, BTW, actually has a bug in it too), or somebody just hit a big snooze button, ala “Lost”, for the past two days. I guess it’s just Metro’s way of saving some cash, or just confusing the hell out of Washington commuters… but maybe they were just concentrating on the new MetroBus lighting

9 Comments so far

  1. Doug (unregistered) on March 12th, 2007 @ 8:47 am

    On my XP laptop, with all the latest service packs and patches installed, the update happened automatically. On an older XP desktop, it did not. No surprise there. Linux and similar OSs need to upgrade their zoneinfo files, which isn’t terribly complicated if you know your way around the system. I can’t speak for Macs.

  2. Tom Bridge (unregistered) on March 12th, 2007 @ 8:52 am

    You’ve got to be kidding me? Metro didn’t prep for the new DST issue? That’s insane! What are we paying those bozos for?

    (with regards to Macs & DST change, Tiger was fine after about 10.4.4 and Panther had an update out a month ago to fix 10.3.9 machines. All five people who use 10.2 still are fubar.)

  3. Paulo (unregistered) on March 12th, 2007 @ 9:07 am

    “What are we paying those bozos for?”

    Red LED lights and quality escalator maintenance, of course!

  4. Tiffany (unregistered) on March 12th, 2007 @ 3:46 pm

    At my company, which has several thousand XP desktops across the country, supposedly all configured identically, about half the machines updated, and half of them didn’t.

    The best part was the email where they warned us that manually changing the clocks ourselves could disconnect us from the network, and we’d better let IT do it for us, remotely. I’m not discounting the possibility that such a thing *could* be the case, but suggesting that any system that depends on my system clock for its network connection is maybe not the best-designed.

  5. Dan (unregistered) on March 12th, 2007 @ 7:35 pm

    You can also just update the zoneinfo file on Mac OS X. It is still unix, you know.

  6. Doug (unregistered) on March 12th, 2007 @ 11:54 pm

    Yes, I do know Dan, although I doubt the casual user would know how to go to a shell prompt, grab the latest zoneinfo archive, extract it, run zic on the sources, copy the results into the right folder, then symbolically link the correct timezone file to /etc/localtime.

    Your average Mac user relies on GUI clicky tools, they don’t want to pop the hood.

  7. Doug (unregistered) on March 13th, 2007 @ 12:33 am

    PS. If you are a Mac user and want to do the update manually, here are some detailed instructions.

  8. David (unregistered) on March 13th, 2007 @ 12:21 pm

    Wow, for a snide/side comment on a quasi-governmental organization’s failings, in such a town as DC, I’m surprised at how many comments.

  9. Don (unregistered) on March 13th, 2007 @ 2:49 pm

    Hey, bust out with the geeky issues and we’re all ready for a pile-on.

Terms of use | Privacy Policy | Content: Creative Commons | Site and Design © 2009 | Metroblogging ® and Metblogs ® are registered trademarks of Bode Media, Inc.