printkey2000 [6]

We have several users running Xmanager 1.3.9 under Window 2000 SP3, and we use the Freeware utility printkey2000 v5.1 for screen captures. Our main application running under emulation is Oracle Forms (4.5 and 6.0).

Problem: when capturing 6.0 screens using printkey2000, the screen image prints fine, but the Xmanager session will freeze or disappear. This does not happen when running Forms 4.5.

Any ideas on this? Using the Auto Cut/Paste Xmanager feature is not a viable option, as the users want to print directly to the printers and not have to copy the contents of the clipboard into another application to print.

Any help is appreciated, Thanks.

Please try to turn off the Auto Cut&Paste option. It may have a conflict with the printkey2000 program.

We will also try to test printkey2000 and inform you the result.

----
Technical Support

Both settings for Automatic Cut & Paste were tried, but the reaction was the same.

We have tried Printkey 2000 with Oracle Forms 6.0 in Solaris 9, Windows 2000. However Printkey 2000 worked well and there was no error found yet. Printing in Windows may freeze an application when the printer doesn't work properly or an invalid printer is selected.

Does the problem happen on all PCs in your network?

Xmanager 2.0 beta will be available in a few days. It includes the Printing feature for X applications. We hope this could help you.

----
Technical Support

Currently the problem exists with all users on a specific subnet. My own PC does not demonstrate the problem.

What is the print feature in 2.0?

Thanks.

In Xmanager 2.0, X application windows will have a Print command on the system menu. So, you don't have to use Printkey 2000 with Xmanager 2.0.

You will be able to display the system menu by right-clicking on the title bar of any X application windows, and then click Print to send the contents or entire window to the printer.

----
Technical Support

Initial look at the 2.0 beta version seems ok. A problem I ran into: it appears not to pass $DISPLAY via telnet. This was a bug I found in 1.3.9 and was fixed in a patch. Is this a known problem with 2.0?
Thanks.