From: "Alexei A. Frounze" Newsgroups: comp.os.msdos.djgpp Subject: Re: serial problem Date: Sun, 16 Apr 2000 16:11:21 +0400 Organization: MTU-Intel ISP Lines: 24 Message-ID: <38F9ADE9.BD9FF56E@mtu-net.ru> References: NNTP-Posting-Host: ppp97-187.dialup.mtu-net.ru Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit X-Trace: gavrilo.mtu.ru 955887123 21507 212.188.97.187 (16 Apr 2000 12:12:03 GMT) X-Complaints-To: usenet-abuse AT mtu DOT ru NNTP-Posting-Date: 16 Apr 2000 12:12:03 GMT X-Mailer: Mozilla 4.72 [en] (Win95; I) X-Accept-Language: en,ru To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com I have already sent him a program that works directly with serial ports instead of the BIOS services which really suck. He said, everything works now. bye. Alexei A. Frounze ----------------------------------------- Homepage: http://alexfru.chat.ru Mirror: http://members.xoom.com/alexfru Eli Zaretskii wrote: > > On Fri, 14 Apr 2000, Damian Yerrick wrote: > > > >I have a rather weird problem with djgpp v2. I have two computers linked > > >together(Both on COM1), using a serial link. And I am using bioscom() > > > > That's your problem: bioscom() is sucks. > > Are you telling there are bugs in bioscom's implementation? If so, > please tell what they are. I have never heard any complaints about > it, and I don't know about any bugs in it.