An OS2 Advisor suggested that I should provide the following information on W4WGs. This information is for those who want to be able to access the Windows for Workgroups (W4WGs) network while still running OS2. This information has been checked and is partially due to a recent thread on the subject.
 
The first point to keep in mind is that it is NOT possible to actually run the W4WGs system under OS2. Only WINOS2 can run under OS2. However, it is possible to gain varying degrees of access to the W4WGs network.
 
The first method is the one I use and allows transfering files  and running DOS programs across the network. An outline of the steps for this method follows. This method is based on the fact that a MS DOS network is actually loaded and started before W4WGs is run. This network (which is the W4WGs network) is directly accessable from DOS without ever using W4WGs. The procedure is the same as that used to run a network such as LANTASTIC or NETWARE LITE (DOS version) from OS2.
 
1) If you installed OS2 BEFORE W4WGs then you can skip this step, although you may want to add the network hooks later to experiment. If you installed OS2 2.1 over an existing W4WGs setup as I did, you will notice that every time you bring up a Windows application or WINOS2, you get a network error message box. This is because the W4WGs WIN.INI and SYSTEM.INI files were used to set up the WINOS2 versions and contain all of the network hooks. Even the File Manager in WINOS2 will be from W4WGs if you migrated all your applications. Unfortunately, the network is not running and cannot be started because it uses DOS virtual device drivers not directly supported by OS2. To eliminate these error messages, first set the Network to No Network Installed using the Windows Setup Icon located in the WINOS2 Program Manager. Now remove ALL network references from the WIN.INI and SYSTEM.INI files located in the  \OS2\MDOS\WINOS2\ subdirectory. WINOS2 and Windows applications will now function normally without network error messages.

2) Now create a specific session (e.g. Dos 6.0 or 6.1) Virtual DOS Machine (VDM) boot disk image. Instructions for creating this disk image may be found in a number of places including on-line HELP and in the OS/2 2.1 Installation Guide, p. 157-163. The CONFIG.SYS and AUTOEXEC.BAT files used in this session should have the same W4WGs device drivers (e.g. protman.dos, workgrp.sys,  smc_arc.dos) and commands (e.g. net start) as the corresponding DOS files used to start the W4WGs system when running from DOS without OS2. The HIMEM.SYS,   EMM386.SYS, and MOUSE.COM statements should refer to those located in the \OS2\MDOS\ subdirectory, NOT those supplied with W4WGs or DOS. The notebook settings associated with this VDM Boot image should have the DOS_FILES set to forty or more, DOS_LASTDRIVE set to Z, DOS_STARTUP_DRIVE should point to the VDM Boot image, and the DPMI_MEMORY_LIMIT set to 4 or more. This will allow you to experiment later if you want to.

3) Make sure a W4WGs machine is running as a server on the network. Start your specific VDM Boot image and the W4WGs network will load. Now you may use the MS DOS network commands to access the network. If you enter NET /? at the DOS prompt, a complete list of commands will be displayed. If help on a specific command is desired, type NET START /? for example. Simply typing NET loads the Pop UP window interface and allows you to establish network connections. This is the only command that I usually use. You may now access files and DOS programs across the network from all servers. You will always act as a client on the W4WGs network and there is no way around this restriction (W4WGs must be running in 386 enhanced mode to act as a server). If you need to do serious work with W4WGs then using DUAL BOOT to run real W4WGs. This is quick and easy but requires that you leave OS2.

If you want to experiment, it is possible to run WINOS2 in the specific VDM Boot session. The only reason for doing this would be if you leave the network hooks in place (omit STEP 1 from the given procedure) and want to be able to access files from WINOS2 run in the VDM. However, this is not a clean solution. You will get error messages every time a Windows application is started and WINOS2 is not really network enabled (e.g. NETAPI.DLL is not installed). However, you can do things like drag and drop files. Experiment at your own risk.

The only way to really enable WINOS2's network capability is to obtain a copy of LAN Server 3.0. Charlie Brown of IBM (who lurks on this forum) has a detailed set of instructions for network enabling WINOS2 so that you can fully access the W4WGs network. Unfortunately, this is an expensive solution if you don't have LAN Server. Contact Charlie for these instructions if you are interested.