[This may be a duplicate message.  My Fido host had a glitch]
[that prevented mail from going out for an unspecified      ]
[length of time, so I have to repost recent messages.       ]


Some senseless babbling from Leonard Erickson to Mike Ruskai
on 11-01-99  02:09 about File Systems...

 -=> Quoting MIKE RUSKAI to LEONARD ERICKSON <=-

 LE> That's nice. I'd like to be able to go one step farther and assign
a
 LE> *specific* shortname to a file without losing the long name. Even
if
 LE> it used up another directory entry. Then we'd be able to keep old
 LE> programs happy indefinitely and still use long filenames. Unix can
do
 LE> this, I just forget the command.

 MR> This is strictly speaking possible, but not taken advantage of by
the
 MR> OS. There's no required attachment between a file's directory name,
and
 MR> it's .LONGNAME extended attribute (which is how what Ian mentioned
 MR> above is done).

 MR> The PM file dialogs don't recognize the .LONGNAME attribute as a
 MR> filename, nor does DosOpen(), the API that opens files.

 LE> That reminds me. I was using an OS/2 UUdecoder that supported long
 LE> filenames (easy to find) and supported embedded spaces (hard to
find).
 LE>
 LE> Anyway, I discovered that when names exceeded a certain length, the
 LE> WPS directory display no longer recognized what *kind* of file they
 LE> were. Any idea what was going on?

 LE> These are mostly WAV files from Star Trek and Star Wars that people
 LE> named with the entire text of what's being said (definite
overkill).

 LE> Silly example:
 LE> "Jack and Jill went up the hill to fetch a pail of water, Jack
 LE> fell down and broke his crown and Jill came tumbling after.WAV"

I'm not aware of any length limitations, but the WPS does assume, for
the
purposes of file extension associations, that whatever follows the
*first*
period in the filename is the extension.  So, if there's a complete
sentence followed by a period in the name, the extension won't be WAV at
all.

If you associate WAV's with a separate program, you can kludge this
behavior to work with those files by adding the masks *.*.WAV,
*.*.*.WAV,
etc.

But if you're relying on the MMWAV class functions, then all you can do
is
manually convert those files to the MMWAV class from the WPDataFile
class.

It may be possible to automate this with REXX, but it wouldn't be
simple.

Mike Ruskai
thannymeister@yahoo.com

... I've tasted love and I want more.

___ Blue Wave/QWK v2.20

--- Platinum Xpress/Win/Wildcat5! v3.0pr2
114/477
147/2021