When I was around 15, I had a close encounter with a rattlesnake. In my tent. No one was bitten, but getting that snake out was an interesting experience. It happened during a week-long summer camp at Lost Valley Scout Reservation in the mountains northeast of San Diego. It was at least my fourth summer camp with my Boy Scout troop, placing it around 1991 or 1992, and at least my second at Lost Valley.

Lost Valley

There are two kinds of campsites at Lost Valley (or at least there were in the early 1990s): One type had simple wooden cabins, which held two bunk beds apiece*. This was the other type, with canvas tents. The canvas made up the roof and walls, and was tied to a metal frame with a plywood floor. (Note: this arrangement is not sealed.) Two cots lay on the floor. Scouts would typically lay out their sleeping bags on top of the cots, and stow their gear underneath.

The site was in a wooded area of the camp — mostly evergreen trees — below a hill, in the Camp Irvine section. Looking in from the road, there was a large rock formation to the right, which I remember a lot of us scouts would climb onto. (It’s the 13th point of the Scout Law: A Scout Climbs Rocks) To the left, the land stayed flat at least as far as the next section of road. Straight back was a fairly steep hill which led up to more campsites and eventually the dining hall, if you were willing to go off-trail and cut through another site. Judging by the map, it looks like it was probably Indian Wells campsite. Edit: My dad points out that the stones had been grinding sites for the local Native American tribes, which may have been the source of the name.

Finding the Snake

My tent was toward the back. One night** as I was getting ready for bed, I set my canteen down before closing it and accidentally knocked it over. I quickly set it upright, then got down with a flashlight to look at the puddle of water spreading back under my cot, and see if I needed to move anything out of the way.

Looking back at me was a rattlesnake. It had apparently set up its own camp under my bed. I said, surprisingly calmly, “Oh, there’s a snake under my cot.”

“That’s nice,” my roommate, Geoff, who was already half-asleep, mumbled. Followed a few seconds later by, “WHAT!?!?”

I think he went to get an adult while I kept my distance and watched the snake. Or possibly the other way around. Or maybe we both went for help. I definitely recall one of those audio relays of boys saying, “There’s a snake in Kelson’s tent!” Someone went to contact camp staff, and the snake crew showed up. (Chances are pretty good that Phil Brigandi*** was among them.)

Keep in mind that it was dark. It was several hours into night, and the only light came from flashlights and propane lanterns.

Removing the Snake

My dad, who was there as a troop leader, adds a little more info:

They used the opportunity to make a point that little rattlesnakes are more dangerous than adults, because they’re less skilled at releasing their venom in small doses. (Otherwise, the snake has no venom for a second strike, in case it needs to fight another enemy.) So little rattlesnakes inject you with everything they’ve got.

Our biggest concern of course was that we didn’t want the rattlesnake to get away while we went and got the snake control guys. (Otherwise, you’ve got the trouble of wondering where it’s GONE!) Of course, nobody was going to try to catch it or anything, so the basic idea was to leave it alone but keep the lights on so we could keep an eye on it. We all counted ourselves lucky when we got back and found that the snake was still where we’d found it!

They don’t kill rattlesnakes when they find them, just relocate them. (Rattlesnakes play a part in the local ecosystem, after all.) Their equipment consisted mainly of a stick with, IIRC, a loop of rope on one end, and a large wooden box. Normal practice involved trying to pick up the snake with the stick, depositing it in the box, closing it in the box, then taking it out somewhere farther away from any people.

There was a problem, though: The snake was too small to pick up. It just kept sliding through the loop. Finally someone (possibly my dad, now that I think about it) picked it up with a shovel and put it in the box. They closed it up, may have loaded it on a truck, and that was the last I ever saw of the snake.

Notes

*It was in one of those cabins that I once rolled off the top bunk in my sleep and woke up on the way down, before I hit the floor. I don’t remember it hurting at all. I just climbed out of my sleeping bag, climbed back up, and went back to sleep.

**I think it was the same night that I took my camera and a tripod out to one of the large meadows and experimented with taking pictures of the night sky. I got some fairly decent (for a first-timer) shots of Sagittarius, Scorpio, and the Milky Way, which I’ll have to see if I can find sometime.

***I was prompted to write this when I read Orange County Historian Phil Brigandi‘s account of the first time he ever saw a rattlesnake bite in his many years at Lost Valley Scout Reservation.

It’s always something.

Last month it was my computer that needed rebuilding. This month it was Katie’s. It’s an old G4 PowerMac, but it’s still plenty for iTunes, web, email, word processing, etc., and we’ve got a newer Windows box for things like games. It failed to boot after a system upgrade, and subsequent troubleshooting determined that the drive was going bad. (This time I ran some more diagnostics, confirming that the rest of the hardware was fine, and Tech Tool Pro found dozens of bad blocks before I stopped the surface scan.)

So: New drive, reinstall system, transfer the data and apps that we can. Which led to this question:

The Leopard or the Tiger?

(Sorry, I couldn’t resist phrasing it that way!)

Last fall I bought the multi-license pack of Leopard so that we could put it on both Macs. We ended up not upgrading the desktop. She was under the impression that the hardware was too old, and I only remembered that Leopard had dropped support for Classic apps. The first problem was easy: I’d checked the specs before ordering, and would only have bought the single-license box if it hadn’t been supported. The second was also easy: in the past year, she’d converted all her documents from old classic-only apps, and wasn’t playing the classic-only games anymore.

So: Installed Leopard, transferred data from old drive & backups.

Side annoyance: transferring a user with the Migration Assistant did not work. First it wouldn’t copy over her account, so I had to create another account, log in, delete her (new) account, then do the transfer. Then, every time it ran into one of the 5 or so corrupted but inconsequential files, it would freak out and remove everything it had copied. Drag and drop copy didn’t work because the alternate account didn’t have permission to read everything. (Remember: admin != root.) I finally resorted to the UNIX commandline, which worked. For reference: sudo cp -rp oldpath newpath Prob. should’ve used tar instead of cp, but I’m not sure how much Mac OS X uses symbolic links in user accounts. In any case, it’s been working, so I’m not going to worry about that.

The real problem: A week later, while doing link maintenance on this site, I stumbled across my blog post about upgrading the laptop, which mentioned the fact that Photoshop 7 won’t run on Leopard.

*facepalm*

Cue Spamusement:

Screaming figure running from a ghost crying, $150...just to UPGRADE

So, what are the options?

  1. Shell out $200 to upgrade to Photoshop CS3. I don’t think so. Not after doing major surgery on two computers, not in this economy. (Incidentally, it took forever to find the system requirements on Adobe’s website and verify that CS3 would actually run on that machine, since everything is focused on CS4…even though it isn’t available yet.)
  2. Downgrade to Tiger. Might just be Archive & Install, might require wiping the new drive and reinstalling. (Reports are mixed.) I don’t think any of the built-in apps she uses have changed data formats, so that’s probably OK.
  3. Find something cheaper or free. Katie pointed out that it has to be able to read PSD files accurately.

We’re going with (c) for now, starting with the OSX version of GIMP.

After several years of inactivity and a quiet relaunch earlier this year, the Dillo web browser has finally released Dillo 2.0.

The open-source project started in 1999 with the goal of creating a small, fast, highly efficient graphical web browser that could run well even on low-end hardware and software. It’s a UNIX application, and runs on Linux, BSD, Solaris, etc. Things stagnated when it became clear that GTK1 was going to vanish, and GTK2 would not fit the project goals, and eventually the browser was ported to the Fast Light Toolkit (FLTK).

If you’ve used Dillo before, some of the improvements in this release are multiple character set support (the old versions were Latin-1–only), tabbed browsing, HTTP compression, anti-aliasing, improved rendering and UI, and smaller(!) memory usage.

It does have its limitations, and a few major items stand out as missing when compared to other modern browsers:

  • No CSS stylesheet support.
  • No scripting.
  • No plug-ins.
  • Limited SSL support.

That said, it’s useful to keep around on an old/slow system, or for situations where speed is more important than rendering, or to test how a website works without styles, scripts, and plugins.

I started building RPMs of Dillo for my own use back in 2002, and became the official RPM packager for the project the following year. I’ve posted Dillo RPM packages for Fedora 9, RHEL 3, RHEL 4, and RHEL 5. Other distros will have to wait until I get my build system out of storage or figure out how to convince mock to let me build two packages together.

Something like 10 years ago, Katie saw a self-storage place in which the opening S was unlit, making it read, “Elf Storage.” She’s been looking for another one ever since, and we finally caught one in Newport Beach a few months ago. This one was even better, because the S had actually fallen off.

Of course, there are other things in the area that could easily come out of a Dungeons & Dragons manual. Such as this Kobold Construction truck.

And then there’s the fact that all fire engines in Orange County are labeled ORC.

Let’s not forget the previously-blogged Hobbit Center in Laguna Beach.

Hobbit Center

And that’s not even getting into all the Tolkien-inspired street names in Lake Forest…

I was just commenting on The Comic Treadmill’s 5-year anniversary, and I realized: K-Squared Ramblings turned six last month. (September 14, to be exact.) I’ve been so busy with Speed Force that I haven’t posted much here, and didn’t even notice the milestone.

Let’s run the numbers:

  • 6 years and not-quite 1 month
  • 1708 posts including this one
  • 2,863 comments including pingbacks and replies
  • 52 categories
  • 9 convention reports (6 San Diego Comic Cons, 2 Wizard World LA, 1 WonderCon)

Top-viewed posts for the year:

Last month I finally got around to a major rebuild of my computer, something I’d been meaning to do since May when I traced some display problems to the motherboard*. I finally bit the bullet when I started seeing signs of disk errors, and dragged the machine into the present day. (64-bit, dual-core, 2 GB RAM, SATA drive, faster everything.)

Then I discovered that some of the display problems actually were the fault of the monitor.

So I went out and bought a new monitor while Fedora was installing, and I took the opportunity to go widescreen.

My criteria were simple: The resolution and physical size both had to be as big or bigger than the old one (17″, 1280×1024), and it had to be under $300. That meant at minimum a 22″ display at 1680×1050, and I found a Hannspree 229HBP for about $190.

There was a Dell right next to it, same size & resolution and comparable specs, and the Best Buy employee had been talking both of them up. The Dell was on sale for $290. I asked what the difference was. He thought about it for a few seconds. “Well, this one [the Hannspree] does run a little bit hotter. But mostly it’s just the name.” Thank you, Best Buy employee whose name I’ve forgotten, for helping me save $100.

The biggest difference, aside from actually having room to show both the toolbox and document windows on GIMP, is that I don’t maximize windows anymore. Not that I maximized apps that often before, not counting the stuck-in-low-res period. I’ll occasionally run a video or slideshow fullscreen, but the only program I regularly maximize is my email client, and that’s because I can put it in three-column mode (Folder tree on the left, mailbox listing in the middle, message content on the right).

Something to watch out for: At first I left the monitor off-center, because there wasn’t enough room on my desk for it. I figured as long as I worked mostly on the right part of the screen I’d be fine. But I ended up having neck problems shortly afterward, and Katie suggested I check the placement of the monitor. I shifted things around so I could center it, then set it on top of an Amazon box to raise it a couple of inches, and the sore neck cleared up.

I’ve only run into two problems (not counting the placement): There’s one dead pixel, but it’s off in a corner so that it’s not really an issue. I almost didn’t notice it at first when I was still setting things up, because the default GNOME layout has a Mac-style ever-present menu bar, and it falls right on the edge. Usually it ends up either on the edge of a window border or lost in the wallpaper noise.

The other problem: the built-in speakers pretty much suck, but I had external speakers already, so again: no big deal.

* It stopped displaying any resolution past 1024×768. I could tell it wasn’t the monitor because it was perfectly happy to show another computer at 1280×1024. And not the drivers or OS because I had the same problem booting from a LiveCD. And not the video card because plugging in another one didn’t solve it. This was particularly frustrating since it was an LCD monitor, so running at less than native resolution made everything blurry. Still, I put off replacing the mobo for months since it’s such a pain to do.