🚀 go-pugleaf

I have an HSD InterFax 24/96 fax/data modem.  This modem worked
out-of-the-box for fax, but at first I could not manage to get it to
transmit in data mode.  after some net.help with configuring kermit,
etc., I do have it transmitting data.

Now, unfortunately, I cannot manage to send a fax.  All the settings
in PrintManager are - so far as I can tell - the same now as they were
when the fax capabilities worked.  When I try to send a fax (in
WordPerfect using "fax" in the print panel), I receive an error
message to the effect of:

  fax cannot be sent ...
  fax software failed during transmission ...
  restart computer & try again ...

I've tried restarting, but that does not help.  Same message on next
try.  Any clues ?  Where should I be looking ?  The notion that
restarting might help seems to suggest that there is probably a very
specific thing going wrong or a specific place I should be looking,
but without more detailed knowledge of the NeXT OS, I can't guess what
those specific things/places might be.

Some other possible clues ...

(1) Between the time I could & could not "fax", I did manage to get
the data transmission capability of this modem to work.  I played
around with a lot of possibilities before getting this to work, but I
do not *recall* that any files had to change ...

(2) A moment ago, I noticed that PrintManager has the faxmodem set as
available "private" ...the modem's manual suggests that setting
availability as "private" should put the modem in fax mode ... the
modem is clearly available to transmit in data mode right now.

(3) When I last ran through PrintManager to see what the settings were
for the fax modem, I hit the first panel's "fax options" button, went
to that panel, saw that everything was still set as it was when fax
capabilities worked, hit the "cancel" button & returned to the first
PrintManager panel.  No problem so far.  When I tried to get out of
PrintManager by hitting the "ok" button on its first panel, the button
stayed highlighted & the "spinning disk" cursor came on & stayed on so
long as PrintManager was in the foreground.

Any clues from the net ?

Thanks.  

John Watts
Krannert School of Management, Purdue University