Hi Mike,

     About "Fdsz" of March 18:

MP> The BBS program is running without a fossil...
MS> ...the lack of ~FOSSIL~ support is like hoping to use an electrical
MS> applicance with no electrical outlet nearby.
MP> ...problem was caused by a PATH statement...  ...on a multi-node...

     Thank you so much for taking the time to keep me informed in such a
way, i received your explanation like a breeze of fresh air - especially
this one where the title and content concur naturally!  8-)  I'm sincere
writing that this later post put me in a good mood, it's RIGHT ON TARGET
as i didn't even have to read it twice to gather the meaning:  yours was
about something i'm familiar with and it felt a lot like you sang an old
favourite tune for me!...  8,-)  Oh my, i sense a tear coming because of
this unexpected sample of poetry!!!  I hardly seek On-Topic reactions by
posting answers these days (neither do i expect much) but thanks anyway.

                                  8^)

MP> Pointed it to the correct one, and all is now well.

     Good!  :-)  So, instead of pointing the external protocol driver at
a missing ~FOSSIL~ port, the `ZMoDem' stream would have been routed to a
dead end because your driver wasn't loaded at all - which is like having
the electrical cord and outlet ready but without an electrical appliance
attached, to continue with analogies...  Well, it sounds classic enough!

                                 Warm salutations and thanks again,  ;-)

                                 Michel Samson
                                 a/s Bicephale
                                 http://public.sogetel.net/bicephale/


... The Technology i used?  No `COM/IP', no `SIO/VMoDem' and no mouse!!!
-!- MultiMail/XT v0.45 + `MS-DOS', `EtherLink', `RLFossil' & `MS-Kermit'

--- Maximus/2 3.01