🚀 go-pugleaf

>   The setup is that in Protocol.ini are:
> Adapter 0 and Adapter 1 are bound to an ethernet NIC.  TCPIP & Netbeui
> are bound to Adapter 0 and TCPBeui is bound to Adapter 1. I also have
> Adapter 2 bound to IBM's virtual NULL MAC (NulNDIS.os2) but excluding
> this make no difference to the VDM problem.
>
>   In IBMLan.ini the following allows VDMs to work OK but if ,NET2 is
> added after NET1 in [Peer], as soon as you invoke any VDM, just a
> command line for instance, OS/2 hangs.  Fortunately CAD will restart
> the computer so you don't get chkdsk having to run with its lengthy
> processing every time this happens.

From recent experience on playing with TCPBEUI:

1) Only *one* LAN or SLIP/PPP adapter may be bound to TCPBEUI

2) The adapter to which you wish to bind TCPBEUI must be the *first*
configured:-

[NETBIOS]
    Adapter0 = tcpbeui,0

[TCPBEUI_nif]
    DriverName = TCPBEUI$
    Bindings = adapter0_nif

[adapter0_nif]
    DriverName = ????????$

3) TCP/IP must be bound to it! (Otherwise, where's the transport!!!)

[TCPIP_nif]
    DriverName = TCPIP$
    Bindings = adapter0_nif

4) If you *also* wish to bind NETBEUI to the *same* adapter you must use a
higher logical adapter no.

[NETBEUI_nif]
    DriverName = NETBEUI$
    Bindings = ,adapter0_nif    <=== NOTE: leading comma defines *no*
adapter "0" (has been used by TCPBEUI). This is adapter "1".

4) then you can set up OS/2 Peer to use these logical adapters

[networks]

    NET1 = TCPBEUI,0,...
    NET2 = NETBEUI,1,...

You *really* would be best advised to use the Install/Configure object of
OS/2 Peer to *correctly* configure your bindings and protocols, until you
understand thoroughly the interrelationship between the values in each
configuration file. You will also need to look at the NETBIOS Names
configuration information, which results in entries in the files
\IBMCOM\RFCNAMES.LST and RFCBCST.LST, amongst others.

HTTH

Tim