On Wednesday 13 February 2008 15:18:01 Teruel de Campo MD wrote:
On Wed, 2008-02-13 at 10:07 +0200, Stan Goodman wrote:
Answer noted in a later article. Thanks for the explanation
Carlos.
I did not know about the possible need for -devel packages if the dependencies were not fully met.
I feel better knowing that.
-- Stan Goodman Qiryat Tiv'on Israel
Stan,
I have not been lurking in this mail list for few days :( I've just saw your problems with faxing. I wrote the guide Istavan refers to and I believe you are trying to implement. If you follow every steps exactly as written you should not have a problem with the installation. If you do please post the details and I hope I can help you. I tried many different solutions and this is the one that for me has worked the best.
Terry... Do I not remember you as being associated with Scandinavian firewall and Internet-connection software for OS/2 dog-years ago? Hi! And thanks much for replying to me. -----snip----- Actually, Carlos gave me the clue to a prepared binary RPM for efax, and that is already installed; nota bene, I did not say it is usable. I have spent a good part of the day trying to understand why it remains in "Inactive" state, presumably connected with the error message that comes up when one presses the "Standby" button. Here is its most recent text: ***** efax-09a 17.34.22 Error: can't open pre-lock file /var/lock/TMP 13605 permission denied efax-09a 17.34.22 finished - unrecoverable error ***** The installation did not create file with that name, so I tried to help it by making one myself, and making it writable for anybody. Didn't help. I have no idea whatever what the program wants from me. Perhaps the developer doesn't either, since he doesn't treat it in his very friendly, but only moderately helpful "help". Other things I have not learned from the "help" or anywhere else I have sought: 1) I understood that the program is capable of providing a virtual printer, so that one can print from an application. I don't know how to do this, and it is nowhere mentioned, as far as I could see. I assume that a driver for it would have to pipe content through ghostscript to efax-gtk, but that is the limit of my guessing. 2) Although there is now no error about being able to find the log file I have defined, when I try to open the log I get a warning reading: "Cannot open logfile for viewing". Why is one of the mysteries of the early 21st century. 3) I will eventually want to delete the long list of error messages, but do not know what file they occupy, since the friendly developer has not troubled to mention this. I do of course have a faxmodem, external USR 56K. It came without any documentation, only a CD with software for installing in WinCrap. I have been hammering on USR support for three weeks to get a printed or downloadable user guide, but evidently USR doesn't believe in such things anymore. The world is not what it once was. As I've mentioned elsewhere, I have already spent far too much time in wrestling with this enigmatic program. If you can see readily where I should turn to learn the missing pieces, I would be exceedingly grateful to you. Else tomorrow I will purchase a fax machine, and have done with the problem, albeit not in the way I would wish.
Ciao
-=terry(Denver)=-
Note: I assume you have a modem. I assume the modem is an external modem or an internal complete modem (no window model). If it is a windows model then the problem can get a little more complicated. This has nothing to do with the efax-gui program.
-- Stan Goodman Qiryat Tiv'on Israel -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org