perhaps my lat$systartup.com file is old ... but it does have:
$! ------------------------- Start LAT Protocol -----------------------------
$!
$! *** NOTE ***
$! If you have a system with multiple Ethernet/FDDI controllers, you may want
$! to create a link in this section of LAT$SYSTARTUP.COM before LAT is
$! started.
$!
$! When LAT is started on a system with multiple controllers, and no link is
$! is created, then the LAT driver will pick the first controller from the
$! LAN Data Structures as the default. This controller may not be connected to
$! the wire. LTDRIVER has no way of determining this condition. As a result,
$! it will not display an error message and LAT will hang.
$!
$! To define a link for LAT, do the following:
$! 1. Find out what controller is attached to the Ethernet/FDDI wire.
$! (In this example we will use EXA0)
$! 2. Insert the following command line before LCP SET NODE /STATE=ON command
$! below:
$!
$! LCP CREATE LINK 1ST$LINK /DEVICE=EXA0
$!
$! 3. If you have more then one controller attached to the wire, then
$! repeat the above command line, calling the next controller "2ND$LINK".
$! i.e. -
$! LCP CREATE LINK 1ST$LINK /DEVICE=EXA0
$! LCP CREATE LINK 2ND$LINK /DEVICE="xxx0"
$!
$! Where, xxx0 is the next controller attached to the wire
$! ...
$! etc
$!
$ lcp set node /state=on
Love it when Engineering puts comments inside the DCL command procedures themselves :-)
Verne
