Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

HPGATE Partial Print IS A NOVELL Bug

1 view
Skip to first unread message

None...@nonegiven.com

unread,
Jan 20, 2004, 10:32:09 AM1/20/04
to
For those people that are currently having partial print problems with the
3.00b HPGATE NLM, don't blame HP, nor their developers. The partial print
problem is a NOVELL defect in their Winsock 2 implementation. If you want
to blame someone, blame them. If you want the problem fixed, switching to
the Novell gateway may not be the answer. The answer is to bug the Novell
developers to fix the problem.

Anonymous

Barry St.John

unread,
Jan 20, 2004, 1:43:14 PM1/20/04
to
Anonymity isn't going to help. If you'd like to provide more
information and let a Novell engineer work with you on this, we might
make some headway, if what you say is accurate.
--

-Barry. [Novell Support Forums SysOp]

blag...@roctwenteplus.almelo.kennisnet.nl

unread,
Jan 21, 2004, 3:42:16 AM1/21/04
to
<None...@NoneGiven.com> schreef in bericht
news:ZRbPb.1772$P5....@prv-forum2.provo.novell.com...

If you know it all so well, why not contact a Novell engineer and work with
him/her to fix the problem ? Ranting sure isn't going to help, mister.

Arjan.


None...@nonegiven.com

unread,
Jan 21, 2004, 8:58:27 PM1/21/04
to

Under certain circumstances (non-overlapped sockets, blocking mode) when
using Novell's implemenation of Winsock for IP or IPX/SPX sockets,
shutdown (for the write side) will return WSAEINPROGRESS. If you call
shutdown and receive WSAEINPROGRESS, you can continue to loop calling
shutdown (after some amount of a delay), and eventually shutdown will
succeed and the output buffers will be flushed. If however you decide not
to loop, and you call closesocket, the output buffer will not be flushed,
and you end up with a "partial print" situation. If you receive
WSAEINPROGRESS from shutdown, and you immediately call closesocket, it
would not be unreasonable to expect closesocket to also return
WSAEINPROGRESS, but this is not the case (regardless of how much data is
in the buffer). Performing a network trace will reveal that the FIN is
never sent. Socket options no not figure in to the behavior either.
Doing a blocking shutdown, should never result in WSAEINPROGRESS. This
error code is meant for non-blocking sockets. Novell developer support is
aware of this issue, and has been since late 2002, early 2003. Novell's
TID 2966160 - http://download.npsh.hu/tid/2966160.html, directly relates
to this issue.

Anonymous

None...@nonegiven.com

unread,
Jan 31, 2004, 1:35:46 PM1/31/04
to

Well, I provided more information.

Anonymous

0 new messages