PRB: Trouble w/ winnet as Secondary Driver & WNetOpenJob() API

Last reviewed: August 22, 1996
Article ID: Q126347
The information in this article applies to:
  • Microsoft Win32 Device Development Kit (DDK) for Windows NT, versions 3.1, 3.5, and 3.51
  • Microsoft Windows NT Server version 4.0
  • Microsoft Windows NT Workstation version 4.0

SYMPTOMS

While 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().

CAUSE

The 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.

RESOLUTION

If 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.

STATUS

This behavior is by design.

MORE INFORMATION

The 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
KBCategory: kbnetwork kbprb kbprint kb3rdparty
KBSubcategory: NTSrvWkst


THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: August 22, 1996
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.