System Requirements; Hardware; Software - 3Com ACCESSBUILDER 4000 Installation Manual

Risc-based multiprotocol, multiport networking devices
Hide thumbs Also See for ACCESSBUILDER 4000:
Table of Contents

Advertisement

3-2
C
3: C
HAPTER
ONFIGURATION
System
Requirements
U
T
A
SING
RANSCEND

Hardware

For best performance, the following system resources are recommended:
A 486 or better platform
A hard disk with at least 3.5Mb of available space
At least 8Mb of RAM
A VGA video card and VGA compatible color monitor or better (SVGA
recommended)
A network adapter card compatible with your TCP/IP or IPX software
If you plan to use this application with a laptop computer that does not
include a color VGA display, be sure the display supports at least 16 shades
of greyscale. Bear in mind, however, that you will lose certain
color-highlighted information, such as the async port status, etc.

Software

TABM 3.2 is compatible with a variety of Microsoft Windows® products
including Windows 3.1, and Windows for Workgroups 3.11.
Before installing TABM, be sure your network client software is functional on
your workstation. For IP networks, you should be able to ping a known host
on the network. For IPX networks, you should be able to attach to a host on
the network. Successful connection from the workstation on which you
plan to install TABM to the network is prerequisite.
IP Networks. This utility requires that you have Windows version 3.1 or
later installed on your PC, and a third-party TCP/IP stack (refer to the
AccessBuilder Release Notes for a list of currently supported products). Be
sure your TCP/IP stack is installed before installing the TABM application.
Within your TCP/IP stack, you will also need to set the TCP connections to a
minimum of 12.
Currently, the Windows socket library used by the TABM application to
communicate with the TCP/IP protocol stack is WINSOCK version 1.1. Refer to
your TCP/IP vendor's documentation to determine that your TCP/IP stack is
compatible with the TABM application.
Although many TCP/IP stack vendors support the WINSOCK.DLL, some do
not provide a WINSOCK.DLL with their standard protocol stack (i.e., Novell's
LAN Workplace). In this case, you must obtain the appropriate
B
M
(TABM)
CCESS
UILDER
ANAGER

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the ACCESSBUILDER 4000 and is the answer not in the manual?

Questions and answers

This manual is also suitable for:

Accessbuilder 4000 series

Table of Contents