Tablet UML News


News and commentary (and whatever else catches my eye)
from Martin L. Shoemaker, author of Tablet UML
and UML and Tablet PC instructor for The Richard Hale Shaw Group

Wednesday, March 4, 2009

6 miles from my current contract?
I am so there!

"I've Got a Golden Ticket!" Update: "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."

Thursday, April 12, 2007

Well, if you insist...
When I'm traveling on my own dollar, I keep an eye out for Red Roof Inn. They're consistently at or near the lowest price of any national chain, and they're consistently clean and well-maintained, with courteous staff. Plus many of their locations are T-Mobile HotSpots, and I have a T-Mobile subscription, so I can get online there easily.

But there's Red Roof service, and then there's Red Roof service...

My new contract work is on a project with some pretty tight deadlines looming, so there are some long days lately. When the days are long enough or the weather nasty enough, I prefer to check into the local Red Roof than risk the trip home. A night there is $45, which is one-third the cost of a wrecker, so it's an easy decision.

Monday was a long day: 18 hours. So I decided to check in to Red Roof. I arrived around 5 a.m. (Tuesday, technically, but still Monday for me), got a room, slept, and checked out at noon.

Tuesday was a shorter day: only 14 hours. Still, that meant it was after 3 a.m., and I was tired. Another Red Roof night. I checked in around 3:30 a.m. (Wednesday, technically, but still Tuesday for me), got a room, and slept.

At just about noon, I got a call from the front desk. They told me they owed me some money, but I told them I was pretty sure we were square. Eventually I realized that they had recorded the Monday/Tuesday check-in as a Tuesday night stay with an early arrival. They said I had paid twice for one night; but I insisted that I had slept two nights and paid for two nights, and as far as I was concerned that was fair. I also said that if the unexpected blizzard continued, I would be back that night.

Well, the blizzard turned to rain, which made the slush nice and slick. And while my day was very short (only 9.5 hours), I was too tired to risk the roads. Back to Red Roof!

But when I got there, the night clerk had a note from the day clerk: if I showed up, my stay that night was already paid for. I explained why I thought I owed them money; but he insisted that their policies said I had paid for two nights and only used one so far. Finally, I decided that if they were going to insist on letting me sleep three nights for two payments, I wasn't going to argue with them. But I sure plan on telling people what good service they provide.

So if you find yourself stranded late at night in the Kalamazoo Portage area, I highly recommend Red Roof Inn West, conveniently close to Western Michigan University and other local attractions.

Tuesday, April 10, 2007

I'll be there, too!
WM Day of .Net May 19, 2007 - I'll be there!

Will you?
My speaking and other travel schedule (Revised April 10, 2007)
UPDATE: To make it easier to find this entry, I've added a link to it in the right sidebar, right under the links for my books and my classes.

West Michigan .NET User Group in Grand Rapids MI. April 17. Topic: Dee Jay: A Voice-Controlled Juke Box for Windows Vista.

Ann Arbor Day of .NET in Ann Arbor MI. May 5. Topic: Talking with Vista.

West Michigan Day of .NET in Grand Rapids MI. May 5. Topics: Do, Undo, Redo, Do Over: A Generics Command Pattern Implementation; Talking with Vista.

Huntsville New Technology User Group in Huntsville AL. September 11. Topic: Dee Jay: A Voice-Controlled Juke Box for Windows Vista.

Wednesday, February 21, 2007

Generically speaking
I'll be speaking on a .NET generic implementation of Undo, Redo, Scripting, and Logging at GANG tonight.

Sunday, November 12, 2006

Public Service Announcement: Beware of WiFi Evil Twins!
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.

The topic is WiFi Evil Twins. What's a WiFi Evil Twin, you ask? That's when some thief goes to a public WiFi hotspot area and sets up a new 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.

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 this interview with Anne P. Mitchell, Esq. (Professor of Internet Law at Lincoln Law School of San Jose, and the President and CEO of the Institute for Spam and Internet Public Policy) explains:


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.

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.

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).

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?

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.

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.

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."

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.


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 — 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 fourth 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.

So what should I do about it? That's troublesome. From the interview with Ms. Mitchell:


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.

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.


While I'm all for user education — that's why I'm telling you this — I'm not so complacent as Ms. Mitchell about informing the police. Michigan's Attorney General has made fighting Internet crime a priority, 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.

Now back to the subject of user education: here are some things you can do to protect yourself.


  1. When in doubt, don't do it. 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 anything at a WiFi hotspot. Certainly 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 if you don't want to take the time to learn how to protect yourself, then you should never use WiFi.

  2. Always download the latest security updates from Windows Update. 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.

  3. Turn on your Windows firewall.

  4. Download and install Windows Defender.

  5. Install a good antivirus/Internet security package, such as McAfee or Symantec, and keep it up to date.

  6. Install a spyware blocker like Ad-Aware or Spybot. 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.

  7. 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.

  8. Change your WiFi settings to Paranoid (i.e., safe). This will involve several steps:

    1. Open up your network connections by selecting Show All Connections from your Start menu:

      Show all connections

    2. When you see the Network Connections dialog, right-click your wireless connection and select Properties:

      Selecting Wireless Network Properties

    3. You should see the Wireless Network Connection Properties dialog:

      Wireless Network Connection Properties dialog

      Switch to the Wireless Networks tab:

      Wireless Networks tab

    4. Click the Advanced button to open the Advanced wireless settings dialog:

      Advanced wireless settings dialog

      This lets you choose from three different ways to access WiFi networks:


      • Any available network (access point preferred). This means that you will connect either to wirless hubs or to other wireless computers, but you'll prefer wireless hubs.

      • Access point (infrastructure) networks only. This means that you will connect only to wirless hubs.

      • Computer-to-computer (ad-hoc) networks only. This means that you will connect only to other wireless computers.


      Unless you know 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 Access point (infrastructure) networks only. Choose that one unless you're sure you have a reason not to.

      This dialog also has a check box: Automatically connect to non-preferred networks. For added Paranoia, make sure that box isn't checked.

      When you're done in this dialog, click Close. But don't close the Wireless Network Connection Properties dialog. You'll do more work there in the next step.


  9. Next you want to disable automatic connection to all of your WiFi networks, or at least to most of them. Your home network is probably 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:


    1. In the Wireless Network Connection Properties dialog, select the network you would like to change:

      Selecting a WiFi network to convert to manual connection

      After you select the network, click Properties. You should see the Properties dialog for the selected network:

      Properties for the selected wireless network

    2. Select the Connection tab:

      The Connection tab for the selected wireless network

      Uncheck the box that says Connect when this network is in range, and then click OK.

      Repeat this for every wireless network. Then click OK in the Wireless Network Connection Properties dialog as well.



    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 View Available Wireless Networks:

    View Available Wireless Networks

    You'll see the Wireless Network Connection dialog:

    Wireless Network Connection dialog

    Select the network you want to connect to, and click Connect.

  10. 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 both a fee-based service like T-Mobile and 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 — or they're clueless and say, "I don't know anything about the wireless" — assume it's an Evil One.

  11. 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 will keep commiting their crimes. I understand why Ms. Mitchell would inform other patrons that they were at risk. Of course, it takes some chutzpah 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.



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.

UPDATE: My lone commenter and fellow Duelist Epee Bill links to this more serious WiFi vulnerability. 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.

The catch is no one's distributing the fix through typical "push" channels. You have to know about it and go pull it down.

Related Posts (on one page):

  1. Not that there's anything wrong with twins!
  2. Public Service Announcement: Beware of WiFi Evil Twins!

Wednesday, August 2, 2006

Something a little out of joint here...
So I pulled into Pinckney pretty late. I knew my buddy Tom Lavey (of L & M Precision Machine) would be asleep already. So I pulled into Busch's (a popular local grocery chain) to get some dinner. Yes, it was almost midnight; but I've shopped at Busch's at all hours. They're a 24-hour place. Only not, apparently, at some of the more rural locations. This one was closing.

Since I was still hungry, I crossed the street to McDonald's. I really wanted something lighter, but I had missed that chance.

Well, it turns out that the Pinckney McD's is also not 24 hour. Oh, I should've been tipped off by all the McD's workers leaving; but the drive-through menu was still lit up. That's pretty much the universal symbol: "Drive through is still open." So I waited for somebody to take my order. But after last night, I wasn't in a mood to wait very long. I pulled around the building; and mine was the last car in the lot.

Still hungry, and knowing from experience that there would be no food at Tom's, I could only think of one place nearby to get food. I drove out to US-23, where I knew the Shell station would be open. It's not the cheapest place to buy groceries, but it was open. And there across the street was another McDonald's, all lit up and with cars in drive-through. So I pulled over there, and into the drive-through lane. Only there, I saw the opposite universal symbol: the drive-through menu was dark. That means, "You still here? It's over. Go home." But darn, there were cars in the line. So I pulled up; and almost immediately, a guy came on the speaker and took my order. When I got to the window, I asked if they knew the light was out. He said yep, it was burned out.

Somehow, something's just not right tonight...

Friday, July 28, 2006

An exhausting night
So I pulled into the convenience store/Shell station/McDonald's combo. I wanted to get some money out of the ATM and some dinner for the trip home.

So I walked up to the ATM, swiped my card, and told it I wanted to withdraw $100. It said, "Sure!" And then it chugged and chugged and chugged — and suddenly, it said, "Withdrawal amount altered. Read receipt." And it dispensed $80. I said, "Wait a minute, I know I have more than that in there." And I checked the receipt, and it showed plenty of funds still in my account. But then I looked at the ATM screen; and in big red letters, it said, "OUT OF SERVICE. CONTACT ATTENDANT." So I did as I was told.

Then I went to the mini-McDonald's. These don't have the full menu. This one, for example, had 10 piece chicken McNuggets and 20 piece, but no 6 piece like a regular McD's has. So I ordered the 10 piece, figuring I was hungry enough for that. Then I took my cup and went over to get my drink. And when I came back to the counter, the manager said, "Sir, I'm afraid we're short three nuggets for your order. Would you like a cheeseburger to fill out the order?"

I decided maybe it was a good thing I didn't need to gas up the car, or I might have caused a local energy crisis.


Monday, July 17, 2006

So your laptop has been stolen. The next question is...
...how recent is your latest backup?

Were I in that unfortunate position, I can now answer, "Last night." Can you?

This post is in honor of Duane, who made a great sacrifice to provide the rest of us with an object lesson...
Posted in Travel by Martin L. Shoemaker on Monday July 17, 2006 at 8:55am. 4 Comments 0 Trackbacks

Sunday, June 18, 2006

My Old Kentucky Home
Well, not really. The Kentucky Derby was a month and a half ago. But I did get out to Churchill Downs today while I was in Lousville for a Tablet PC class. I figured if I got that close and didn't get some photos for Sandy, I was a fool. You just shouldn't pass up opportunities like that. And besides, our anniversary is only a week away, and this was a shopping opportunity I wouldn't normally have.

I hoped to get on the road early, and the Kentucky Derby Museum opens at 9 a.m. The races today didn't start until 1:15, and I wanted to be long gone by then. But I decided to sleep in, and then had to check out, and then had to take care of some FAXing and mailing before I hit the road. By the time I reached Churchill Downs, it was the start of the first race. So I decided to see more than the museum. Again, you just shouldn't pass up opportunities like that.

Here are some photos of my Churchill Downs experience.

Some enterprising locals tried to sell me parking at $5 per day on their street, but I found free parking at the Downs. But it was a bit of a walk on a hot Kentucky afternoon.

The Stands from my Parking Spot

Finally, I got up near the stands.

Approaching the Stands

I really like the architecture of the back side of the stands. It's a nice blend of function and style.

Behind the Stands

Behind the Stands

Here's a plaque, commemorating the Derby:

Derby Plaque


KENTUCKY DERBY


Referred to as "The Run for the Roses," the first Kentucky Derby was run on this track, May 17, 1875. Black jockey Oliver Lewis rode H. P. McGrath's Aristides to victory. The 1 1/4 mi. race for three-year-old Thoroughbreds is the oldest continuously run stakes race in America, "greatest two minutes in sports," and the first jewel in racing's Triple Crown.


This statue stands behind the plaque shown above.

Derby Statue

From this angle, the horse statue appears to me to be laughing.

Horse Statue Laughing

Anyone who thinks horses have no humor has never met a horse. Every horse person has been laughed at by a horse who slipped away or otherwise eluded them on a fine sunny day when the horse would rather play games than ride.

Finally, some real live horses!

Schooling Stalls

Another thing every horse person knows is that horses are skittish. They're very easily spooked by the unfamiliar. After all, they evolved as a prey species, and they evolved one of the classic prey survival strategies: run like the wind at the first sign of trouble. Sandy likes to tell how a horse can spook at a blade of grass that the horse has passed every day for a month, simply because the grass moved funny that day. So it's important to familiarize horses with new situations before you put them under stress in those situations. These Schooling Stalls are places where trainers bring young horses on race day, simply so the horses can get used to the crowds and the track and the whole experience.

Schooling Stalls

And yes, I was sure to ask permission before I snapped these pictures. I didn't want to interfere with a training regimen.

Schooling Stalls

Schooling Stalls

Schooling Stalls

Schooling Stalls

This is the tunnel that leads from the horse barns to the track.

Tunnel to the Track

The pedestrian path crosses the horse path; but when horses are coming through, a gatekeeper (the gentleman in the vest and hat) closes off the gates. Note that the riders in this picture aren't wearing any colors. That's because these horses aren't racing today, either. They're more horses-in-training, getting used to the experience of riding onto the track and back under tack.

Here was my first look at the track itself.

First Look at the Track

I was amazed both at how close to the track they let you get, and at how many open seats there were right at the front. Only later did I realize that:


  1. The seats right out front are out in the bright sunlight. It gets hot out there.

  2. You can't see the whole track from those seats, only the home stretch.



The shaded seats higher up are much more popular. But since I was there to get horse pictures for Sandy, that was fine with me. The closer, the better!

This tower-like structure sits right in the center of the oval track.

Center Tower

Here are yet more horses-in-training, being walked out to the starting gate and back to get used to a track surrounded by people.

Horse on Walkout

Horse on Walkout

Horse on Walkout

A lot of the horses were walked out before I got there. Here they're starting to walk back.

Horse on Track

Horses on Track

Horse on Track

Horses on Track

Horses on Track

Horse on Track

Horses on Track

Horses on Track

Horse on Track

Horses on Track

Horse on Track

Horses on Track

Horse on Track

Horse on Track

Horses on Track

Horses on Track

Horses on Track

Yes, that's a lot of horse pictures. Why do you think I was there?

And here's one of the student horses we last saw in the tunnel, now riding the track. They all gathered near the tunnel entry, and some rode out to the starting gate and back.

Student Horse

Student Horse

Student Horse

Student Horses

Student Horses

Student Horses

Student Horses

Student Horses

Student Horses

Student Horses

Student Horses

Student Horses

Now we see some colors: the competitors are entering the track. Here horse number 1 seems to be conferring with the student horses.

Number 1 with the Students

Horse number 3 emerges from the tunnel.

Number 3

I figured I couldn't get the whole Churchill Downs experience without placing a bet. But there were some problems with this plan:


  1. I don't believe in gambling. It's not a moral thing, or anything like that; I just know that really smart statisticians and accountants are paid very well to make sure the house wins. I know that if you look at gambling as anything but recreation, you're in for a big disappointment.

  2. I'll change that opinion slightly, however, in contests where individual skill can come into play. Face-to-face poker, for example, isn't gambling in the hands of a skilled player. And for those who really know the horses and the tracks, I'll concede that horse racing may not be gambling.

  3. But I'm not one of those people who knows the horses and the tracks. Heck, I barely know most of our horses.



So any bet I placed was guaranteed to lose. Just guaranteed, unless just random chance played a factor. How then to make the bet interesting? Well, I could've picked the favorite, and that would be the safe bet. But it wouldn't have been a fun bet. No, if I wanted a fun bet, there was only one way to go: bet on the longest shot in the race. And that was number 6, Angel Love, whose odds were 22-1 when I placed my bet. Here Angel emerges from the tunnel.

Angel Emerges from the Tunnel

Horse number 7 enters the track.

Number 7

Horse number 8 prepares for the race.

Preparing for the Race.jpg

The competitors head to the starting gate.

Heading to the Gate

And there goes Angel!

Angel Love

And they're off!

In the Back Stretch

And as the center field monitor shows, Angel Love held a strong second place all the way into the back stretch. Not bad for a horse whose odds have climbed to 65-1, eh?

And here they come around the final turn.

Around the Final Turn

Angel Love has fallen back to third place. That would still pay an impressive $1,275 on a $2 bet; and on my $10 bet, well, you can understand how someone might get excited by this sport, right?

But no, Angel Love doesn't have what it takes for the long haul, and finishes sixth. Still, it was exciting there for a minute or so.

Oh, well, off to the museum. The entry is a set of starting gates.

Museum Entrance

Here's a statue of a horse with the blanket of roses.

Roses

Here's a display of Derby cups.

Cups

Here's a display of silks (i.e., uniforms) worn by Derby jockeys.

Silks

A display on the ideal conformation of a Thoroughbred.

Conformation

Note the correct spelling: conformation. This is often misspelled as "confirmation", as if a show judge is confirming that the horse looks good. (The same term and the same misspelling also occur in dog shows.) What the judge is actually assessing is whether the horse correctly conforms to ideal standards for the breed.

A display of the grain that a yearling might eat in one day of training.

Grains

Common training equipment.

Training Equipment

Model of a horse barn.

Barn Model

I wish I could build Sandy a barn like that; and if I did, she'd find the horses to fill it.

An example of a saddle and tack.

Saddle and Tack

Man, those are light, tiny saddles!

A display on jockeys as athletes.

Jockey as Athlete

Without even reading it, I can tell you what it says: that jockeys use more and different muscle groups than any other sport, and that jockeys are uniquely fit compared to other athletes. How do I know it says that? Because that's what devotees say about every sport I've ever looked into: fencing, swimming, soccer, martial arts, you name it. They can't all be the most fit, of course. Maybe bowlers and archers don't try to sell this line, but it seems like every other kind of athlete does.

A display of common veterinarian tools.

Veterinarian Tools

A display of common farrier tools.

Farrier Tools

A display of common grooming tools.

Groom Tools

This little mechanical ride lets you experience trying to stay in the stirrups on a moving horse for the duration of a Derby.

Ride in the Derby

No, I didn't try it.

I thought Sandy would like this horse banner.

Horse Banner

The museum has more than its share of stubby-legged horses. It seems kinda sick to me...

Pat Day Exercise Horse

This one is Pat Day's exercise horse. Pat Day, for those who don't recognize the name (like me), is a Hall of Fame jockey. I can't really tell if he's that much better or more famous than other jockeys, except for one thing: he's the only one with his own walk-through room at the Kentucky Derby Museum (including a Pat Day cut-out that you can stand with to get your picture taken). I assume that means he's a pretty big thing among jockeys.

And apparently, exercise horses are big business.

A harness racing cart. I didn't know they did harness racing at the Downs.

Cart

A starting gate display, complete with a mock horse in the gate.

Starting Gate

In the Gate

Note: yet another stubby-legged horse...

Yes, folks, there really is an International Horeshoeing Hall of Fame.

International Horeshoeing Hall of Fame

It's about the size of a walk-in closet, and it's on the second floor of the museum.

Famous Farriers

But just because it's small, doesn't mean it's not serious. A thrown shoe can cripple a very expensive race horse and end its career. Bad feet can be lethal for a horse. The very wealthy owners have great respect for good farriers.

And if you think the farriers get a tiny space, well, the veterinarians get only a wall — inside the International Horeshoeing Hall of Fame.

Famous Vets

Still, their names are up there.

These banners of past Derby winners hang over a multimedia theater on the first floor.

Banners

Like many another city, Louisville has done the giant animal art craze; and of course, in Louisville the animal chosen was horses. (I guess the horses aren't giant; but some city, I forget which one, was infested with giant rabbits.) This piece, called "Aristides" after the first Derby winner, is painted with a wrap-around scene of Churchill Downs itself. I thought that was pretty clever.

Colorful Horse Statue

Finally, it was time to hit the road.

Everybody Remember Where We Parked

Every time I see a sea of cars like this, I'm reminded of what the great man once said: "Everybody remember where we parked."

Friday, March 24, 2006

Boston, here I come!
It's a little late to announce this — particularly since the class is full — but it's worth mentioning for future reference. The Richard Hale Shaw Group is presenting our Visual Studio Team System class at the Microsoft Technology Center in Waltham, MA, with me as lead instructor.

We're also trying to find another chance for me to present Ink in 60 Seconds while I'm there.

Sunday, March 19, 2006

Hamburger WHAT?
So while I was in Montreal, two different restaurant menus that I saw listed an item called "Hamburger Michigan". Now I have to tell you: I've lived in Michigan all my life; and as far as I know, there's nothing unusual about how we serve hamburgers here.

So I was curious; but other things on the menu tempted me. I didn't want to end up with either a plain hamburger or something unrecognizable. So instead, I had a gyro platter from Kostas Souvlakis for Wednesday dinner, and a smoked meat sandwich (another popular menu item) at Orly's Restaurant (can't find a Web site for that one). The gyro was one of the finest I've ever had (so good that I called them back to offer my compliments to the chef, and I've never done that before), and the smoked meat was tasty; so I don't mind my choices. But that still left me curious.

And a Web search left me even more curious, because a search for "Hamburger Michigan" turns up incredibly few hits. A Google search for the exact phrase turns up only 71 hits. (Of course, that will be 72 when Google gets around to indexing this entry.) And most of the ones that it does turn up are restaurant menus. Most of those in French. Most of those from restaurants in Montreal. And none of them define what Hamburger Michigan is. It must be one of those things that if you're from Montreal, you just know, and nobody need bother to explain (I'll bet he would know); and if you're not from Montreal, you would never have heard of it, and so you would never think to ask.

The best possible answer that I found came from all the way down on the third page of the Google search. It led me to an entry on Cooks.com. Now the entry had moved over time; but a search on Cooks.com led to these entries for "Michigan Sauce". They all seem to be recipes for what sound like sloppy-joe-like sauces of tomato paste and crumbled hamburger, to be served on hamburgers or hotdogs. (Meat sauce on meat. Go figure...)

I also found a comment thread somewhere (but now I can't find it again, naturally) where people discussed Michigan Sauce and traded recipes on it. No one there seemed to know why it might be called that.

So I'm at a loss. Is this what they mean by Hamburger Michigan? I guess I'll have to go back to Montreal to find out. Why have I lived 43 years in Michigan and never even heard of it before now? And why is it called that? That may be one of those rare answers that just isn't to be found on the Web.
A geek pilgrimage
And while I was in Montreal, I was in fact presenting right on the very edge of McGill University. The Microsoft office there is in fact only a block away from the University on Avenue McGill College. So I was rather amused to be presenting there.

What's that? You mean you've never heard of McGill University? What sort of a geek are you? Don't you recognize the alma mater of one of the icons of the geek world? Doesn't everyone know where he went to school? Well, OK, I didn't until the Biography Channel ran an episode on him, which included a cross-country bus ride to McGill. That was shortly after he won his first Emmy. First, meaning he won another one. Some people say, "I don't mind. They're not laughing at me, they're laughing with me." Other people say, "You're a fool. They're not laughing with you, they're laughing at you." He seems to be saying, "Let them laugh, as long as I get to work. And I'll have the last laugh, all the way to the bank." He has made a third (or is it fourth? or fifth?) career out of mocking himself the way his critics have mocked him in the past; and he's still working, while many of them are still going nowhere. Or as the man himself says:


I've heard of you
The ready-made connecting with the ever-ready
Yeah
The never was talking about still trying
I got it
Forever bitter gossiping about never say die
May I inquire what you've been doing mister?
Jack
Never done Jack
And you partner, what's the News of the World, Dick?
I don't say dick
Don, of all the people you must be the Tattler
Two thumbs up
What are you afraid of?
Failure?
So am I
Has been implies failure
Not so
Has been is history
Has been was
Has been might again


I can only hope that at his age I can still be working in my field and having a ball doing it. And if people laugh at me, I hope I have the grace to laugh along and the wits to turn it into an opportunity.

Unfortunately, my pilgrimage wasn't quite complete. I didn't make it to this place. Oh, well. The name's not official, anyway. McGill just calls it the University Centre. But I have to believe he finds it more amusing this way.
Bonjour, Montreal!
This is a little late, because I've been doing post travel stuff, and then getting ready for the new VSTS class coming up. To the fine folks in Montreal, I say: Pardonnez-moi, svp, mes amis!

So on Wednesday night in Montreal, I gave my presentation to GUMSNET: Ink in 60 Seconds. Despite my rather hideous attempt to apologize in French for not being able to speak French, they were most gracious hosts. (And darn it! I rehearsed that apology over a dozen times on the trip, until I had it down pat; and then I fell apart when I actually had to give it. Here's what I meant to say: Bon soir, monsieurs! Mon nom est Martin L. Shoemaker, et je ne comprends pas le français. Pardon, si vous plais. Je suis un debutante en français. Mais mon Tablet PC comprend le français!)

I got caught in a lot of Montreal traffic, and also had to fight to find parking in Centre-ville, so I was just a bit late. And then my machine had to reboot. But we finally got rolling, and I started writing little Tablet PC demos, with a 60 second clock running. There were occasional laughs at my expense when I missed the 60 second mark; but on the other hand, many of the demos were done in under 30 seconds. The Tablet PC API is just that powerful. By the time we were done, we were drawing pictures, editing them, erasing them, saving them, loading them, and exporting them as images. We were also drawing shapes that the Tablet PC recognized and identified. We were converting handwriting to text, in both English and French. And we even wrote some text by hand and then had the Tablet PC speak it out loud. We finished with ten ideas for great Tablet PC apps just waiting to be written. I hope that I inspired someone in the audience to go write one.

There was one hang-up in the presentation; and I promised the good folks from GUMSNET that I would blog about it, including what I learned afterward. Late in the presentation — right about the time I tried to do handwriting recognition, when I needed really good ink collection — my wonderful Gateway CX200X Tablet PC started exhibiting dead spots that were strangely reminiscent of the bad old days of Toshiba. The dead zones weren't as consistent, but they were irritating. And they always seemed to be right where I was writing text en français to try to show off the multi-lingual power of the Tablet PC. The audience was forgiving for this, but they did insist on knowing the answer when I learned it. Well, here's what I think I have learned. I noticed that the pen seemed to behave better when I held it at different angles; and then I remembered that when we broke for dinner, I dropped the pen. And as far as I can recall, there were no dead zones before the break, only after. I suspected that maybe I had jammed something in the pen tip; and with a little experimentation, I found that rotating the pen around its axis or relative to the screen could sometimes make the dead zone go away. Suspecting a pen problem rather than a screen problem, I pulled out my spare pen. And I have had no dead zone problems since.

All in all, Montreal was a delightful place to visit, and I hope to return some day when I have a little more time to visit. And the folks at GUMSNET were a great audience. I ran about 40 minutes over time (gee, there's a surprise); and they were all alert and attentive right to the end. We would probably have stayed longer, but the Microsoft employee who was keeping the facility open for us wanted to go home!

Of course, Richard would have my hide if I didn't mention that Ink in 60 Seconds is the opening segment of our Tablet PC Programming Workshop, where you can learn all this and much, much more about building your own Tablet PC applications. In the class, you won't just watch: you'll build a full-featured Tablet PC application yourself, and learn the Tablet PC from the inside. I hope we'll be adding a public Tablet PC class to our schedule first, but you can always bring us to your site.

Monday, March 13, 2006

Ink in 60 Seconds
So why aren't you writing Tablet PC applications with .NET yet?

Do you think it's too difficult? Do you think you're too busy to learn the Tablet PC API? Well, I say you're wrong.

Or do you just not see what sort of Tablet PC app you might build? Do you think that there's no great Tablet PC applications out there for you? Well, I say you're wrong again.

And I'm so sure you're wrong, I'm going to prove it to you at the Groupe d'utilisateurs de l'archutecture Microsft .Net de Montreal by building some simple little Tablet PC samples — samples you can easily adapt into your own applications — each written in under 60 seconds. (Note: In order to meet that time limit, I'll be writing these in C#, the language I know best. Every single one of these demos could be written in 60 seconds in VB.NET, but only by a better VB programmer than me!)

Then after each sample is running, I'll explain to you what I did, how I did it, and how you might expand on it. Some of the samples I'll build include:


  • 60 Seconds to Ink: Capturing Ink in a window in your application.

  • 60 Seconds to Ink Anywhere: Capturing Ink in any window in your application.

  • 60 Seconds to Programmatic Ink: Adding Strokes programmatically to an Ink surface.

  • 60 Seconds to Saving Ink: Saving your drawings.

  • 60 Seconds to Loading Ink: Loading your drawings.

  • 60 Seconds to Saving Some Ink: Saving part of a drawing.

  • 60 Seconds to Loading Some Ink: Loading a drawing into an existing drawing.

  • 60 Seconds to Exporting Ink: Savinging your drawings as images you can share with non-Tablet PC users.

  • 60 Seconds to Selecting, Moving, and Resizing: Manipulating the Ink that you draw.

  • 60 Seconds to Erasing: Erasing the Ink that you draw.

  • 60 Seconds to Drawing Attributes: Drawing with multiple colors, transparent Ink, and different shapes and sizes of pens.

  • 60 Seconds to Clipboarding: Really simple Ink clipboard functionality — and why it doesn't work!

  • 60 Seconds to Simple Handwriting Recognition: Simple handwriting in a form.

  • 60 Secondes au Français: Identification d'écriture en français.

  • 60 Seconds to More Handwriting Recognition: Handwriting recognition mixed with typing.

  • 60 Seconds to Handwriting Recognition Anywhere: Handwriting recognition from any Ink surface.

  • 60 Secondes à Plus Français: Plus d'identification d'écriture en français.

  • 60 Seconds to Text-to-Speech: A simple talking application.



And just in case those samples don't inspire you to devise a great new Tablet PC application, I'll finish the presentation by spending 60 seconds (probably more) describing each of ten different killer Tablet PC applications that I'm just too busy to write myself, but which I think somebody should be writing.

So fasten your seat belts. This is gonna be one heck of a fast ride!

And no, I'm not doing this talk just for the free pizza from INETA and the free trip to Montreal. I certainly hope that some of the attendees are so excited that they'll want to take our Tablet PC Programming workshop, where we'll go places you just can't reach in 60 seconds.

Friday, February 3, 2006

Realization slowly dawns...
So I was somewhat surprised that I didn't get a First Class upgrade on either of my flights today. Not that I'm guaranteed an upgrade, or anything; but usually I get them on about two out of three flights since attaining NWA Gold status. Oh, well...

Then I get to the airport in Seattle, and I notice that it's really, really crowded. And slowly it dawns on me...

What has been the big topic on the radio here in Seattle all week? The Superbowl.

Why has it been the big topic? Because Seattle is playing in it.

When is it? This weekend.

Why was it the big topic on the radio all last week in Michigan? Because it's in Detroit this year.

What's the big airline with hubs in Seattle, Minneapolis (where I'm stopping), and Detroit? NWA.

Am I going to have incredibly crowded flights and airports all day? Yep.

Do most of these people have any clue at all how to make the security and check in procedures go smoothly and efficiently? Nope, none at all.

Is my day going to be nothing but hassle? Probably...

Monday, January 30, 2006

What a long, strange trip
iPaq Power Connector

The item pictured above is an iPaq Power Connector. The power adapter plugs into the synch cradle, and then I plug the iPaq into the synch cradle to recharge the batteries. With the iPaq Power Connector, I can plug the power directly into the iPaq, skipping the cradle. The iPaq Power Connector has a little rubber loop that fixes it to the power adapter cable; but it's flexible, and detachable.

Earlier this month, as I wrapped up the power connector, I felt some resistance. I tugged on it, and it came free from whatever it was caught on; but when it did, the iPaq Power Connector was gone. I looked under the bed, under the backpack, under the power strip, and under every other thing I could see that might have both caught and concealed the iPaq Power Connector. No luck. It was gone.

So ever since, everywhere I've taken my iPaq, I've had to also take the synch cradle if I've wanted to be able to recharge my phone. I stuck it in my backpack, and I took it everywhere: to Kinko's multiple times, to McDonald's and various other restaurants, to friends' houses, you name it. Even on a flight from Grand Rapids to Yonkers and back by way of Detroit. Everywhere I went, I had the synch cradle in my backpack, which wasn't exactly convenient: it's an odd shape and size, and makes it harder to fit the backpack into tight places like under airline seats. But especially on business trips of multiple days, I have to be able to recharge the phone.

This latest trip to San Francisco started with a stop in Minneapolis. And Saturday travel is pretty light, so NWA uses smaller planes where they can. This time, the plane was a small one with very limited overhead luggage space. The gate agent strongly insisted on doing gate checks for all luggage. Actually, the backpack could've fit under the seat just fine — even with that bulky synch cradle in it — but I didn't know that. So against all my usual habits, I let the gate agent tag the backpack; and then when I got to the plane, I put it on the cart for checking. I figured it was only an hour flight, and I could be without my CX200X for that long. Besides, I had some new reading to keep me occupied.

So when I got to Minneapolis, I rushed to the gate check pickup shelf. Just because I gave the machine up didn't mean I was comfortable with it sitting on a shelf where anyone could pick it up. But thanks to some slow passengers, "rushed" wasn't quite the right word. By the time I got to the shelf, my backpack was the last piece of luggage there.

And on the floor, right below where my backpack lay, was... my iPaq Power Connector.

I can't even fathom the odds...

Thursday, December 15, 2005

More from KSC
Here are more photos from my visit to the Kennedy Space Center. This visit coincided with my completion of Apollo, so my whole brain was prepped for the experience.

Here's a peek at the Rocket Garden as you approach the Visitor Center:

KSC Visitor Center

If you want to take one of the special tours (NASA Up-Close and Cape Canaveral: Then & Now), you're strongly encouraged to make reservations in advance. I made a reservation for NASA Up Close; and thanks to some navigation difficulties (I programmed my Hertz Never-Lost for the KSC Federal Credit Union, not KSC itself), I arrived just in time to start the tour. Our guide for the day was Don Garretson:

Our guide, Don Garretson

Don started his career in the oil business, specializing in fluid flows, gas detection, and related instrumentation. That led him to a job with the KSC engineering staff working on gas detection, containment, and transfer during construction of various facilities such as the ISS preparation buildings. Once those facilities were complete, NASA cut back on contract engineers in those areas. So Don found a job as a KSC tour guide. He's very knowledgeable and personable, and provides a great tour.

There was one down side to the tour:

NASA Bus

I have mentioned on other occasions how much I loathe buses. Well, for this tour, I just had to put up with the bus.

For reference on the tour, here's a map of KSC (from this site):

KSC Map

As we pulled out of the Visitor Center, Don pointed out this:

VAB from 5 miles out

That building you see there is the Vehicle Assembly Building, or more commonly known as just the VAB. As Don pointed out, it only looks small in this picture because of how far away it is: 5 miles. It's actually the third-largest building in the USA by volume, and has the tallest single storey anywhere. We'll see a lot more of the VAB in later photos.

Don also pointed out some other buildings. Here's the KSC Headquarters:

KSC Headquarters

And here are some shots of the Operations and Checkout building (O&C), where spacrecraft modules are checked out before assembly, and where astronauts stay immediately before and after a flight:

O&C Building

O&C Back Side

O&C Door to Nowhere

If you look closely at the second storey of that last shot, you'll see the Door to Nowhere: a door with no stairs leading up to it. Beyond that door is the O&C clinic. After a lengthy Shuttle mission or especially an ISS mission, astronauts sometimes are in no shape to walk. They may have trouble with balance, or they may have weakened muscles and bones. The carrier that takes them from the Shuttle landing strip to the O&C is designed to lift stretchers straight up to the Door to Nowhere and into the clinic without the astronauts ever having to get up.

Our first stop on the tour was a viewing stand where visitors can sit on bleachers and look across the water to various prep launch facilities:

Launch facilities

The left-most building is devoted to a new approach. In the traditional prep-and-launch, the rocket and its payload (collectively known as "the stack" are assembled in a building and the slowly, carefully hauled out to a launch platform. In this new facility, the stack is assembled, and then the building is moved away. The stack remains motionless, so there's no chance of anything being dislodged in transit. As Don explained it, this can reduce prep time from months to hours.

Here's a shot of the VAB from the same bleachers:

VAB from shore

Our next stop was a preparation center for elements of the International Space Station (ISS). We couldn't photograph the modules themselves, not for security reasons, but rather to avoid a hazard: the fire suppression systems in the prep rooms might interpret camera flashes as a fire, and then drench and ruin a lot of very expensive equipment. While we were there, they were preparing the three cargo modules used to haul supplies to the ISS and haul garbage back. These are named Leonardo, Raphael, and Donatello — no, not for the Ninja Turtels, for the Italian painters. The cargo modules are made by Italy as part of their contribution to the ISS. Don told the story of how, when Raphael first came down with a load of garbage, the stench was so bad that the workers refused to go in. After sealing it up with charcoal pellets for a week, it was finally tolerable, and they could finish the clean-up.

While the ISS components could not be photographed, the ISS center included a visitor center with models and mock-ups. Here's an ISS spacesuit:

ISS Suit

Here's a model of Skylab, the first space station:

Skylab model

And here's a model of Mir, the second space station.

Mir model

And finally, here's a model of the ISS itself:

ISS Model

Here's a model of Canada's contribution: a robotic arm used for moving modules and cargo containers. I'm not sure this name is official, but I've heard it called the Canadarm:

Canadarm

Here's a mock-up of one of the Habitat modules:

HAB 1 Module

Inside the Habitat module, here are a restroom, a shower, and a sleeping chamber:

ISS Restroom

ISS Shower

ISS Sleep Chamber

I never figured out what the NOD module was, but here it is:

NOD 1 Module

And inside, you can see that the ISS is a luxury condo as spacecraft go:

ISS Module

(If you don't believe me, jump ahead to the photos of the interiors of the Mercury and Apollo capsules.)

I didn't get an exterior shot of the Lab module (and frankly, they all look kinda the same from outside); but here's the gasmap, one of the experiments in the Lab:

Gasmap experiment

Next, the bus took us on a drive around the VAB:

VAB

Now the word for the VAB is big; but no picture can possibly convey just how big it is. To try to give you some hint of the size: each stripe in that flag on the side is wider than the bus we were riding.

Here are the big doors used for taking spacecraft out for launch:

VAB big doors

Again, the word is big. The Statue of Liberty could fit comfortably through those doors. A fully ready Saturn V stack with an Apollo CSM and an escape tower, though, came within 5 feet of the top of the doors.

So how would you move that massive Saturn V stack to the launch pad? That's where the crawler carrier comes in:

Crawler Carrier

The crawler carrier is a massive tracked vehicle with the surface area of a baseball diamond. Moving at a top speed that's about as fast as a leisurely walk, it would haul the Saturn V out, slowly but surely, to the Pad 39 complex. (More on that below.) Today, it serves the same purpose for Space Shuttles, hauling each one out atop the Shuttle launch platform:

Shuttle launch platform

This is much more than a platform: it's really a small building, complete with offices and machine shops. The crawler carrier slides under it, lifts it up, and carries it into the VAB. There a crane lifts the orbiter and the external tank and the booster engines into place, so that workers can attach them. The two pylon-like buildings on top of the platform help stabilize the orbiter's tail.

But before the orbiter can be placed on the launch platform, it has to be prepped in one of the three Shuttle "garages". Here's the door into one:

Shuttle work bay

Notice the door has a notch in the top to allow for the orbiter's tail fin.

Once the orbiter and the tank and the boosters are assembled, the crawler carrier pulls them out along this path:

Crawler path

The two lanes allow for the two sets of treads. The lanes are not gravel, but rather Tennessee River Rock from Alabama. (Hey, it was funny when Don said it!) This rock is chosen because of its small round size and hardness, but especially because it is pretty much immune to sparking under compression. In the Apollo days, sparks might be a problem, but not too big of a problem: the Saturn V engines used liquid fuel (kerosene and liquid oxygen), and were fueled up while on the launch pad. The Shuttle orbiter also uses liquid fuel; but the external boosters are solid fuel rockets. That means that they're fully fueled and ready to ignite as the Shuttle goes down the path. A stray spark at the wrong moment could lead to a fire; and that could lead to a real disaster.

After the VAB, the bus took us out to a photo stand on the Pad 39 complex. There we could see the two launch pads used for the Apollo launches as well as almost every manned NASA launch. (Unmanned rockets usually launch from the Air Force's facilities at Cape Canaveral.) Here's Pad 39A, from which Columbia launched on both her first and last flights:

Pad 39A

And here's Pad 39B, from which Challenger launched on her last flight:

Pad 39B

That shot of Pad 39B was a close-up as we drove past to our next stop, the Space Shuttle landing strip. Further along, we passed the Media Center where reporters and camera crews set up to cover missions:

Media Center

And then we arrived at the Space Shuttle landing strip:

Space Shuttle landing strip

This is another place where a picture just can't capture the immensity. That landing strip is 15,000 feet long, making it one of the largest in the world.

Here's the traffic control tower for the landing strip:

Space Shuttle traffic control

Along the way to our last stop, we passed what looked like a futuristic junk yard:

Testing Grounds

What it actually is is what my buddy Tom Lavey would call a bunch of giant test shims. These pieces of "junk" are actually mock-ups of various fittings and assemblies from the launch pads and elsewhere. When engineers are working on new systems that have to integrate with these fittings and assemblies, they can bring their equipment here and test it on the test fittings first, rather than waiting for time on the actual launch pad and possibly wasting a lot of time. While it may sound funny to think about having the wrong sized parts at launch day, NASA knows it's not funny at all. As Murray and Cox explain in Apollo, the heat shield on the very first Mecury test capsule turned out to be larger than the missile, and had to be carved down to fit, right on the launch pad. It's better to learn that sort of thing before launch day.

Our last stop on the tour was the Saturn V Center. The Saturn V at KSC used to be outside; but when weather began to take its toll, NASA built a special exhibit center and then moved the rocket inside and refurbished it. You enter the Saturn V Center through a small stand-up movie theater which introduces you to the Apollo program. Then from there, you move into the actual Apollo Launch Control room:

Launch Control

There they present a complex multimedia presentation of the last three minutes of an Apollo launch. As recorded voices from the various comm loops play over the speakers, each console is spotlighted when the corresponding voice is on the loops. Meanwhile, screens overhead show video from the various cameras: Launch Control, the launch pad, and elsewhere. The presentation ends with the building-shaking sound of the Saturn V launch. And then the doors open, and they let you in to see the Saturn V itself. We'll start with my traditional rocket butt shot:

Saturn V butt shot

Those five F-1 engines combined to produce 7.5 million pounds of thrust; and yet as powerful as they were, they were also delicately gimballed, so that they could pivot in different directions to control the angle of thrust. Growing up, I would see film of the engines, and I always thought I was only imagining that things that big and powerful were moving; but it was no illusion.

Here's a close-up of the plumbing for one F-1 engine:

F-1 Plumbing

Here's a length-wise view from Stage II forward:

Stage II on up

And here are the five J-2 engines of Stage II, as well as Stage II itself:

Stage II J-2s

Stage II

Here's a length-wise view from Stage III forward:

Stage III and CSM

And here's the single J-2 engine of Stage III, as well as Stage III itself:

Stage III J-2

Stage III

Here's an Instrumentation Unit that sat between two stages and provided cameras and other sensors:

Saturn V Instrumentation Unit

Here's the Service Module:

Service Module

Note the spherical tanks, which I believe contained H2, O2, and water.

Here's the Command Module and the escape tower (the rocket and tower which would fling the Command Module to safety in the case of an emergency before launch or early in the launch):

Command Module and Escape Tower

And here's a length-wise shot from the nose backward:

Saturn V lengthwise

They have a second Command Module and Service Module (collectively, Command and Service Module, or CSM) on the ground beneath the nose of the Saturn V:

CSM

I think that the Command Module here is the actual CM from the Apollo-Soyuz mission:

Command Module (Apollo-Soyuz?)

It's supposed to be at the Saturn V Center, and I didn't see it anywhere else. Also, this CM was sealed in plexiglass, something they usually reserve for actual flight articles:

Command Module through the top hatch

But I didn't see every sign, and I never saw a sign that identified this Command Module, so I can't be certain. (I'll verify this on my next trip.)

Here's another angle on this Command Module:

Command Module at an angle

And here's a rare opportunity, a butt shot of the Service Propulsion System or SPS, the main engine of the CSM:

SPS butt shot

And here's an even more rare butt shot:

LM butt shot

That's the Descent Engine of an actual Lunar Module (or LM, pronounced "LEM"). Not a mock-up or a tester, but a real LM. Most of the real LMs went on missions, and were left in space. Those that went to the Moon left their Descent Stages there, while their Ascent Stages usually were crashed into the Moon to gather seismic data. Other Ascent Stages burned up in the atmosphere. One went into a solar orbit.

But this LM never flew. It was commissioned and built for the Apollo 15 mission; but then they redesigned the LM to carry the Lunar Rover, and this LM no longer fit the spec. And so now it hangs from the ceiling in the Saturn V Center:

LM

Here's a model of a LM in the adapter stage of a Saturn V:

LM in adapter (model)

And speaking of the Lunar Rover, there was one parked near the Saturn V:

Lunar Rover

Lunar Rover front view

And nearby is a replica of an Apollo spacesuit:

Apollo Spacesuit

And near the nose of the Saturn V was the Moon rock I showed in my previous post:

Touching the Moon

Here's a description of the Moon rock:

Mare Basalt details

Also near the nose was this van used to carry the astronauts out to the launch pad:

Astronaut Van

And there was also another multimedia theater which showed movies of the actual landing footage from Apollo 11. And then, at just the right moment, they switched from movies to stage performance, dropping a replica LM down to a simulated Moonscape. It came out of nowhere and was a very effective special effect. Then they showed movies of Armstrong and Aldrin exploring the Moon; and at just the right moment, the replica Ascent Stage took off back into the sky. It was awesome (but not quite authentic: during the actual Apollo 11 ascent, the exhaust from the Ascent Engine actually knocked over the American flag that Armstrong and Aldrin had planted; but it stayed standing in this presentation).

A different bus took us back to the Visitor Center; but before I discuss that, there are a couple of miscellaneous shots from the tour. Don was sure to point out several times that most of KSC (130,000 acres out of 140,000) is a wildlife refuge. In particular, he liked to point out the alligators, from the safety of a moving bus. I wasn't fast enough to get many alligator shots, but this was the best one:

Alligator

And here were some birds:

Birds

Because the waters around KSC are home to manatees, outboard motors are severely restricted; but air boats are common:

Air Boat

Back at the Visitor Center, the first place I went was the Rocket Garden. Here's a Redstone:

Redstone

Here's an Atlas:

Atlas

And here's an Atlas with an Agena rocket attached:

Atlas Agena

Here's a Titan:

Titan

Here's a J-2 engine:

J-2 Engine

And here's an F-1 engine:

F-1 Engine

Here's an actual Saturn V gantry, which took the astronauts from the launch tower to the White Room and then into the Command Module:

Gantry to White Room

You could walk this (safely on the ground) into the White Room and then look inside a Command Module mock-up:

CSM Interior

And here's a Saturn I:

Saturn I

It was held in reserve as a possible lifeboat for Skylab, but was never needed.

After the Rocket Garden, I went to the Exploration in the New Millenium pavillion, where they have exhibits on past, present, and future missions beyond the Moon. Here's a mock-up of the Viking probe on Mars:

Viking model

And here's a mock-up of the Cassini-Huygens probe that explored Saturn:

Cassini-Huygens

After that, I waited for the last Astronaut Encounter of the day. This guy didn't seem too impressed:

Big deal!

"He flew. Big deal. I've been doing that since I left the nest!"

Finally, astronaut John Fabian appeared and spoke to the audience:

Astronaut John Fabian

Colonel Fabian was in Air Force ROTC at Washington State University, and then served as a combat pilot, with 96 missions to his credit. He was a Mission Specialist on STS 7 (Sally Ride's first mission) and STS 51G (where he served alongside Sultan Salman Abdulaziz Al-Saud). After his talk, he posed for photos:

Me and John Fabian

By that point, it was almost closing time, so I missed out on this:

Shuttle mock-up

That's a full-sized Shuttle mock-up, in an area of the Visitor Center that I never got to. But fear not, Shuttle fans! I'll have more photos. I'll be back Saturday, including a reservation for the Cape Canaveral: Then & Now tour. (And if I still haven't got all the photos and info I need, I can spare almost half a day there Sunday.)

But just because KSC was closing didn't mean my day was done. The Astronaut Hall of Fame (just across the bridge to the mainland) stays open 90 minutes later. 90 minutes isn't really enough there, but it's a start. Here's the entrance:

Astronaut Hall of Fame

And here's the dedication:

Hall of Fame dedication

And when you walk in the door, the first thing you see is Alan Shepard, first American in space, cast in bronze:

Alan Shepard in Bronze

And behind that is a tremendously large mural of an astronaut reaching for the stars:

Mural by Alan Bean

But that's not just a mural. The signature at the bottom reads Alan Bean, the fourth man to walk on the Moon. Since his retirement in 1981, Captain Bean has made his career as one of the preeminent space artists in the world.

Beyond the turnstyle, you'll find actual Mission Control consoles from Project Mercury:

Mercury Mission Control consoles

As well as an actual Project Mercury spacesuit:

Mercury spacesuit

But those are just lead-ups to this:

Sigma-7

That's the Sigma-7, the Mercury capsule flown by Wally Schirra. Here's an interior shot:

Mercury Interior

But that's not the only hardware to be found at the Hall of Fame. Here's my main goal for this visit:

Apollo 14

That's the Apollo 14 Command Module, flown by Alan Shepard, Stu Roosa, and Ed Mitchell, completing the mission to the Fra Mauro highlands that was interrupted by the Apollo 13 disaster. Here's an interior shot:

Apollo 14 Interior

And here's a shot of the hatch:

Apollo 14 Hatch

Spacesuits evolved from the Mercury era. This intermediate stage was nicknamed the Grasshopper:

Grasshopper suit

By contrast, this is an exhibit of flight helmets worn by aviators who went on to be Hall of Fame astronauts:

Flight helmets

Well, that's a start. Look for more photos after my return visit Saturday.

Monday, December 12, 2005

Where I'm blogging from...
...Kennedy Space Center. Because I can (T-Mobile willing).

Here's just a quick photo:

Touching the Moon

The hand in the photo is mine (identifiable by my wedding ring). And the black wedge shape I'm touching? That's a Moon rock.

Yes, I touched the Moon today.

(Well, actually, the rock is under a very thin layer of plastic; but that's still close enough for me.) Update: Further research, while not conclusive, indicates that you get to touch the actual rock. It just happens to have a rather smooth surface.

More later.

Thursday, December 8, 2005

Frontiers of Flight
So quite by accident, I ended up visiting the Apollo 13 and Apollo 16 Command Modules. And next week, thanks to an unexpected .NET BootCamp gig in Orlando, I'll get a chance to visit the Kennedy Space Center (where the Apollo-Soyuz Command Module is located) and the United States Astronaut Hall of Fame (where Apollo 14 is located).

And that led me to wonder where the various Command Modules are today; and that led me to this site, which tells where to find all sorts of American spacecraft. And that plus Microsoft MapPoint led me to produce this map (warning: large download):

Apollo Command Modules

The dark blue triangles represent Apollo Command Modules. (Not shown: Apollo 10, found at the Science Museum in London, England.) The light blue triangles represent Apollo Command Modules that I have visited:


  • Apollo 8, at the Museum of Science and Industry in Chicago. I haven't been there in two decades, so I don't have any digital photos to post. But I've seen it.

  • Apollo 9, now at the San Diego Aerospace Museum, but formerly at the now-defunct Michigan Space and Science Center. I used to make side trips there whenever my travels across the state allowed, so that I could gaze on Apollo 9 and remind myself that my job's not rocket science. But again, that was before I had digital photo capability.

  • Apollo 13, at the Cosmosphere in Hutchinson.

  • Apollo 16, at the U.S. Space and Rocket Center in Huntsville.

  • Apollo-Soyuz, at the Kennedy Space Center. Sandy and I went there during one day of our honeymoon. Again, that was long before digital photos. But we were there!



And then I realized: I have visited five out of fifteen Command Modules (sixteen, if you count the test module in Seattle, listed here). And that began to sound suspiciously like a quest: to visit or revisit them all, and get a complete set of photos posted here on my blog.

So imagine my delight when I realized that I was speaking in Dallas this week, and that the Apollo 7 Command Module is located at the Frontiers of Flight Museum at Love Field, a museum dedicated specifically to ground-breaking aircraft that set the course for aircraft to follow. I made sure to squeeze time into my schedule for a visit, so that I could convert one of those triangles from dark blue to light blue. The photos that follow are the results.

Let's start with the star of the show. As you enter, you see Apollo 7 from the rear:

Apollo 7 Back

Then you come around the side, and see the open hatch:

Apollo 7 Side

And then you climb steps for the front view:

Apollo 7

The Apollo 7 Command Module fits the mission of the museum well, since it was the first manned launch of a Command Module. This is also the first Command Module I've seen where it was easy to see the hatch interior:

Apollo 7 Hatch

And of course, there's the obligatory interior shot (behind plexiglass, as always):

Apollo 7 Interior

Apollo 7 was not the only Apollo-era memorabilia at the museum. Here's Don Eisele's spacesuit:

Don Eisele's spacesuit

Here are Charlie Duke's gloves:

Charlie Duke's gloves

In the background, you can also see one of the dread urine collector packs. Here are some other pieces of Apollo gear:

Apollo gear

Here's a pressure chamber used in Skylab to test how astronauts' lower extremities behaved in various pressures and zero gravity:

Skylab pressure chamber

Here's a Skylab exercise bike, used to test how astronauts systems behaved under exertion in space:

Skylab bike

And here's a Skylab Experiment Support cabinet:

Skylab Experiment Support cabinet

From what I could tell, the top part of the cabinet contained slots into which various powered modules could be plugged for various experiments. The bottom part looked like it contained drawers for supplies for the experiments.

Near Apollo 7, they had a very small movie theater showing Apollo footage. That also held a tiny chunk of Moon rock:

Moon rock

And they had a roughly three-foot model of a LM:

LM model

I'm so jealous!

Near the theater, they had exhibits from Beal Aerospace's new developments in lifting vehicles and engines, many of which are being manufactured or tested in the area. Here'a a scale model of the BA-2 launch vehicle:

Beal BA-2 model

And here's a (large) description:

Beal BA-2 description

Here's a combustion chamber and nozzle from one of their BA-810 engines:

BA-810 Combustion Chamber

And here's a (large) description of the engine:

BA-810 Description

And here's part of their PR material (again, large):

Beal Pitch

Near the Beal display is a Regulus II cruise missile:

Regulus II

I don't think I ever realized how large a cruise missile is, nor how much like an airplane it is. I guess that's the point: rather than following a ballistic arc, it cruises to the target like a plane.

And in keeping with my tradition ("Always include a butt shot of the rocket"), here's a butt shot of the Regulus II:

Regulus II engine

Here's a Huey helicopter:

Huey

And here's an F-16 fighter, famed for still today beating aircraft that are 30 years newer:

F-16

An Airman I know works on the explosive ejection seat mechanisms for fighters. He should appreciate this history of ejection seats:

Ejection Seats 1

Ejection Seats 2

Ejection Seats 3

Ejection Seats 4

Ejection Seats 5

Here's an A-7 Corsair II:

A-7 Corsair II

Here's a Crusader RF-G:

Crusader RF-G

And here's some plane:

Some plane

And here's some other plane (I think it might've been the "Sopwith Pup"):

Some other plane

There were more details about those last two planes, and a lot of other exhibits as well; but my camera batteries were failing. And besides, I wanted to get back to my hotel and off the roads. Dallas was starting to do this:

Crunch!

Man, a little glare ice all over the place, and these Texans just forget how to drive...

Update: I'm a little disappointed. I've visited Atlanta, Cleveland, Dayton, Seattle, and the Pensacola region, and I never realized there were command modules nearby. Those could have put me up to eleven, twelve after next week. I'll have to try to correct those mistakes.

And I have no idea how I'll find an excuse to get to London...

Wednesday, December 7, 2005

More excellent customer service (really!)
Of course, the down side to the travel arrangements that Justin made for me was that I was traveling:


  1. One way.

  2. On extremely short notice.

  3. With no checked luggage.

  4. On a ticket paid for with somebody else's credit card.



And naturally, somewhere in there I won the TSA lottery: my boarding pass was marked with the magic symbols that mean "Give this guy a full screen."

Now as I wrote before, I take airport security seriously. I know it's common for people to grumble about TSA's screening, especially the random screenings. But I support the screening process, including the random screenings: if you only screen according to a set of rules, that creates a pattern that terrorists can discover and exploit. Random screenings mean that any attempt at discovering such a pattern can be discovered. Plus I put myself through college working as a security guard, and I know how hard that job can be for those who are conscientious about their work. So I'm not going to complain about being selected for screening, especially when my travel circumstances probably did fit a risk profile.

But still, there's not complaining; and then there's being impressed by how professional the screeners are. Back in the 2002-2003 time frame, screening was much more frequent, and I could expect extra screening almost one trip out of five. Then the screening rate dropped. This was probably the first time I've been the subject of extra screening since 2003.

And the process has changed. As I said, it's professional. No, I think an even better word might be polished. The TSA screeners at SEA-TAC were polite, efficient, patient, professional, and polished. They explained what was happening, and they explained the process in full before they proceeded. They let me choose how much privacy I wanted. They were careful with all of my belongings. They were as unintrusive as they could be while still doing a thorough screening job. And with me on a relatively short schedule, they held me up for only as long as it took to clear my stuff and my person. As a former security guard, I was very impressed with how these folks did their job effectively and still managed to be considerate toward the public.

Because of my tight schedule, I didn't get their names or badge numbers. I regret that, because I would like to commend them by name to their supervisors. There's another lesson from my days as a guard: everyone complains if you slip up, but no one seems to notice if you do your job well. Well, this passenger noticed; and I thank those TSA screeners for making travel safer and still making it as pleasant as possible.

Related Posts (on one page):

  1. More excellent customer service (really!)
  2. And speaking of good customer service
And speaking of good customer service
I wake up. Check the clock. 6:10 a.m. OK, I'm in Seattle. That means it's really 3:10 a.m., since I never change the time zone on my computer. My flight is set for 6:00 a.m., and I requested a 3:30 a.m. wake-up call from the hotel. I guess I might as well get up now, since I have to get ready to leave.

Wait a minute. I didn't get the time from my computer. I got it from the TV. Which is on Pacific time. Just like my flight.

Which left Seattle ten minutes ago.

Oh, crap. I call the front desk. They have no record of my wake-up call being requested.

Yes, I was angry. I'm human, after all. I had to get home for a my nephew's Eagle Scout award and for a family funeral. This was not helping.

But then I remembered: the hotel staff are human, too. And getting mad won't do anything to make it better.

Here's my message to companies that want my business: I don't expect you to be any more perfect than me (which isn't a very high bar); but when you make a mistake, I expect you to make it right, just as I would hope that I would do in your shoes.

And that's just exactly what Justin Gaston, Operations Manager for the Bellevue Redmond Courtyard, did. His staff immediately offered me a free breakfast (for which I had no time, but the offer still was nice); and Justin personally got on the phone, called the airline, and arranged a new flight home for me, all at no charge to me. Justin was polite, helpful, apologetic, and sympathetic; and he absolutely did right by me.

Yes, I got to DTW eleven hours later than scheduled. Yes, the hour was then so late and the weather so bad that I had to spend the night in a hotel near DTW. Yes, I got home over a day late, by the time all was said and done. Yes, the world's an imperfect place. Nothing's perfect.

But the service that Justin and his staff provided and the efforts they did to correct their mistake came pretty darn close to perfect.

If you'll be in the Redmond area, I strongly encourage you to patronize the Bellevue Redmond Courtyard, 14615 NE 29th Place, Bellevue, WA 98007 (Ph: 425-869-5300). They have reasonable rates and fine rooms, with free high speed Internet access. They're conveniently right across the highway from Microsoft's main campus if you have business there. And they have a staff that should make the Marriott chain proud.

Related Posts (on one page):

  1. More excellent customer service (really!)
  2. And speaking of good customer service

Saturday, November 19, 2005

In Kansas?!?!?!?
So in order to keep my flight costs down (long story), I was stranded in Wichita through Sunday after my talk at Wichita Developers .NET. So I turned to 360Wichita for things to do; and what I found was the Cosmosphere in Hutchinson, Kansas: one of the finest space museums I've ever seen.

In Kansas?!?!?!?

Well, at least they have a sense of humor about it. Rather than be offended by that question, they actually printed up a small handout called "Why Hutch?" In it, they explain how Patricia Brooks Carey (a local heiress) had a passion for astronomy and organized local volunteers to build a planetarium in the Poultry Building on the Kansas State Fairgrounds. Later, they added some exhibits; and then fortunate timing led to a liaison with the Smithsonian, and thus to a full-fledged museum showcasing some major artifacts from the Apollo era and more. And then later still, they acquired a large number of artifacts from the Soviet programs as well. Almost half a world away from the Baikonur Cosmodrome, the Cosmosphere has one of the largest collections of Soviet space hardware anywhere. As the handout wraps up:

"It all goes to show, with vision, timing and a chicken coop, anything is possible. You can even build a space museum in Kansas."

Since I didn't know I would be sightseeing on this trip, I didn't bring the camera. The best I could do is the camera in my iPaq; and I'm still learning how to use that without a lot of blurring. So the shots I got weren't as good as I would've liked. What you see below are the best ones.

As you approach the building (it's not in the Poultry Building any more), it doesn't look much different from any typical college building:

Cosmosphere Entrance

Except, of course, for the small detail of a Redstone rocket out front:

Mercury Redstone

And then as you approach the entrance, you see a bronze statue of Gene Cernan, last man on the Moon (to date):

Gene Cernan

And then you know that there's something special here. Once inside, even before you get to the main exhibit area, you see two space probes:

Surveyor

This is a replica of the Surveyor, a probe sent to the Moon to study surface conditions in advance of the Lunar landings. On the Apollo 12 mission, Commander Pete Conrad and LM Pilot Alan Bean landed within a short walk of the real Surveyor. They took samples from it to help study how the metal had been affected by years on the Lunar surface. (I wish I had a better picture, but this was the best I got. Gotta learn to hold the iPaq still long enough for it to autofocus. No quick snaps with the iPaq!)

Viking

This is a replica of the Viking, a probe sent to Mars. No one has visited it for samples. Yet.

They also had two rocket engines:

H-1

These are the H-1 (top) and the RL-10 (bottom). Both were used on various pre-Apollo rockets, though I can't recall which ones.

RL-10

But that was all in the lobby area. From there, I descended the stairs to the main exhibit area. The two most interesting things about the Cosmosphere are that the exhibits are mostly underground, so space is limited; and yet they use that limited space very effectively, organizing the exhibits by themes and eras over time. Most historical museums do this to some extent; but I thought the Cosmosphere did an excellent job of this. Their use of color and space gave a definite feeling of transition as I walked from one era to another. Places like the U.S. Space and Rocket Center may have more artifacts (after all, it's hard to top a Saturn V); but the Cosmosphere presents a better historical experience. Unfortunately, that experience would be hard to capture even with the best camera. It's not something you can easily capture in a snapshot. You have to actually walk through it to get the effect.

One way in which their historical perspective is more extensive is in their coverage of the German rocket program. The Space and Rocket Center doesn't ignore this history, by any means; but perhaps because of local sensibilities (von Braun and his German team settled in the Huntsville area, and many of their families can still be found there today), it's treated relatively briefly. The Cosmosphere has a lot of detail on the V-2 program, including this exhibit:

V-2 Nose-on

V-2 and Slave Labor

The plaque tells how over 10,000 slave laborers died on the V-2 program — more than double the number of people killed by the rocket attacks. The Cosmosphere exhibit makes very clear how evil the Nazi regime was. It makes you think how important it is that we never let that happen again.

Here's another view of a V-2:

V-2

Next, they showed artifacts and information from the earliest days of the space race, days that were dominated by Soviet launches:

Sputnik

This somewhat fuzzy image is a replica of Sputnik, the first artificial satellite in orbit. The exhibit tells of von Braun's frustration at the Soviets' success, because he felt the American program was ready to launch sooner. He felt that all we lacked was vision and nerve; but he wasn't calling all of the shots.

Laika

This is a cutaway model of the Soviet capsule that launched Laika, first dog in space — before we had yet launched a single satellite. Actually, Laika was the first living creature of any kind in space, and was launched to help the Soviets measure the effects of launch and weightlessness on a living creature. (Sadly, they had no recovery mechanism at that time, so Laika's life was sacrificed in the experiment.)

So while the Soviets were launching a satellite and then a capsule with a live animal, the best we could do was this:

Vanguard

That's a replica of the Vanguard, a grapefruit sized satellite with short little communication antennae. By contrast, the Sputnik was well larger than a basketball, and its antennae were more than eight feet long. Yet even with such a small ambition, we failed: the Vanguard's launch vehicle blew up just after liftoff, and the satellite was lost.

But weren't completely without successes in that era. While we weren't making much headway in the launch area, we were making great strides in propulsion, as these exhibits showed:

X-1 Rocket Plane

This is one of the Bell X-1 Rocket Planes, such as Chuck Yeager flew when he broke the sound barrier for the first time. (Another test pilot from the X-1 program would go on to some acclaim, a young man named Neil Armstrong.)

Rocket Sled

This is a rocket sled, used for ground-based testing of rocket engines and also for tests of how humans could stand up to high acceleration.

Yet despite these successes, the big game in the Cold War was in space; and we were losing there. One reason was the RD-107 or "Red Thunder" rocket engines:

Red Thunder

These were the workhorses of the early Soviet launches; and at the time, we had nothing to match them. These were used for many purposes, including launching the first manned probe, the Voskod:

Voskod

The Cosmosphere personified the space race with statues of two men:

Nikita Krushchev

This is Nikita Krushchev, the Soviet Premier who boasted, "We will bury you. Our rockets could hit a fly over the United States."

John F. Kennedy

And this is President John F. Kennedy, the man who decided, "That's not gonna happen." Or to quote him exactly:


We choose to go to the moon. We choose to go to the moon in this decade and do the other things, not because they are easy, but because they are hard, because that goal will serve to organize and measure the best of our energies and skills, because that challenge is one that we are willing to accept, one we are unwilling to postpone, and one which we intend to win, and the others, too. It is for these reasons that I regard the decision last year to shift our efforts in space from low to high gear as among the most important decisions that will be made during my incumbency in the Office of the Presidency.


And through his inspiration, we accepted the challenge, we didn't postpone it, and we won. And step one of that success was Project Mercury:

Atlas Engine and Sphere

This is an engne and a fuel sphere from the Mercury Atlas, the vessel that replaced the Redstone (above) for Project Mercury. The Redstone was used for sub-orbital flights; but when it came time to launch John Glenn to become the first American in orbit, it was the Atlas that did the job. (I have a photo of a Mercury capsule replica from the Cosmosphere, but it's too blurry to show here.)

Project Mercury got Americans to orbit; but it was on Project Gemini that we launched teams of two, with a plan to practice and master vital skills for the Lunar missions: rendezvous, docking, orbital navigation, and space walks. And for its Project Gemini exhibits, the Cosmosphere pulls out all the stops. Welcome to Launch Complex 19:

Launch Complex 19

This is an actual Titan launch facility, transplanted to the Cosmosphere. When you walk into it (or actually out to it, since it's outside, you're transported back in time and space to an actual Gemini Titan launch. Hidden speakers play back the actual recorded sounds from the launch prep, so you're immediately met with the rumble of engines and systems coming on line. And then you look up:

Gemini Straight Up

Gemini Titan

Gemini Top

Gemini Middle

Gemini Base

And here's a close-up of the engines:

Gemini Titan Engines

And then, if you're patient, and sit through all the holds and the final countdown, the launch itself rumbles over you. It's all realistic enough that you can imagine the flames erupting around you. That's not a good image for the faint of heart!

Back inside, I got a rather blurry photo of a Gemini capsule:

Gemini

And after Gemini, of course, came Apollo. But I'll save those photos for a later post. I'm off to visit my aunt and uncle!

Tuesday, November 15, 2005

Two more photos from Huntsville...
...just for my brother Joe, the tire man:

Space Shuttle tire

Somehow I expected the Shuttle to have larger tires.

Tire Patch

That patch doesn't make me feel all that safe. (The tire looks like a Goodrich. I wonder if it's in Joe's catalog...)
A Tale of Two Vessels
This is the tale of two vessels I visited on my recent trips to Boston and Huntsville.

This is the U.S.S. Constitution, a.k.a. "Old Ironsides", the world's oldest commissioned warship still in service and still afloat:

U.S.S. Constitution, a.k.a.

(The H.M.S. Victory is a fine ship with a glorious history, and is both older and still commissioned; but as the U.S. Navy is fond of pointing out, the Victory is "afloat" in concrete.)

This is not really a vessel at all:

Saturn V Monument

Rather, it's a full-sized replica of the Saturn V, commissioned by the Alabama Space Science Exhibit Commission and unveiled on July 17, 1999. (Bonus points if you can tell me why that particular date.) It almost has to be a replica, because all of the vessels in this line were one-shots, and the pieces have mostly either burned up on reentry or sunk beneath the waves. Still, an actual Saturn V (one which never flew) is shown here:

Saturn V on its side

Both can be seen at the U.S. Space and Rocket Center. (Actually, that photo of the real Saturn V is from my trip last year. So sue me. This year, the Saturn V is under restoration, and you can't get close enough for that angle.)

The motive power for the U.S.S. Constitution is hinted at here:

Rigging

That's a shot of some of the rigging of the ship. When under way, some number of sails would be hung from those lines: more sails to catch more wind for more speed; fewer sails when scouting and otherwise traveling at a more leisurely pace, or when too-strong winds might make the sails a risk. Under full sail with the right winds, she could make 13 knots, or nearly 15 mph.

The motive power for the Saturn V was a little bit more complex. It starts with the F-1 engines:

F-1 Engine

That's just one of them. The Saturn V had five of those monsters in its first stage. If you stand next to it, you feel tiny; but that's hard to tell from a photo. So to give you a sense of scale, the folks at the Space and Rocket Center have helpfully placed picnic tables under the monument:

Picnic Tables under the Saturn V monument

Those five F-1s got the Saturn V off the ground, and burned for 150 seconds. That got the vessel up to around 5,300 mph, and a height of nearly 38 miles. Then the first stage would drop off, and five J-2 engines would kick in:

J-2 Engine

A J-2 is pretty big when you first see it; but by comparison to the F-1, it's pretty tiny.

Those five J-2s would burn for 360 seconds, and then the second stage would drop off. That got the vessel up to around 15,300 mph, and a height of nearly 115 miles.

The third stage had a single J-2 engine, which would burn twice, for a total of 500 seconds. By the end of the second burn (also known as TLI, or Trans Lunar Injection), the remainder of the vessel would be traveling over 22,300 mph — fast enough to escape Earth's gravitational pull. After the Command and Service Module (CSM) docked with the Lunar Module (LM, but sometimes pronounced "lem"), the third stage would drop off. That left the CSM and LM free to go to the Moon. I didn't get any shots of a full CSM (or even a simulator); but here's the actual Apollo 16 Command Module, without the Service Module (of course):

Apollo 16 Command Module

The CSM had it's own engine, the Service Propulsion System, or SPS (not pictured here); but the main motive power for the SPS was gravity. As the CSM's velocity carried it away from Earth, the Moon's gravity grew stronger and eventually dominant; and so a primary use of the SPS was actually as a brake, slowing the SPS and the LM down enough to attain a stable Lunar orbit. Later, the SPS was used for Trans Earth Injection, breaking free from the Moon's much weaker gravity and sending the CSM back toward Earth.

When the LM cut loose from the CSM and descended to the Moon, it did so on this Descent Stage Engine:

Descent Stage Engine

This one was actually pretty small, maybe half my height. Of course, it was supporting a tiny fraction of the Saturn V's mass against one-sixth the gravity, so it didn't need to be nearly as large as an F-1.

Before the Apollo crews reached the Moon, some scientists speculated that the Lunar surface might be deep in dust and might trap a vessel that landed there. In hindsight, it seems like we had plenty of probe evidence and other observations to counter this theory, but it was a valid safety concern. And no one knew quite how rough the terrain might be at a landing site. There was some fear that leaving the Moon might be a lot harder than landing, because there might be no stable ground from which to launch. So in what I've always found to be the most clever engineering solution of the whole LM program, the engineers decided to have the crew bring their own launch platform with them. The LM was designed in two stages: a descent stage which would land and plant its feet on the surface; and then an ascent stage which would use the descent stage itself as a stable launch platform. Even if the descent stage landed in deep dust or was somehow damaged during landing, it would still support a launch of the ascent stage in all but the most catastrophic scenarios. I don't have details on the ascent stage engine, but it was the last major element of motive power for the Apollo missions.

I haven't found any reference for the top speed of the CSM; but it was at least 1,500 times faster than the U.S.S. Constitution. The longest voyage possible for the U.S.S. Constitution was a circumnavigation of the Earth, or something more than 25,000 miles. An Apollo crew on a Lunar mission traveled much more than ten times that far:

Return trip: TLI to Splashdown

This is a small glimpse of the crew quarters of the U.S.S. Constitution:

Hammocks

Officers had it slightly better, but not much. The captain fared better still, because Rank Hath Its Privileges. 450 officers, enlisted men, Marines, and ship's boys slept in shifts in these cramped quarters. (The ship's boys were given education in academic matters and shipboard duties and a decent stipend for the day, in exchange for some vital combat duties: they were the only ones small enough to crawl into the cramped powder lockers and cannon ball stores and haul out the powder and ammunition. Some very brave soldiers won some very risky battles on the U.S.S. Constitution; and every time they fired a cannon at an enemy ship, they were able to do so because some ship's boy was on the job supporting the cannon crew.)

This is a glimpse of the "crew quarters" in the Apollo CSM:

Command Module Interior

It looks like cramped was still the rule of the day; and unlike the U.S.S. Constitution, Rank Had No Privileges when it came to living space in a CSM. (Actually, I believe this photo is from a Command Module simulator, not from the real Apollo 16 Command Module. The real thing is behind plexiglas, and all my photos of it have flash reflections right in the most inconvenient places.)

While I don't have any pictures of them, the U.S.S. Constitution had ship's boats for going ashore when port facilities weren't available.

The CSM had a ship's boat of sorts as well, i.e., the LM itself:

Lunar Module

This was a two-man landing craft, and one of the most challenging flying experiences any aviator could face. The story of the design and construction of this craft is an inspiration to engineers everywhere, and is my favorite episode of From the Earth to the Moon. I'll never be an astronaut, and I can't really see myself as one. A space tourist or mission specialist is as close as I can imagine (and I'm not holding my breath). But I could see myself and my colleagues in every scene of this story of engineers facing near insurmountable challenges on nearly impossible deadlines. When the lead engineer says goodbye to his baby and knows it's never coming back, I choked up. (And keep an eye on the rubber balls for one of the nicest little bits of visual shorthand I've ever seen in a film.)

And on later missions, the "landing craft" itself carried a "landing craft" of sorts, the Lunar Rover:

Lunar Rover

These battery-powered vehicles could fold up and fit inside the cargo area of the LM. With a top speed of 8 mph, the rovers greatly extended the territory that astronauts could explore.

Here Seaman Rob Shaughnessy of Bellows Falls, Vermont tells us about grog:

Seaman Shaughnessy and the grog cask

(Seaman Shaughnessy was a most excellent tour guide, and I enjoyed his presentation immensely. He should have a fine career in public speaking if he ever decides to do so; but since he was both a fireman and an EMT before joining the U.S. Navy, I suspect he prefers a career with a little more action.) In the days of the tall ships, sailors were issued a small daily ration of rum (or other alcohol, but rum was most common). This helped boost morale and helped the men to sleep, as well as providing them with at least something safe to drink. (More on that in a moment.) But the ration was small, not enough to make a healthy, active man drunk; and so sailors got inventive, and hoarded their rations to the weekend. A week's ration was enough to get a man good and drunk; and while that may have pleased the men, it highly displeased the captain. A crew of drunk (or hung over) sailors makes a lousy fighting force (Duelist jokes notwithstanding). So our Navy borrowed a trick from the Royal Navy: the recipe for grog. This was a mixture of rum, lime juice (which also provided vitamin C, and thus helped stave off scurvy), and water. It was acceptable to drink on the day it was served; but if you hoarded it for a week, it went bad, and would make you quite ill. And so the ship's surgeon (who was also the dentist and the cook) was on orders to report any man who showed up with signs of grog-sickness, particularly on the weekends, so that the man could get extra duty assignments.

And why did the grog go bad? Well, I'm sure that the lime juice started to go a bit bad over a week; but for the real answer, Seaman Shaughnessy pointed us to the scuttlebutt:

Scuttlebutt

This was the water cask; and it contained what the crew called "lively water". This was long before water purification, remember; so when the ship put in at some river mouth to refill its stores of water, the "fresh" water most assuredly had microorganisms and more living in it. And every day, the cook would go down to the stores and fill the scuttlebutt and haul it up to the gun deck. The sediments would have largely settled before the scuttlebutt was filled; but microorganisms and algae and even small fish and polliwogs and whatnot would still get into it. And by the time those organisms had had a week to grow in a nice nutrient-rich bottle of grog, well, they'd be just ripe for making a man ill.

Another thing to know about the scuttlebutt is that it was the only place on deck where the enlisted men were allowed to talk. The main deck was the domain of the captain and his officers: no one spoke except on official duties, so that the captain's orders could be more clearly heard and conveyed. And the berthing deck was always occupied by sleeping men (they had to sleep in shifts, remember) who would not appreciate a lot of idle conversation. So the scuttlebutt was the place the men gathered to talk and to gossip; and thus the term scuttlebutt entered our slang as a term for gossip. To this day, drinking fountains in the Navy are still referred to as scuttlebutts.

The final bit of dining lore that Seaman Shaughnessy shared regarded the harness cask:

Harness Cask

The meat in the stores was kept heavily salted to preserve it; so to render it edible, each day the cook climbed down into the stores, carved off enough for the day, and put it in "fresh" water in the harness cask so that much of the salt could be soaked out of it. The resulting meat, though, was still very salty, and very tough. The sailors liked to claim it was horse meat, and to try to convince new crewmen that if they kicked over the harness cask, a horsehead would spill out, still wearing its harness.

The Space and Rocket Center did have exhibits of Apollo food, but I forgot to get a photo. Still, griping about the food is something of a military tradition, so I'm sure the Apollo astronauts did plenty of that. And the story of John Young's orange juice farts is legendary.

Make no mistake about the U.S.S. Constitution: she was a warship, pure and simple. Here's a view of some of her cannons:

Cannons

There were 54 in all: 32 24 pounders, 20 32 pounders, and 2 24 pounder bow chasers. When the 32 pounders fire, they fly backward with the equivalent kinetic energy of an SUV going 30 mph. Then they're caught by the massive ropes, and they bounce around so much that the maker's crests forged into the tops of the barrels are actually imprinted into the beams above the guns. The larger guns were actually given to the U.S.A. by the British, in order to aid the Constitution's original mission: fighting piracy on the high seas. But they were given with a condition: that these guns never be used against British vessels or interests. And so, when the War of 1812 broke out, the Constitution honored that agreement, and fought only with her smaller guns. Despite that, she never lost an engagement, and won over 30 battles, including an amazing victory against superior odds in her battle with the Cyane and the Levant. And though it's habit to speak of these as the ship's battles, of course most credit must go to the fine crew, including the 312 men who died defending freedom aboard her decks. Still, the ship herself deserves some credit, along with her designer, Joshua Humphreys. The ship design was very advanced for her time, with great structural strength. And the hull was an amazing innovation for its day: in a time where double walls were common (with one wall running vertical and the other horizontal, so they could buttress each other, Mr. Humphreys designed a triple hull, with both inner and outer walls running horizontal, while the middle wall ran vertical. This by itself added more structural support; but beyond that, the middle layer was made of Southern live oak, a tree at the time found only in Georgia, USA, and so dense that it actually won't float by itself. This combination of reinforced design, triple-walled hull, and live oak was such that during her battle with H.M.S. Guerriere, British cannon shots actually bounced off the sides. One observer shouted, "Huzzah! Her sides are made of iron!", thus giving her her nickname.

While no actual declared war was involved with the Saturn V, the race to the Moon was actually one front in the Cold War with the now-defunct Soviet Union. Still, she bore no weapons, and carried the message, "We came in peace, for all mankind." Despite that global message, though, both vessels proudly declared what country gave them birth:

Flag flies above the U.S.S. Constitution

Flag flies at a recreation of Tranquility Base

It makes me humble to think that these two vessels, so different in almost every respect and yet so similar in spirit, are part of our heritage. And a chance to see both in three days was not something I'll soon forget.

Monday, November 14, 2005

Where've you been, Martin?
All over the place! And it has kept me hopping. Plus I've been in a string of low-speed-connection zones that made posting more difficult, interspersed with a string of low-speed-and-intermittent-connection zones.

But now I'm on the T-Mobile HotSpot for what Microsoft tells me will be a minimum of a 4.5 hour download. That's assuming no one else comes into Kinko's and starts using the connection. Right now, the Kinko's staff tells me I have a whole T1 line to myself; and it's still a 4.5 hour download.

So I may do a few catch-up posts here (while recognizing that each post delays my download a few seconds).

Saturday, October 29, 2005

You keep using that word. I do not think it means what you think it means.
And the word in question tonight is "final". As in, I'm sitting here in SEA-TAC airport, waiting to fly home from the Microsoft double secret training; and Northwest Airlines has just made what has to be their fifteenth "final" boarding call for the flight to Detroit. (Not my flight: I'm going through Minneapolis.) In the last nine or ten "final" calls, they called out the missing passenger by name (including once in Japanese, though the name was the only part I recognized).

I understand their reasoning, which is two-fold: they really don't want to strand a passenger and leave him or her disappointed and angry; and in today's security climate, if that passenger has checked luggage, they have to hold the plane and unload that luggage, which may mean unloading a lot of other luggage to get to it. This all can delay a flight a lot, so holding it up for one more "final" boarding call may make the plane less late than letting it go.

But this is just like the lesson parents have to learn: if they keep giving the kids one more last chance, the kids learn that a last chance is something they can safely ignore. If I weren't obsessive about getting to the airport early, NWA would've just trained me that their deadlines are really just suggestions, and I can be late if I want. Not a good attitude to encourage.

Related Posts (on one page):

  1. You keep using that word. I do not think it means what you think it means. (II)
  2. You keep using that word. I do not think it means what you think it means.

Saturday, October 15, 2005

Seen around the tech blogs this week
Ever have a night when you really need to get up early, and yet things keep you up late, and finally it seems like the safest course is just to stay up? Or does that only happen to me? Either way, this is one of those nights. In five-and-a-half hours, my plane leaves Atlanta. I've been away from Sandy and the dogs and our home for four weeks. I am going to be on that plane. And I already learned this week that this hotel's wake-up calls are still pretty unreliable. And while the M200 has pretty good speakers and usually serves as my alarm clock, it's having some problems right now. (Never buy Toshiba. Toshibas are junk.) And this 3500 has had the speakers repaired, but they pretty much suck, and I can barely hear them. (Never buy Toshiba. Toshibas are junk.)

So at this point, the safe way to be sure I'm on that plane is to stay awake until I board, and then sleep on the plane. So to find things to keep me going, I decided to do something I haven't done in a while. It's time for another installment of Seen around the tech blogs.

--------------------------------------------------------

Richard Hale Shaw makes an interesting argument against the C# using statement (not the using directive; and thank you, C# team, for that bit of confusing language). I disagree with him; but it will take time and sleep before I can fully explain why. The short preview: he says you can't force people to use your class correctly; I say I can, and I'll show you how, soon.

--------------------------------------------------------

Joe Kunk passes along some suggestions on porting MFC code to .NET, including some discussion of tools to automate parts of the port. Since I have a presentation on this topic, I'm going to check out those tools.

--------------------------------------------------------

From the Earth to the Moon links to this discussion of where the Apollo capsules are today. Until it shut down, the Michigan Space and Science Center in Jackson was home to the Apollo 9 capsule. (Commander McDivitt was a Jackson-area native.) I used to go there for inspiration whenever I had a spare afternoon. When I think of what those engineers accomplished at a time where the sum total of all the computers at NASA amounted to less memory than I have in my hand, I realize that no job of mine is that tough. It was a sad day when I learned that MSSC had closed. Now I have to go all the way to San Diego to see Apollo 9. Of course, my flight home tomorrow ends in Dayton (I started this trip with INETA meetings in Cincinatti and Dayton), and Apollo 15 is at the Air Force museum there; and later this year I'll be in Huntsville for another INETA presentation, where Apollo 16 is. So I'll get my fixes then. (Bonus: outside of Dayton and on the road toward home is the Neil Armstrong Museum!)

--------------------------------------------------------

James Avery is looking to switch blog engines, and wishes he had a decent, easy to use and extend .NET solution. I could be wrong, James, but I think it will be really easy to build your own with ASP.NET 2.0.

--------------------------------------------------------

Tablet PC Buzz points out this post by Josh Einstein about fixes that will make Tablet PC components work properly under .NET Framework 2.0. I'm getting a new version of Tablet UML ready, so this was important news to me!

--------------------------------------------------------

Space Law Probe has a round-up of reactions to China's manned space launch.

--------------------------------------------------------

I don't have James Hudnall under Tech Blogs, because I think of him as a comics guy. His Espers is one of my favorite series. But he's also a computer geek. This week, he posted about the latest story on e-paper, and we drooled over the possible comic book applications.

Marvel has released 40 Years Of The Amazing Spider-Man on CD. I haven't picked it up yet, because I'm afraid someone may get it for me as a gift, and I wouldn't want to spoil that. I really would love to read that collection on a Tablet PC (particularly my new Gateway CX200X Tablet PC, to be ordered next week); but a programmable e-paper comic would be equally cool.

(And I hope that Marvel and DC and others release a lot more of their back stock this way.)

--------------------------------------------------------

Mike Swanson shows off the 5 best videos from the PDC. I wish I could've been there, but I was earning the money that will pay for my new Gateway CX200X Tablet PC.

--------------------------------------------------------

Matt Propst announces the Formal Cancellation of Grand Valley Programming Competition. That's too bad, but I hope they can pull it off next year. Josh Holmes and I were asked to be judges. One of my oldest programming memories is high school programming competitions at Grand Valley, so this would've been like going full circle.

--------------------------------------------------------

And speaking of Josh Holmes, he has a couple of posts on his latest work with Compact Framework and Win CE. Josh is my goto guy on this Windows handheld stuff, and he should be yours, too.

--------------------------------------------------------

Sam Gentile posts about a Channel 9 interview with him and Ward Cunningham. Since neither gentleman is shy — especially with their opinions! — it's pretty no-holds-barred.

--------------------------------------------------------

And speaking of Robert Scoble (the guy behind Channel 9), he's on a crusade to get Microsoft to focus on blog searching.

--------------------------------------------------------

Julie Lerman has a 512MB memory chip for a Toshiba Portege M200. Julie, Julie, Julie... Some day you'll learn: never buy Toshiba. Toshibas are junk.

Look at this Gateway CX200X Tablet PC, Julie. Look at the 14" wide-screen. Isn't it... tempting? Look at that optional 4-year, on-site, parts and labor and accidental damage warranty look... comforting?

--------------------------------------------------------

Lora at What Is New posts that the Windows Mobile PC Team (i.e., the Tablet team plus) now has a group blog.

--------------------------------------------------------

And speaking of the Windows Mobile PC Team... This is a little belated note (since I just learned of their blog from Lora): they write of the work their people did in helping to support Hurricane Katrina relief. I've already noted the contributions by Best Buy, WalMart, Home Depot, Edward Jones, McDonald's, and others; so it's only fair that I point out that my favorite software company has pledged over $9 million in cash, materials, and support to the relief effort. Thank you, Microsoft.

--------------------------------------------------------

Howard Lovy has retired NanoBot. That's too bad, but his new job probably keeps him plenty busy.

--------------------------------------------------------

Thom Robbins forwards an announcement of the general availability of the "Project Server Visual Studio Team System Connector" application. "The solution provides guidance for integrating Project Server and Visual Studio Team System. It demonstrates how Project Server and Visual Studio Team System can be integrated together to provide extended value for project and resource managers and guides developers through the process of building and customizing components that link the project management and software development tools. This is a foundation for partners to build applications that can integrate the two server products and provide specialized functionality."

As someone who's more and more excited about process and practices, I'm pleased by this news.

--------------------------------------------------------

James Kendrick — a.k.a. jkOnTheRun — links to this Detroit Free Press story about Bill Gates's visit to Ann Arbor. (Oh, sure, Bill... Come to town when I'm three or four states away! OK, I wouldn't have been invited anyway, since his presentation was for students. But still...) I think the story hints at one reason why I suspect for Microsoft's strong support for the Tablet PC: Bill loves his Tablet, and has wanted one for a long time. You don't believe me? He described his vision of the platform in drooling detail way back in The Road Ahead (or maybe it was Business @ the Speed of Thought — I'm on the road, remember, so I don't have my books with me). There are few people who are more fanatical about Tablet PCs than I am, but Bill's clearly one of them. And so I have a sneaking suspicion that, just as Microsoft will always sell a version of Basic so long as Bill's involved, so too will they make sure that somebody's making new Tablet PCs for Bill to play with.

(NOTE: The above is tongue-in-cheek, and I know nothing about Microsoft's internal platform decisions nor the reasons for those decisions. But I do know that it's true that Bill loves his Tablet PCs.)

--------------------------------------------------------

And speaking of jkOnTheRun... He links to more proof that Toshibas are junk. And he has a plea:


Let’s help Tracy get her Tablet back. Anyone with a Toshiba horror story about repair or customer service difficulties please chime in here with a comment. Let’s see if a string of unsatisfied customers can get Toshiba’s attention about Tracy’s plight. It’s worth a shot as she has nothing to lose since she is already without her precious.


I'm about to throw some links your way, James, as you asked. But at this point, you may already know my conclusion: never buy Toshiba. Toshibas are junk.

--------------------------------------------------------

There! That worked out just about perfectly. I planned to start prepping and packing at 0600, and it's 0553. That gives me just enough time to do a cursory proofread, and then post.

When next you hear from me, I hope to be H*O*M*E! Sandy, I'm on my way!

Related Posts (on one page):

  1. Seen around the tech blogs this week
  2. Seen around the tech blogs this week...

Wednesday, August 24, 2005

Look out, world! I've got the wheel now!
My brother-in-law Carl led me to check out the latest news from Windows Automotive. It looks like the software now supports the .NET Compact Framework. That means that, when I can get ahold of one of these, I know how to program the car. Eeeevil ideas are brewing. Heheheheheeeee...