Printing from Application Server

[Ned L]

I'm trying to print something on my local printer from a Providex session running under Application Server in a remote location.
I thought I could just
OPEN (1) "*winprt*"
to get a Windows pop up window that would allow me to select a printer known to my Windows system.
But nothing comes up.  It just accepts the command.  If I
PRINT PTH(1)
it replies "*winprt*"
What am I doing wrong?

I am starting Windx using the following target:
"C:\PVX Plus Technologies\Windx Plugin 2017\pxplus.exe" -mn "*client" -ARG "x.x.x.x" 10020 DMIAPP -ka -ssl

My application works well, except that I need to know how to print.

Thanks in advance for any help.

Ned Lee
AMS Software, QA Solutions Division

[James Zukowski]

I'm guessing that you're running on a Windows server. Try:
OPEN (1) "[lcl]*winprt*"

[Ned L]

James -
Thanks for your prompt reply.
Yes, you are correct.  The App Server IS running under Windows.
But when I tried your suggestion, I got
OPEN (1)"[lcl]*winprnt*"
Error #61: Authorization failure

I tried starting WindX as Administrator, but that didn't change anything.

Also note that the printer I want to use is sitting on my desk (rather than connected to the system that is running App Server (which is in another state.))  Does Providex consider my printer a 'local' printer?  Or are local printers ones that are known to the server running the App Server.

Thanks again for your help.
- Ned

[James Zukowski]

Which did you type:
OPEN (1)"[lcl]*winprt*"
or
OPEN (1)"[lcl]*winprnt*"
...?
Be sure it's the first...

[Ned L]

James -
Sorry for the typo in my post.
When I tested your suggestion, I DID use
OPEN (1)"[lcl]*winprt*"

The typo occurred when I was writing my post.  Sorry for causing confusion.  I will be more careful in the future.
I still have the problem:
OPEN (1) "[lcl]*winprt*"
and
OPEN (1) "[wdx]*winprt*"
both generate
Error #61: Authorization failure
How can I get the system to print to the printer on my desk?

Thanks again for all your help!
- Ned

[James Zukowski]

I'm going to have to defer to others for deeper details, as I have not used Application Server. These are just items that I would have anyone check if they're having local printer problems.

[Ned L]

James -
Thanks for your time and willingness to help.
- Ned

[Ned L]

New information:
My question has become:
"How do I use WindX with a remote App Server?"
See below for details.

Apparently I'm not running under WindX.  That would explain my problem.
As mentioned earlier, the icon on my local desktop has target

"C:\PVX Plus Technologies\Windx Plugin 2017\pxplus.exe" -mn "*client" -ARG "x.x.x.x" 10020 DMIAPP -ka -ssl

I thought that meant I was running WindX

But now I see that the App Server configuration has, on the Apps tab details:
Client Type: "Any Client Type"

If I change that to "WindX Clients only", then when I try to log in I get
"Your are attempting to connect and run an application which is not able to handle your Client Software.  The application is designed to work with WindX only."
So the above target isn't considered WindX.
I can understand that I need to be using WindX in order to access my local printer.
So my question becomes:
"How do I use WindX with a remote App Server".

Any help or advice would be greatly appreciated.

- Ned Lee

[Mike King]

Generally you can access the local printer on a WindX session by issuing

OPEN (1) "[lcl]*winprt*"

HOWEVER -- If the user has enabled the WindX security and has not provided you access to the workstations resource you will receive an error 61 - "Authorization Failure".

By default the first time WindX starts up the user is asked if they want security enabled to which the default answer is "Yes".
When security is enabled whenever the host asks to access a local resource the user will be asked if they want to allow it to which the default response is "No -- refuse access" and will result in an error 61 on the server.
The user also has the option to make his response the default response to avoid being repeatedly asked the same question.

To reset security you should be able to press ALT-SPACE and select the "Reset WindX Authorization" option from the system menu.

[Ned L]

Mike -
That solved it!
Thank you for your help and expertise.