![]() |
>From my experience, Hayes compatible usually means "mostly compatible". I too have M2 and M3 available for my Hayes compatible modem, but they don't do anything. I would be suprised if Hylafax is doing anything to your strings other than passing them to the modem. You really need to try a terminal program (or even a chat script) to talk to the modem and see what works. Ari on 29/12/99 5:14 am, Ekkard Gerlach at SPS_Gerlach@online.de wrote: > Nico Kadel-Garcia wrote: >> >>> my config.ttyS1: >>> >>> [...] >>> #ModemSetVolumeCmd: "ATM0 ATL0M1 ATL1M1 ATL2M1 ATL3M1" >>> ModemSetVolumeCmd: >>> "ATM2L3" >>> #ModemEchoOffCmd: ATE0 # disable command echo >>> [...] >>> >>> 1. ATM2L3 does not work ! Why ? >> >> The M register is a binary: 0 for off, 1 for on. M2L3 will generate >> an error code, as you can see if you use kermit or minicomm to >> talk to the modem directly and try the command. >> > My docu for hayes-compatible (like mine) modems says: > M0 : Speaker always off > M1 : Speaker on until connection established > M2 : Speaker always on > M3 : Speaker on until connection established but off during > dialing > > Does Hylafax not recognize M2 to M3 ? Wich command do I have to > execute > to reach modem behaviour like M2 ? > > BTW: With minicom all M2 , M3 is recognized > > > Ekkard > > --------------------------> ish group pty ltd 7 Darghan St Glebe 2037 Australia phone +61 2 9660 1400 fax +61 2 9660 7400 email info@ish.com.au PGP fingerprint 08 57 20 4B 80 69 59 E2 A9 BF 2D 48 C2 20 0C C8