Jeff Duntemann's Contrapositive Diary Rotating Header Image

Accidental Steampunk

5,000 words in two days. Wow. I haven’t done fiction at a rate like that since I was wrapping up The Cunning Blood in early 1999. It’s the main reason you haven’t seen me here much recently: I have a hard deadline for a story (this is uncommon; deadlines are for things like computer books and articles) and if I don’t produce at this rate for a little while longer, Drumlin Circus won’t be finished and laid out in time for AnomalyCon in Denver at the end of March. I have 27,200 words down now, out of a target 37,000 – 40,000. That’s heading out of novella territory into the strange turf of short novels, where I’ve never worked before.

But that’s the idea. Ruts are horizons pulled in too close, and I’m trying to push ’em back as much as I can, in as many ways as I can. Those who are familiar with my drumlins stories have gotten comfortable with a sort of Weird Western ambiance, and perhaps a hint of Cowboys & Aliens, except that the aliens are gone to parts unknown, having left all their incomprehensible machinery behind. (I was actually inspired more by Fred Pohl’s Gateway novels, at least in terms of the alien machinery.) So far I’ve focused on the rural and frontier areas of the drumlins planet, but much of Drumlin Circus takes place in the planet’s largest city. There were cowboys aplenty in 1890s Colorado, but out east in 1890s Chicago or 1890s New York, society was radically different.

The Drumlins Saga as a whole is about human castaways on an Earthlike planet who slowly re-create Earth technology and civilization, hoping eventually to repair their starship and return home. They “pass through” stages of technology roughly corresponding to advances in Earth history, and at the time of Drumlin Circus they’re basically gotten to 1890, with steam power and the beginnings of electricity. (The first three Drumlins Saga stories are collected with others in this book. More are planned.)

However, there’s a wildcard: alien machines scattered all over the planet, analogous to 3-D printers with a back-end database of manufacturable parts. Enter a 256-bit binary code, and…something…comes out. Some of these somethings are familiar and useful, some can be repurposed, and some, well, they’re just weird–and maybe dangerous. (Furthermore, there’s a lot of somethings. Do the math.)

So it’s 1890 with a twist.

Drumlin Circus itself recounts a sort of low-level war between a traveling circus and a cultlike research organization called the Bitspace Institute, which is very much a steampunk bad-guys version of the Ralpha Dogs from TCB. The steampunk part wasn’t deliberate, and when I was first defining the Drumlins Saga back in the early 2000’s, I hadn’t read any of the steampunk canon yet. But it’s tough to set a story in an 1890s technological milieu these days and not be accused of steampunking, so at some point I gave up and said, Awright awready. I’m a steampunker. (I’ve even had a top hat since 1999, and you’ve seen this. And this.) I’ll deal with it.

(More tomorrow.)

Uphill Melts First

We’ve had a miserable cold winter here, and whereas we haven’t gotten any more snow than average, the snow that we’ve gotten has been a long time leaving. Over the past four or five days the temps have finally been trending up, and as the snow melted on our sidestreets I once again noticed something I’ve seen the last few winters: The uphill lane melts first.

It’s a fascinating business. It’s consistent, and there are a lot of stiff inclines here on the slopes of Cheyenne Mountain. No matter what street I drive on after a snowfall, it’s the uphill lane that melts first. So the citizen scientist in me started chewing on the question: Why?

My first hypothesis was that on the eastern slope of a mountain, roads running east and west have the uphill lane on the north side, meaning that the southerly winter Sun is more likely to fall unshadowed on the north-lying lane. This may be a factor on some streets, but I quickly found hilly streets running north and south and at odd angles. In all cases (I didn’t find even one exception!) the uphill lanes melted first. This was true even on the north sides of small hills where the road surface got little if any sunlight at all.

This left me only a single hypothesis: That car engines have to work harder to move a vehicle uphill, and therefore the undersurface of the car (engine and exhaust system) are hotter going uphill than downhill, when the engine is basically idling. Heat radiating from the undersides of uphill-traveling cars melts more snow than vehicles idling their way downhill. This is a suburban area rather than rural, and there are a lot of houses up here, all on smallish lots. So traffic is significant, especially at rush hours, when conga lines of minivans and four wheelers (necessary on winter roads with 12% grades) commute down and back to Colorado Springs.

I don’t know how true this is, nor how to test it in a controlled fashion. The snow is now gone, but come next week another experiment will be set up, and I’ll have a chance to look again. (I need to keep a camera in the car so I can snap a picture of the effect in action, something I haven’t done yet.)

If you’ve seen something like this happen in your area, let me know.

Odd Lots

Review: How to Train Your Dragon

DragonRide.jpg

Having seen Despicable Me and Monsters vs. Aliens in the past couple of years, I was ready for another delightfully silly kid-flick adventure. And so, my being on the upswing out of the worst flu virus I’ve confronted in twenty-five years, we rented How to Train Your Dragon. Ready for silly! Ready for snotty! Ready for dumb!

Whoa. Not ready. Not. Not even close.

Wow!

Now, how was I fooled? Consider the premise: Spindly young teen Viking kid named Hiccup assists Gobber the Blacksmith on Berk Island, which has dragons like some Viking islands have mice. The whole tribe considers Hiccup a pointless nuisance–especially the chief, who, alas, just happens to be his father. The other and only slightly older kids have all won their horned helmets and are already in dragon-fighting school. Killing your first dragon is the only way in, and Hiccup tries, not by main force but by building goofy hornpunk weapons like a crossbow that flings bolos. Wham! He downs a dragon with his first shot, but then gets a bad case of empathy and can’t bring himself to finish it off as would earn him the tribe’s respect–and perhaps a second look from long, leggy Viking girl Astrid.

Instead, filled with remorse for having shredded an aerodynamically necessary section of the dragon’s tail with his bolo artillery, Hiccup befriends it, feeds it, and (in his offtime at Gobber’s forge) builds a tail prosthetic to allow the dragon to fly again, teaching it to carry him in the bargain.

That’s how I understood the plot going in, training the dragon and all that. There was plenty of silliness to go around, and the plot twist from you-kill-it-you-eat-it to you-hurt-it-you-heal-it was predictable in a good way. That’s where the surprises began. The first thing that jumped up out of nowhere was the dazzling panoply of landscapes, seascapes, and cloudscapes, rendered with a gorgeously detailed hyperclarity that bordered on surrealism. Backing up these distant descendents of matte paintings was an electrifying score from John Powell (solo, Henry Gregson-Williams was not involved this time) that draws heavily on Celtic themes and gives you a white-knuckle sense for the exhilaration of flying over open water and between the impossible stone spires of Berk’s archipelago.

I was a little surprised that Hiccup was not played more for laughs than he was. Maybe nerd fortune is turning around: Hiccup is a geek and a maker and a sort of Dark Ages citizen scientist, who observes closely and takes good notes in his leather parchment chapbook, quick to challenge the conventional dragon-fighting wisdom of his people and capitalize on his new knowledge. (There is dragon catnip, for example, and Hiccup makes good use of it.) Ultimately, what he discovers is that everything he and his people thought they knew about dragons was wrong, including an extra-large economy-sized surprise that I confess I did not anticipate at all.

The dragon (which Hiccup names “Toothless” before he notices that its teeth are retractable) is a beautifully realized character itself, with a very expressive face that suggests a lot more intelligence than you’d expect in a cartoon animal. All the adult Vikings speak with Scots accents while the kids talk like Chicago north-siders, which seems to be a trope in fantasy film these days. I wonder how many kids understood the sly reference to Hiccup’s horned helmet being made from half of his late mother’s bra. Beyond that, well, no quibbles–basically, no quibbles at all. It’s a fantasy tailored to the peculiar daydreams of geeky 14-year-old boys, and it reminded me how full of daydreams 14 had been.

Daydreams? What’s missing? Nothing: You jump into the saddle of your dragon, the girl whose heart you just won climbs in behind you and wraps her arms around your chest (!!!) and with a roar you’re off into the sky to rescue your knucklehead grownups from their own stubbornness, and prove to your father that he was wrong about you. The neighborhood kids who used to give you wedgies are now your friends and followers and they fall in behind you, each on a dragon too. But you’re not on just any old dragon: Your dragon is the Corvette of dragons, the ink-black, blue-lightning-spitting Night Fury that no one–no one–has ever tamed before you did.

Yeeeeeeeeeeeeeeeeeeeeeeee-hah!

I won’t spoil the rest, assuming there’s anybody in the Western Hemisphere who hasn’t seen it yet. The crude humor is kept to a minimum (compared especially to Shrek and Robots) but I think preschoolers will find the dragons frightening. And while I admit that I’m peculiarly vulnerable to films about boys who win their fathers’ respect, I still insist it’s the best cartoon fantasy in years.

Very highly recommended.

Snow Witches In Your Area!

I am not completely (or even mostly) recovered, but I decided to get out of bed, put real clothes on, and walk around some today. My chest congestion is lingering even as runny nose and burning eyes improve, and it is possible for a weakened individual to contract hypostatic pneumonia just by lying horizontal in bed for too long.

That all by itself was motivation to stop living in my robe. I am not running any marathons (not when it’s -5F outside) but I’m fighting back the chaos in my inbox and eating real food on a regular basis.

And I was watching Tom Skilling this morning on the WGN cable feed to get a sense for the precedented (I froze my 14-year-old ass in the precedent) but still impressive snowstorm about to descend on Chicago. I found myself paying attention to something I typically ignore: realtime closed captioning. Carol had turned it on last night while she was grinding the Pack’s collective toenails with her very effective but noisy cordless Dremel. Captioning does help in noisy environments, as anyone who’s watched TV in a crowded fitness center will testify.

I soon discovered a wonderful source of found humor. When one of the announcers said, “If you go out in the snow, please dress appropriately!” the caption read IF YOU GO OUT IN THE SNOW PEAS DRESS APPROPRIATELY. Later on we had a Web cam view from POSOLE, OKLAHOMA, where the snow is coming down as thick as…hominy? (I don’t recall what the audio actually said.)

But I laughed until I coughed (not that that’s hard) when the announcer said “…of the snow which is in your area” and the caption read …OF THE SNOW WITCHES IN YOUR AREA.

Eek!

So don’t blame the Jet Stream. Or moist Gulf air. Or global warming. It’s the witches, people. WGN said so. Quick, Aslan, the Flit!

The Inexplicable Pirate Box

PirateBoxCafe3.jpg

I’m still on the long climb back to functionality and can’t do much computing because the current bug has hugely irritated my eyes. However, I did want to call quick attention to one more thing in the pirate universe before going back to bed: David Dart’s Pirate Box. I got the tip from the Jolly Pirate a couple of days ago, and most of the gadget blogs have now picked up the story. It’s a make-it-yourself wireless filesharing node in a pirate lunchbox.

Lesse here: You carry this into a crowded coffee shop so that people can connect from their laptops and smartphones and download whatever pirate goodies are in the box, at least until somebody calls the Bomb Squad.

Ok, I’m just funny that way. But read through the DIY, and ask what I’m asking: Isn’t this a lot of fooling around just to create a wireless file-sharing node? Even a five-year-old beater of a laptop can run Debian and a file server, and software router apps are routine. Furthermore, a laptop looks like a laptop, and when there’s a dozen people at Panera running laptops, it’s a little less easy to tell who’s the pirate.

Unless that’s the idea. This certainly seems to be more about cachet than practical piracy. I’m reminded of warchalking, a silly near-hoax that was getting people’s twickers in a nist back in 2002 or so: marking the locations of wi-fi networks on the sidewalk in chalk, god help us, as though there were no other way to know something was there.

I have the late Harry Helms’ books about pirate radio and I think I understand the psychology. It’s about being a Merry Prankster more than actually getting anything accomplished. And I’m good with that, especially since the 17 people on Earth who will actually build this thing and hang out with it are unlikely to do much damage. (I do grant them points for creativity.)

The Pirate Box reminds me a little of AirStash, which has the advantage of being able to hide in your pocket. The notion of hidden local physical filesharing is an interesting one, and I’m sure that there are better concepts for it hiding out there somewhere. (A USB thumb drive mortared into a brick wall is just one of the gonzo notions I’ve seen recently; something like geocaching with data.) If you know of any more, send me links.

And now it’s back to bed for me.

Kill Switches and File Hoarding

I am so flat on my ass.

My own fault, too. Back in December Carol went in for a re-check on her pancreatitis issue, and the doc said, “Hey, how about a flu shot?” We’re usually good about getting them every year, but this year she got one almost by accident, and the whole issue then slipped my mind. So this past Tuesday afternoon the nausea began, and by Wednesday lunch I was coughing hard and so wobbly I could barely stand. I crawled out of bed here and there during the week to clear my spam and maybe answer an email or two, but more than that just wasn’t in the cards. This morning I’m feeling better than I have since Wednesday, but my chest still aches from the coughing and I’ve lost five pounds.

Shame; lots of interesting things have been going on this week, and I just haven’t been able to write about them. I got two notes from the Jolly Pirate after a long absence. I’ll take up the first one tomorrow. The second one was shorter, and cooks down to one sentence: “Egypt is why I hoard.”

I’ve talked about him here before. He’s one of my eccentric fans, an unapologetic file hoarder who fills hard drive after hard drive with pirated content and freely admits he’ll never even look at (or listen to) most of it. He’s not some sort of wunderkind topsite scenemaster. He’s a thirtyish single guy, and (in his own words) “not especially high tech.” We’re not talking about mysterious Darknet interconnections here. Jolly gets most of his stuff from Usenet or from his friends. They have occasional LAN parties (which are often about file sharing as much as gaming) but mostly they just pass external hard drives around, and copy content among their laptops by the terabyte while watching TV. 2 TB drives are down to $80 on NewEgg. I’m guessing his habit isn’t making him broke.

He worries a lot about the “kill switch” idea, and won’t assume that content you find in the Cloud today will still be there tomorrow, nor that it will still be safe to grab it. Mubarak very quickly and effectively knocked Egypt out of the Cloud this week. Jolly isn’t worried that our President will literally take the Net offline to combat file sharing, but that security concerns will lead to forced logging of all server traffic and detailed monitoring of every packet we send and receive, nominally to keep order but with the full encouragement of Big Content.

In essence, the Kill Switch will be the threat, and a tightening of Net surveillance will be the fallback, since, hey, we’re better than Egypt. We don’t have to shut it off. We just haveta watch it harder.

The real problem with kill switches may be something like that: They’re a form of theater, pandering to popular fears but in reality serving multiple interlocking agendas that few people understand. Lots of powerful groups dislike the Internet. Big Content is only one of them.

Pay attention to what the weasels you elect to office are doing. In the meantime, the Jolly Pirate is responding what may well be rationally: Get It While You Can. The buckets are cheap and the faucets are still wide open.

Luck Happens: The Blotter and the Pocketwatch

WorkingWatch500Wide.jpg

A couple of people have asked me where I got the Windows blotter wallpaper discussed and shown in the photo on my January 19, 2011 entry. I stumbled across it while looking for art depicting steampunk airships. Jim Strickland and I have been tossing ideas around for a drumlin airship, and I wanted to see what other people had done in that area. Just clicking around, and alluva sudden I was looking at this. Egad, it’s 1600 X 1200 too–no need for me to do any resizing. If you’re widescreen, you might consider this one instead.

I like blotters. I had a desktop blotter at Borland that was an Ampad Efficiency Deskpad 24-003. It was basically a faux-leather frame surrounding a pad of 17″ X 22″quadrille paper, which I have always liked for sketches and off-the-cuff coding. When Borland laid us off they told me I could have it, since they were just going to dump it (and everything else in my desk) anyway. It’s followed me around ever since, though I’m not sure the quadrille paper for it is available anymore.

The only thing that bothered me about the blotter wallpaper was the pocket watch, which (while well-drawn) was just an image, and always read 3:37. (Days later, I found a version of the blotter wallpaper without the watch.) If the watch had to be there, it had to work. And then I remembered something I had seen a long time ago and forgotten.

There’s a widget engine for Windows called Rainmeter. It was mentioned on one blog or another that I followed back in 2008 or 2009. A widget engine is an app that runs without a conventional windowed UI, and allows you to display frame-less output on your desktop. The widgets are basically skins, and the output can be drawn in easily parameterized ways. There are myriad skins for Rainmeter, and while I was experimenting with it back then I ran across a clock skin called Pocketwatch. It looked a little bit Stickley (as does much else in this house) and I would still have it running had I kept Rainmeter across the last couple of Windows reinstalls. (I did not.)

On a hunch I did the obvious: I took a 6″ steel rule and measured the size of the Pocketwatch widget on the screen, then measured the static pocketwatch image on the blotter wallpaper. The face of one was precisely the same size as the face of the other. (The Pocketwatch skin is the face only; the blotter has the whole pocketwatch.) I quickly installed Rainmeter and Pocketwatch. I centered Pocketwatch over the face of the pocketwatch image, and then un-checked the Draggable setting on Pocketwatch’s context menu. Bang! The watch on my wallpaper now keeps time. All free, too. C’mon, people: What are the chances? Sometimes luck just happens.

Odd Lots

  • At our most recent nerd gathering here, four of my friends and I managed to carry our 1997-vintage, 198-pound Sony CRT TV set up our precipitous stairway out to the 4Runner, and a few days later I paid Blue Star recycling $37 to see it to its final rest. Many thanks to the guys–we had been pondering how to get rid of it for the past several years. Friends are most excellent to have, especially for people like me who can’t lift 100 pounds anymore.
  • And this means we’re shopping for a downstairs TV. I came across a good site focused on plasma TVs, which as a class may be problematic at our current altitude of 6600 feet. Apparently they buzz and run far too hot, though the physics of the phenomenon remain obscure to me.
  • I’ve found the first (thin) review of the Motorola Xoom. Few details yet, but I will say up front that the cloud-based ebook system doesn’t thrill me. Early releases of Honeycomb may not support the XD card slot, but Motorola hints that an OS update will take care of that. That’s important here: Given that 16GB MicroSD cards are already down to $35, sideloading my entire ebook library would be a snap, with room left over for lots of music and videos.
  • I also recently found out that the Xoom GUI borrows from the quirky but interesting BumpTop, recently bought by Google and then pulled from general distribution.
  • I may be too old to appreciate the BumpTop 3D metaphor (I always think it looks like working inside a refrigerator box) but some good themes have been created for it, including this steampunk specimen.
  • Xoom has a “barometer.” Most commenters, including the LA Times , don’t seem to understand that a barometer can measure altitude with more accuracy than GPS. I doubt that the Xoom’s barometer will have anything to do with weather reports. (Else there’d be a thermometer and a hygrometer as well.)
  • There’s a long-running feud between Samsung and US cell carriers over who pays for Android updates, with the result that many Samsung phones are stuck at Android 2.1 and may never get an update from the vendor. (Applying the update yourself is not for the squeamish.) Yesterday afternoon, of course, Samsung denied it all. As intriguing as the Galaxy Tab looked when I played with it back in November, issues like this may keep me away from Samsung wireless products entirely.
  • Some images speak for themselves. Like this one. (Thanks to Pete Albrecht for the link.)
  • Oxytocin may be the biochemical basis for tribalism, racism, political parties, and just about everything else that the human species would be better off without. “Cuddle hormone” my ass.
  • Good-bye to seigniorage, not that one person in ten thousand ever knew what it was–or how to spell it.
  • Ahh, well. I may have eaten my last pistachio.

Displaying Wallpaper on One Monitor Only

DualMonitorSetup500Wide.jpg

I got annoyed the other day (finally!) after being annoyed off and on since, well, almost forever. The problem was this: I was following a Web tutorial explaining how to do something in InDesign. I had InDesign up and maximized (as I always use it) and the Web tutorial in a Firefox window. Firefox wasn’t maximized, but that didn’t matter: Each time I selected a menu item in InDesign to tweak a setting, Firefox vanished under InDesign. That’s just the way Windows has always worked, and for a long time (ten years? more?) I was wondering if there were a better way. Tiling is not an option, not if I want to work on spreads in InDesign. So I just kept on keeping on, with Firefox appearing and vanishing as I ticked off steps on the tutorial.

Until this morning, when shadows on the wall told me that the light bulb had appeared over my head. Yes!

I ran downstairs and got an old monitor off the shelf. It’s a 15″ Samsung SyncMaster 570B, bought for Carol in 2003. She used it until I got her a 20″ display a couple of years ago. It has a mount pivot, and can be used in either portrait or landscape mode. I plugged it into the idle VGA video connector on my desktop, and without any fuss I had dual displays.

I’ve done that before to see how it was done, but never had the desk space for two identical (big) monitors. It wasn’t until today that I hit upon the refinement of putting the second monitor in portrait mode, which takes some space but not as much as anything in landscape mode. Now I can put a Firefox window on the secondary display while working on something full-screen on the primary display, without having to rescue the tutorial window from behind the app window each time I do something in the app window. Victory is sweet–and contains no fructose.

One peculiarity: My desktop wallpaper was partially duplicated on the second, lower-resolution display. The wallpaper image is a desktop blotter (complete with stains) and it just looked wrong having only part of it on the smaller monitor. I wanted the wallpaper on the primary display only, with just a blank color field on the secondary. Remarkably, there is no obvious way to do this. I dug around for most of an hour, trying things in both Control Panel’s Display applet and the NVidia control applet, without success. Then I hit upon this article. The gist is this:

  1. Return the wallpaper image setting in Display | Desktop to None; that is, turn off your current wallpaper. Both screens will now have the same blank color field for background.
  2. Select Desktop | Customize Desktop | Web. What you’re going to do is add a static image (the wallpaper of your choice) for Active Desktop, instead of a Web page.
  3. Click New. In the New Desktop Item dialog, click Browse, and select your wallpaper image from wherever it lives. Open it. Click OK on New Desktop Item. Click OK on the Web tab. Click OK on the Display applet as a whole to close it.
  4. The image you selected will be displayed, probably spanning both monitors. (It did on mine.) Hover over the top edge until the Active Desktop title bar pops up. Click and drag the image to whichever minotor you want to have it as wallpaper. When it’s moved completely onto one display, click the maximize button in the title bar. Bang! There’s your wallpaper, on one display only.

Now, as best I know Active Desktop was eliminated from Windows Vista, so this mechanism applies only to XP and (I presume) earlier versions. (Let me know if I’m wrong about that; I have no Vista or 7 instances here.) Active Desktop used a lot of CPU time and memory, but I think that was due to continuous refresh of the Active Desktop HTML and inane things like Pointcast that people have long forgotten. I don’t see any resource hit for having a static image in place of a Web page.

If I see any system flakiness in coming days I’ll reverse the change and let you know, but so far I haven’t seen a downside. I may try other uses of the secondary display, but I also think I may just turn it off unless I need to read a Web page while doing something else on the primary display. We’ll see.