Différences

Ci-dessous, les différences entre deux révisions de la page.

--- documentation:hamradio:ax25:flexnet:index [2022/08/18 00:36] – créée f1sls
+++ documentation:hamradio:ax25:flexnet:index [2022/08/18 01:32] (Version actuelle) – f1sls
@@ Ligne 1: / Ligne 1: @@
-{{:documentation:hamradio:ax25:flexnet:rmnc_node.jpg?direct|}}
+{{:documentation:hamradio:ax25:flexnet:flexlogo.jpg?direct|}}
-====== RMNC (RHEIN MAIN NETWORK CONTROLLER) FLEXNET ======
+====== RMNC (RHEIN MAIN NETWORK CONTROLLER) & PC/ FLEXNET ======
 ===== DOCUMENTATION =====
   * {{ :documentation:hamradio:ax25:flexnet:dcc1995-flexnet-dk7wj-n2irz.pdf |An Introduction to FlexNet ‒ Gunter Jost (DK7WJ) FlexNet Gruppe Darmstadt & Donald Rotolo (N2IRZ) Radio Amateur Telecommunications Society ‒ TAPR DCC 1995}}
+  * {{ :documentation:hamradio:ax25:flexnet:iapc_06_digis.pdf |Commandes du RMNC FlexNet Version 3.3f ‒ IAPC, Genève, Suisse }} // ➜ https://www.iapc.ch //
+===== PC/FLEXNET =====
+==== Installing PC/FlexNet ====
+PC/FlexNet runs completely in the background as a TSR, that means that other applications can run simultaneously if there is enough memory left. However, the FlexNet infobox and the beacon generator may not be serviced under some circumstances, so that a dialogue with the node is impossible. This only happens when using badly programmed applications. QSO’s via the digi and the internode communication are not affected and should always work, whatever the PC has to do. Probably things get slowed down a little bit.
+Hard- and Software Requirements
+  * PC/XT, better AT with at least 512kB RAM - PC/FlexNet needs 200kB RAM, plus space for the L1 drivers and applications
+  * Operating system MS-DOS 3.1, better 5.0 or 6.2. Tests with MS-DOS 6.0 caused problems, we have no experiences with DR-DOS or other DOS versions. We recommend the use of MS-DOS 5.0 or 6.2, here most modules can be loaded into the UMB’s, provided there is enough memory available.
+  * IO-ports as necessary, according to the L1 drivers available
+Principally, a PC/XT will work. The gained performance mostly depends on the speed and the throughput of the L1 hardware drivers. PC/FlexNet supports several loadable L1 drivers. They are installed in the memory by simply calling them. This makes it easy to support any hardware. A "driver development kit" for interested developers is available from the author. The port numbers derive from the order of the driver installation. A single driver can support more than one port depending on the hardware. FlexNet, however, is limited to a maximum of 16 ports, the last port (15) is reserved for internal purposes. The port drivers are included on the distribution disk, depending on which drivers are available. For every L1 driver there is a appropriate *.DOC-file which explains the installation. By starting the drivers with the option /?, you will get a short help as well. Many people on different places are working on PC/FlexNet at the same time. Thus, there always new versions of kernels, drivers and applications. It is always a good idea to ask for new versions if there occur any problems. Changes, even in the installation procedure, may happen. Please read the *.DOC-files carefully!
+Installation and Configuration
+At the beginning, all files must be copied into a directory which should be in the DOS search-path. The start of PC/FlexNet should be done via a batch file because most of the L1 drivers need additional command line arguments. Occurring errors should abort the batch file. A sample batch file is on the distribution disk and can be easily changed to fit your needs.
+FLEXNET.EXE must be loaded first, then - if a node is to be installed -FLEXDIGI.EXE. Pure endpoints (Terminal, Cluster, BBS and so on) should not use it. Then the L1 drivers follow in the order you require. At last, the activation of the modules is made by the utility "FLEX". After doing this, no more port drivers can be installed.
+FLEXNET.EXE has an optional parameter, which specifies how many RAM may be used by FlexNet. Default is 15kb, but this lasts only for few QSO’s. The minimum for nodes with several ports is about 80kb. Depending on how many ports you use, you should experiment with this value. FlexNet loves memory more than everything else and runs best when it has about 30kb per port and additional 20kb for administration.
+To load the modules, generally (from DOS 5.0 onwards) you should use the "LOADHIGH" or "LH" command. It does not do any harm if there is not enough memory in the UMB; the file is loaded into conventional memory then. You still gain a little memory, since the environment blocks do not fragment the memory. You may check this by using the "MEM /D" command.
+Calling FLEX.EXE with the argument "/U" uninstalls all L1 drivers and removes FLEXNET.EXE from memory. As usually on DOS, no other TSRs should be loaded after FlexNet, otherwise your machine might crash.
+The first start of FLEXNET.EXE creates an empty parameter file. Port 15 is generally the interface for applications. The parameter AUTOSYSOP ("y") is set on this port, you should not change it. Now you should set the sysop secret code using "SYSNUM.EXE". The secret code becomes valid at the next start of PC/FlexNet. With "TNC.EXE" you can connect the node now and continue in setting the parameters. If you made a mistake, you could simply delete the file "FLEXNET.FPR" and begin again. "TNC.EXE" is a simple TNC emulation. With "<ESC> H <CR>" you get a short help. The node can be connected with "<ESC> C <CR>".
+The parameter setting of the software can be done now either by the TNC emulation or via remote control. Please check the documentation of the L1 port drivers. Like always on FlexNet, the rest of the parameter settings is very easy and can be finished in a short time.
+Before you decide to build a digipeater using PC/FlexNet now, you should think about the following: The RMNC is still the preferred platform for FlexNet, and something that does not work there will not work on the PC either, except from some bagatelles. The user shall find a uniform and well known (from the RMNCs) user interface. Who prefers the optimum of reliability and performance for minimal costs and maintenance should use the RMNC.
+//Source: http://www.torborg.com/ka2dew/packet/flexnet/manual/pc_flexnet.htm //

Outils pour utilisateurs

Outils du site

Différences

Outils de la page