home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Online Praxis 1997 March
/
OP2_97.BIN
/
cd-rom
/
treiber
/
itk
/
w95
/
pico221.exe
/
DISK1
/
ENGLISH
/
README.TXT
< prev
next >
Wrap
Text File
|
1997-01-27
|
2KB
|
62 lines
This text is subject to change.
1) Setup
Using CAPI protocols from other vendors:
Setup will bind a CAPI20 protocol to the ISDN board driver
automatically. If you like to use a different CAPI protocol
you have to launch setup with the command line option +A .
In this case you are responsible for binding a CAPI protocol
on top of the board driver yourself. If no CAPI protocol is
present, the board driver will not be loaded.
2) CAPI2.0 driver for Windows95
The Windows95 CAPI 2.0 Interface supports 16 bit
programs (CAPI20.DLL), 32 bit programs (CAPI2032.DLL)
and device drivers (vcapid.vxd). The DOS interface
(INT F1) is not supported in this version.
3) WAN Miniport driver for Windows 95 Version 1.0
All board specific configuration items must be adjusted via
the extra property pages provided by the ISDN board
configuration.
Following features are included with this version:
- connect as a remote node to a RAS server (either
Windows NT or Windows 95)
- allow dial in as a Windows 95 RAS server
- Since Microsoft supports only one ISDN connection at
a time under Windows 95 this driver it is not possible to
connect to more than one destination concurrently.
- Microsoft supports the dial-up to a RAS server with
PPP-Multilink support making use of 2 b-channels for one
logical connection. This has been tested.
- No support of multiple ISDN adapters; due to the above
mentioned restrictions, this is not very important, anyway.
- Support of "Accepted MSN" to specify calls to which
MSN should be accepted.
- Support of "Own MSN" to specify which MSN is calling
on generating a call.
Known Problems:
- The ISDN Accelerator Pack Version 1.1 seems to have a
severe bug concerning the IPX protocol. The actual
throughput with IPX on a file copy towards the remote
system is very close to 60 kBit/sec, while the netto
throughput is less than 40 kBit/sec. Since the same
behaviour can be observed with already certified drivers
from competitors and does not show up with other
protocols (IP, Netbeui) we believe that it is caused by a
bug in the ISDN Accelerator Pack.