Article View: comp.os.netware.misc
Article #528Re: Programming problem: IPXListenForPacket
From: Ramon Carlos
Date: Mon, 27 Nov 1995 00:00
Date: Mon, 27 Nov 1995 00:00
26 lines
1628 bytes
1628 bytes
dougf@startel.com (Doug Cornholio) wrote: >At first I thought that polling often would prevent the Novell client >from changing the inUse value, so I waited 10 seconds before polling. >I know for sure that I am sending a valid packet from another >workstation, as I am using already-tested software on that end; yet my >listening side never receives a message (or at least the inUse value >never changes). >Any suggestions? If you are doing this in Windows, look in the Novell Developer Product Support\All Sample Code web site, url: http://netwire.novell.com/home/devsup/sample/all there are a couple of sample programs: IPXRCV and IPXSED, which show how to handle this.. If you are doing this in DOS, then I'd suggest looking back at the return code from NWCallsInit() and IPXInitialize(). You did call those, did you not? Ramon Carlos rcarlos@ix.netcom.com
Technical Details
Message-ID:
<49d31j$mpg@ixnews6.ix.netcom.com>Path:
arc1-ca.pugleaf.net!unknown!not-for-mailReferences:
<480oiq$esp@cybernews.cyberus.ca> <wzpweu3m5b.fsf@albert5.fuw.edu.pl> <48gkps$21e@ocean.silcom.com>Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: fe659,37cccaad457dac4e X-Google-Attributes: gidfe659,public X-Google-Thread: f8bf7,37cccaad457dac4e X-Google-Attributes: gidf8bf7,public X-Google-Thread: fa939,37cccaad457dac4e X-Google-Attributes: gidfa939,public From: rcarlos@ix.netcom.com (Ramon Carlos) Subject: Re: Programming problem: IPXListenForPacket Date: 1995/11/27 Message-ID: <49d31j$mpg@ixnews6.ix.netcom.com> X-Deja-AN: 120209749 references: <480oiq$esp@cybernews.cyberus.ca> <wzpweu3m5b.fsf@albert5.fuw.edu.pl> <48gkps$21e@ocean.silcom.com> organization: Netcom x-netcom-date: Mon Nov 27 11:20:19 AM PST 1995 newsgroups: comp.os.netware.misc,bit.listserv.novell,comp.os.netware.connectivity