Q126347

• Microsoft Win32 Device Driver Kit (DDK) for Windows NT, versions 3.1, 3.5, 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 query words: 3.10 3.50

Keywords : kb3rdparty kbnetwork
Issue type :
Technology : kbWinNTsearch kbWinNTWsearch kbWinNTW400 kbWinNTW400search kbWinNT400xsearch kbWinNTSsearch kbWinNTS400xsearch kbWinNTS400 kbAudDeveloper kbWinDDKSearch kbWin32sSearch kbWin32DDKSearch kbWin32DDKNT310 kbWin32DDKNT350 kbWin32DDKNT351 kbWin32DDKNTSearch