[rjonkman]

The problem at which it stopped working was a minor change in the software. The operating is windows 2000 advanced server (which i know symantec does not recommend from an earlier topic). I was however able to get it to work, and it has worked for months now. It seemed just like a fluke that it wouldn’t send anything anymore.

After the reinstalling i did today (with complete removal of every file and registry setting winfax-related), I could get faxing to work again, using exactly the same settings, exactly the same program and exactly the same faxes.

(I must say that i had some problems removing one of the dll files from the winfax directory. I don’t recall the name, but after searching the registry it was apparently mounted to some dcom configuration number, which after deleting it and a restart, would let go of it’s lock on the file. This was already in safe mode.

Thanks for your help in this. I must say i was a bit desparate when the problem persisted after the initial reinstall of winfax. Everything seems to be fine now, though 🙂

The only problem I have now is that the markup of the page still is different everytime (from the other topic), but that’s because the guy who programmed the ‘main’ program didn’t really care for setting some kind of standard. Faxes come in either 200 or 600 dpi, with different settings for linespacing, font size, etc, which by some kind of miracle did work on the older version… But that’s my own problem 🙂 — thanks for your help.

[rjonkman]

Sending a fax from another program appears to be no problem; Same goes for anything I just send to the ‘winfax’ printer. Ofcourse in that case, no winfax object is needed to send settings to or receive an entryid..

(getting the entry id is the only problem, the rest of the communication works ok).

I’ll try if a complete uninstall (using this guide at symantec), then reinstall without using backup settings and check back here. Thanks 🙂

[rjonkman]

First of all: I have had no luck reinstalling just the system part of winfax

I was referring to the output problem, not the missing printer driver. Its possible that the output problem only occurs in the application you are using, and not other applications.

I have just tested with word; It prints just fine, though, one may argue that word might send the data to be printed as a single image, which doesn’t need any recalibrating. The program works a bit differently–
Consider the page to be printed a ‘canvas’ on which lines of text will be drawn. The location of such a line is defined by it’s starting coordinates; for example, a line may start at (1000,1000) which brings the start of the line 1000 pixels from the left and 1000 from the top.
The problem now, is caused by a difference between the size of this canvas reported at the start; consider the width and length of the document to be 2000×3000 pixels. if the document is spaced and lined out on this number, but it’s in reality a lot more, say 2000×6000 pixels, the distance between lines will be about twice as big, and the document now takes 2 pages to print.
Something like this is currently happening at the computer we are using.

Symantec claims incompatibility with Windows 2000 Advanced Server (they don’t recommend WinFax being used on it)

You are right, I was under the impression it was supposed to work because of this document. After a little querying on account of your post i found this
one, which indeed states this incompatibility/unrecommended situation. I can only hope this doesn’t make it unresolvable.

Does this app have to run on the server? have you tried using it on another test machine to see if you get similar results?

It has run successfully on both windows xp (after some tweaking on the timing) and windows 98 (winfax 9) in the past.

At this moment, there is no computer available which can be accustomed to this task. If the problem persists, this might be the course of action to take. It’s either that, or looking for another faxing solution with scripting posibilities.

At this moment, I’m trying to solve the problem by modifying the program to use a fixed size for the canvas. It’s less generic code, but it should do the trick for this specific problem. The fact that the ‘printer’ is gone at every restart would ofcourse not be solved by this.

[rjonkman]

I have tried reinstalling a couple of times (logged in both as administrator or as a user with administrative rights); but not program files only. I’ll try that possibility next time I’m on location.

We use winfax only for the custom program described above. The problem should occur in programs like word too, since the ‘printer’ winfax installs is just gone. This is the basis of the entire problem — there is no ‘winfax’ printer visible in the printers pane of the control panel.

I’ve also tried getting winfax to work by adding a printer and trying to connect to a winfax port, but had no success in that regard. Is this a line of thought worth persuing? I’m not really familiar with these settings.

[rjonkman]

I fear I have wasted a bit of your time by neglecting to say that I have already visited the symantec support database. By using some relevant search terms I did end up at this link, which gives some basic info about dealing with this kind of problem on windows 98. At the bottom there’s a link to the page you undoubtedly refer to with your statements about framedyn.dll

I have tried this (putting framedyn.dll at ‘WINNTSystem32’ ), but to no avail – the problem sadly remains. Because the problem I’m having is win2000 and the description of the problem said it should only pop up after installing service pack 1. Ofcourse, the change that brought this about might also have been implemented in a service pack or patch for windows 2000, but it doesn’t seem to be fixable in the same way.

Is there anything else you think might be worth giving a try? thanks!

[Author]

Posts