Unnatural Causes

An Adam Dalgliesh mystery by P.D. James.

Unnatural CausesI mentioned in a previous post that I’d taken two novels with me to the hospital for something to do while recovering from surgery. In that same post, I also mentioned that drugs kept me unable to read for the entire time I was there. I caught up yesterday by reading one of the two books I’d lugged down to Phoenix and back: Unnatural Causes by P.D. James.

I’m a big reader of mysteries, but for some reason I’ve always shied away from P.D. James. I think I must have had a bad P.D. James experience in my past. You know what I mean. You get a book from the library and have every intention of reading it, but when you open the book and begin to read, the book fails to grasp your attention. You put it aside, planning to pick it up later to read it, and wind up just returning it to the library — late, of course — with a new idea in the back of your mind: you don’t really care for that author’s work.

I don’t remember this happening to me with a P.D. James book, but it must have. There’s no other explanation for why I have avoided her work for so long.

The Great P.D. James Avoidance, however, ended last week when I picked up one of her books at Wickenburg’s local library. And yesterday’s reading of Unnatural Causes dissolved any preconceived notions I had about her work.

The book, which was originally published in 1967, concerns the discovery of a dinghy carrying the body of a dead man whose hands have been cut off. The dinghy washes ashore at the seaside town where it originated, which is also the same place the victim lived: Monksmere. The town has an unusually high percentage of full- and part-time residents who are either writers or crititcs. The dead man was a writer.

The book is nearly 40 years old now and it shows its age. Not in a bad way, mind you. More like a “look back” way. A part of the plot concerns the typing (on a typewriter) of the dead man’s manuscripts with and without carbon paper. If you’re old enough to remember typewriters, you’re likely to remember carbon paper, too. Not only did it give you the ability to make a copy of a document as you typed it, but it preserved that document on its shiny blue or black side — until you reused it so many times that you couldn’t read the carbon. Remember the days? Glad they’re gone? Me, too!

I won’t go into any more detail about the story line or suspects because I don’t want to spoil the book for any future reader who likes a good British “cosy” mystery. That’s what this is, through and through. P.D. James and Agatha Christie were cut from similar molds, although I think James has better use of the English language and much better descriptive skills. Her desciptions of the coastal town were so clear that they brought me there — from central Arizona! — and I was able to hear the waves and feel the dampness of the sea air. There’s something to be said for an author who can do that.

My final word? If you like mysteries and haven’t read any P.D. James, Unnatural Causes is a good place to start.

No Uncertain Terms

A slow but enjoyable read.

In No Uncertain TermsI’m currently wading through William Safire’s book, No Uncertain Terms: More Writing from the Popular On Language Column in The New York Times Magazine. The odd thing is, I’ve been reading it for over a month.

William Safire writes the “On Language” column in the New York Times Magazine. That’s the magazine that comes with Sunday’s New York Times. When we lived in New York and New Jersey, we were occasional subscribers and I’d read the column whenever I got my hands on the magazine.

“On Language” points out recent word or phrase usage in the press, usually quotes by politicians and other oft-quoted people. (I had to look up oft-quoted just to make sure it was a correct usage; it wouldn’t do to make a mistake in usage in this particular entry.) Mr. Safire basically tears the victim word or phrase apart, discussing its development throughout the years and pointing out first recorded usages for each meaning that applies. It’s like reading an entry of the Oxford English Dictionary, but it’s full of puns and things to make you smile — if you catch them. And, of course, it points out whether the word was correctly or incorrectly used and why.

I’ve been reading the book at bedtime and I must admit that I can’t read more than four or five pages before my eyelids grow heavy and I have to put the book down. This isn’t because it’s boring. I think it’s because it’s forcing me to read slowly and carefully and think about almost every word.

This isn’t an exercise I’m accustomed to. When I read novels, I breeze through them so quickly that I just don’t get my money’s worth when I buy the darn things. But this book, which was a “bargain book” on BN.com (and was part of my Christmas list so I didn’t actually pay for it anyway) is definitely worth the money. It’s helped keep me entertained and enlighted — and made it easier to fall asleep — for the past month! That certainly says something.

It’s also taught me a lot about words that I use and other words that I’ll probably never use. It’s made me realize that the English language is even richer than I thought. And although I’m a writer — a real one who actually writes for a living — my knowledge of vocabulary is not nearly what I think it should be.

Perhaps that’s why I often pause while writing these entries, trying to find the right word to say what I mean. (And in most cases failing.)

But then again, it’s hard to build a strong vocabulary when you spend most of your time writing sentences like: “The Save dialog appears. Enter a name for the file in the Name box and click Save.”

Sheesh. I think that sentence appears in every single book I’ve written.

Anyway, I think this book is helping me to build my vocabulary and understanding of word usage. If you’re a word lover, I think you might like it, too.

Stalled by a Bad CD-R/DVD-R Drive

I get ready to wipe my server clean and start installation but get hung up by bad hardware.

By Friday, I had all my Web sites moved over to GoDaddy.com. The LangerBooks.com site, which had been having problems since I initially set it up there on Monday, was not fixed by Friday. So I deleted the setup an started again. Within minutes, it was set up properly and ready to go. Over the weekend, the DNS change was propagated through the system. Just about every browser looking for one of the 18 domain names I host was pointing to the appropriate site on GoDaddy.com.

My e-mail is already hosted by GoDaddy.com. All my e-mail addresses use the theflyingm.com domain name and that domain has been hosted on GoDaddy for at least a year now. So I didn’t need to move any of my e-mail server stuff. Although it exists on my local server, nothing points to it.

There are only three things that remain hosted on my server:

(1) FileMaker Pro provides live access to searchable data. I’m running FileMaker Pro Server 6 on that machine, even though version 8 is current. I wrote all my Web-compatible routines using FileMaker’s CDML language, which is no longer supported by FileMaker Pro 8. So if I updated to the new version of the software, I might have to rewrite the Web interface. That’s not something I want to do. FileMaker also creates the static text ssi files I use on serveral sites. Those files are now put into place using AppleScripts that call Fetch into action. A cool solution, if I do say so myself. After I install the server, I’ll have to reinstall FileMaker Pro, including all the databases and CDML files that run with the Web sites. I’ll also have to reinstall Fetch and make sure the AppleScripts go in the right places. This should take about an hour.

(2) Nicecast is what gets KBSZ-AM radio on the Internet. It’s pretty much plug and play with just a few settings to tweak. I expect this to take about 20 minutes to reinstall.

(3) Evocam is what creates the Webcam image for wickenburg-az.com. It’s actually two images and a movie. It has FTP built right in. Reinstalling should be pretty straightforward.

One other piece of software runs on the server all the time. It’s called Audio Hijack Pro and its job is to automatically record and save certain broadcasts from KBSZ’s stream. For example, the 8 AM news report is available online every day after 8:20 AM. This is all automated: Audio Hijack Pro records the show and runs an AppleScript routine that uses Fetch to upload it to the appropriate directory on the KBSZ-AM Web site (now at GoDaddy.com). Likewise, Audio Hijack Pro records the daily “Around the Town” show and the first hour of the weekly “Rock-a-billy & Beyond Show.” (Starting tomorrow evening, it’ll also be recording my first radio show, “Classic Rock Cuts.” You can tune in online on Wednesday nights at 8 PM MST. I’m looking for sponsors; call KBSZ at 928/668-1250 during office hours to see how much bang you can get for $5 or $10 bucks. Make sure you tell Jo you want to advertise on my show, which will be podcast, too.)

So yesterday morning, I had a clear idea of what I needed to do and what files I needed to preserve from the server. I made copies of all the files I needed to preserve and put them in a folder that I’d use to create a CD. This would make it easy to load them all back in after I wiped the computer clean and reinstalled the software.

And that’s where I hit a brick wall. The CD burner wouldn’t work. It kept giving me error messages.

No problem. I used my network to move all the files over to my main production computer and created the CD there. Now I was all ready to install.

I put the Mac OS X 10.4 Server Unlimited Client DVD disc into my server computer and slid the drawer close. Then I waited expectantly for the disc icon to appear onscreen.

Nothing happened.

I pushed the button to slide the disc in and out and in and out. Nothing. I pulled the disc out and put in the first install CD. (It comes on one DVD or a bunch of CDs; I’d rather use the DVD so I don’t have to switch discs.) Nothing happened.

I put the DVD into my production computer. It appeared onscreen just like it should.

Shit. I had a real hardware problem.

I blew canned air into the CD drive. Lots of dust flew around. Not good.

My office can be a very dusty place. Part of the problem is that a few years ago, some idiot decided to drive a perfectly good western business — the Big Corral horse boarding/riding facility — out of its downtown home and bulldoze all the trees, shrubs, and buildings off the property. In its place, the idiot planted a “For Sale” sign and erected part of an ugly chain link fence. To this day, the land lies open and barren, baking in the sun, supplying that side of town with all the dust it can handle. In my situation it’s a bit worse. I had some work done on the floors in my unit’s kitchen and bathroom and the sanding done by the floor guy sent more fine dust into the air than I thought possible. With a big fan on the back of each of my computers sucking air in, it’s no wonder they were filled with dust.

Of course, I’d already used the canned air on that computer. Just a few days before, I’d installed 512 MB of RAM. While the machine was wide open, I’d used the canned air on it and it was pretty clean. But I hadn’t dusted the drives.

Long story short, I couldn’t get the drive to work. And I didn’t have a spare. And the nearest Apple store didn’t have one. And Apple’s telephone support people told me a replacement drive would cost $354 with tax and shipping. But while I was waiting on hold to hear this bit of news, I discovered I could buy an external Firewire drive for about $100. Sheesh.

By this time, it was after 2 PM and too late to do any installation anyway. I figured I’d bring my new 80 GB external Firewire hard drive — the one I bought t help out my PowerBook — to the office, make a disk image of the DVD onto that, and use the disk image to install the server. If that didn’t work, I’d just buy an external CD-R for the computer and use that. Of course, all this was putting me back in schedule, but I really had no reason to rush. The Web sites were enjoying their new home and were paid up for 2 months.

Of course, I had to give the CD-R/DVD-R drive one last try at repair. So I went to the local hardware shop, bought a cheap ratchet screwdriver with a bunch of heads, and removed the drive from the computer. This was no easy task because although the computer opens easily enough, the CD drive and the Jaz drive I’d bought to go with it (and used about 4 times) were really jammed in there. Then, with the computer up and running without it — no reason to keep that software offline — I removed screws and protective plates until the optical lens and drive mechanism were revealed. I had to peel back two pieces of tape that were obviously in place to prevent the average user from doing what I’d done. I blew more air on it and moved the drive mechanism back and forth with my fingers. It didn’t look screwed up. Satisfied that I’d done all I could do, I put it all back together and stuffed it back into the computer. I fired it all back up and pressed the button to slide the drawer out.

The drawer wouldn’t slide out at all anymore. I’d mounted it a tiny bit too high and it was catching on the computer case.

So I opened up the computer while it was running and did what anyone else in my position would do: I banged on the top of the CD drive to nudge it down. The drawer slid open.

I stuck the DVD in there, fully realizing that that might be the last time I ever saw it. Then I slid the drawer back in.

Would you believe it? It worked!

I couldn’t believe that it was really reading the DVD as well as it was, so I decided to test it by starting the computer from the DVD. That worked, too.

Of course, I didn’t really want to install the software then. It was after 3 PM and I didn’t feel like tackling the installation that late in the day. So I restarted from the hard drive and let all that software come up and run again.

But now I have my work ready for me today.