On Tue, 11 Jul 2006 19:55:44 +0200, Toni Mueller wrote: > Hmmm? If the fax is garbled, I suspect that you have flow control > problems with your modem.
No. That was just quite another item. See below. First, second and third I want to thank 3 nice guys for helping me offline !!! Now to what transpired; FYI: 1. 4.1.5 has a procedural problem to faxsetup and faxaddmodem on recent OpenBSDs. It doesn't go through; observed by others as well. 2. Some unofficial port (or the straightforward make && make install) of 4.2.5 or 4.3.0 do go through *if done from scratch* 3. faxaddmodem of 4.2.5 and 4.3.0 will *not* go through on a system that had 4.1.5 installed earlier. 3.a. pkg_delete hylafax leaves a lot of files inclusive the whole /var/spool/hylafax intact. That's from where a faulty variable stems that hinders any faxaddmodem to go through. Therefore 4. in order to get it running, a fresh make && make install on a fresh system (or one cleansed from any hyla and fax) of 4.2.5 or 4.3.0 is needed. 5. The EOL error of my out-of-the-box install of original hylafax4.3.0 is completely unrelated: http://www.hylafax.org/archive/2005-12/msg00255.php One might think of setting Class2RecvDataTrigger: "\022" in ..../etc/config.tty0x by default Uwe
