I have had some trouble setting up the network devises for warp3 on MS Virtual PC -- anyone have some suggestions on which NICs work and how to get that virtual os2 to share network resources? I can't find a thing.

You using V3 or V3 Connect. V3 has no networking features at all, but there is a internet connection package for dialup.

Warp 3 Connect.

you need the driver of the Intel 2104x/2114x 10/100 mbps Ethernet Controller in: http://pws.prserv.net/mckinnis/nicpak/dec.zip Its also wise to use the Dani ATAPI driver: http://hobbes.nmsu.edu/pub/os2/system/drivers/storage/daniatapi0314.zip For display IBM's GRADD drivers are recommended. You can install them later (first selecting SVGA). If the network installation hangs because the CD is not recognised reboot with alt-F1 and rename startup.cmd (" ren startup.cmd startup1.cmd"). Then change the config.sys to use DANI's ATAPI drivers. Then "ren startup1.cmd startup.cmd", reboot and finish the installation from CD. http://www.sjoerd-visser.demon.nl/vpc/virtualpc.html

Thanks so much for your reply - those NIC drivers work great (so far). I got the NIC set up properly and I can ping myself but I cannot see anything else - not my host computer nor any other LAN resources. I set it up with NetBios over TCP/IP - what else do I need to set up?

<<I got the NIC set up properly and I can ping myself but I cannot see anything else - not my host computer nor any other LAN resources. I set it up with NetBios over TCP/IP >>> That's okay. Its much faster on VPC than the poorly emulated NIC netBIOS protocol. <<what else do I need to set up? >> Set up NetBios over TCP/IP via the MTPS.exe program: Select NetBios over TCP/IP in Adapter and protocol configuration. Choose edit. Configure (NetBIOS) Names: enter the proper IP adresses for the netBIOS names. NetBIOS names and IP hostnames are not automatically the same under OS/2. But I recommend to use the same hostname and NetBIOS name for the same PC. Net view //192.168.1.1 works under Windows but not OS/2. OS/2 wants to see proper NetBIOS names. Also configure the (TCPBEUI) broadcast list. Make sure the VPC host is informed about the OS/2 client by entering its IP adress or the hostname (should be in the hostfile or be a valid DNS adress) in the broadcast list. OS/2 does not automagically broadcast its presence to the IP broadcast adress of the workgroup (Windows does, to make it easier, but your shares could also automagically show up in the same IP range of your ISP, especially when you call your homenetwork "workgroup", as everyone does ;-). You also want to instruct the Windows server/host to announce its presence to OS/2 SMB client/server. By default Windows only announces its presence to Windows clients. For this it does not use proper NetBIOS names but IP adresses (guess why). Log in as root/administrator and go to the Windows registry program regedit and look (Ctrl-F) for the key LMannounce. LM is OS/2 or MS Lan manager, the original SMB protocol. Set the "value data" 1 for it (the default 0 disabled means nada OS/2 nor samba). HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\lanmanserver\parameters\Lmannounce=1 Another OS/2 tweak is: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Nbf\Parameters\ MaximumIncomingFrames=00000001 You can also edit the windows lmhost so that it uses proper netBIOS names: MS hides it under \winnt\system32\drivers\etc\lmhosts See also: http://support.microsoft.com/default.aspx?scid=kb;en-us;Q180094 The last barrier MS made (to get rid of the LM OS/2 servers) was to encrypt the SMB passwords. MS LAN Manager, OS/2 Connect (1994), OS/2 Warp 4 (1996), WfWG 3.11, Windows 95 and Windows NT (< Service Pack 3) use unencrypted (plain) samba passwords. But from Win95 (OSR2) on MS decided to enforce SMB connections with encrypted passwords on Windows NT (SP3), 95 (OSR2), 98, ME, 2000 and XP. This means that ONLY connections with encrypted passwords were accepted. So OS/2, WfWG 3.11 and Win 95 users (plain passwords) could no longer communicate with the clienst/servers with encrypted passwords (a good reason to upgrade isn't it?). You cannot force OS/2 Warp 3-4 to use win encrypted passwords. Unless you upgrade to a recent version of OS/2 (eCS and Warp 4 MCP connect with encrypted passwords). But you can force recent Windows clients to accept connections with plain passwords. Again go to the Windows registry and enable plain text passwords: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsNT\CurrentVersion\SeCEdit\RegValues\MACHINE/System/CurrentControlSet/Services/LanmanWorkstation/Parameters/EnablePlainTextPassword Search for EnablePlainTextPassword and put the value on 1. BTW If OS/2 is configured well, it only shows its unencrypted password to the client is connected with.