Amazon 7 #26 October 27, 2009 QuoteI am missing your point? If you mean that Microsoft has released a fix for the issue, I'm not disagreeing. My point was that they should not be held responsible for patching decade old software. Whether they do or don't is their choice My point was the patch is still there by running the time zone exe. Quote Share this post Link to post Share on other sites
bob.dino 1 #27 October 27, 2009 QuoteI love how Microsoft blames their shitty programming on the rest of the world rather than themselves. As this is one of my personal pet peeves, some facts of note: 1- Yes, it sucks that TZ info is hardcoded in most OSes 2- There is no single authoritative source of TZ info 3- Stupid fucking governments change the dates around every other year. Sometimes with only 3 weeks notice. 4- When Win2K was released, you could not assume that most machines had internet connectivity, so they don't auto-sync TZ info 5- Win2K was designed for business, not workstation 6- If your 2K machine is connected to a domain, the time will update correctly This set of circumstances explains why the time was off. Quote Share this post Link to post Share on other sites
