Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>I got this answer from WordCraft (company behind Unimessage Pro)</p> <blockquote> <ol> <li><p>Create a file named WilCapAX.INI in the main Windows folder, e.g. C:\Windows\WilCapAX.INI The file should contain the following: [WilCapAX] Commands=C:\Commands.DAT Where "C:\Commands.DAT" is the name of a text file you are going to create in your .NET application to pass the<br> embedded commands to Unimessage Pro. You can edit the path if necessary, but keep to short form file and<br> folder names.</p></li> <li><p>In your .NET application when you have something to send via<br> Unimessage Pro you then need to:</p> <p>2.1 Create a text file named, depending on the name defined in WilCapAX.INI, C:\Commands.DAT containing:</p> <pre><code> BLANK LINE [[TO=Fax Number or Email address]] [[SUBJECT=Whatever you want the subject to be]] </code></pre> <p>The first line of the file must either be blank or contain something other than an embedded command - it will be skipped. The other lines in the C:\Commands.DAT file should each contain an embedded command. </p> <p>2.2 Print ONE message to the Unimessage Pro printer - the Unimessage Pro printer accept the print job and will look for the file specified in WilCapAX.INI. If the file specified in WilCapAX.INI (C:\Commands.DAT) is found, embedded commands are extracted from it and then the "C:\Commands.DAT" file is deleted and the print capture processed together with the command extracted from the C:\Commands.DAT file.</p> <p>2.3 Wait for the C:\Commands.DAT file to disappear (indicating that it has been processed by the Unimessage Pro printer) and then repeat as necessary.</p></li> </ol> </blockquote> <p>This solved the problem! :)</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload