home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
swCHIP 1991 January
/
swCHIP_95-1.bin
/
chip
/
carbcopy
/
install
/
acs.tx_
/
acs.tx
Wrap
Text File
|
1995-12-11
|
5KB
|
126 lines
Using Carbon Copy with an ACS
=============================
EBIOS/INT14-based ACS Packages
------------------------
Our testing with INT14-based ACS packages reveals that
many of them do not work properly with Microsoft Windows.
The most common problem is dropping characters when
running at speeds greater than 4800 baud. This is highly
dependent on your hardware and the specific ACS you are
using. Microcom recommends using an NCSI/NASI-based ACS
if possible. If your ACS provides both an INT14 API and
a NCSI API, you should use the NCSI API, which is always
more efficient.
If you must use an INT14-based ACS, the BUFFER14 utility
included with Carbon Copy will help to solve some of these
problems. BUFFER14 is designed to help minimize the
switching from protected to real mode when using character-
at-a-time INT14 packages with Windows.
The BUFFER14 TSR is designed to be loaded after your INT14
provider TSR is loaded. The TSR is loaded by typing
BUFFER14 <Enter>
at the DOS prompt.
BUFFER14 can be unloaded by typing
BUFFER14 /U <Enter>
at the DOS prompt.
The steps required in order to use BUFFER14 are:
1. Load your network software.
2. Load your INT14 ACS provider TSR from the DOS prompt.
3. Load BUFFER14 from the DOS prompt.
4. Load DOSHOST (optional - needed only for DOS remote control)
5. Start Microsoft Windows.
6. Start Carbon Copy for Windows.
Network Drivers for EBIOS/INT14-based ACS
-----------------------------------------
NDIS or ODI network drivers are highly recommended
on the user's workstation for proper operation of
EBIOS/INT14-based ACS software on a Novell network
with Carbon Copy. The monolithic (IPX.COM) versions
of Novell's drivers do not work well in this
configuration.
Using the "Start Connection" Parameter with an ACS
--------------------------------------------------
Microcom's testing has shown that most ACS products
work with "RING" Message, Carrier Detect, or Data
Received, but not with Ring Indicator. For most uses,
the default option ("RING") will work.
Using Carbon Copy with a LANexpress Server operating as an ACS
--------------------------------------------------------------
In order to dial-out through a LANexpress server, it
is necessary to load the NCSI.EXE TSR provided on
the LANexpress NCSI Utilities Diskette.
ACS Error Messages
------------------
The following messages related to the Carbon Copy ACS
drivers are not found in the User Guide.
"The specified Port or ACS Server could not be found."
This indicates one of the following:
1) The specified ACS is not running,
2) The specified ACS and/or Port doesn't exist,
3) If using Novell NACS, this may also indicate
the specified Port is not available.
Suggestion: Verify your ACS (NCSI/NASI) configuration is
correct and that the Server is running.
"The specified Port is not available."
This indicates that the specified port is currently in use
or has been disabled.
Suggestion: Reconfigure for another port or try again later.
"Your local ACS driver is not loaded."
This indicates the ACS interface driver included with
the ACS product and required to communicate with the ACS
is not loaded on your workstation.
NOTE: It is not always possible for Carbon Copy to determine
whether an INT14 driver is loaded because the INT14 API
does not support a method to get this information.
Suggestion: This driver must be loaded for Carbon Copy to
access the communications server. If you do not
have access to this driver, contact your network
administrator for access and usage or consult the
ACS user guide.
"Your BUFFER14 driver is not loaded."
This indicates the Carbon Copy file BUFFER14.EXE has not
been loaded. This file is required when Carbon Copy is
configured for EBIOS/INT14 communications.
Suggestion: Load BUFFER14.EXE after your local ACS INT14 driver.
"Communications port did not respond."
When using INT14, this error may occur if a COM port was specified
that does not exist on the local system. Use a COM port name that
is an existing COM port that is not currently in use by another
application.
End of File