Message-Id: <3.0.6.16.20000510223655.3f37662a@mail.cybercable.fr> Organization: Michelle's Internet Service X-Link: http://www.michelle-is.com/index.htm X-Moto: Micr0$oft = What do you want to crash today? X-Note: Sending S P A M is a violation of german, french and US law and will at least trigger a complaint at your provider's postmaster. X-Sender: starone AT mail DOT cybercable DOT fr X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.6 (16) Date: Wed, 10 May 2000 22:36:55 +0100 To: djgpp AT delorie DOT com From: Michelle Konzack Subject: Re: DJGPP and network programming In-Reply-To: References: <8f5cn7$g2a$2 AT bob DOT news DOT rcn DOT net> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id SAA00862 Reply-To: djgpp AT delorie DOT com Errors-To: nobody AT delorie DOT com X-Mailing-List: djgpp AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk >> Networking Programing is not a static subject and for you >> to sit there and tell people to look in some FAQ that really doesn't >> answer the questions people have is quite frankly laughable. > >If the FAQ doesn't answer questions people have, please suggest how to >make it better. In this particular case, I think the FAQ says most of >what was posted in this thread. Hello, I think it is enough, if the FAQ tell you the link to the networking libs and anone which need to get better infos may join the mailing-list of the networking lib... Please note, that I am using watt-32 with DJGPP and C/C++ since more then 12 month without any problems. The Mailing-List is watt-32 AT onelist DOT com and ther is a new version of Watt-32 v2.1 dev.rel.2 Please note, that libnet will give you millons of trouble with DJGPP... Watt-32 is the perfect one you should use. Michelle -- Don't cc: me on mailinglists, I'm subscribed, if I write there. ---------------------------------------------------------------------------- Linux rebootet man in drei Fällen: Neuer Kernel, neue (Board-)Hardware, Stromausfall.... Aber Windows rebootet man auch in drei Fällen: Schutzverletzung, Bluescreen, keinen Bock...