1  IMPORTANT NOTES ABOUT USING ETDIAG 3.10


1.1  General

Here  is  collected  some  important and useful information about
using the Aminstal Utility (ETDIAG). It is preferred to read this
file before using ETDIAG.

Especially you may find help from here if you encounter  problems
in  using  ETDIAG  in either configuring the cards or running the
diagnostics.


 1. Running  ETDIAG  Utility  requires  MS-DOS  (version  3.3  or
    later).

 2. The current version of ETDIAG requires 375k of free memory to
    run (to configure and run the diagnostics).

 3. If  there  is not enough memory for full functionality of the
    utility, it is still possible to start ETDIAG  in  "configure
    only"  mode.  This requires that there is 350k of free memory
    available.

 4. If there is less than 350k free memory available, then it  is
    not possible to start the utility in the actual system.

 5. If  it  is  not  possible  to  start  Aminstal in your system
    (either not enough memory or a  "non-DOS"  platform),  do  as
    follows:

     1. Make MS-DOS system diskette (FORMAT A: /S).

     2. Copy  the  files  from  the root of the EtherTeam PCI/ISA
        Utilities Diskette to the created system diskette.

     3. Boot using the created system diskette and  start  ETDIAG
        utility.

 6. If  you run ETDIAG Diagnostics from the diskette, do not keep
    the diskette Write Protected (the diagnostics  will  write  a
    log  file  SAFET.LOG  to the diskette). Of course, do not use
    your original diskette but use a copy of it!

 7. Although booted from  hard  disk,  you  may  run  the  ETDIAG
    utility  faster  by copying the contents of the ICL EtherTeam
    PCI/ISA Utilities disk to a temporary directory on the system
    hard disk and start ETDIAG from there, for example:

       md c:\etdiag.tmp
       copy a:\*.* c:\etdiag.tmp

 8. It is not recommended to start ETDIAG from Windows DOS-Box or
    when the network is active. Instead, start ETDIAG from MS-DOS
    command prompt after boot.

 9. It  is  not  recommended  to  select  the  "Automatic"   Card
    configuration option. Use "Custom" configuration instead.

10. Typically  there is no need to configure the I/O-Address, DMA
    Channel or IRQ level of the card (the factory settings of the
    card apply both in Pnp and non-Pnp machines).

    The factory default settings of ICL EtherTeam ISA card,  when
    installed in a non-PnP machine, are the following:

      I/O Address = 02A0
      IRQ Level   = 10
      DMA Channel = 5

    When  installed  in  a  PnP machine, the actual resources are
    allocated to the card by the system (PnP BIOS,  Configuration
    Manager).

11. Be  careful  in  avoiding possible conflicts if you decide to
    set the card as a "Legacy Card" in a Pnp machine.  Especially
    this must be noted if you move the card to another machine.

    conflict  exists  (often you may see some conflict message on
    the screen already in the boot phase). For example,  you  can
    use the ISA Configuration Utility to verify that the settings
    of the EtherTeam PCI/ISA do not overlap with any other system
    card.

12. To   enable/disable   the   BOOTROM   Address,   the   Manual
    Configuration Mode must  be  (temporarily)  selected.  Do  as
    follows:

     1. If  originally  the  PnP Configuration is set, select the
        Manual Configuration. This  makes  BOOTROM  Address  menu
        accessible.

     2. Select  the  BOOTROM  Address  (or DISABLE). The selected
        BOOTROM address as such applies to  Manual  Configuration
        only.  In PnP Configuration the actual BOOTROM Address is
        allocated by the PnP System.

     3. Restore  the  PnP  Configuration,  or  leave   the   card
        intentionally in the Manual Configuration.

13. Do  not  blindly trust to the recommended (green) settings of
    the I/O resources. In some cases it may be that  ETDIAG  does
    not  detect  an  existing conflict and may suggest an invalid
    value.

    For example, the value 2A0 typically is a safe selection  for
    the I/O-Address.

14. If   the   network   does   not  start  correctly  after  the
    configuration (and soft boot), try hard boot.

15. If the network still does not start correctly, check that  no
    conflict  exists  (often you may see some conflict message on
    the screen already in the boot phase). For example,  you  can
    use the ISA Configuration Utility to verify that the settings
    of the EtherTeam PCI/ISA do not overlap with any other system
    card.