🚀 go-pugleaf

In article <1992Dec9.135744.314@aki.en.open.de> peter@aki.en.open.de writes:
>Hey !
>
>This is the really funny NXFax1.02 feature :
>
>> see file NXFaxInstaller.app/After.rtf 
>>
>>Important Note:
>>
>>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  ?
>
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.

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.

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.
-- 
Bob Peirce, Pittsburgh, PA         rbp@investor.pgh.pa.us         412-471-5320
venetia@investor.pgh.pa.us [NeXT Mail]  !uunet.uu.net!pitt!investor!rbp [UUCP]