Mail Archives: djgpp/1998/06/24/17:02:07
71231 DOT 104 AT compuserve DOT com (Richard Slobod) writes:
> libsocket ( http://www.geocities.com/SiliconValley/Lab/3216/lsck.htm )
> will give you Winsock access under Win95, but not under Win98 or
> WinNT.
Have you ever used this library? It seems to work partially on my
win95 machine, but if i want the library to resolve a hostname the
program crashes. For example if i write:
httpget http://134.169.34.240/index.html
everthing works fine (since 134.169.34.240 is the ip of our local www
server www.ibr.cs.tu-bs.de) but
httpget http://www.ibr.cs.tu-bs.de/index.html
gives the follwing output:
Failed...
Trying nameserver...
Nameserver: [(null)]
and then the program crashes with an illegal access and the details section
sais that there's something wrong in WSOCK(01) + 00001834. I don't use
WSOCK 2 and i use libsock 0.72.
It seems that libsock somehow doesn't finger out the name of our dns server
(which is properly configured in win95, winipcfg reports dns to be enabled
and the correct ip of the dns server) and instead gives a null pointer
down to the wsock-lib which immediately crashes.
Does anybody know, what's wrong with this??
Please answer to harbaum AT ibr DOT cs DOT tu-bs DOT de, since i miss a lot of traffic
in this group.
Ciao,
Till
--
Dipl.-Inform. Till Harbaum
Institute of Operating Systems and Computer Networks Tel.: +49 531 391-3101
Technical University of Braunschweig Fax.: +49 531 391-5936
Bültenweg 74/75, 38106 Braunschweig, Germany EMail: harbaum AT ibr DOT cs DOT tu-bs DOT de
- Raw text -