[Migrated content. Thread originally posted on 31 October 2007]
We have 2 installations of our software, one using thin client and the other is windows based doing a runcbl32. My question is if anyone knows how I can tell which way the application was invoked? We did not have any issues with this until we started making calls to system dlls, like kernel32 and/or user32.[Migrated content. Thread originally posted on 31 October 2007]
We have 2 installations of our software, one using thin client and the other is windows based doing a runcbl32. My question is if anyone knows how I can tell which way the application was invoked? We did not have any issues with this until we started making calls to system dlls, like kernel32 and/or user32.
accept TERMINAL-ABILITIES from TERMINAL-INFOThe IS-REMOTE field is set to "true" if the program is running with AcuXUI or thin client. When IS-REMOTE is "true", CLIENT-MACHINE-NAME is set to the name of the client that is running AcuXUI or thin client, plus a hyphen ("-") and the hex value of the client process ID.
[Migrated content. Thread originally posted on 31 October 2007]
We have 2 installations of our software, one using thin client and the other is windows based doing a runcbl32. My question is if anyone knows how I can tell which way the application was invoked? We did not have any issues with this until we started making calls to system dlls, like kernel32 and/or user32.accept TERMINAL-ABILITIES from TERMINAL-INFOThe IS-REMOTE field is set to "true" if the program is running with AcuXUI or thin client. When IS-REMOTE is "true", CLIENT-MACHINE-NAME is set to the name of the client that is running AcuXUI or thin client, plus a hyphen ("-") and the hex value of the client process ID.
Already have an account? Login
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
77 4th Avenue
Waltham, MA 02451 USA
