PRB: Trouble w/ winnet as Secondary Driver & WNetOpenJob() APILast reviewed: August 22, 1996Article ID: Q126347 |
The information in this article applies to:
SYMPTOMSWhile trying to get your winnet driver to work under Windows for Workgroups version 3.11 or Windows 95 as the secondary driver, you're having a problem with WNetOpenJob().
CAUSEThe file handle returned to Print Manager by WFWNET is not the same one returned by the secondary net driver. This results in Print Manager printing to a bogus file handle.
RESOLUTIONIf the third-party winnet driver claims to support WNetWriteJob(), it should stop supporting WNetWriteJob() and ensure it is returning a handle that can be written to using a file I/O.
STATUSThis behavior is by design.
MORE INFORMATIONThe Windows version 3.1, 3.5, or 3.51 Shell does not use WNetWriteJob() (it is not documented as supported anymore). Therefore a claim to support WNetWriteJob breaks multinet configurations because it implies that a winnet driver's handles are not valid file I/O handles, and that the Shell must call WNetWriteJob to print jobs.
|
Additional reference words: 3.10 3.50 4.00
© 1998 Microsoft Corporation. All rights reserved. Terms of Use. |