Article View: comp.os.msdos.programmer
Article #2806Re: Networks, PRN, and a programs.
From: Joe Doupnik
Date: Thu, 25 Oct 1990 02:39
Date: Thu, 25 Oct 1990 02:39
10 lines
827 bytes
827 bytes
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.
Technical Details
Message-ID:
<40914@cc.usu.edu>Path:
arc1-ca.pugleaf.net!utzoo!attcan!uunet!know!zaphod.mps.ohio-state.edu!caen!hellgate.utah.edu!fcom.cc.utah.edu!cc.utah.edu!cc.usu.edu!jrdShow Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!attcan!uunet!know!zaphod.mps.ohio-state.edu!caen!hellgate.utah.edu!fcom.cc.utah.edu!cc.utah.edu!cc.usu.edu!jrd From: JRD@cc.usu.edu (Joe Doupnik) Newsgroups: comp.os.msdos.programmer Subject: Re: Networks, PRN, and a programs. Message-ID: <40914@cc.usu.edu> Date: 25 Oct 90 02:39:50 GMT Lines: 10