
Across the Boards
Communications Device Drivers
Section 5 - General Configuration and Usage Information
Page 198
cfSOFTWARE Confidential,
2000
5.13 CFXVXDT/CFXVXDS Usage
- ATB/Win16 Driver Access for ATB/DOS
Selected ATB/Win16 drivers can be used from ATB/DOS applications when the DOS application is running in
a DOS session under Windows 3.1 (386 Enhanced Mode only) or Windows 95. Windows NT is not supported.
The use of such a driver is mostly transparent to the ATB/DOS application, but some system setup is required.
The following steps should be followed when adding support for a CFXVXDT supported driver to an
ATB/DOS application:
- The inter-VM communications virtual device driver, VCFXATB.386, must be installed. Copy the
VCFXATB.386 module to a drive available when Windows is starting and add the following line
to the SYSTEM.INI, in the “[386Enh]” section:
device=
x:\dir
\vcfxatb.386
- Windows must be restarted to complete the installation of the virtual device driver.
- Run the program CFXVXDS.EXE. It is recommended that an icon or shortcut be created for
CFXVXDS. To start CFXVXDS automatically, a copy of the icon/shortcut may be placed in the
Windows “StartUp” group/folder. Alternatively, CFXVXDS may be started with a WIN.INI load=
statement or the appropriate registry entry in Windows 95.
The first time CFXVXDS is run, no visible action will occur, nor will CFXVXDS be listed in the
task list or on the taskbar. Running CFXVXDS a second time will bring up the CFXVXDS
“Control Panel”, which can be used to check the status of CFXVXDS, to enable or disable
debugging logs, and to shut CFXVXDS down.
CFXVXDS should generally be left running. It is a small module and will have minimal system
impact if it is not being used by an ATB/DOS application. CFXVXDS is the server module that
will load and manage the ATB/Win16 driver on ATB/DOS’s behalf.
- Copy CFXVXDT.DDL to the
Across the Boards
driver directory for the application.
- Review the search path usage for the application (
see below
).
- Modify the application to specify the correct driver number.
- Complete any configuration requirements for the new driver.
- Ensure that the DOS session in which the ATB/DOS application will run is enabled for
background execution and is not set for exclusive execution. This is the default for Windows 95.
Under Windows 3.1 the setting must be changed manually for the DOS session, or a new PIF must
be created with the correct settings (at the user’s discretion, one of the standard PIFs may be
modified instead).
- Run the application with the new driver.
Search Path Usage with CFXVXDT Supported Drivers
Basic
Across the Boards
search path processing is unchanged with CFXVXDT supported drivers, but the
distributed run-time nature of these drivers leads to several anomalies which must be compensated for by the
application. The search path used by the ATB/DOS application is passed to CFXVXDS when it is asked to load
the ATB/Win16 driver. Because CFXVXDS is running in a different VM, with a different environment, with a
different “current directory”, the same search path can be interpreted differently by the ATB/DOS modules in
the DOS application and CFXVXDS. This can lead to unexpected results when the various Windows modules
(CFXVXDS and drivers) are searching for files.
Komentáře k této Příručce