From: Richard Dawe <richdawe AT bigfoot DOT com>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Sun RPC for djgpp?
Date: Tue, 16 May 2000 21:29:45 +0100
Organization: Customer of Planet Online
Lines: 24
Message-ID: <3921AFB9.FD71F12@bigfoot.com>
References: <39201D5E DOT 595121FB AT inti DOT gov DOT ar> <39203E55 DOT F221A9C8 AT bigfoot DOT com> <392188E3 DOT 1D56D2F0 AT inti DOT gov DOT ar>
NNTP-Posting-Host: modem-70.tellurium.dialup.pol.co.uk
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Trace: newsg3.svr.pol.co.uk 958510814 16027 62.136.43.70 (16 May 2000 21:00:14 GMT)
NNTP-Posting-Date: 16 May 2000 21:00:14 GMT
X-Complaints-To: abuse AT theplanet DOT net
X-Mailer: Mozilla 4.51 [en] (X11; I; Linux 2.2.14 i586)
X-Accept-Language: de,fr
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

Hello.

salvador wrote:
> Gisle Vanem ported the client stuff to WATTCP. It uses packetdrivers and
> I'll run the client in Win9x boxes so I don't think I'll be able to use
> it.

You can get an NDIS-to-packet driver shim, called NDISPKT (I think). I
tried this once, but I couldn't get it to work. Gisle Vanem has mentioned
it on the Watt-32 mailing list, so I guess it works and I just have no
idea how to set it up properly. ;)

> BTW: libsocket seems to define some RPC structure in the headers, why? I
> think it makes collisions with some RPC header.

Good question. I think they were there when I took over maintainership of
libsocket. Which RPC structures do you mean? I can remove them for
libsocket 0.7.4 beta 4.

Thanks, bye,

-- 
Richard Dawe
richdawe AT bigfoot DOT com ICQ 47595498 http://www.bigfoot.com/~richdawe/