[hylafax-devel] Re: ["Dr. Harald Pollack" <Harald.Pollack@datanews.at>]Re: Re: My RTN patch and many other changes/enhancements, third edition :-)

[Tim Rice <tim@trr.metro.net>]

On 14 Apr 2000, Dmitry Bely wrote:

> 
> Sorry, but I have to forward this. Harald! Please do not leave the list,
> here is at least one person (me) who needs your comments :-) Just ignore
> messages, that exasperate you, I will fight their authors myself :-)))
                                        ^^^^^
And I thought we were all on the same team. :-)

> 
> 
> 
> From Harald.Pollack@datanews.at Fri Apr 14 10:39:57 2000
> On Thu, 13 Apr 2000 13:44:33 -0600 (MDT), Steve Williams wrote:
> 
> Hello Dmitry!
> 
[snip]
> WRITING to the non volatile RAM (NV_RAM, which is in fact an EEPROM) of modem
> by AT&W is LIMITED 
> to a few thousand times!!!

Quit true.

> 
> >When HylaFAX starts up, and does 
> >an ATZ, things are going to break because it will NEVER see an OK come back.
> 
> As long as any people use such applications, there is no way to make behaviour
> of HylaFax 
> better!!!
> 
> >My personal opinion is that ATZ has ABSOLUTELY no place in ANY config file 
> >because there is no predicting what exactly it will do.

Perhaps there is a way. The predictable part is that it resets to NVRAM.
We just don't allways know what's been programed to NVRAM.
So if we use ATZ we have to make sure it's not a fatal error if no
result is returned. Then we should send "ModemResultCodesCmd:" next.
 
> ATZ is the ONE AND ONLY initialisation!!!!!!!!!!!!!!!!!!
> 
> 

-- 
Tim Rice		Multitalents	(707) 874-1130 (voice)
tim@trr.metro.net


____________________ HylaFAX(tm) Developers Mailing List ____________________
 To unsub: mail -s unsubscribe hylafax-devel-request@hylafax.org < /dev/null