Scribd
Upload
34 views12 pages

Brickware For Windows: Release 5.1.1 July 5, 1999

The document provides release notes for BRICKware for Windows version 5.1.1, describing new features, bug fixes, and known issues. Key updates include a new Windows activity monitor, fixes to the configuration wizard, improvements to TAPI and CAPI support, and changes to ensure Y2K compliance.

Uploaded by

niko67
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
34 views12 pages

Brickware For Windows: Release 5.1.1 July 5, 1999

The document provides release notes for BRICKware for Windows version 5.1.1, describing new features, bug fixes, and known issues. Key updates include a new Windows activity monitor, fixes to the configuration wizard, improvements to TAPI and CAPI support, and changes to ensure Y2K compliance.

Uploaded by

niko67
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 12

BRICKware for Windows

Release Notes
Release 5.1.1
July 5, 1999

BRICKware for Windows Release Notes

New Software
Release 5.1 Revision 1
This document describes the new features, bugfixes and changes made to the
software BRICKware for Windows for Release 5.1 Revision 1.

BRICKware for Windows Release Notes

Upgrading BRICKware for


Windows

New Features in BRICKware for


Windows 5.1.1

2.1

Windows Activity Monitor

Bug Fixes

3.1

Configuration Wizard: More than One DNS Entry on


the PC

Configuration Wizard: Different Compuserve


Networks

Configuration Wizard: Incorrect Login String for


Compuserve II

3.4

Configuration Wizard: Filter Settings

3.5

Configuration Wizard: Software Version

3.6

DIME Tools in Continuous Operation Mode

3.7

Incorrect Format of Dates in DIME Browser

3.8

MS TAPI Client Management Program for TAPI 2.1

3.9

TAPI: PCs with Windows NT Could Hang

3.10

TAPI: Problems when Permanently Active

10

3.11

Problems with CAPI Applications

10

Known Issues

11

4.1

Error Message when Deleting Faxes with


DIME Browser

11

Configure Telephony Driver

11

3.2
3.3

4.2

BRICKware for Windows Release Notes

BRICKware for Windows Release Notes

Upgrading BRICKware for


Windows

Retrieve the current software BRICKware for Windows from BinTecs


WWW server at http://www.bintec.de (Section: Download). To reach the
section Download, click Solutions & Products.

We also recommend retrieving the current online reference BRICKware


for Windows (in Adobes PDF format) from the address noted above.

Deinstall the former version of BRICKware for Windows on your PC.


Install the current BRICKware for Windows by double-clicking the received
file. The setup program will guide you through the installation (described in
BRICKware for Windows).

BRICKware for Windows Release Notes

New Features in BRICKware for Windows 5.1.1

New Features in BRICKware for


Windows 5.1.1

2.1

Windows Activity Monitor

With BRICKware for Windows Release 5.1.1 the Windows Activity Monitor is
available. With the Activity Monitor, Windows users can monitor the activities of
a BRICK in an easy and clear way.
Information monitored covers

the transmission rate performed on a channel


the state of a channel
the number of open channels
the state of the BRICKs WAN partners
For a detailed description of this feature, see the current documentation BRICKware for Windows (available at http://www.bintec.de, Section: Download). To
reach the section Download, click Solutions & Products.
To support the Windows Acitivity Monitor, the Setup program of
BRICKware for Windows and the Configuration Wizard have
been modified.

BRICKware for Windows Release Notes

Configuration Wizard: More than One DNS Entry on the PC

Bug Fixes

3.1

Configuration Wizard: More than One


DNS Entry on the PC

If your PC with Windows 95 or 98 contained more than one entry for DNS and
you configured a BRICK via Configuration Wizard Quick Mode, a defective configuration file was generated.
This bug has been fixed.

3.2

Configuration Wizard: Different


Compuserve Networks

If you access the Internet with Compuserve, different networks can be used:
Compuserve (CPS), Compuserve II, Datex-J. When configuring a BRICK for Internet access with Compuserve via Configuration Wizard, the type of network
had to be specified by entering the telephone number. This was not always unmistakable, the access could fail sometimes.
Now the Configuration Wizard offers a drop-down list box where you select the
required network.

3.3

Configuration Wizard: Incorrect Login


String for Compuserve II

If you configured a BRICK via Configuration Wizard for Internet access with
Compuserve II, the Login string contained a wrong entry. So the connection to
Compuserve II failed.

BRICKware for Windows Release Notes

Bug Fixes

This bug has been fixed.

3.4

Configuration Wizard: Filter Settings

If you configured a BRICK via Configuration Wizard Expert Mode and selected
CAPI/TAPI Filter, but not NetBIOS Filter additionally, the resulting filter settings
were not complete. So the BRICK could not be accessed via LAN (e. g. using
telnet).
This bug has been fixed.

3.5

Configuration Wizard: Software Version

When configuring the BRICK not via the serial connection, but creating a local
configuration file (Expert Mode), a request for the BRICKs software version occurs normally. With the English version of Configuration Wizard, this request
was not displayed. So the Wizard could generate an incorrect configuration file.
This bug has been fixed.

3.6

DIME Tools in Continuous Operation


Mode

In rare cases, using DIME Tools in continuous operation mode a DIME Tools
crashed when the DIME Tools main window was minimized and many trace
messages were received.
This bug has been fixed.

BRICKware for Windows Release Notes

Incorrect Format of Dates in DIME Browser

3.7

Incorrect Format of Dates in DIME


Browser

DIME Browser did not display all dates (e. g. in fax storage, syslog) in a format
which was Year 2000 compliant.
This bug has been fixed, DIME Browser is Year 2000 compliant now.

3.8

MS TAPI Client Management Program


for TAPI 2.1

The Microsoft TAPI Client Management Program for TAPI 2.1 on a Windows NT
server did not work correctly with BinTecs Telephony Service Provider (TSP)
because of missing Permanent Line IDs.
This bug has been fixed.

3.9

TAPI: PCs with Windows NT Could


Hang

In rare cases, PCs with Windows NT with BinTecs Remote TAPI installed had
problems, for example they could hang when starting the system.
This bug has been fixed.

BRICKware for Windows Release Notes

3
3.10

Bug Fixes

TAPI: Problems when Permanently


Active

If BinTecs Remote TAPI was permanently active for a long time on a Windows
PC (more than one day), the Remote TAPI did not work any longer in some cases.
This bug has been fixed.

3.11

Problems with CAPI Applications

In rare cases, 32-bit CAPI applications under Windows NT with increased requirements of resources did not work error-free or caused a system crash.
This bug has been fixed, the performance of CAPI has been improved.

10

BRICKware for Windows Release Notes

Error Message when Deleting Faxes with DIME Browser

Known Issues

4.1

Error Message when Deleting Faxes


with DIME Browser

When deleting faxes in MIB table msgDirTable (fax storage), DIME Browser
cannot display the result immediately and an error message appears because
DIME Browser tries to read the line of the correctly deleted fax. Ignoring the error message and reloading the whole table (e. g. by pressing F5) will show the
msgDirTable without the deleted fax.
The SNMP Manager DIME Browser handles every MIB table irrespective of
type and content. So the inconvenience described above is not a bug but a correct reaction and will not change.

4.2

Configure Telephony Driver

Using CTI programs, it can occur in some cases that an error message appears
when trying to configure BinTecs telephony driver via these programs.
In this case, configure the driver by clicking the Windows Start button and then
Programs BRICKware CAPI and TAPI Configuration. Enter the required settings in the Remote Clients Configuration window that appears.

BRICKware for Windows Release Notes

11

12

Known Issues

BRICKware for Windows Release Notes

You might also like