
Across the Boards
Communications Device Drivers
Section 1 - Device Driver List
Page 6
cfSOFTWARE Confidential,
2000
(5) An ATB/Win32 driver named *3.DLL exists.
NOTE
: Unless note (T) is also specified, this driver can be loaded by ATB/Win16 via the
CFXNTGT thunking module.
See Section 5.8 for additional information.
If a Win16 driver of the
same driver also exists (“2” or “3”), the Win32 driver can be loaded via an alternate device
name/number if note (H) is also specified.
(6) An ATB/DOS extended DOS driver named *.DLL exists.
(9) This driver number/name assigned to ATB/Unix and ATB/Mac implementations. (These drivers
are not available as standard components. Contact cfSOFTWARE for additional information.)
(D) This ATB/Win16 driver can be loaded by ATB/DOS via the CFXVXDT/CFXVXDS mechanism.
See Section 5.13 for additional information.
(H) When loaded by ATB/Win16, this ATB/Win32 driver must be referenced by another XAPI driver
number or Dialog name.
See entries with note (W), and Section 5.8 for additional information.
(S) This driver can support both structured field and non-SF modes of operation. A second XAPI
device number is assigned for the alternate mode of operation.
(T) Unlike most ATB/Win32 drivers, this driver cannot be loaded by ATB/Win16 via the CFXNTGT
thunking module.
(W) This XAPI driver number and Dialog name is used to access a Win32 driver normally assigned a
different device number.
See entries with note (H), and Section 5.8 for additional information.
(Y) Special use driver. Contact cfSOFTWARE for additional information.
(Z) Driver unavailable as of 02/01/00. Contact cfSOFTWARE for additional information.
Comentarios a estos manuales