Sorry about that

I’ve been trying to figure out for these past few hours whether I’m making one of the biggest mistakes of my life. From my experience, usually those questions alone are a really bad indication.
I have to go to work now. But I think working through this in writing will be a good exercise. And if I post it, someone might find it useful.

Yes, I’m here and looking for something to write about.

I’ll post later once I’ve figured something out. ‘K?

Don’t read this if you don’t want a cheap (under $200) DVD burner

Long ago, I used to hunt for killer prices on computer equipment, and when I’d find something good, I’d post it here. It seemed to be a fairly popular feature. I haven’t done that in a long time, mostly because I haven’t been in the market for anything.

Read more

Creating images of floppy diskettes with Linux or DOS

If you want to archive floppies–a good idea, since a floppy disk can sit for months unused and go bad between the time you made it and the time you really needed it, and since it’s hard to shuffle through a collection of hundreds of disks and find the one you need–Linux is an ideal environment for it. To create a disk image, use the following command:
dd if=/dev/fd0 of=filename bs=18k

The if parameter tells it the input device or file (the floppy drive, in this case), and the of parameter tells it the output device or filename. The bs parameter is block size. Most people use a block size of 512, since that’s the size of a disk sector, but it’s slightly faster to write an entire track at once. The speed increase is only slight, but I thought you might like to know. Floppies are already slow enough as it is. I’ve also heard allegations that reading and writing entire tracks at once is more reliable, but I can’t substantiate those claims.

To write out a disk image, simply reverse the if and of parameters:

dd if=filename of=/dev/fd0 bs=18k

Disk images in this format are portable; any Unix can rewrite them to disk, as can the DOS/Windows utility rawrite, which you’ll find on virtually every Linux installation CD. Most other popular disk-imaging programs for DOS and Windows can handle this file format as well.

If you want an equivalent DOS/Windows command-line program to create dd/rawrite-compatible disk images, check out fimage. You can even make those images self-extracting executables with sfx144, if you wish.

SCO stoops to RIAA tactics

SCO is now threatening legal action against corporations that use Linux, since it supposedly infringes on their intellectual property but they haven’t revealed the infringing code yet. I guess they need to start by suing themselves.

Cinelerra 1.1.6: An open-source video editor for Linux

I noticed today that Cinelerra, possibly the best-known video editor for Linux, has hit version 1.1.6.
I’ve played around with Cinelerra a bit, and found it competent, but not intuitive. While it’ll do things that Adobe Premiere won’t do, or that Premiere makes exceedingly difficult, there are an awful lot of things that Premiere will do that Cinelerra won’t. Want to mix stills with your video clips? You’ll have to convert those stills to single-frame MPEGs first. (That means becoming good friends with ImageMagick.) Want to pan and zoom? Forget it.

Now, if you’re trying to make the next Blair Witch Project, Cinelerra is more than up to the task, feature-wise. The only question is stability, but that can even be a question with Premiere or with Final Cut Pro. And Cinelerra gets minor point releases a lot more frequently than the commercial big boys.

But if you’re wanting to make documentaries, or, more likely, edit your home movies, Cinelerra will probably frustrate you. Kino will be easier to learn and possibly more feature complete. If you’re willing to pay some money, you’d be better suited with one of MainConcept’s offerings. (MainActor is included in the purchase price of SuSE Linux 8.2.) Or, assuming you run Windows some of the time, you can mess around with the video editor included with Windows Me and XP.

Life has returned to Royals Stadium

The last time I went to a Royals game at Royals Kauffman Stadium (it’ll always be Royals Stadium to lifelong fans like me), it was 1996. Mike Sweeney was riding the bench. Johnny Damon was lifted for a pinch-hitter when the opposing team brought in a left-handed pitcher. And the place was as quiet as a library.
On Saturday night, I finally returned. The Royals were in first place, powered by a young and hungry starting pitching staff, the bats of a bunch of people who never got a chance elsewhere like Desi Relaford and Raul Ibañez (superstars Mike Sweeney and Carlos Beltran have been hurt much of the year). But the weather looked threatening and they’d just lost 4 straight, two to the traitor Johnny Damon’s Boston Red Sox and a doubleheader to the Baltimore Orioles. You can explain away the losses to the Red Sox. You’re happy to take one of three from them. Baltimore’s a different story. Maybe the Royals were fading.

Yet, 25,930 still turned up for the game. A year ago, the attendance would have been half that. There have always been much better things to do in Kansas City on a Saturday night than to go watch the Royals lose.

I knew things were different when earlier that day, I’d gone to the grocery store and I saw people wearing Royals hats and t-shirts. Those had become nearly as common in St. Louis as in Kansas City. Royals hats had become something worn by the fashion-conscious because their royal blue color looked good with the rest of their outfit. Most of them probably didn’t even know that hat had anything to do with a pro sports franchise. Then, on the way to the game, I saw ticket scalpers stationed along the exit ramp off I-70 near the stadium. I haven’t seen people scalp Royals tickets in, well, forever.

The stadium itself is electric. I remember the Royals’ division championship season of 1984. George Brett was still in his prime, and Bud Black was electrifying hitters and the rotation was rounded out with rookies like Bret Saberhagen, Danny Jackson, and Mark Gubicza, none of whom is a hall of famer, but all of whom showed signs of brilliant careers to come. It wasn’t a great team, but it was a fun team to watch.

There was more fire in that stadium on Saturday than I remember seeing in 1984. Well, at the start of the game, that is. The word “Believe” floated across the scoreboard, fading out to highlights of the still-young season like Ken Harvey muscling out home runs and Michael Tucker and Desi Relaford making diving catches in the outfield. A left-handed pitcher wearing number 32 took the mound. Twenty years ago, the Royals had a left-handed pitcher who wore number 32. His name was Larry Gura. He was good for 15-18 wins and made the All-Star team a couple of times.

This guy’s name was Chris George. If he can pitch like Larry Gura, I thought, this is gonna be a good year.

George retired the first batter on two pitches. The crowd was electric.

By the end of the inning, it was like a library again.

Chris George had a no-hitter through four innings. A walk here and there and a balk here and there had gotten him into trouble, but an umpire can call a balk if there’s a guy on first base and he doesn’t like the way you scratched yourself. Just ask my cousin. He was the perennial league leader in balks throughout the 1980s, pitching for Cleveland and Chicago. I think Chris George must have known that, because he pitched out of those situations. George impressed me. He’s definitely a finesse pitcher–he didn’t register higher than 88 MPH once that night–but he mixed up his stuff enough to keep Baltimore guessing and he racked up plenty of strikeouts.

But then Baltimore scraped together a couple of runs. The Royals came back in the bottom of the inning, with a couple of speed demons on first and second and the smooth-hitting Joe Randa at the plate. Randa stroked a double to center field. One run scored. Desi Relaford rounded third and was halfway home when he noticed his third base coach screaming for him to hold. He tripped, tried to make his way back, and was tagged out to end the inning.

That got the crowd’s attention.

The next inning, Baltimore’s slugging young right fielder, Jay Gibbons, hit a two-run bomb to right field. Well, the way the wind was blowing that night, I probably could have hit something that would clear the right field. fence. But it counts. Baltimore was up 4-1. But there’s some life in the Royals’ bleachers. Before Gibbons had rounded the bases, his homerun ball was back on the field.

By then, the temperature had dropped more than 30 degrees since the start of the game. The fans were shivering. Many had left. I stayed, only hoping there was as much life left in the Royals’ lineup as there was in that fan who’d thrown the ball back on the field.

The Royals rallied for three runs in the seventh off a Baltimore left-hander named Ryan and the immortal Kerry “Freak Boy” Ligtenberg, acquired from Atlanta in the offseason. Ligtenberg puts up good numbers, but every time I’ve seen him pitch in person, he’s given up a busload of runs. He didn’t disappoint. By the time Freak Boy managed to put out the fire, the game was tied, 4-4.

D.J. Carrasco, one of the best of the Royals’ young flamethrowing relievers, held Baltimore hitless in the top of the 8th.

With flamethrowing Mike MacDougal warming up in the bullpen, Raul Ibañez led off the bottom of the 8th with a double, which brought up Royals bruiser Ken Harvey. Harvey overswung at a couple of pitches, then cranked an up-and-in fastball 378 feet against the wind over the left field fence, giving the Royals a two-run lead. “It’s Mike MacDougal time,” I muttered. Fans jumped up and started chanting, “Har-vey! Har-vey!”

But this was to become the neverending inning. Between Baltimore meetings on the mound and Kansas City hits, the bottom of the 8th drug on for what seemed like 30 minutes. I swear that by the time the inning ended, MacDougal looked like Tom Hanks in Castaway. And the Royals had a 4-run lead. There’s no reason to bring in your closer to protect a four-run lead.

Except so much time had passed since the last time Mike MacDougal pitched, the rookie probably had two kids in college. And, well, when you’re Kansas City, you have to give the fans something exciting to watch. Royals fans used to pay to see George Brett, no matter how the rest of the team was playing. And Mike MacDougal is the kind of guy fans want to see.

So in the top of the 9th inning, the bullpen door opened, and MacDougal ran onto the field. The scoreboard went black. “Mike” appeared on the screen in white letters as “Rock You Like a Hurricane” blared on the stadium’s speakers. The word faded to show MacDougal striking out a couple of batters. “MacDougal” appeard in white letters on a black screen, followed by still more strikeouts. An animated baseball trailed by flames lit up the scoreboard. A few more highlights from MacDougal’s spectacular 10 prior saves showed up.

By now the crowd was pumped. And so was the team.

MacDougal’s a bit wild, but that’s a big part of his mystique. The guy can throw 103 miles per hour. He generally tones it down into the mid-90s because his pitches have more movement at lower speeds. When someone can throw 100 miles per hour, he tends to be effective. But he’s more effective when nobody–not the batter, not the catcher, not even the pitcher himself–knows where the ball’s going to end up. It’s harder to hit when you’re afraid for your life.

MacDougal gave up two hits, but his control was on. He threw 21 pitches, and 13 of them were actually strikes. Despite the two hits, he managed two outs without giving up any runs. The final Baltimore batter fouled off a pitch that registered 46 miles per hour on the gun.

“Bull,” I muttered. “When MacDougal throws a paper wad in the trash, it clocks higher than 46 miles per hour.”

He struck him out on the last pitch.

And the stadium sounded like anything but a library.

My brief experience with a Proliant ML570 server

Last week, I built a Compaq HP Proliant ML570. Quad-CPU, 1.9 GHz Xeon, 2 gigs of RAM, and about 200 gigs’ worth of 10K RPM SCSI storage in two RAID arrays.
Yes, being one of the first people to see a $20,000 computer and being the one who gets to take it apart to install the optional add-ins is my idea of fun.

Opening it up shows this is a real, honest-to-goodness server, not just any old commodity motherboard slapped into a rack-mount chasis or a case with big casters on it. The memory is on a riser card. There are standby slots on the card, so that if as many as two DIMMs fail, the backups take over. The riser cards are hot-pluggable, but of course how the computer handles you hot-plugging the memory depends on the operating system.

Most of the PCI-X slots are also hot-pluggable. They’re 64-bit and run at 100 MHz.

Of course, the hard drives are hot-pluggable as well. Which brings up the RAID stuff. The drives are Ultra320 SCSI. There are two drive cages. The only Ultra320 RAID controller HP is currently offering (remember, this is May 2003 as I write) was a single-bus. Well, there’s a second bus, but it’s external.

If you put in two of these controllers, you get the full bandwidth of the bus but you can’t stripe across the buses, which you will probably want to do for performance, and almost certainly will have to do in the future for expansion. The only two-bus RAID controller HP was offering was an Ultra160. So we bought that. Under the best-possible circumstances, a single 15K RPM drive can’t quite deliver 80 MB per second. So with two of the newest 15K drives on an Ultra160 bus accessing the very front of the disk, you’d still have a little bandwidth to spare.

These particular Fujitsu 10K RPM disks deliver between 40 and 70 MB per second under optimal conditions. So the Ultra160 controller isn’t a huge liability. But we’ll be ordering more of these, and if HP delivers an Ultra320 controller that meets our needs, we’ll get one.

It runs Linux really, really fast. I compiled a kernel in about 4 minutes, without doing anything special to it. Linux was only on it for a few hours though, while I waited for its RAID controller to come in. Then I installed Windows 2000 and SQL Server 2000.

It’s nice. But with nearly 8 GHz worth of CPU power onboard, it had better be.

I took the plunge. I bought a Civic.

It’s silver. It’s a year old. It’s fully loaded. It rolled 10,000 miles while I was test-driving it. It’s an EX, not the miserly HX. I like miserly. But it’ll hold value better than an HX, and it cost me about $500 less. The difference between 40 MPG on the highway and 38 MPG on the highway just wasn’t worth it to me.
It’s a bit showy for me–it’s got a sunroof, I mean moonroof, whatever the difference is, for Pete’s sake–but hey, I’m still fairly young and it’ll be fun. And it’s costing me less than my Neon, so I can afford it.

And when I no longer have use for it–it’ll be a number of years–I can sell it to a wannabe homey and still get four figures for it. Apparently the Civic is a favorite model to put ground effects and move-to-the-music groovin’ shocks and other, umm, things. I won’t be finding out firsthand. But I did notice the trunk is certainly big enough for a bass tube. So I could turn my latest–and it’d better be my last for a long time–major purchase into a groovemobile and introduce south St. Louis County to David Crowder.

Hey, it’s mission work.

I’m kidding. I hope you know that.

Anyway, like I said, I’m hoping this is my last major purchase for a long time.

Good news for Optimizing Windows fans

O’Reilly wants to release my 1999 book, Optimizing Windows for Games, Graphics, and Multimedia , under an open content-style license. I’d love to see the thing released so it can gain widespread distribution, which it never really had.
The forms for me to sign are in the mail. My understanding of the license is that it permits changes, so long as the original author and publisher are cited. This will give me the freedom to make a few changes I’ve wanted to make since the book’s initial release, which I intend to take advantage of. I won’t spend months rewriting the manuscript, but I would like to incorporate some corrections I accumulated over the past three and a half years. Not to mention the tools that have changed version numbers since then.

I’m excited at the possibility. I’ll be sure to post an update once I know something. More and more obsolete technical books are getting released in some form or another, and this is a very good thing.