JRD@cc.usu.edu (Joe Doupnik) (10/25/90)
Network printing: the printer does not awaken until the applications task has exited to DOS. The most likely reason this happens (to lots of systems) is the printer device handle (4) from DOS is still being held open until the app prog exits. The server thinks more information is coming and waits. Command.com usually owns this handle and gives us a copy of it. The usual away around it is to open another handle to the device in the program and close it when real printing is required. Joe D.