[Fwd: Re: [FADCA] The Discovery Channel]

[fadca@mailman.qth.net]

John H. Green wrote:
> One more time
>     I set the send to be text only..
> 
> 
> Hi All
> See below
> 
> wchast@utilpart.com wrote:
> 
>> Charles S Schuman wrote:
>> 
>> 
>>> Some of the problems discovered while varifying the FPAC docs:
>>> 1. FPAC won't Shell out w/ F9... Apparently Command.com must be in
>>> the FPAC directory. 
>>> 
> Works here without command.com in the fpac directory.  I end up in the
> c:\fpac dir. Maybe something to do with the different dos you are
> running? I tried several thing here and it works no matter what I
> remove from the autoexec.bat or config.sys. You might try adding c:\
> to the end of the second path statement in the autoexec.bat file.
> Try looking at the memory control blocks by entering mc - I have
> command.com copy #1 in the owner column on lines 3,5 and 6. Maybe a
> link is missing somewhere.
> 
>>> 2. The Information texts are not displayed according to the docs.
>>>      Cmd I returns the INFO text from the NODE file.
>>>      Cmd Ix  returns the INFO numbered texts from INFO.TXT.
>>> I tested this connected to the NODE  - with the USER port set to 0 1
>>> & 2. The P (Primary Message) behind a message does not replace the
>>> message defined in the NODE file.
>>> 
> User port that is set in the cnf file has nothing to do with it - you
> have to connect on what fpac thinks is port 0. This must be configured
> in the cfg file as com=0   The files I sent you have com=0 commented
> out so port 0 is not used.
> What is the node file - I don't have one here in the Labelle switch?
> Usually the i returns the info from the cnf file or if you are on
> port 0 and have a P in the txt file ($M0,P) you get whatever message
> the P in on - could be $M1, 2 etc.
> 
>>> 3. I have discovered two un-documented commands K & MS.
>>>    K appears to be the same as C.
>>> 
>>> 
>> 
>> C is a level 2 connect command, you are using the switch as a
>> overloaded terminal program, and indeed your connect is either
>> to a station on the default port or on the stipulated port. i.e.
>> c k0zxf (connects to k0zxf on the default port)
>> c 3:k0zxf (connects to k0zxf on port 3)
>> 
>> 
> If you are on the fpac console and try to connect to port 3 this way
> you will be trying to connect to 3:k0zxf on the default port. To use
> port 3 you enter pt 3 and then the c k0zxf. It's really crazy, but
> that's the way the French did it..
> The c 3:xxx is used for users to connect out on a different port than
> the default port when connected to the switch.
> 
> By the way, I used to think that the pt command set the default port
> but this is not the case. The default port for users is set by the
> userport = x  statement in the cnf file while the pt command sets the
> outgoing port for console connects.
> The cnf file also has a default port x statement which doesn't seem to
> do anything. All mine are set to 0 and we, for the most part, are not
> using port 0 (the exception being a collocated bbs). Since the cnf
> file is generated by netmgr and was originally used for rose it might
> be a leftover..
> 
> 73  John
> 

That did it!! it was the html, best to turn it off anyhow. There are
a whole list of reasons not to use HTML, and one of this is that most
list will barf on it. This is the one that is appended to the list
server mime stripper;
http://www.expita.com/nomime.html


Chuck Hast
-------------------------------------------------------------------------
To paraphrase my flight instructor;
"the only dumb question is the one you DID NOT ask resulting in my going
out and having to identify your bits and pieces in the midst of torn
and twisted metal."


*****************************************************************
This e-mail and any files transmitted with it are confidential and are
intended solely for the use of the individual or entity to whom it is
addressed. If you have received this transmission in error, please notify
the sender immediately and destroy any hard copies you may have printed and
remove all copies of the e-mail from your hard drive. Opinions, conclusions
and other information in this message that do not relate to the official
business of Utility Partners, Inc shall be understood as neither given nor
endorsed by it.

Visit us on the web at http://www.utilpart.com 
*****************************************************************