Mario,

Thanks for the help, but I am still unable to make this work on machines
that have OS/2 2.1 and the old Communications Manager installed.

I forgot to mention that there is a new Lan Server version installed
on the machines on which it works. Maybe this is the reason ??
Some Rexx return-codes changed with this new version I believe.
I am no Rexx-specialist, but I believe returncode 255 becomes 0 now...

 MS> DosCopy is an OS/2 API, so it has nothing to do with CSET++.

That's why I think it has to do with the difference between OS/2 2.1 and 2.11.
But because I only have the problem with copying to a network printer-port,
not with a destination-file on disk, maybe Lan Server is the culprit ??

 MS> #define ERROR_INVALID_HANDLE    6       /* MSG%INVALID_HANDLE */

OK, but what handle ? DosCopy has no handles as parameter.

I use DosCopy(pszFileToPrint, "LPT1", DCPY_EXISTING);

Strange enough, this works on some machines, but not on others.

Does anyone know another possibility to print an ASCII file to a printer ?
I used the following methods, but they aren't very good, because they don't
give you enough error-control, which is very important in this case:

* Open the file for READ and WRITE each char to the printerport.
  You can't control any errors, because when the network-alias for the
  printer is not there, you write the file to your local LPT-port, and even
  if there is no device attached, the DosCopy call still has returncode RC_OK.

* Use the 'copy' command (DosExecProgram call) to copy the file.
  There is no way to get the return-code, so no control over errors.

Anyone suggestions ?

Greetings,

//Peter.

                           

--- Terminate 1.50