Has this been fixed?


[ Follow Ups ] [ Post Followup ] [ Signature.net Forum ]

Posted by Marc Shevick on April 11, 2008 at 11:15:49:

I had an issue a while back where a client was using a printer name NP1 instead of LP1. The problem was that there was no NP1 set up as a printer, however, there was an object file called NP1 in the program directory. The result was the NP1 program was corrupted. I thought I remembered seeing a change was made to COMET to prevent this from happening. However, I can't find it in the release information that this change was done. Unfortunately, I have another client with a new employee who is now using an existing program name for the printer. Did I imagine that this was changed? If not, which version of COMET contains the fix.


Follow Ups:



Post a Followup

Name:
E-Mail:

Subject:

What is the name of the main Signature System's Product?  

Comments:

Optional Link URL:
Link Title:
Optional Image URL:

You may attach up to 5 files to your followup (see below):





Each file can be a maximum of 1MB in length Uploaded files will be purged from the server on a regular basis.


[ Follow Ups ] [ Post Followup ] [ Signature.net Forum ]