🚀 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.

[networks]

  net1 = NETBEUI$,0,LM10,100,150,14
  net2 = TCPBEUI$,1,LM10,100,150,14

[requester]

  wrknets = NET1,NET2
  wrkservices = MESSENGER,PEER

[peer]

  SRVSERVICES = 
  srvnets = NET1

  Of course leaving NET2 out stops Linux Samba from being able to
connect (wanting SMB connection is the driving force for development 
here). Editing VDOSTCP.sys out of a VDM Device configuration in
Properties makes no difference.  The file VDOSCTL.exe which Config.sys
loads checks OK with a backup copy.  OS/2 is Warp 4 with FP14 applied.

  What's the fix?

Victor Bien
VCB Computing Alternatives (R)
http://sydney.dialix.com.au/~vcbien/