![]() |
Thanks to all who replied (Lee, Eduardo). I will probably upgrade the modem first, then after all is well, upgrade HylaFAX. I am really struggling with the old "If it isn't broken, don't fix it" adage. But the newer versions of HylaFAX have a feature I really need, so I guess I'll go for it. JM > -----Original Message----- > From: Eduardo Páez Trujillo [mailto:edpaez@xxxxxxxxxxxx] > Sent: Tuesday, March 22, 2005 3:33 PM > To: hylafax-users@xxxxxxxxxxx > Subject: Re: [hylafax-users] USR Modem, upgrades > > > Be aware, Jim. I also believe my USR was alright until I > revised Hylafax > logs. Hylafax does not notify any problems at 4.1.8. ("MODEM > <Empty Line>" > issue) > Version 4.2.1 is much better. I give you two recommendations: > check your > logs and change your modem. > > > I would really like to upgrade HylaFAX to a newer version, > > but am afraid > > that by doing so, I will upset the balance that has made this > > server perform > > so well. My questions are these: are these fears unfounded? > > If so, what > > is the safest upgrade procedure for me to ensure continued > > stability and > > minimize downtime? > > > > ____________________ HylaFAX(tm) Users Mailing List > _______________________ > To subscribe/unsubscribe, click > http://lists.hylafax.org/cgi-bin/lsg2.cgi > On UNIX: mail -s unsubscribe > hylafax-users-request@xxxxxxxxxxx < /dev/null > *To learn about commercial HylaFAX(tm) support, mail > sales@xxxxxxxxx* > ____________________ HylaFAX(tm) Users Mailing List _______________________ To subscribe/unsubscribe, click http://lists.hylafax.org/cgi-bin/lsg2.cgi On UNIX: mail -s unsubscribe hylafax-users-request@xxxxxxxxxxx < /dev/null *To learn about commercial HylaFAX(tm) support, mail sales@xxxxxxxxx*