[Prev][Next][Index][Thread]

Re: E/L (and possibly others) 1.99q9 BUG: will not recognize



On Fri, 15 Mar 1996 18:20:15 -0500, Ian Viemeister wrote:

snip...

>I guess when saving to the unix filesystem, the filename is passed
right 
>thru, but when saving to an hfv, it uses the real HFS filesystem.
>
>>There's either one of three things wrong here:
>>
>>a) "FAQ- Running Executor under FreeBSD" is NOT a valid Mac filename,
and
>>   either Word and/or Executor was at fault in NOT telling me "hey,
that's
>>   not a good filename" when I saved it.
>
>That sounds like it

snip...

>Sounds like this would happen on Linux, FreeBSD or Win95 (does E/D
under OS/2 
>support LFNs?}

Unfortunately DOS under OS/2 is still restricted to 8.3, and the use of
a file-system translator such as AMOS only appears to work from a
natively-booted DOS (but that may have changed recently). The bottom
line is therefore 'no'. As reported by others above, the 31-char Mac
filename is the theoretical upper limit. (I believe Mac files can have
a '0' or null filename - how the Mac filesystem copes with that I have
no idea.)

Cheers,

Alex Newman