FlexNet Documentation |
|
This document describes features and the basic installation procedure for the PC/FlexNet for WIndows95 Add On Package.
An Overview
The draft, which finally is based on the Alphatest-stage is assembled as in the following: The FlexNet modules (kernel and driver) are still available as DOS-Versions, which means they still run under DOS. Therefore the istallation method remains the same for the time being. The program has to be installed under DOS, before starting Windows. However, all modules can adjust to the new conditions after starting Windows. Especially the Interrupt-Routines of the drivers are now "dual mode" which means, depending on the machine's condition, they are executed in Real- or Protected Mode, supported by a 32bit-virtual driver (VxD). Therefore the same performance as under DOS was obtained, concerning the interrupt latency. Basically, the drivers are compatible to the 3.3e-versions, which means they can be mixed. The desired performance under Windows can only be achieved with the new drivers. If using a DOS-installation, an update is also recommended. Aside from
the Windows support the kernel itself had only one change - 1 letter. It
now has the number 3.3f.
Upgrading to PC/Flexnet V 3.3f
Important changes concerning the Ethernet support are:
Installation of PC/FlexNet V3.3f under Windows 95
FlexNet is not intended to be used under older Windows-versions.Before installing FlexNet, the Windows hardware manager should be checked. The necessary resources for the FlexNet drivers (i. e. COM- and LPT-ports) should not show any conflicts. Any installed printers or modems will be disconnected by FlexNet anyway, this means, they should be deinstalled from the begin with. Basically the system has to run stable and the hardware manager should not show any problems before installing FlexNet, otherwise the results are unpredictable - you should not expect a more stable system after installing the package. The installation of the basic modules (kernel and hardware drivers) is the same as in DOS:
If everything works well, Windows can be booted. After the GUI has been activated, the FlexNet-Logo shows up for a few seconds, offering a menu. If an error is reported instead or additionally, fix it and try again. The taskbar should show the FlexNet logo. When clicking on it, a small
menu with various modules is opened. These modules should be self-explanetory.
They were not build to win a beauty-contest, they just offer some basic
functionality.
Applications
32bit applications are under development by several authors, so wait for many interesting new applications to be available in the near future. Important: the applications have to use different MYCALLs (or SSIDs)! Otherwise there may be conflicts in the outgoing QSOs. For incoming QSOs it would be undefined which application will get it. The trace mode (monitor) is still quite limited. Only one application
can use trace mode, all other applications should have trace disabled.
Here an improvement is under development which will be introduced together
with the 32bit version of the PC/Flexnet package.
Ethernet drivers
The command line parameters for ETHER32 are described in ETHER32.DOC. The protocol type for every channel is entered; for AXIP_UDP additionally the IP destination is needed. After starting Windows, the parameters can be checked or changed using "ETH32CFG". This can be done in a DOS box under Windows. The corresponding Windows sockets (WSOCK32) are needed for communication with the Ethernet. The own IP address and other parameters are entered in the network configuration (control panel). The corresponding link to the Windows networking kernel is internally
carried out by several modules: FLEXNET.VXD, FLXAP32.DLL
and FLEXCTL.EXE. They are loaded automatically, the "FlexNet Control
Center" performs as a helper application to link the modules.
Summary
As a beginner, first read the documents attached to the modules. It is necessary to boot DOS first and test the package. Only if everything runs without errors, Windows should be booted, and new features can be explored. This includes the TCP/IP-support. Then the Ethernet driver may be installed if needed. If following this order, possible problems can be pinpointed easier. If the whole package is installed at once it may be hard to find the source of a problem. 73' and have fun with all the new stuff |