
APAR= II10307
NETSOFT NS/ROUTER V2 WINDOWS 95 32-BIT TWINAX CONNECTIVITY


** Last updated 06/17/97 **

Client Access Windows 95 32-bit Twinax Connectivity Information

Contents:

1. Description
2. Migration
3. Installation
4. Configuration
5. Non-IBM/OEM Twinax card support
6. Compatibility with IBM Personal Communications for Windows 95
7. Version levels
8. Known problems
9. Error Message Descriptions
10. Debug Tips


1. Description
==============

New Windows 95 32-bit Twinax support is now available
in the following Client Access service packs:

V3R1M0  SF39053 - initial release
V3R1M1  SF39059 - initial release
        SF40081 - added translated installation and readme
                  for French, German, Italian and Spanish.
V3R1M2  SF39220 - initial release
        SF40828 - added translated installation and readme
                  for French, German, Italian and Spanish.

This replaces the original Windows 95 twinax support.

These drivers can be used with the following Twinax adapters:

 -  The Enhanced 5250 Display Station Emulation Adapter
    (Part/Number 30F5383 - US)
    (Part/Number 30F5384 - EEC)

 -  The 5250 Emulation Adapter/A
    (Part/Number 64G3494 - US)
    (Part/Number 64G3496 - EEC)

 -  The IBM System 36/38 Workstation Emulation Adapter/A
    (Part/Number 69X6279)

 -  The 5250 Emulation PCMCIA Adapter
    (Part/Number 92G5360 - US)
    (Part/Number 04H0103 - EEC)

 -  The IBM 5250 Emulation PCI Adapter
    (Part/Number 88H0207)

   THIS TWINAX SOFTWARE UPDATE ONLY APPLIES TO THE WINDOWS 95
   OPERATING SYSTEM. SUPPORT FOR WINDOWS NT IS PROVIDED WITH
   THE BASE V3R1M2 CLIENT ACCESS PRODUCT.

2. Migration
============

The twinax installation program will handle migration from the
existing support to the new 32-bit support. The following will
be migrated:

CONFIG.SYS
 The following entries will be optionally removed:
 EMM386

AUTOEXEC.BAT

 The following entries will be removed:
 E5250AH, NSTWINAX, ENB5250, WSEAH, LDMCAAH


SYSTEM.INI

 The following entries will be removed from the  386Enh
 section:
 VDTWINX.386, VDNSWQ.386, VDNSWQ.VXD, VDNSWQHEAPSIZE


The following will not be migrated:

CONFIG.SYS

 If DOS Point-Enablers were used make the PCMCIA twinax card
 work, these will have to be manually uninstalled. Also, if
 the PCIC/PCMCIA controller was disabled, this will have to
 be reenabled under the Device Manager.

SYSTEM.INI

 If an EMMExclude=xxxx-xxxx entry was added to the  386Enh
 section to reserve memory for the twinax card, this entry
 will have to be manually removed from the SYSTEM.INI file.

Device Manager - Computer -  Reserve Resources

 If you have previously reserved twinax card resources
 (IRQ, PORT, MEMORY) in the Device Manager, you will need to
 manually remove these resources from the reserved resource
 list.

3. Installation
===============

After you have the installed Client Access Service Pack, a
new subdirectory with the updated software will be created on
your computer. This TWINAX directory will be created under the
directory in which Client Access was installed.  The path is
normally "C: Program Files IBM Client Access twinax", where C:
is the drive where Client Access is installed.  Print off the
README.TXT in the TWINAX directory.  Follow the README.TXT
instructions to go through the installation process
(INSTALL.EXE).

The installation procedure only needs to be run once. To change
the twinax card resource settings after install, use the Windows
95 Device Manager located on the properties page of the
"My Computer" desktop icon.

Always check the Device Manager for any hardware resource
conflicts after installation and reboot.

The installation program always creates a log file in the root
directory of the boot drive (usually C: ) called IBM5250.LOG.

All files that are modified during installation will be backed
up.

To Un-Install, use the installation program (INSTALL.EXE) and
select the Un-Install option. This option will remove the
twinax drivers from your hard drive and remove any references
to these drivers from your SYSTEM.INI file. No changes will be
made to your hardware configuration. Use Windows 95 Device
Manager to remove the Twinax card hardware configuration.

If the Client Access product or the Client Access service pack
are un-installed from the PC, the Twinax directory will remain.
This will allow you to use the un-install option of the Twinax
installation program if necessary. The Twinax directory can then
be deleted from your PC.

4. Configuration
================

After installation and reboot, the twinax card will appear in
the Windows 95 Device Manager located on the properties page of
the "My Computer" desktop icon. Using Device Manager, the
resource settings (IRQ, PORT, MEMORY) can be viewed and
modified.

5. Non-IBM/OEM Twinax card support
==================================

If using a non-IBM twinax adapter, it must be 100% hardware
compatible with the an IBM adapter that is supported.
Contact the adapter manufacturer for information,
instructions or assistance.

Non-IBM Twinax cards that are not 100% hardware compatible and
require a OEM Twinax device driver are NOT supported with
this new Windows 95 32-bit Twinax support at this time. The
testing of OEM twinax cards is in progress, check back here for
the latest information on this topic.

6. Compatibility with IBM Personal Communications for Windows 95
================================================================

One of the device drivers for this new support (PDLWATWV.VXD),
is also shipped with IBM Personal Communications for Windows 95
(PCOMM). The PCOMM version of the driver is NOT compatible with
Client Access. If you install PCOMM after installing the new
Windows 95 32-bit Twinax support, the Client Access version of
PDLWATWV.VXD located in the WINDOWS SYSTEM directory, will be
overlayed with the PCOMM version, and Client Access SNA twinax
support (NetSoft) will no longer work. To correct this, copy
the PDLWATWV.VXD file from the Client Access TWINAX directory
to the WINDOWS SYSTEM directory.

7. Version Levels
=================

  Version  Service Pack  PDLWATWV.VXD  VDNSWQ.VXD  INSTALL.EXE
  -------  ------------  ------------  ----------  -----------
  V3R1M0     SF39053       01.063        01.063      1.13
  V3R1M1     SF39059       01.063        01.063      1.13
  V3R1M1     SF40081       01.063        01.064      1.26
  V3R1M2     SF39220       01.063        01.063      1.13
  V3R1M2     SF40828       01.064        01.064      1.26

8. Known problems
=================

 A. The Client Access Windows 95 32-bit Twinax support is also
    shipped on a diskette with some new IBM Twinax cards. This
    version will not work when a IPX/SPX protocol stack is
    installed. Install the Client Access service pack listed
    above to resolve this problem.

9. Error Message Descriptions
=============================

The Client Access Windows 95 32-bit Twinax support will display
message boxes for errors that occur during the initialization
of the twinax card. The following is a list of possible messages
with error recovery information. The message box caption will
be "CA/400 Twinax VxD".

- Open Twinax adapter failed. rc=000000xx

  01 = Card not found. Check card installation. Check card type
       in Device Manager. Check for resource conflicts in
       Device Manager.
  02 = Memory range conflict. Check for resource conflicts in
       Device Manager. If no conflicts, try a different memory
       range for the twinax card.
  03 = Card hardware error.
  04 = Driver file not found.
  05 = Another twinax driver is already active.
  06 = Internal MAC driver error.
  10 = Non-IBM/OEM driver could not be loaded/found.
  15 = Port range conflict. Check for resource conflicts in
       device manager. If no conflicts, try a different port
       range for the twinax card.
  16 = Could not virtualize IRQ. Check for resource conflicts
       in device manager. If no conflicts, try a different IRQ
       for the twinax card.
  17 = Cable hardware error. Check cable connections. Replace
       cable/connectors.
  18 = Invalid data from AS/400. Check PTF level of AS/400.
  20 = Invalid data during disconnect.

- Open Twinax station failed. rc=000000xx

  FF = No poll from AS/400. Check twinax card and cable
       connections. Check AS400 line/controller/device.
  FE = Parity error. Check twinax card and cable connections and
       retry.
  FD or
  FC or
  FB = Possible station address in use or station timeout.
       Check station addresses and retry.

- Error loading PDLWATWV.VXD driver. rc=000000xx

  02 = File not found. The drivers must be in WINDOWS SYSTEM dir
  05 = Access denied. The file is in use by another application.

- Twinax adapter driver error. rc=AAAA000x

  An internal error occurred in the drivers.

- NetSoft Eventlog messages

ÕTwinax-03þ = Invalid router config, delete and recreate config.

ÕTwinax-16þ = No card was found in the registry. Run install.exe
              VDNSWQ.VXD not in SYSTEM.INI. Run install.exe
              TSR support is still enabled. Run install.exe
              The twinax router already running. Restart the pc.

10. Debug tips
==============

If the pc has ever had any 16-bit Netsoft product installed,
verify that it has been completely removed.  If any of the
16-bit NetSoft for Windows 3.1 code is still on the PC,
Client Access for Windows 95 may fail to connect.

Whenever possible, install the Twinax card on the bus first.
As the Plug and Play feature starts looking for devices,
it searches in bus order.  Plug and Play handles legacy
devices (non-plug and play devices like most twinax cards),
much better when it sees and configures them before plug and
play devices.

When debugging a hardware conflict, remove all adapters
from the PC and then add them in one-by-one (starting
with the twinax card) watching the Device Manager each
time a card is loaded.  If the Device Manager ever lists
an exclamation point next to a device, resolve that conflict
before going further.

If you can connect on a cold boot consistently, but fail
on a warm boot, check IRQs for conflict.

Don't forget to verify that the AS/400 is ready for the
connection.  If QAUTOCFG is not turned on, the 5150 devd
must be varied on.  When in doubt, turn on auto-configuration,
delete the devd and let it recreate.  This can be done also
for the APPC ctld and devd.  But, to do this, you must vary
off the lind that the ctld is attached to (this is usually
QTDLxxxxx).

Keywords:  netsoft-net-soft-w95-win95-infoapar-twinax-twinaxial
           cawin95-ca400winopt-nsrouter-vxd-device-ipx

