Forum Replies Created
-
Posts
-
Thanks.
I was able to finally successfully install by simply ignoring the fields that cause the problems. While this will omit some CSID info, hopefully that will not be too bad (e.g., like some receivers refusing to connect without a CSID number).
Some day I might try uninstalling IE and see if that helps (and/or installing various visual basic runtimes that it seems might also be part of the problem). I think that in general, this type of problem is caused by a wrong gui runtime, so the vb fix seems very promising, unless it ends up breaking something else.
@Moderator wrote:
Thanks, but I can’t afford to buy a subscription at this time.
I would still be interested in knowing what the cause of the problem is, even without the solution.
Thanks.
I infer from your suggestion that:
1. Winfax pro 10.x was written in c++.
2. It uses side-by-side assembly. (Which, despite being a c++ programmer, I don’t know what that is.)
3. It used runtimes that were older than this and therefore which might have bugs.I might add that in my experience as a c++ programmer, primarily under Linux, I found that the MS compiler very often produced incorrect code, especially when one used the more esoteric features of c++, so I’m encouraged that this may solve the problem. (But, on the pessimistic side, the problem looks more like a programmer error than a compiler or library bug. What’s worse, it could be a bug in a different driver — e.g., causing a buffer overrun into someplace that Winfax uses). But, without source code, it’s all a giant mystery.)
In any case, I will first try renstalling the Winfax printer drivers when I either have time to or are forced to reboot.
Thanks yet again. I have a few physical printers installed on both systems, though mainly different ones.
I tried installing an HP Laserjet on the desktop machine. We shall see if that cures it. I don’t want to precipitate a crash right now, and I’m not sure if the crashes are guaranteed every time, so it may be some time before I update this thread with the results.
As for why this might work, I seem to remember reading long ago that these kernel-mode printer drivers might have some daisy-chaining they do, and it’s possible, e.g., that uninstalling some driver had some unintended consequences. Or, impossible as it may seem, windows might have a bug :wink:. More likely, though, is my original theory — some recent security fix broke something that the driver was assuming.
Thanks for responding again. One of the first things I did was to try to reinstall the driver using the maintenance tool. However, the tool responded with “driver already installed”.
It is not clear to me how to “delete” the driver. For example, I could simply discover where it is kept, and rename it. Or, can it be uninstalled from the windows device driver manager component of computer manager? I can’t recall if I investigated that before. However, that is risky, because installing might later fail and then I will have no faxing at all, as opposed to sometimes blue screens.
However, I think it is very unlikely that the problem is due to corruption of the driver, because the identical symptoms exist on both my laptop and desktop machines, which have very different stuff installed, and are used for different purposes.
Thanks for the suggestion. One of the first things I did was to look at the event logs. Nothing of interest there. Although there are errors, they have been occurring for a long time, and pertain to irrelevant things, like an uninstalled VPN device not installing, or timeouts on some firewall software drivers, or performance counters not working. These have been occurring for a long time before this problem came up. These are generally errors that occur *after* the reboot from the blue screen. There are no errors in the event log before the blue screen, either system or application. (Not too surprising, since the blue screen occurs instantaneously as soon as the output is sent to the printer driver.)
However, I don’t know what you mean by “SideBySide” errors?
