Mail Archives: djgpp/2002/05/22/16:22:02
Hello.
deckerben wrote:
[snip]
> I'm really happy for any advice that is given to me in a positive manor. I
> will try to make up a diff package and send it to you.
I won't really be able to comment on how you've ported it, unless I can see
the diffs. I'm not sure I know enough Python, to test out the port. ;)
[snip]
> > The problem with socket libraries is that they only work on a subset of
> > the platforms that DJGPP runs on. That really is pretty inconvenient for
> > the user.
> > Until there's one library for all platforms, I'm not sure it's worth
> > trying to add Socketmodule.
>
> Then, I guess what is needed is a C library (please, NOT TSR) that can
> detect a Win95/NT winsock-tcpip connection _if_it_exists.
Yes. That's the problem. Incidentally there is a driver for Windows NT (and
maybe it works with 2k, XP) that tries to emulate the Windows '95 interface
that libsocket uses. It could do with some more testing & work:
http://www.phekda.freeserve.co.uk/gabor/wsockvdd/
Unfortunately it did not work very well last time I tried it.
> Otherwise, it tries its own connection via comm port. It needs to have all
> the Libsocket definitions, though, so that porting UNIX stuff is made easy.
> Just my thinking.
When you say "tries its own connection via comm port", do you mean that the
program should make a connection via modem and run all the networking
protocols itself? That's quite a task. Also it would not work very well on a
LAN.
Bye,
--
Richard Dawe [ http://www.phekda.freeserve.co.uk/richdawe/ ]
- Raw text -