
141
TNPP Limitations and Specifications
Multi-Node), so that they recognize that the pages we send are intended for them.
Find out this address or addresses, and tell us.
For all TNPP address values, please find out if they are being stated in hexadecimal (base
16) or decimal (base 10).
Software Configuration
Following are the differences in configuration between regular Multiport and TNPP
configurations:
There is a different image file, so CONFIG.CDS looks like this (example):
13 8 8tnpp8c3.img; card 13, multiport TNPP rev. 8c3
And OPARAM.CDS would look like the following example.
;
; Network 14: Physical Node ID = 0908h
;
; Set the Port attributes
;
; full 1200 accpt ukn dst
; dplx baud any route
0E 01 09 05 03 01 00 10 80 00 00 00 ;
0E 02 09 05 03 01 00 10 80 00 00 00 ;
;
; Routing information for known node IDs
; Node ID Route Accept
;Card Cnt Op to route to from Inertia
0E 00 0A 04 00 00 08 01 00 07 00 07 09 ; CAP CODE I/O
0E 00 0A 04 00 00 08 07 00 05 00 06 02 ; From rest of Net, to us
0E 00 0A 04 00 00 08 00 00 02 00 01 02 ; From us
;
; Incoming pages addressed to the physical node ID are always
; routed into the terminal.
;
; The next line should always be the last in the TNPP card settings
;
; TNPP params: Physical Node ID
0E 00 0A 17 09 08 00 00 00 00 10 00 04
Limitations of Single-node TNPP (Older Systems)
If you are running a version of ZPAGE that is older than version 310 then there are several
restrictions to TNPP on your system. TNPP prior to V310 ZPAGE could only do capcode
paging; ID paging was not supported.
You are restricted to directly connecting to just one node. Only a single incoming address
is accepted. Likewise, only a single outgoing address can be specified. In other words,
when sending a page FROM other equipment on the network TO the Zetron, the other
equipment must send to one and only one particular address.
When sending a page FROM the Zetron TO other equipment on the network, only a single
destination address can be specified.
Kommentare zu diesen Handbüchern