[FADCA] RE: The Discovery Channel

[Charles S Schuman]

Good feed-back guys! I realize that most of the stuff I am throwing out 
here is console stuff and most Switches are operated remotely. The 
effort, at this time is to document this stuff so that future operators 
have a clear idea of their options.

1. Chuck Hast asked : What is the NODE file?
The NODE file is a generic name for the file that is converted by CONF2. 
Some name it <Address.Cnf> others call it <Call.Cnf> in any case it ends 
up as FPAC.TXT

2. It appears that when FPAC shells-out it issues a Call to Command.Com. 
If it is not in the FPAC Dir or Path a "Bad Command or File" error is 
displayed. 

 3. The discussion on  Port defaults...
      The Node file does indeed define the default User port. When I 
change the User port statment in the Node file I can see the port number 
change in the Stats Report. As Chuck pointed out - the User port and the 
Test port are Not the same. The term  "User Port" may be a term used 
only when refering to ROSE ports. In ROSE the RF port is the User Port  
because a User could not normally access the TNC's RS232 port. In FPAC a 
User can acccess All of the Ports via the RF ports of  the TNCs .

4.  John Green suggested that the Info texts worked as documented if 
Port 0 was the first active port.
    The convention seems to be - set this port aside for use with a 
co-located BBS. I re-configured my Switch  to use Ports 0 &1. The Info 
messages work the same as when the active Ports are 1 & 2.  In the 
Info.Txt file a P added behind a $Mx does Not replace the Info text 
defined in the Node file. I plan to delete the Node file's Info section 
and see what happens.

The numbered texts are Not accessable from the console.