home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 29 Fixes_o
/
29-Fixes_o.zip
/
dg130h1.dsk
/
DGNATIPS.TXT
< prev
next >
Wrap
Text File
|
1996-06-11
|
11KB
|
251 lines
DATAGLANCE SETUP SUGGESTIONS:
Following are key tips that relate to common DatagLANce setup problems.
If you have trouble understanding these recommendations, you should
consider contacting your local IBM representative to request consulting
support or further education. DatagLANce is a product that requires a
solid technical knowledge to understand and use.
Currently Supported Levels:
You MUST be at the current level of DatagLANce and OS/2 in order to
ensure correct function. As of June 1996, the current level of
DatagLANce is 1.30g. Levels prior to 1.30 have known adapter
compatibility problems and MUST be upgraded. You can determine your
level by running DGNAVER from the DGNA subdirectory. If you do not get
a response, your version is NOT SUPPORTED.
CSDs are on the PCCo BBS/FTP site, so you can obtain them by web browser
at http://www.pc.ibm.com. FTP is also supported at FTP.PC.IBM.COM. At
the above site, the files are located in the /pub/pccbbs/network
directory.
You can also FTP to IBM FTP.SOFTWARE.IBM.COM. Login as ANONYMOUS with
your email address as the password. Change directory to
/ps/products/dataglance/fixes/v1.x/dgnadisk for the DGNAGAD1.DSK ->
DGNAGAD4.DSK disks. Change directory to
/ps/products/dataglance/fixes/v1.x/dg130g for the DG130G1.DSK ->
DG130G2.DSK disks.
To upgrade to 1.30g - download/apply the CSD images DGNAGAD1.DSK ->
DGNAGAD4.DSK (4 disks). This upgrades from DG 1.2x to 1.30. Shutdown
the system. Then download/apply the SERVICE upgrade DG130G1.DSK and
DG130G2.DSK. This upgrades from 1.30 to 1.30g.
DatagLANce is known to work on many IBM-compatible machines, but the
user must insure that all the appropriate options are tested. Trying a
few does not mean that DatagLANce cannot work on any given machine.
CONFIG.SYS:
You should ALWAYS set up your machine with DatagLANce first and get it
working before trying to add support for other communication or
application programs. DatagLANce has specific requirements which may
conflict with other programs. It is assumed that if you require a
networking trace machine, you will dedicate a machine to DatagLANce, if
needed. Be careful to save your working DatagLANce CONFIG.SYS. If you
add something to the machine and DatagLANce does not work, you can use
your saved CONFIG.SYS to get DatagLANce functioning again.
It's possible you may need to reinstall DatagLANce from scratch.
DatagLANce always saves the orginal CONFIG.SYS as CONFIG.S00 and any
succeeding installations as .S01, .S02, etc.
One major incompatibility with DatagLANce is LAPS or MPTS--the standard
token-ring support. DatagLANce token-ring adapters do function as
standard token-ring adapters, BUT NOT AT THE SAME TIME. These are
mutually exclusive. If you have only one adapter to be used for both,
you MUST use two separate CONFIG.SYS files to boot either DatagLANce or
MPTS Token Ring support--not both. If you have two adapters, we
recommend that DatagLANce be identified as the ALTERNATE or adapter 1
with MPTS token-ring support using adapter 0. Again, get DatagLANce
working FIRST. Then add other applications one at a time afterward.
Setup:
Most 30xx errors, TRAPs, and hangs are fixed by hardware configuration.
Many times there are conflicts with IRQ settings or memory allocations
established by your machine. You may have to try all unique
combinations of IRQ and memory allocations to resolve these conflicts.
IRQs range from 1 to 15. Some lower IRQs are frequently reserved. If
you are having trouble locating an available interupt, try IRQs in the
upper ranges and even numbers. Memory allocations should be made in hex
4000 segments (x'4000')--normally in the range C0000 to DC000 range
(C0000, C4000, C8000... through DC000). There cannot be overlap. We
generally recommend that you use the ranges D0000 to DC0000 if
available.
DatagLANce IRQ and memory allocations are defined in DatagLANce adapter
device driver (DEVICE=DGxxx$.SYS ...) lines in the CONFIG.SYS. See the
READ.ME file for details on these parameters. (See further suggestions
below.)
RMVIEW: WARP utility that allows display of memory and IRQ use (RMVIEW
/MEM, RMVIEW /IRQ). It can be useful to debug IRQ, TRAP 000D, SHARED
BASE, etc. problems. Note that the values shown by RMVIEW are already
reserved by your machine--they may not be used by DatagLANce. NOTE also
that RMVIEW may not report all resources in use.
If you get a Trap D, your total BUFFERS and TRAFFIFO usage may be too
great for available memory. Try smaller buffers starting with the
default values to first get DatagLANce working, then try to get the
maximum size you want.
LAN Streamer adapters are not presently supported for use with
DatagLANce.
If you are connected to a busy network, and the screen and keyboard seem
to lock up, try disconnecting DatagLANce from the network and waiting a
few seconds. If it clears up, DatagLANce was too busy keeping up with
the network traffic to respond. Refer to Congestion Handling in the
DatagLANce User's Guide, p. 110 for more information.
To get DatagLANce working with Warp (avoiding hang, trap, and access
violations), apply the latest Warp Fixpack upgrade. Also, try changing
the IBM2SS01 to IBM2SS02 or vice versa in the BASEDEV statement of
CONFIG.SYS. The original WARP (known as Warp redbox) is not supported
with DatagLANce and must be upgraded.
IRQ and RAM Information:
For ThinkPad 350 with Ethernet: Try IRQ5, 9, 10, 14. IOBASE=240. IRQ=3
doesn't work.
Thinkpad 360 with Ethernet, try IRQ 5, 9, 10, 11, IOBASE = 240. IRQ 3
doesn't work.
ThinkPad 755. Try SHAREDBASE = D4000 for Ethernet. Default was D0000.
ThinkPad 755. PCMCIA Ethernet II appeared to be installed correctly,
but maintained a "not ready" status. The problem was solved by
installing PCMCIA support from the "ThinkPad Utilities" diskette and
changing the CONFIG.SYS to point those device drivers instead. (See LAN
Problem Determination and Monitoring Using DatagLANce, SG24-4546-00, pp.
12,13.)
ThinkPad 760. Remove any DatagLANce adapters from the Auto
Configuration Utility.
Interrupt Level 2 doesn't work with ISA machines. Use Level 3 or Level 9
which is the substitute for Level 2. An interrupt conflict on Level 9
does not necessarily mean the interrupt is unavailable.
Error Messages:
"The installation program did not find the IBM Socket Services device drivers."
If you are using OS/2 Warp, this message does not indicate an error. OS/2
has installed the device driver as a BASEDEV. Please hit Enter to proceed.
3044 Thinkpad 701 701C. Token Ring and Ethernet worked using Token
Ring: MMIOBASE=D0000, SHAREDBASE=D4000 IRQ 15. Ethernet:
SHAREDBASE=D8000 IRQ=11.
Error 2000 or "The adapter is not a DatagLANce adapter" in ThinkPad 755
with two token-ring cards. Put DatagLANce adapter in the bottom PCMCIA
slot.
Error 2001 with Thinkpads. Try SHAREDBASE = D8000, MMIOBASE = DC000.
Play with interupt level.
3044 with Thinkpad 755. Try Interupt 9 or 5, 2 doesn't work.
3044 with ThinkPad 755 or 755Cx. Do not use C0000 or D0000 for base
address.
3044 Thinkpad 701 or 701C. Token Ring and Ethernet worked using Token
Ring: MMIOBASE=D0000 SHAREDBASE=D4000 IRQ 15. Ethernet:
SHAREDBASE=D8000 IRQ=11.
3044 error. Make sure you're using a DatagLANce version of the
token-ring card.
Error 3044 or 3002 with Thinkpad 750CS. Make sure you're not using
Interupt 10--same as used by audio circuits.
3045 errors. Commenting out all lines in CONFIG.SYS that had IBMCOM,
CMLIB, LAN, or MPT (removes LAPS and CommMgr.) solved the problem on a
ThinkPad 755C.
Error code FFFF. Commenting out the CMLIB, IBMCOM, and LAN device
driver strings in config.sys solved the problem--maybe a conflict with
MMIO base address.
Error FFFF - Ethernet and Token Ring DatagLANce cards. Customer
had INTERFACE=0 on one device driver line, INTERFACE=1 on the other.
Setting both to 0 worked. INTERFACE should always be set to 0 unless
you have two of the same type of DatagLANce network (Ethernet or
Token Ring) cards, then one should be 1, and the other should be 2.
For Ethernet, the symptom is error code FFFF after Go!
Re-install software paying close attention to selected device driver or
edit CONFIG.SYS (line with DGEN0$.SYS) to point to the correct device
driver directory.
".....No IBM DatagLANce Token-Ring 16/4 Adapter found." during device
driver load.
Re-install software paying close attention to selected device driver or
edit CONFIG.SYS (line with DGTR0$.SYS) to point to the correct device
driver directory.
Miscellaneous:
New DatagLANce ISA token-ring adapters (PN 73G8308) are AutoSense adapters. To
use, the customer must use the LANAID diskette to set the card to MANUAL
and match interupts and SHAREDBASE with the DGTR0$ input.
LANAID is a utility that comes on a diskette with the Plug-and-Play
AutoSense adapters. DO NOT USE THE LANAID UTILITIES IN OS2 VIRTUAL DOS
MODE!!! It MUST only be run by booting the LANAID diskette.
LANAID is best run by using the command line version LANAIDC (To do
this, press PF5 to get a command prompt).
Syntax: lanaidc /pnp=n /lock=y /io=a20 /ram=d8000 /rom=d0000 /int=3
/ramsize=16 /busw=16 /auto=n (io=a20 is PRIMARY; ram, rom, and int
are variable but these are common).
In a machine with two autosense cards, LANAID must be used to set each
card independently with the other OUT OF THE MACHINE. One must be
IO=A20 the other IO=A24.
If using LANAID or LANAIDC to setup an AutoSense DatagLANce adapter, user the
IBMTOK.OS2 driver on the LANAID #2 diskette. It is the latest
(2/20/95). LAPS may install a later date IBMTOK.OS2 (3/95) which is
really an earlier mis-dated copy.
Repower the machine after each use of LANAID or LANAIDC.
If DatagLANce reports no activity on your network, consider that
DatagLANce may be seeing no traffic because: (1) there is no activity on
the LAN, (2) the port is disabled at the hub, (3) there is some wiring
problem, (4) your cable connecting DatagLANce to the LAN is defective,
(5) your adapter assigned to DatagLANce is defective.
Supported Adapters & Product Numbers for DatagLANce:
- IBM DatagLANce Token-Ring 16/4 ISA Adapter 73G8308
- IBM DatagLANce Token-Ring 16/4 MC Adapter 73G8309
- IBM DatagLANce Token-Ring 16/4 CC Adapter 73G8310
- Token-Ring Network 16/4 Trace & Performance 74F5121
Adapter
- Token-Ring Network 16/4 Trace & Performance 74F5130
Adapter/A
- IBM LAN Adapter for Ethernet TP 60G0605
- IBM LAN Adapter for Ethernet CX 60G0615
- IBM LAN Adapter for Ethernet 48G7169
- IBM PS/2 Adapter/A for Ethernet Networks 6451091
- IBM PS/2 Adapter/A for Ethernet Twisted-Pair 6451136
- IBM LAN Adapter/A for Ethernet 48G7171
- Credit Card Adapter for Ethernet 10base2 0933280
- Credit Card Adapter for Ethernet 10baseT 0933290
- Credit Card Adapter for Ethernet 10base2 0934330
- Credit Card Adapter for Ethernet 10baseT 0934331