RB> Then I tried to crashmail a Ezycom IBM bbs and it did not allow 
 RB> the file
 RB> names that M A X's BBS suport ?..

 RB> The file name that M A X's produced was  3.622.446.0.we0
 RB>                                                      ^^
 RB>                                                       |
 RB>                                                        \
 RB>                                                         Which is 
 RB> wednesday

 RB> This Breaks the 8.3 IBM limit, can someone help me on this 
 RB> problem ??

TrapDoor uses such filenames all the time, because as they are about to be
transmitted, they are renamed to the IBM 8.3 format.

The LEADING numbers (before the .WE0) are what used to be a net/node
difference.  But you don't need to worry about that, because basically
ANYTHING will work.  So simply renaming it to 12345678.WE0 will keep the
other end happy.

Your only problem now is to coax Max's BBS into sending it.

You'll need to rename not only the actual file itself, but also to edit the
the .FLO file which lists this filename to reflect the new name you give
it.

EG if you start with 3.622.446.0.we0 and 3.622.446.0.FLO in the outbound,
rename the .WE0 file to 12345678.WE0 and then change the entry in the .FLO
file to 12345678.WE0.

Max's BBS can't possibly be THAT bad however?  Surely files ARE renamed as
they are sent to 8.3 names?????  The thing IS _SUPPOSED_ to be compliant in
theory, and 8.3 is a prerequisite for that!

  Mea Culpa,
 Peter Deane

--- Plutonic 2.15 #1