> Anyone who names a *file* with a question mark or an asterisk should
> simply be shot.

Sorry Austin, but that's just a completely asinine statement. First of
all, some might say such things about method names too! --which is what
these file names are based on. Secondly, let's back up a couple decades
and try statements like, "Anyone who names a *file* with more then 8
characters should simply be shot." You may think of filenames as
nothing more the special grepable_computer_ id keys, but the reality is
_people_ have to use them to give documents recognizable names. But
alas as far as I'm concerned we're still in the dark ages when it comes
to managing our data. Why it's not stored in RDBMS yet is beyond me.
Anyhow, this is taking us away from the real issue.

Thanks for the info on the limitations of Window's filenames. I did not
realize they still existed.

So now I have to change the file names. Great! Well, I'll let you all
know when the fixes are uploaded.

Any suggestions on naming these is welcome.

T.