#Supra modem probs fax
5 messages in this thread
Can anyone tell me, if there is a difference between an Amiga 4000 RS232
(Modem) and an IBM (compatible) RS232 ???
My SupraFAXmodem V.32bis can send Faxes from my notbook but not from the Amiga
!!!
Please help me
Ernst
>=====on AutoPilot_1.80 [what else?] for AMIGA—–> from Europe/Austria/Vienna
Ernst, do you have the FAX software for the Amiga? I believe there is a
shareware version in the libraries here, and a commercial program.
—Betty
Betty,
>do you have the FAX software for the Amiga
Yes I have tried several software (AmigaFAX, TRAPFAX etc.) nothing will work!
🙁
The modem dials the number, the FAX of my office is there, but they can't
understand each other with the result of NO CARRIER !
If I try the same FAX_number with the same modem connected to my laptop
everything is fine [same initstring !!!] and I can fax 🙁
So I think it could be a difference in the RS 232 port of Amiga and PC and the
error depends on the cable ????
BTW when I use FaxTalk on my Amiga (Using PC-Task) the same error occurs.
Please help me.
Ernst
>=====on AutoPilot_1.80 [what else?] for AMIGA—–> from Europe/Austria/Vienna
Ernst – that truly IS a mystery! you can use the same serial cables and the
e initialization as in AT&F2) on the Amiga, rather than
alternatives. I just go with ATZ, which initializes the modem to the built-in
defaults, and GPFax and terminal software work fine.
In short, it's not the serial port that's different, it's the initialization
command that comes with the modem that should be altered. The modem should work
at least as well on the Amiga side, all else being equal.
Now I notice you're also trying to use the serial port via PC Task, meaning you
are running MS-DOS software through the Amiga serial port. In that case it may
be PC Task's method of addressing the serial port that's the problem. There, I
would use the PC standard F sequence in the initialization, not F2.
— from Milwaukee, Wisconsin, via Amiga AUTOPILOT v1.80
[the only way to fly cyberspace]
it could be because it lacks hardware carrier detect support?