[FADCA] Info Text

John H. Green [email protected]
Sun, 04 Apr 2004 22:00:02 -0400


Hi

Charles S Schuman wrote:

> You may Not eliminate the Text Block from the Node file. If you do the 
> compiler gets all weirded-out and starts bouncing off the walls. If 
> you �null� the text, you get a empty Info text in responce to the I cmd.
>
> I'm still unable to get the Info.Txt message to replace the Node.Cnf 
> Text Block message.
>
> Has anyone used this feature?

I set this up here and it worked fine, again you have to be an incoming 
connect on port 0 for this to work. You will need to change the cfg file 
to make port 0 an operating port, com=1 change to com=0, nul=0 to #nul=0 
and #nul=1 to nul=1 and of course add the ,P to the message you want to 
use in the txt file.  You can tell what port you are connected on by 
connecting to the switch and entering ux - the results should show you 
connected as a ax25 user on port x.

I'm gonna hazard a guess that you are making some of these changes in 
fpac.cfg and node.txt, if so, runfpac.bat is doing you in.. :-) . The 
following shows the part is runfapc.bat that starts fpac:

:fpac
cd %fpacdir%
copy %NODE%.cfg fpac.cfg
copy %NODE%.txt info.txt
copy %NODE%.pwd fpac.pwd
conf2 %NODE%.cnf
call %node%
fpac
ipl
goto start

The copy %node%.cfg and .txt statements are going to overwrite any 
changes made to the base fpac files.  This is why I always make any 
changes to the npannx.* files and let the system take care of the rest.. 
Also, if your discussions use the napnnx files it will be easier for 
others to follow along, I for one, don't even think in terms of 
node.txt, etc - too much for the ole brain to handle.. :-)
73  John

>
>
> _______________________________________________
> FADCA mailing list
> [email protected]
> http://mailman.qth.net/mailman/listinfo/fadca
>