Peter Gray's community posts

Yes, now there's a key file (key.rlicense) that you need to drag-n-drop to License key storage, or just open the Windows Open dialog and select the file on the disk and it will get added to the license key storage.

OK
I upgraded my license, and got an email with a (much longer) text string containing the license key.
I copied that into a text file and saved it, with a .rlicense extension.
I then input that file to the license key dialog.  It seems to have worked.
Perhaps this process, or a refined version of it, should be added to your licensing help information?

I've just installed V 7.0.0.0 viewer on a test machine (XP) over the top of vv6.12.4.0 beta.4
Up to beta 2, the viewer used my old licence key.  Beta 3 had built-in beta license, so did beta 4, licencse key storage was not available.
7.0 seems to need a licence key file, whereas previous versions wanted a text string.
How do get my existing starter licence into v 7.0?

Hi Polina.

I've just downloaded the beta 3 and installed the Viewer on my primary XP machine.  I can now connect with it to my primary Win 7 machine (which is still at beta 2).  Too late this evening to do any further tests.

Many thanks for the long-awaited update!

Peter

Hello David and Polina.

Fromm my experience, 6.12.2.0 Beta 2 viewer will not work on Win XP.
See page 6 of the Remote Utilities 6.12 Beta thread.

Peter

Hello Polina and Simon

I too have had problems with reomote printing while working from home; I'm not doing that so much now, so won't be able to do much testing, but here's what I remember.

Viewer is 6.10.10.0 on Windows XP; can't upgrade to 6.12.2 beta, it won't work on XP.
Host was originally 6.10.10.0 on Windows 7, since upgraded to 6.12.2 beta.
Printer is Epson ET-2720

Most of my documents are A4 size, but the remote printing usually tries to print as 8.5 x 11 inch, there doesn't seem to be a way to tell it otherwise.  This is unfortunate, because the printer is set up for A4 paper.

Some (but not all) Excel spreadsheets come across as blank documents.

Sometimes, I have had a message that the remote printer has stopped working, then no document is received.

printing PDF files usually works OK (I use Foxit PDF viewer, and the prints come over as A4 if I tell it to use paper size same as document size, otherwise remote printer defaults to 8.5 x 11 inch)

Printing jpeg or other images from Irfanview seems to be able to set the paper size to whatever I want.

I would like to be able to upgrade the viewer.  Is there any prospect of a 6.12 beta 3 being released?

Best Regards, Peter.

I have had a similar problrm with one specific host, on a direct connection, both viewer and host running version 6.10.10.0, and lately with the host running version 6.12.2.0 beta 2.  If I have the full control window on screen, then do something else so the window is not visible, but has not been minimied, then when I come back to it after a long enough time, the window is frozen.  NOT disconnected.  If I click anywhere in the window, one of two things happens.  Either after a short wait the view refreshes and I again have control, or (usually after a longer wait) the window goes black for a while, and then recovers, and the host displays a message something like "the display driver stopped responding and has recovered"  I have always put this down to a problem with that host.

It is hard to tell, but the problem may be less severe since changing to the beta host.

If I switch to a different tab on the full control window to work on a different host, or minimise the window, before going to do something else, the problem does not seem to occur.

Perhaps Gaz's host is goimg to sleep in some way (screen saver or something) and not waking up when he returns to the viewer?

Hello Polina.

Polina Krasnoborceva wrote:

We have managed to reproduce the issue on both Viewer and Host when used on WindowsXP OS. We will implement a fix for this in the next beta version update. Sorry for the inconvenience.

Splendid news!

I don't normally have any reason to use the Agent, but I have just checked; the beta Agent also has the issue on Windows XP.

I am eagerly looking forward to the next beta release.

With best wshes

Peter.

Hi Polina

Polina Krasnoborceva wrote:

I have checked with our developers on the issue. Perhaps, it might be occurring if the OpenSSL library is blocked somehow. Could you please provide us a screenshot of the following folder: C:\Program Files (x86)\Remote Utilities - Viewer\? You can send it to [email protected].

I need to work out how to regain remote access to the problem machine in order to do that easily.  Perhaps turn off the host and use version Agent 6.10.10.0?  I'll see what I can manage.

Polina Krasnoborceva wrote:

In addition, please check if the issue occurs as well when using the 6.12 Beta 2 version of the Portable Viewer. Namely, please see if there's any unusual behavior of antivirus software if there's any installed.

I put versions 6.10.10.0 and 6.12.2.0 beta 2 Portable Viewer onto USB drive, each in its own folder.  I had some problems running them at first, involving display language and expired trial period, but that's not the issue here.  I also had to shut down the installed viewer before running them, or I just got the installed one!

When run on my main XP machine (the one that has Viewer and Host version 6.10.10.0 installed) the 6,10 portable viewer was able to log onto and control a sample W7 machine..  The beta portable viewer had the Access Denied behaviour.  This happened even with Avast anti-virus temporarily disabled.

Moving the drive to a W7 machine, both versions of the portable viewer were able to log on to and control the sample machine.

This problem with the beta viewer seems to me to be specific to Windows XP.

On comparing the two portable versions , I see that the beta has libeay32.dll and ssleay32.dll in the assets folder, which are not present in the 6.10 version.  Are these related to the use of OpenSSL?

Hi Polina.

Did you get my second email with log files for W7 beta viewer trying to log in to XP beta host?

Polina Krasnoborceva wrote:

Unfortunately, we couldn't reproduce the issue. Could you please also clarify what authentication methods are enabled for the remote Hosts that you're not able to connect to?

All the hosts have single password authentication Enabled, and all other methods Disabled.

To summarise.  I have one W7 with beta viewerr and 6.10.10.0 host istalled, a different W7 with beta host and 6.10.10.0 viewer installed, one XP with both beta viewer and beta host installed.  One other XP and W7 here and serveral W7 elsewhere have 6.10.10.0 viewer and host installed.

The XP with beta viewer cannot log onto any of the other machines (Access Denied), whichever OS and host version they have.

None of the other machines, whichever OS and viewer version they have, can log onto the XP with beta host (Access Denied).

Both XP and W7 machines with 6.10.10.0 viewer can log onto the W7 with beta host.

Here's an update on using version 12 beta 2 with windows XP.
Yesterady I installed the beta viewer on an XP box and a W7 box.  Both could see my other machines (all with version 10.10.0.0 host) on direct and internet connections, but the XP viewer could not log on to any of them.  It responded Access Denied, and I sent you reader and host log files.
The W7 viewer, on the other hand, could log onto and control other machines both XP and W7.
This evening I used the W7 beta viewer to remote install the beta host onto an XP box and a W7 box.  Both installations reported successful completion, and after the usual delays while the hosts restarted etc., the viewer could see the hosts come online.  The version 10.10.0.0 viewer on the XP box that I am typing this on also saw the hosts come online.
The W7 beta viewer could log on to and control the W7 beta host.  Even better, the XP v10.10.0.0 viewer on this box could also log into and control the W7 beta host!
However, the W7 beta viewer could not log on to the XP beta host, it got Access Denied.  This XP v10.10 viewer also got Access Denied from the XP beta host.
I have now run out of machines I can safely experiment with.
I can no longer remotely control the XP beta host; when I manage to get physical access (that is, find and connect the keyboard, mouse and monitor!), I'll get log files and send them to you.

On a side note, earlier posts mention that the v12 host does not use the display driver.  Does intalling the new host automatically remove the driver, or does that have to be done separately?