🚀 go-pugleaf

>>>Before using NXFax, it is very important that any getty processes
>>>currently in use on the NXFax serial line be turned off.
>>
>>Has everyone some hints (a new getty) for me, that I can login
>>to my customer who uses NXFax  ?

You don't need a new getty, as NXFax acts as the getty for the modem.
It checks to see if the incoming call is a FAX call or a data call.
If its data, then it runs a program (by default, /bin/login, I
believe).  All automagic.

>I haven't had to look into this on the NeXT yet, but on my SysV box I
>have a modem that normally is set up to receive but switches over to
>send, which seems like a similar process.  SysV has init states where
>you can identify whether a tty is on or off in that state.  Switching
>states handles the problem.  Under SysIII I did not have that and I set
>up alternate inittabs which I would copy into the active inittab using a
>shell script.

You don't have to play these games.  The NXFax software determines on
a call-by-call basis if its a data or fax call.

>Similar techniques probably will work on the NeXT as long as you are
>just talking about sending faxes.  If you must also receive, then I
>think you have to establish times when the fax is receiving and times
>when the getty is receiveing.  I am assuming here that a calling fax can
>tell that it has not connected properly and will try again.  I am also
>assuming that you can identify whether the line is use and for waht
>before attempting to switch it.

Again, this isn't a problem on the NeXT with NXFax.

>Query, is all fax soft/firmware like this?  It seems to me the modem
>should be able to identify whether it is receiving a fax or a dial-in
>and do the right thing.  The software on the computer should do the
>same.

As far as I know, the NeXT NXFax software is one of the few that just
identify the call and do the right thing.  Of course, I've not had the
occasion to investigate Sun or other platforms.

louie