*BSD News Article 6561


Return to BSD News archive

Newsgroups: comp.unix.bsd
Path: sserve!manuel.anu.edu.au!munnari.oz.au!sgiblab!zaphod.mps.ohio-state.edu!usc!venice!gumby.dsd.trw.com!eel.dsd.trw.com!gottloeb
From: gottloeb@eel.dsd.trw.com (Jeffrey R. Gottloeb)
Subject: Re: fax software for 386bsd?
Message-ID: <1992Oct14.220415.19640@gumby.dsd.trw.com>
Sender: news@gumby.dsd.trw.com
Organization: TRW, INC.
References: <1992Oct5.103838.13036@Informatik.TU-Muenchen.DE> <1992Oct5.105838.13230@Informatik.TU-Muenchen.DE> <1992Oct14.184210.16229@gumby.dsd.trw.com>
Date: Wed, 14 Oct 1992 22:04:15 GMT
Lines: 57

In article <1992Oct14.184210.16229@gumby.dsd.trw.com> gottloeb@eel.dsd.trw.com (Jeffrey R. Gottloeb) writes:
>In article <1992Oct5.105838.13230@Informatik.TU-Muenchen.DE> gebhart@Informatik.TU-Muenchen.DE (Ralf Gebhart) writes:
>>In article <1992Oct5.103838.13036@Informatik.TU-Muenchen.DE> gebhart@Informatik.TU-Muenchen.DE (Ralf Gebhart) writes:
>>>>
>>>Hi
>>>I'm currently working on porting GNU-netfax to 386BSD.
>>>I have already compilid it (need GNU-make for this).
>>>With the exception of one ioctl, I only had to change some #defines.
>>>I don't know yet if that ioctl is really necessary, because I don't know
>>>what it does. Ultrix and SUNos have it, but 386BSD not. Unfortunately
>>>I couldn't get any docs/info about that ioctl yet.
>>>Another problem is, I am currently very busy with other things,
>>>so it will take at least another month, til I have finished that beast.
>>>BTW: I'm working with a ZyXEL 1496E.
>>>
>>
>>I forgot some things to mention.
>>I used Version 3.2.1 of GNU-fax
>>
>>and is there anyone who can tell me what 
>>
>>ioctl(fd, TCXONC, TCOOFF);  exactly does ?
>>
>>I know it has something to do with XON/XOFF, but is so special to it,
>>can it be replaced by one of the usual XON/XOFF-related ioctl ?
>>
>>
>>      Snake
>>
>
>
>I've got most of done and am testing it right now.  I am able to send faxes
>out via the spooler but I am having difficulty receiving faxes.  The problem
>seems to be a time-out problem after receiving the CONNECT message.
>
>One thing I found out about the ZyXEL's is that they are not returning
>Class 2 values that are strings (eg. FCSI, FTSI) properly.  The values
>should have double-quotes around them (eg. +FCSI:"18005551212") but do not
>(at least with the V5.02 ROMSs).
>
>I also needed to increase the timeout value TIMEOUT_ANSWER in c2proto.h from
>15 seconds to 60 seconds to allow for long carrier detect times (all those
>protocols :-).
>
>Something that made by efforts easier was a patchfile that was posted here
>earlier.  If you don't have it, email me.

Actually it was comp.dcom.modems.  My mistake.

>
>I don't remember at the moment what I changed that ioctl to but I can check
>tonight.
>
>Jeff Gottloeb
>gottloeb@gumby.dsd.trw.com