<?xml version="1.0" encoding="UTF-8"?>

<rdf:RDF
 xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
 xmlns="http://purl.org/rss/1.0/"
 xmlns:content="http://purl.org/rss/1.0/modules/content/"
 xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/"
 xmlns:dc="http://purl.org/dc/elements/1.1/"
 xmlns:syn="http://purl.org/rss/1.0/modules/syndication/"
 xmlns:admin="http://webns.net/mvcb/"
>

<channel rdf:about="http://tabletumlnews.powerblogs.com/">
<title>Tablet UML News</title>
<link>http://tabletumlnews.powerblogs.com/</link>
<description>News and commentary from Martin L. Shoemaker, author of Tablet UML</description>
<dc:language>en-us</dc:language>
<dc:date>2007-05-27T19:05+00:00</dc:date>
<items>
 <rdf:Seq>
  <rdf:li rdf:resource="http://tabletumlnews.powerblogs.com/posts/1178289509.shtml" />
  <rdf:li rdf:resource="http://tabletumlnews.powerblogs.com/posts/1179738649.shtml" />
  <rdf:li rdf:resource="http://tabletumlnews.powerblogs.com/posts/1167226862.shtml" />
  <rdf:li rdf:resource="http://tabletumlnews.powerblogs.com/posts/1163342650.shtml" />
  <rdf:li rdf:resource="http://tabletumlnews.powerblogs.com/posts/1159975499.shtml" />
  <rdf:li rdf:resource="http://tabletumlnews.powerblogs.com/posts/1149889302.shtml" />
  <rdf:li rdf:resource="http://tabletumlnews.powerblogs.com/posts/1144626139.shtml" />
  <rdf:li rdf:resource="http://tabletumlnews.powerblogs.com/posts/1136364155.shtml" />
 </rdf:Seq>
</items>
</channel>

<item rdf:about="http://tabletumlnews.powerblogs.com/posts/1178289509.shtml">
<title>6 miles from my current contract?</title>
<link>http://tabletumlnews.powerblogs.com/posts/1178289509.shtml</link>
<description>I am so there!...</description>
<dc:creator>Martin L. Shoemaker</dc:creator>
<dc:date>2009-03-04T21:03+00:00</dc:date>
<content:encoded><![CDATA[<a href="http://www.airzoo.org/mssc/mssc-announcement/">I am <i>so</i> there!</a><br />
<br />
<b>"I've Got a Golden Ticket!" Update:</b> "Because you were a member and supporter of the Michigan Space & Science Center in Jackson, I would like to extend an invitation for you to join us for the member's 'pre-opening' event at the new Michigan Space Science Center at the Air Zoo. This will be taking place 11:00 am to 7:00 pm on Firday, June 8th in the Air Zoo's East Campus building."<br />
]]></content:encoded>
</item>

<item rdf:about="http://tabletumlnews.powerblogs.com/posts/1179738649.shtml">
<title>A punch in the gut</title>
<link>http://tabletumlnews.powerblogs.com/posts/1179738649.shtml</link>
<description>That's what this felt like to me:...</description>
<dc:creator>Martin L. Shoemaker</dc:creator>
<dc:date>2007-05-21T09:05+00:00</dc:date>
<content:encoded><![CDATA[That's what <a href="http://www.usatoday.com/news/world/2007-05-21-cutty-sark_N.htm">this</a> felt like to me:<br />
<br />
<a href="http://www.usatoday.com/news/world/2007-05-21-cutty-sark_N.htm"><img src="http://i.usatoday.net/news/_photos/2007/05/21/cutty-sarkx-large.jpg" /></a><br />
<br />
I've never seen the Cutty Sark. Perhaps now I never will. But I've loved that ship for over 30 years. In middle school, I took a modeling class. I built a model of the Cutty Sark. Mom did the rigging. We did it together, and that makes it special.<br />
<br />
If I look closely, I can see how crude my modeling and painting work was (and I doubt I'd do any better now). But if I look from across the room, I see the Sark, full sail, riding the waves. I hear the gulls, and the Captain shouting out orders. I smell the salt spray.<br />
<br />
That's our ship, Mom's and mine. I've taken it with me wherever I've lived in all the years since. And I always wanted to see the real thing, but business never took me to London. Now, despite their optimism, I suspect it's gone for good.<br />
<br />
But <i>our</i> Cutty Sark still sails.]]></content:encoded>
</item>

<item rdf:about="http://tabletumlnews.powerblogs.com/posts/1167226862.shtml">
<title>Goodbye to a good man</title>
<link>http://tabletumlnews.powerblogs.com/posts/1167226862.shtml</link>
<description>...</description>
<dc:creator>Martin L. Shoemaker</dc:creator>
<dc:date>2006-12-27T13:12+00:00</dc:date>
<content:encoded><![CDATA[<a href="http://en.wikipedia.org/wiki/Gerald_Ford">President Gerald R. Ford, 1913-2006.</a>]]></content:encoded>
</item>

<item rdf:about="http://tabletumlnews.powerblogs.com/posts/1163342650.shtml">
<title>Public Service Announcement: Beware of WiFi Evil Twins!</title>
<link>http://tabletumlnews.powerblogs.com/posts/1163342650.shtml</link>
<description>OK, this may be old news to some of you; and it's obvious, once you think about it. But it's news to me, so I want to pass it along....</description>
<dc:creator>Martin L. Shoemaker</dc:creator>
<dc:date>2006-11-12T17:11+00:00</dc:date>
<content:encoded><![CDATA[OK, this may be old news to some of you; and it's obvious, once you think about it. But it's news to me, so I want to pass it along.<br />
<br />
The topic is <a href="http://www.theinternetpatrol.com/wifi-hotspot-evil-twins-mimic-wi-fi-hotspots-and-steal-your-data">WiFi Evil Twins</a>. What's a WiFi Evil Twin, you ask? That's when some thief goes to a public WiFi hotspot area and sets up a <i>new</i> public WiFi network with the same or similar name, in hopes of getting people to sign in through his WiFi instead of the public one. Then he can attempt to upload viruses, record traffic, capture credit card information, etc. Usually he uses a stronger antenna, so that you're more likely to find his network than the legitimate network.<br />
<br />
There are variations on this. One might be called the Evil One: he doesn't duplicate the existing network, he just creates a new network. As <a href="http://www.scambusters.org/eviltwin.html">this interview with Anne P. Mitchell, Esq.</a> (Professor of Internet Law at <a href="http://www.lincolnlawsj.edu/">Lincoln Law School of San Jose</a>, and the President and CEO of <a href="http://www.isipp.com/">the Institute for Spam and Internet Public Policy</a>) explains:<br />
<br />
<blockquote><br />
Anne: Yes. Just last week I was sitting in my local Starbucks, where they offer wifi hotspots from T-Mobile. In order to log into a T-Mobile hotspot, you must have an account with T-Mobile, for which you must pay.<br />
<br />
Even though I don't use the T-Mobile hotspots, I always check (with my laptop) to see what wifi hotspots are available at any given location because, well, that's part of my beat.<br />
<br />
Sure enough, users at that Starbucks who opened their laptops and searched for a local wifi Internet connection were presented with the option of "T-Mobile Hotspot," as they should be, but were also presented with a second option, called "Free Wifi from Team WiFi," which I am 99% certain was an evil twin (and indeed Starbucks confirmed that there was no special offer going on which would have otherwise explained that second hotspot).<br />
<br />
Now, notice a few things about this second, uninvited hotspot. First, it uses the term "free wifi." Who wouldn't want to use that, especially compared to the T-Mobile hotspot, where you have to pay?<br />
<br />
Second, though, note the friendly and familiar sounding "Team WiFi." By using familiar terms for their evil twin, along with telling people it is free, they are making it very easy for an unsuspecting user to go ahead and click and connect to that evil twin. In fact, users may just think that it's a special offer from the T-Mobile Hotspot people.<br />
<br />
Sure enough, Audri, this evil twin caught some people. As the gentleman who was sitting next to me got up to leave, after being on his computer for quite some time, I asked him whether he had logged in to the Internet while he was there.<br />
<br />
When he said that he had, I asked him whether he was a T-Mobile user. "Oh no," he replied, "they have a free wifi hotspot set up here."<br />
<br />
I advised him that it was almost certainly an evil twin, and that if he had done anything online while logged in through that "free" hotspot which might have compromised any sensitive information, he should take immediate measures to remedy the situation, such as changing any passwords he had sent while logged in.<br />
</blockquote><br />
<br />
And for me, this is more than just theory: I'm pretty sure I've met an Evil Twin in the wild. A hotel I've been staying at offers free WiFi (more and more of them do these days &mdash; it's a lot cheaper than stringing wires to the rooms). They have three WiFi hubs: "hotel name", "hotel name2", and "hotel name3" (names changed because I'm not sure I'm right yet). That's what the owner believes, anyway; but when I check for available networks, there's a <i>fourth</i> network, named "Hotel Name". And it has a stronger signal than any of the other hubs. What's more, when I connect to the other three hubs, they all give me the same IP address; but when I (carefully and briefly) connect to the fourth hub, it gives me a radically different IP address on an entirely different subnet.<br />
<br />
So what should I do about it? That's troublesome. From the interview with Ms. Mitchell:<br />
<br />
<blockquote><br />
At this point your readers may be wondering why I didn't alert the authorities. And this is why user education is so very important.<br />
<br />
There really was nobody for me to effectively alert. I could have called the police, but they would not have had the resources to even figure out where this evil twin was located, let alone to figure out who and how it was being done. The best thing I could do at that point was to let people know not to use that hotspot.<br />
</blockquote><br />
<br />
While I'm all for user education &mdash; that's why I'm telling you this &mdash; I'm not so complacent as Ms. Mitchell about informing the police. <a href="http://www.michigan.gov/ag/0,1607,7-164-17334_17364-46967--,00.html">Michigan's Attorney General has made fighting Internet crime a priority,</a> so I've informed their High Tech Crime Unit. It may be a waste of time; but if I don't try, I'll always worry that someone might be getting ripped off, and I didn't do anything to stop it.<br />
<br />
Now back to the subject of user education: here are some things you can do to protect yourself.<br />
<br />
<ol><br />
   <li>When in doubt, <b>don't do it.</b> These scammers are good. This is how they make their living. If you don't feel comfortable trying to detect and outwit the scammers, then don't do <b>anything</b> at a WiFi hotspot. <b>Certainly</b> don't enter any passwords, credit card numbers, etc. Save that work for when you have a direct connection. I'm not saying you should never use WiFI; I'm saying that <i>if</i> you don't want to take the time to learn how to protect yourself, <i>then</i> you should never use WiFi.</li><br />
   <li>Always download the latest security updates from <a href="http://windowsupdate.microsoft.com/">Windows Update</a>. Set up your machine to download the updates automatically. Don't tell me you're too busy. If you're too busy, then stay off WiFi. In fact, stay off the Internet, period. The scammers are working hard to find new victims, and you're volunteering to be one. And don't tell me that the updates "break" your machine. While I'll grant that's possible, it's most likely something you're doing wrong, and you need to fix. I've had automatic updates activated on all of my machines for years, and I've never had a problem.</li><br />
   <li>Turn on your Windows firewall.</li><br />
   <li>Download and install <a href="http://www.microsoft.com/athome/security/computer/default.mspx">Windows Defender</a>.</li><br />
   <li>Install a good antivirus/Internet security package, such as <a href="http://mcafee.com/us/">McAfee</a> or <a href="http://www.symantec.com/index.htm">Symantec</a>, and keep it up to date.</li><br />
   <li>Install a spyware blocker like <a href="http://www.lavasoftusa.com/software/adaware/">Ad-Aware</a> or <a href="http://www.safer-networking.org/">Spybot</a>. In fact, install both of them. They're free, and they seem to complement each other well. And yes, Windows Defender and McAfee and Symantec all have adware/spyware blockers as well; but since each product has its own strengths and weaknesses, it can't hurt to have multiple layers of protection.</li><br />
   <li>Despite my advocating Ad-Aware and Spybot, be careful with "free" software. Software takes time to develop. Time is money. Although we programmers will often write code for fun or passion, the most common motivation is money. If someone's offering it to you for free, it's very likely because he hopes to make money somewhere else. In many cases, that's by selling ads through adware/spyware; but sometimes, it's by installing viruses and keyboard recorders to steal your banking information. If you're installing "free" software, make sure you trust the company or person that's providing it.</li><br />
   <li>Change your WiFi settings to Paranoid (i.e., safe). This will involve several steps:<br />
<ol><br />
   <li>Open up your network connections by selecting <b>Show All Connections</b> from your <b>Start</b> menu:<br />
<br />
<img src="/files/tabletumlnews-Show_All_Connections.jpg" width="500" height="527"  alt="Show all connections"><br />
   </li><br />
   <li>When you see the Network Connections dialog, right-click your wireless connection and select <b>Properties</b>:<br />
<br />
<a href="/files/tabletumlnews-Wireless_Properties.jpg"><img src="/files/tabletumlnews-Wireless_Properties-small.jpg" width="500" height="373"  alt="Selecting Wireless Network Properties"></a><br />
   </li><br />
   <li>You should see the Wireless Network Connection Properties dialog:<br />
<br />
<img src="/files/tabletumlnews-Wireless_Properties_Dialog.jpg" width="367" height="450"  alt="Wireless Network Connection Properties dialog"><br />
<br />
Switch to the <b>Wireless Networks</b> tab:<br />
<br />
<img src="/files/tabletumlnews-Wireless_Networks_Tab.jpg" width="367" height="450"  alt="Wireless Networks tab"><br />
   </li><br />
   <li>Click the <b>Advanced</b> button to open the Advanced wireless settings dialog:<br />
<br />
<img src="/files/tabletumlnews-Advanced_Wireless_Settings.jpg" width="306" height="227"  alt="Advanced wireless settings dialog"><br />
<br />
This lets you choose from three different ways to access WiFi networks:<br />
<br />
<ul><br />
   <li><b>Any available network (access point preferred)</b>. This means that you will connect either to wirless hubs <i>or</i> to other wireless computers, but you'll prefer wireless hubs.</li><br />
   <li><b>Access point (infrastructure) networks only</b>. This means that you will connect only to wirless hubs.</li><br />
   <li><b>Computer-to-computer (ad-hoc) networks only</b>. This means that you will connect only to other wireless computers.</li><br />
</ul><br />
Unless you <i>know</i> you're intending to work with friends or coworkers and plan to meet somewhere without a WiFi network, it's always a bad idea to connect to other wireless computers. That's the easiest way to get viruses; and it's a very easy way to get hoodwinked by an Evil Twin: the scammer doesn't even have to set up a hub, just rename his computer to look like a network. The Paranoid setting here is <b>Access point (infrastructure) networks only</b>. Choose that one unless you're sure you have a reason not to.<br />
<br />
This dialog also has a check box: <b>Automatically connect to non-preferred networks</b>. For added Paranoia, make sure that box isn't checked.<br />
<br />
When you're done in this dialog, click <b>Close</b>. But don't close the Wireless Network Connection Properties dialog. You'll do more work there in the next step.<br />
   </li><br />
</ol><br />
   <li>Next you want to disable automatic connection to all of your WiFi networks, or at least to most of them. Your home network is <i>probably</i> safe, as are those of your friends, and your office; but even in those places, if there are neighbors nearby, there's the chance of an Evil Twin. So the Paranoid (i.e., safe) approach is to only make manual connections. Now if you're like me, you probably already have a number of known Wireless connections; and if Evil Twins are as new to you as they are to me, then those are probably set up for automatic connection. So you'll need to switch those to manual, following these steps for each network:<br />
<br />
<ol><br />
   <li>In the Wireless Network Connection Properties dialog, select the network you would like to change:<br />
<br />
<img src="/files/tabletumlnews-Selecting_a_WiFi_Network.jpg" width="367" height="450"  alt="Selecting a WiFi network to convert to manual connection"><br />
<br />
After you select the network, click <b>Properties</b>. You should see the Properties dialog for the selected network:<br />
<br />
<img src="/files/tabletumlnews-Wireless_Network_Properties.jpg" width="368" height="450"  alt="Properties for the selected wireless network"><br />
   </li><br />
   <li>Select the <b>Connection</b> tab:<br />
<br />
<img src="/files/tabletumlnews-Connection_Tab.jpg" width="368" height="450"  alt="The Connection tab for the selected wireless network"><br />
<br />
Uncheck the box that says <b>Connect when this network is in range</b>, and then click <b>OK</b>.<br />
<br />
Repeat this for every wireless network. Then click <b>OK</b> in the Wireless Network Connection Properties dialog as well.<br />
   </li><br />
</ol><br />
<br />
Once you've disabled automatic connection, you'll need to connect manually to any network. To do this, right-click the wireless network connection icon and select <b>View Available Wireless Networks</b>:<br />
<br />
<a href="/files/tabletumlnews-View_Available_Wireless_Networks.jpg"><img src="/files/tabletumlnews-View_Available_Wireless_Networks-small.jpg" width="500" height="373"  alt="View Available Wireless Networks"></a><br />
<br />
You'll see the Wireless Network Connection dialog:<br />
<br />
<a href="/files/tabletumlnews-Wireless_Network_Connection_dialog.jpg"><img src="/files/tabletumlnews-Wireless_Network_Connection_dialog-small.jpg" width="500" height="381"  alt="Wireless Network Connection dialog"></a><br />
<br />
Select the network you want to connect to, and click <b>Connect</b>.<br />
   </li><br />
   <li>While you're in the Wireless Network Connection dialog, search for Evil Twins. If you see two networks with the same name, one is probably an Evil Twin. If you see a network with a seductive name like "Free Wifi from Team WiFi," that's probably an Evil One. Here's a hint: Internet service isn't free. If a cafe or restaurant or hotel puts in WiFi service, it's because they're hoping it will bring them customers. And the only way it can bring them customers is if customers know about it. That means they'll advertise it with signs on the wall or the front door. If you don't see an advertisement for it, it's probably an Evil One. And if there's <i>both</i> a fee-based service like T-Mobile <i>and</i> a "free" service, the "free" service is almost conclusively an Evil One. When in doubt, ask the management. If they don't know about it &mdash; or they're clueless and say, "I don't know anything about the wireless" &mdash; assume it's an Evil One.</li><br />
   <li>If you think you've found an Evil Twin or an Evil One, I disagree with Ms. Mitchell: inform your Attorney General. They get our tax follars to pursue cybercrime, but they can't be everywhere. If they don't know about the crime, they can't pursue it. Maybe nothing will come of it, and the criminals may keep commiting their crimes; but if no one does anything, then they <b>will</b> keep commiting their crimes. I understand why Ms. Mitchell would inform other patrons that they were at risk. Of course, it takes some <i>chutzpah</i> to start telling random strangers in a cafe that they're at risk; and worse, it may also upset the scammer, and he may take steps to shut you up. And even if you inform the management, it's possible that someone in management is the scammer. I think it's best to leave law enforcement to the law enforcement authorities. Tell your AG.</li><br />
</ol><br />
<br />
Robert A. Heinlein once wrote: "Anything free is worth what you pay for it." My cynical addition is "If you're lucky." That "free" WiFi could end up costing you everything you've got in your bank account, and a whole lot more.<br />
<br />
UPDATE: My lone commenter and fellow <a href="http://www.aaduelist.org">Duelist</a> Epee Bill links to <a href="http://www.realtechnews.com/posts/3755">this more serious WiFi vulnerability</a>. It's a WiFi driver flaw affecting laptops from Dell, HP, and Gateway, as well as other devices. Because it's driver-level code, it works at a privileged level in your system and can give a hacker complete control.<br />
<br />
The catch is no one's distributing the fix through typical "push" channels. You have to know about it and go pull it down.<br />
]]></content:encoded>
</item>

<item rdf:about="http://tabletumlnews.powerblogs.com/posts/1159975499.shtml">
<title>Congratulations to Josh Holmes!</title>
<link>http://tabletumlnews.powerblogs.com/posts/1159975499.shtml</link>
<description>My good buddy Josh Holmes announced some major news this week: he's joining Microsoft as an Architect Evangelist....</description>
<dc:creator>Martin L. Shoemaker</dc:creator>
<dc:date>2006-10-04T15:10+00:00</dc:date>
<content:encoded><![CDATA[My good buddy Josh Holmes <a href="http://www.joshholmes.com/2006/10/02/NewCareer.aspx">announced some major news this week</a>: he's joining Microsoft as an Architect Evangelist.<br />
<br />
As someone whome he hit up for a reference, I've been waiting a long time to say: Congratulations, Josh!<br />
<br />
<b>Update:</b> Revised Josh's URL.<br />
]]></content:encoded>
</item>

<item rdf:about="http://tabletumlnews.powerblogs.com/posts/1149889302.shtml">
<title>One more reason why the news was good yesterday...</title>
<link>http://tabletumlnews.powerblogs.com/posts/1149889302.shtml</link>
<description>...</description>
<dc:creator>Martin L. Shoemaker</dc:creator>
<dc:date>2006-06-09T21:06+00:00</dc:date>
<content:encoded><![CDATA[...I no longer have to remember which one's al-Zarqawi and which one's al-Zawahiri. The live one (for now) is al-Zawahiri.]]></content:encoded>
</item>

<item rdf:about="http://tabletumlnews.powerblogs.com/posts/1144626139.shtml">
<title>Insufficient system resources exist to complete the API.</title>
<link>http://tabletumlnews.powerblogs.com/posts/1144626139.shtml</link>
<description>Ever since I got my wonderful Gateway CX200X &amp;mdash; and even before, with my less-than-wonderful Toshiba M200 (which I'm managing to put to productive use, but cautiously) &amp;mdash; I've...</description>
<dc:creator>Martin L. Shoemaker</dc:creator>
<dc:date>2006-04-10T00:04+00:00</dc:date>
<content:encoded><![CDATA[Ever since I got my wonderful <a href="http://tabletumlnews.powerblogs.com/posts/1130922413.shtml">Gateway CX200X</a> &mdash; and even before, with my less-than-wonderful <a href="http://tabletumlnews.powerblogs.com/posts/1128232808.shtml">Toshiba M200</a> (which I'm managing to put to productive use, but cautiously) &mdash; I've had this annoying problem. When I would shut the lid, with every expectation that that would suspend the machine, I would be deceived. I would put the machine in my backpack, and head off for the road or the plane or wherever, expecting that my machine was obediently sleeping, preserving battery power; and instead, it was still running along, drinking down that battery juice. Yumm! And even worse, it was locked away in my backpack, a confined and somewhat insulated place, where the machine served as a most effective heating system, thoroughly roasting any heat-sensitive system inside &mdash; such as, say, <b>itself</b>. And when I would open the backpack, I would pull out a horribly overheated machine with half its battery power gone. And the first thing I would see would be a message box: "Insufficient system resources exist to complete the API." No explanation of which resources were lacking &mdash; and trust me, my Gateway's a powerhouse, packed with all the RAM and CPU and disk it could possibly hold, and even the Toshiba has lots of RAM (keep that in mind) &mdash; nor which API (Application Programming Interface, or operation for you non-geeks) was failing, nor which program was having the problem. And often the box appeared multiple times. And once I finally closed them all, I could use the half-depleted, overheated machine.<br />
<br />
There was one other symptom, which I was sure was related but couldn't prove: if I closed the machine's lid, and then happened to be near it maybe thirty minutes or so later, I would sometimes hear the standard Windows error chime that means "Hey, something just failed." My assumption (true enough, as it happens) was that that error chime corresponded to the message box appearing.<br />
<br />
Now since the problem was common to both machines, I naturally assumed that it was due to something I had installed on the Toshiba, and then later moved to the Gateway. But despite some experimentation, I didn't figure out what it might be. I resigned myself to doing a full power down whenever possible. It's a lot slower, but it's safer. But I was still puzzled at what application might be preventing the machine from sleeping.<br />
<br />
Little did I suspect that it was <b>the operating system</b>.<br />
<br />
Last week, I got fed up with using my machine as a backpack heater, and I got fed up with waiting through power down and power up. So I did a quick Internet search, and I found <a href="http://support.microsoft.com/?kbid=909095">this Microsoft Knowledge Base article</a>. It explains that this error happens in Microsoft Windows XP SP 2, because of a flaw in the hibernation engine. (And before anyone asks why I used Hibernate rather than the much faster Standby mode: I <i>am</i> using Standby; but I have a battery-saving power mode enabled that switches to Hibernate if it's inactive for half an hour. Or it would if it could; but instead, this error happened. And when it did, the message box would appear, and the error chime would sound. See, it all starts to come together now, eh?)<br />
<br />
And the nature of the error has to do with what Hibernate does: it captures the state of your machine, and saves that to your hard drive, and then powers down; but when your machine powers back up, it sees that hibernation state file, and it recreates that state as if your machine had never been sut off. So that means it has to make an exact image of your entire RAM, so that it can reload that exact image when it starts up again. But here's the flaw: sometimes it couldn't get the resources (file handles or something, I don't think I've ever found out) to create the RAM copy; and so rather than lose the contents of your RAM, it would simply refuse to hibernate.<br />
<br />
And here's the real kicker: the more memory you had, and the more you used it and fragmented it into a lot of smaller chunks, <b>the more likely it was that the hibernate engine would run out of resources.</b> So if you're somebody like, say, a programmer, who puts a machine through a lot of memory churn... And if you decided when buying a new machine that the best way to deal with memory limits was to just buy lots and lots of memory... Then you were <b>more</b> likely to have this problem!<br />
<br />
And as the KB article explains, Microsoft does have a fix. Unfortunately, this problem was found <i>after</i> XP Service Pack 2. And short of utter calamity, Microsoft has no plans for another Service Pack for Windows prior to Vista. And as many of you have probably heard, Vista has been pushed back to the first quarter of next year. So there's no official path to obtain the fix for this problem.<br />
<br />
Except for one path: a hotfix. As the KB article explains, Microsoft does offer a hotfix for this problem. For those who haven't run into one before, a hotfix means:<br />
<br />
<ol><br />
   <li>Microsoft hasn't had a chance to test this on nearly as many machines and configurations as they would like.</li><br />
   <li>In particular, Microsoft hasn't had a chance to regression test this. Regression testing is a way of testing that no old bugs have somehow been reintroduced in the process of fixing a new bug.</li><br />
   <li>It may take a little more expertise to install than does a usual set up program.</li><br />
   <li>Microsoft has to be sure that you get the version of the hotfix that's right for your operating system. (XP isn't the only OS where they found this problem.)</li><br />
   <li>Microsoft can't support the hotfix. If you must have it, they strongly <b>encourage</b> you to do a <b>thorough</b> backup before installing it.</li><br />
   <li>Microsoft strongly <b>discourages</b> you from installing the hotfix unless you're actually suffering from the problem it was designed to fix. For instance, most people never hibernate desktops, and not all laptops or Tablets are experiencing this problem, so don't apply the hotfix to those!</li><br />
</ol><br />
<br />
In the case of this hotfix, they're extremely cautious to be sure that only people who really need the fix get it, and that they get the right version: they don't offer it as a download, but rather require you to call them on the telephone (how quaint), give them the Knowledge Base article number (that's <b>909095</b>, for those of you who need it), and request that they email you a URL for the hotfix. And when they send you the URL, it includes a password that expires in a week. They <b>really</b> don't want you to install this unless you <b>absolutely</b> need it.<br />
<br />
But I have to tell ya, I installed it Thursday, and already I'm thrilled. Suspend-to-Hibernate transition <b>just works</b>. I know that's no big deal to some of you, but it's a <b>huge</b> deal for me. No more roasted machine!<br />
<br />
Now I don't fault Microsoft for having the bug. All code has bugs. I don't fault Microsoft for not releasing another Service Pack with this fix, because I understand that release schedules on a major product like an operating system are very difficult to manage. I won't go into all the reasons, but I'm very sympathetic to how difficult this schedule must be for them. And I'm not even upset about the multiple-step hotfix approach, nor about their caution in releasing it and their reluctance to support it. I think I understand all of their reasoning for these decisions.<br />
<br />
But I'm a little annoyed at Microsoft for not publicizing this problem and the hotfix for it more. I have been at two major Tablet PC promotional/educational events at Redmond in the past half year, plus the MVP Summit. Power management came up as an issue at all of them. And the roasting-computer-in-the-backpack problem came up at every one of them. And Microsoft people promised that this was a driving force for some of the advanced power management features coming up in Vista.<br />
<br />
But not once did anyone mention that I could have a fix for my <b>immediate</b> problem <b>immediately</b>.<br />
<br />
I'm going to assume that the problem is so obscure that most Microsoft people don't even know about it. But at a Tablet PC talk specifically about power management? Where they cite roasting computers as a problem that people are complaining about? I have trouble believing that no one there knew about this problem and the hotfix.<br />
<br />
There may be some acceptable explanation for not telling us about this. I'm willing to listen. But there's no reason I can see not to tell the world as loudly as my little blog can. So I'm going to join <a href="http://blogs.msdn.com/smguest/archive/2006/03/13/550940.aspx">the</a> <a href="http://www.u-g-h.com/InsufficientSystemResourcesExistToCompleteTheAPISOLIVED.aspx">chorus</a> <a href="http://www.robertwray.co.uk/blog/archives/2006/03/insufficient_sy.html">of</a> <a href="http://betweengo.com/miscellaneous/2006/03/11/hibernation-insufficient-system-resources-exist-to-complete-the-api/">many</a>, <a href="http://www.ntwizards.net/2004/10/13/hibernate">many</a> <a href="http://translocator.ws/2005/11/06/hibernation-insufficient-system-resources/2/">bloggers</a> <a href="http://g.msn.com/9SE/1?http://microsoft.blognewschannel.com/index.php/archives/2006/04/04/windows-xp-hibernate-bug-solved/&&DI=293&IG=64a84477e8ba48ca93f53918af65803b&POS=4&CM=WPU&CE=3&CS=AWP&SR=3">and</a> <a href="http://g.msn.com/9SE/1?http://www.notebookforums.com/forums&&DI=293&IG=64a84477e8ba48ca93f53918af65803b&POS=8&CM=WPU&CE=7&CS=AWP&SR=7">others</a> <a href="http://g.msn.com/9SE/1?http://www.devportal.hu/Portal/Blogs.aspx&&DI=293&IG=64a84477e8ba48ca93f53918af65803b&POS=10&CM=WPU&CE=9&CS=AWP&SR=9">telling</a> <a href="http://g.msn.com/9SE/1?http://www.tabletquestions.com/forumdisplay.php?s=8bf9647fcdeb0ad9e42d76c0cc2449a5&f=31&&DI=293&IG=64a84477e8ba48ca93f53918af65803b&POS=11&CM=WPU&CE=10&CS=AWP&SR=10">the</a> <a href="http://g.msn.com/9SE/1?http://www.bharat.name/modules/bfeed/&&DI=293&IG=2055ae8a34a24027a7151e8a36ec5d26&POS=3&CM=WPU&CE=2&CS=AWP&SR=2">world</a>: "If you're getting to message 'Insufficient system resources exist to complete the API,' read <a href="http://support.microsoft.com/?kbid=909095">KB article <b>909095</b></a>." I can't recommend that you install the hotfix, because only you know how willing you are to risk having to rebuild your machine if something goes wrong; but I can make you aware of the hotfix, and I can let you know that it works on my machine.]]></content:encoded>
</item>

<item rdf:about="http://tabletumlnews.powerblogs.com/posts/1136364155.shtml">
<title>Prime Directive -- Not!</title>
<link>http://tabletumlnews.powerblogs.com/posts/1136364155.shtml</link>
<description>Professor Reynolds links to this very lengthy essay on cultural contamination, and how that may not be as bad as some people want you to believe, by Kwame Anthony...</description>
<dc:creator>Martin L. Shoemaker</dc:creator>
<dc:date>2006-01-04T08:01+00:00</dc:date>
<content:encoded><![CDATA[<a href="http://instapundit.com/archives/027824.php">Professor Reynolds</a> links to <a href="http://www.nytimes.com/2006/01/01/magazine/01cosmopolitan.html?pagewanted=all">this very lengthy essay on cultural contamination</a>, and how that may not be as bad as some people want you to believe, by Kwame Anthony Appiah. There's far too much good content here for me to summarize, so I'll just pull out what I think is the most critical point:<br />
<br />
<blockquote><br />
So liberty and diversity may well be at odds, and the tensions between them aren't always easily resolved. But the rhetoric of cultural preservation isn't any help. Again, the contradictions are near to hand. Take another look at that Unesco Convention. It affirms the "principle of equal dignity of and respect for all cultures." (What, all cultures - including those of the K.K.K. and the Taliban?) It also affirms "the importance of culture for social cohesion in general, and in particular its potential for the enhancement of the status and role of women in society." (But doesn't "cohesion" argue for uniformity? And wouldn't enhancing the status and role of women involve changing, rather than preserving, cultures?) In Saudi Arabia, people can watch "Will and Grace" on satellite TV - officially proscribed, but available all the same - knowing that, under Saudi law, Will could be beheaded in a public square. In northern Nigeria, mullahs inveigh against polio vaccination while sentencing adulteresses to death by stoning. In India, thousands of wives are burned to death each year for failing to make their dowry payments. Vive la difference? Please.<br />
</blockquote><br />
<br />
I'm currently reading Jack McDevitt's <a href="http://www.amazon.com/gp/product/0441012108/qid=1136363778/sr=8-2/ref=pd_bbs_2/002-3457350-0441603?n=507846&s=books&v=glance">Omega</a>, which involves a sorta Prime Directive situation like in <i>Star Trek</i>: a catastrophe looms for a primitive culture, and the cultural preservationists would rather let the natives die than save them and thus expose them to a more advanced culture. The older I get, the more arrogant the Prime Directive sounds to me: sacrificing people's lives for some supercilious view of "culture" that sounds on awful lot like "keeping the primitives in their place". Kwame Anthony Appiah skewers this notion quite adeptly. His essay is long, but it's well worth your attention.<br />
<br />
UPDATE: I just read the credits at the end of the essay. It turns out to be an extract from the author's book, <a href="http://www.amazon.com/gp/product/0393061558/qid=1136364709/sr=1-1/ref=sr_1_1/002-3457350-0441603?s=books&v=glance&n=283155">Cosmopolitanism: Ethics in a World of Strangers</a>, coming later this month. Gee, just what I needed: an excuse to shop for books...<br />
]]></content:encoded>
</item>

</rdf:RDF>