Subj : Ezycom & OS/2
To   : Leonard Erickson
From : Mike Tripp
Date : Tue May 13 2003 10:29 pm

Hello Leonard!

13 May 03 08:04, Leonard Erickson wrote to Mike Tripp:

 LE> 0 Netware
 LE> 1 NETBIOS
 LE> 2 TCP/IP

 LE> 0 Netbios
 LE> 1 Netware
 LE> 2 TCP/IP

 LE> Booted ok, but still couldn't connect to Netware server or to the
 LE> Internet.

0 Netware
0 TCP/IP

is what is working here for years now, but it has worked with 0 and 1 for 
logical adapter numbers in the past.

A few more possible hacks/clarifications:

Clear the slate by removing everything in reverse order...ie, each protocol, 
and then the NIC.  Then go through the process of adding NIC, add Netware 
Requester, configure Netware Requester, add TCP/IP.  Don't just play with the 
"change number" button to give them new logical numbers.

Be sure to "edit" the Netware protocol settings and put "no" in the token-ring 
fields and "yes" in the ethernet fields for frame-types.  They like to default 
to just the opposite of what they need to be sometimes.  Manually typing in the 
MAC address coule make or break with some of the older 8-bit ISA SMC and 3Com 
cards, so you can always try that while you're in there if you've written it 
down somewhere.  Assuming an ODI NIC driver rather than NDIS, you should end up 
with an \IBMCOM\PROTOCOL.INI that looks something like:

=== Cut ===
[PROT_MAN]

   DRIVERNAME = PROTMAN$

[IBMLXCFG]

   ODI2NDI_nif = ODI2NDI.NIF
   TCPIP_nif = TCPIP.NIF
   E100BEO2_nif = E100BEO2.nif

[ODI2NDI_nif]

   DriverName = odi2ndi$
   Bindings = E100BEO2_nif
   NETADDRESS = "00d0b73ea414"
   TOKEN-RING = "no"
   TOKEN-RING_SNAP = "no"
   ETHERNET_802.3 = "yes"
   ETHERNET_802.2 = "yes"
   ETHERNET_II = "yes"
   ETHERNET_SNAP = "yes"
   TRACE = 0x0

[TCPIP_nif]

   DriverName = TCPIP$
   Bindings = E100BEO2_nif

[E100BEO2_nif]

   DriverName = E100B$

=== Cut ===

I'll be happy to email/netmail a CONFIG.SYS over to you with the sensitive bits 
mangled if you think it'd do you any good, but I'm sure there's no shortage of 
examples on the www these days.  The hard part is making any sense out of 
them... :)

 LE> BTW, the non-working versions of the CONFIG.SYS were noticably
 LE> *longer* than the one where Netware works.

One where both work at the same time could be longer still... <gd&r>

 LE> I've saved the files, and still have the one where TCP/IP works,
 LE> but Netware doesn't. I'll be running them thru a file compare
 LE> utility looking for differences later.

You may not find much of value.  From my hack-by-hand experience, for 
multi-protocol, the sequence can be more critical than the content.

 LE> BTW, I seem to vaguely recall being told that using MPTN to modify
 LE> network setup was just about guarnteed to make a mess...?

When it fails, it fails miserably.  When it works, it works (fairly) 
painlessly. There is nothing painless about the manual route.  You can 
basically "remove" everything in MPTS and lose the corresponding mess, if it 
fails miserably. Unless you need to peer, dump the NETBIOS out of the equation 
and go for two.  If NETBIOS is a must, I won't have much "guru value" for 
you...sorry.

..\\ike

--- GoldED 2.50+
 * Origin: -=( The TechnoDrome )=- Austin,TX 512-327-8598 33.6k (1:382/61)

.