All,
I do not remember at which version it occurred, think 4.01, but the problem has consistently been in the code since, and though I emailed in the problem, don't think it got a serious look, but let me describe the problem:
Something in the code now looks for and make decisions based on printers, do not know what or why, cause printers and their defs should never be in or play with the base code.
Anyway if the default printer goes offline or down, an error of "Error Initializing the printer." with a Title Caption of "OpenCurPrinter: printer: printerpath\name" appears and for each email selected 5 to 10 occurrances of the error "Error creating font." with Title Caption of "CreateOneFont(b)" occur.
Oh Yes, everytime the POP3 executes to search for mail this whole series of messages starts again, regardless of where you are in the mailbox.
This is extremely annoying, and causes major problems especially in our company, where the default printer is a networked HP4L on a NetGear PS110 and when it goes down, about 25 people are getting the set of messages. This would be much worse in even larger companies. Oh Yes we use PMail commercially and have since 1998.
Please fix it so it will work right. Nothing in the Email engine should ever looks at any printer defs until an actual print is asked for.
Thanks!
OMR
P.S.
Forgot the most important part of this bug. When this error occurs, no mail can be seen or read as all the view are blank, such as occurs in the view window when the "Preview mode" is not "on" or "selected". To work around this problem, we have to:
1. Create "null printer" defs/sessions on each computer,
2. Close PMail,
3. Assign the default printer on each computer to the "null printer",
4. Re-open PMail.
Of course this causes problems, cause the users no longer get their error messages from the printer, forget and start printing to the null printer, etc. and then when the printer comes back up we have to reverse the process above and then re-assign all print jobs to the correct printer, which is a hassle, especially when .pdfs or postscript files print as the generic null printer defs cause problems on the HP4L.
OMR
<p>All,</p><p>&nbsp;</p><p>I do not remember at which version it occurred, think 4.01, but the problem has consistently been in the code since, and though I emailed in the problem, don't think it got a serious look, but let me describe&nbsp; the problem:</p><p>&nbsp;</p><p>Something in the code now looks for and make decisions based on printers, do not know what or why, cause printers and their defs should&nbsp; never be in or play with the base code.</p><p>&nbsp;</p><p>Anyway if the default printer goes offline or down, an error of "Error Initializing the printer." with a Title Caption of "OpenCurPrinter: printer: printerpath\name" appears and for each email selected 5 to 10 occurrances of the error "Error creating font." with Title Caption of "CreateOneFont(b)" occur.</p><p>&nbsp;</p><p>Oh Yes, everytime the POP3 executes to search for mail this whole series of messages starts again, regardless of where you are in the mailbox.&nbsp;</p><p>&nbsp;
This is extremely annoying, and causes major problems especially in our company, where the default printer is a networked HP4L on a NetGear PS110 and when it goes down, about 25 people are getting the set of messages.&nbsp; This would be much worse in even larger companies.&nbsp; Oh Yes we use PMail commercially and have since 1998.
</p><p>&nbsp;</p><p>Please fix it so it will work right.&nbsp; Nothing in the Email engine should ever looks at any printer defs until an actual print is asked for.</p><p>&nbsp;</p><p>Thanks!</p><p>&nbsp;</p><p>&nbsp;OMR</p><p>&nbsp;</p><p>P.S.&nbsp;</p><p>Forgot the most important part of this bug.&nbsp; When this error occurs, no mail can be seen or read as all the view are blank, such as occurs in the view window when the "Preview mode" is not "on" or "selected".&nbsp; To work around this problem, we have to:</p><p>1. Create "null printer" defs/sessions on each computer,</p><p>2. Close PMail,</p><p>3. Assign the default printer on each computer to the "null printer",</p><p>4. Re-open PMail.</p><p>&nbsp;
Of course this causes problems, cause the users no longer get their error messages from the printer, forget and start printing to the null printer, etc. and then when the printer comes back up we have to reverse the process above and then re-assign all print jobs to the correct printer, which is a hassle, especially when .pdfs or postscript files print as the generic null printer defs cause problems on the HP4L.</p><p>OMR&nbsp;</p>
