Hi Michael,
 MV> Trying to use the NT Network printing services from a winos2  
 MV> session, can not setup printer other then the local printer.
A small background on how WinOS/2 actually works may shed some light on this 
for you. The WinOS/2 code supplied with Warp, operates as a 'local only' 
system with NO networking knowledge or support (IE as Windows 3.11, not WFWG 
3.11). That means that if a Windows session needs to access Network 
resources, then OS/2 MUST see those resources first. Once OS/2 sees those 
resrouces, it presents those resources as if they were LOCAL resources to the 
WinOS/2 session. OS/2 handles WinOS/2 networking this way for 2 main reasons 

  1. OS/2 Networking is much more efficient and robust that Windows 
     style networking. 
  2. Adding seperate Networking suport to WinOS/2 would consume more 
     resources than really required. 
In most cases this should not be a problem (uless you are using a Windows 
device that does not have OS/2 Networking support), however one trap I have 
seen many fall into (including myself) is that the OS/2 Network resource 
connections MUST be established BEFORE the WinOS/2 session is started. If you 
connect (IE if you start up a connection) to a resource AFTER the WinOS/2 
session has been started, then that particular resource is still not 
available in the WinOS/2 session unless the WinOS/2 session is ended and 
restarted.
I have no problems using printers connected to remote Windows machines from 
either an OS/2 session or WinOS/2 on my machine.
Note - If you are running Red pack Connect (IE OS/2 with YOUR Windows code), 
then I am aware of problems that people have run into if they try and use 
WFWG and establish Networking connections from WFWG directly. IMHO, the best 
way to work this is to still allow OS/2 to establish all the Network 
connections, and then access those resources as local ones in Windows 
sessions.
I hope thsi helps.............pk.
--- Maximus/2 3.01
---------------