For those of you who want a friendlier launcher for DOSBox, Radnor may be just what you are looking for.

Sveinbjorn brought it to my attention when asking about my optimized DOSBox binary distribution. In his own words:

Radnor, my launcher for DOSBox, is pretty much done and can be downloaded at http://sveinbjorn.vefsyn.is/radnor. I’ve bundled your binary with it and it runs like a charm.

Thanks for your work, Sveinbjorn – many MacOS X DOSBox users rejoice!

I’ve managed a few moments to update my build from Mortis’ 0.8.9 release. You can download it, as always on my software page.

After a few years deterred in California, I’ve made it back to Reno. The weather is exactly as I remember; the highways seem to be under perpetual construction, which is certainly a sign of growth.

Ah well, it’s nice to be back home. There’s certainly more of a technological industry, but I must admit that I do miss the saturation of geekiness of California.

I was posed the following inquiry: “Basically I have 6 boolean variables and I need to document every possible true/false combination. I’m having difficulty finding a basic method to write all combinations out without repeating.”

I offered the following solution (yes, in PHP):

for($var = 0; $var <= 63; $var++) { echo str_pad(str_replace(“0”, “F”, str_replace(“1”, “T”, decbin($var))), 6, “F
”, STR_PAD_LEFT) . ”\\n”;
}
?>

It simply counts from zero to 64, prints that in binary, and I have it manually toggle 0 to ‘F’ and 1 to ‘T’ for true/false. The str_pad is called due the fact that the first few numbers will ‘not fit’ with the diagram properly, and there’s no sense to manually fill it.

The reply I was given to this was: “Brilliant, and insane – yet, it’s in PHP, so I’m beside myself.” Gee, thanks. :)

I often find myself curious as to what libraries and frameworks a program relies upon. Thanks to a recent entry by Marc Liyanage, I’ve managed to make this task rather automatic, lifting most of his little command verbatim.

Note that this is a ZSH style alias, but should be trivial to make work with the shell of your choice:

libdepends () { echo Dependencies for: $* otool -L $* | cut -f 1 -d ’ ’ | grep -v ’:’ | xargs -n 1 ls }

When called, you’ll get something similar to the following:

%libdepends =mutt Dependencies for: /usr/local/bin/mutt /usr/lib/libSystem.B.dylib /usr/lib/libssl.0.9.7.dylib /usr/lib/libcrypto.0.9.7.dylib %

Pretty useful, huh? The way it’s written, you’ll get an error (from ls, of course) if any of the shared libraries do not exist. Thanks for this tip, Marc!