Hylafax Mailing List Archives
|
[Date Prev][Date Next][Thread Prev][Thread Next]
[Date Index]
[Thread Index]
Re: Hylafax Installation -- A Plea for Help
Darren Nickerson <darren@hylafax.org> writes:
> +> USRs are OK in Class1. Sometimes.
>
> Dmitry> ... because of Class1 bugs in Hylafax (seems to be fixed). I don't
> Dmitry> know any firmware related problem for USR Class1 implementation.
>
>
> You keep talking about these Class1 bugs you have fixed, but the -devel list
> has yet to see the patches! ;-)
Already writing "whatsnews" :-)
> +> IIRC most of the personal (Windoze) fax apps drive modems in Class1, the
> +> simplest and most reliable way to operate in a low-latency, high resource
> +> setup such as a single workstation.
>
> Dmitry> Class 1 is also the reliable way for heavy loaded server. Have you
> Dmitry> read Class 2/2.0 vs Class 1 discussion in hylafax-devel?
>
> Of course I have. It was hardly a conclusive discussion though. Harald felt
> that timing issues in Class 1 were not so important, because the tolerances
> were on the order of seconds. I've had a server go busy up for a few seconds .
> . . have you? ;-)
.. and OS scheduler gives your fax process absolutely no time to run? Then
you have the broken OS (Win95? :-)) and the fax server won't work at all
(with any fax class). Remember, Phase C timing requirements (most
time-critical part of T.30 protocol -- sending/receiving the message
itself) are *the* *same* for both Class2 and Class1. And if your server is
unable to feed necessary data in time during Phase C, you are obviously in
trouble...
> Dmitry> Actually *not* *needed* (all this Class2* stuff and useless modem
> Dmitry> init string in existing configs ...) Almost all modems will work fine
> Dmitry> with the default settings (as soon as my changes is applied). You'll
> Dmitry> see ... :-)
>
> Promises, promises ;-)
Already writing "whatsnews" :-)))))
> +> and we'd be driving them in Class 2 as well!
>
> Dmitry> Not neccessary. I'm quite happy with Class 1 now (and need not to
> Dmitry> thing about Class2 firmware specifics, i.e. bugs). Now it's time to
> Dmitry> implement ECM :-))) (impossible for Class 2/2.0)
>
> Have fun!
Hope to hear from you soon,
Dmitry