Peter Gray's community posts

Hello Conrad.

Viewer 7.1.2.0 installed OK on my XP machine.  So did Host 7,1,2,0.  Both seem to work OK.

Thank you.

Just been forced to upgrade viewer to version 7, biut it crashes in WinXP. Not hsppy.

Viewer 7.0.2.0 works fine on my last working XP machine.
Updated to Viewer 7.1.0.0.  Try to run, get pop-op error message "Viewer\rutview.exe is not a valid Win32 application", but does not crash.
Updated to Viewer 7.1.1.0.  Try to run, get a different error report about EAccessViolation.  OK that and viewer comes up, but without list of connections.  Attempt to close viewer, get error message again, Viewer does not close.  Had to force close using task manager.
And now I can't revert to Viewer 7.0.2.0 without first uninstalling v 7.1.1.0, but the uninstall fails with gibberish error messages!
I'll have to try a complete manual uninstall when I have the time.

Hi Pauline.
I've not checked all the combinations, but for all those I have checked, Advanced Mouse Scroll is enabled,
In the list below, Scroll works means the selected application on the host is scrolled; Scroll fails meand it is not, but the host desktop may be scrolled within the viewer window.
H4, C4 etc. are the various machines.  There are others with the problem, but they are remote from me.
Video capture is more than I can cope with at this tme of night (9:40 pm).

H4: Intel Pentium 4 Win XP Pro (v2002) SP3 32 bit
Viewer 7.0.2.0, Host 7.0.2.0
Viewing H5: Scroll works
Viewing S1: Scroll works
Viewing HL: Scroll works

C4: AMD Athlon Win 7 Pro SP1 64 bit
Viewewr 7.1.1.0, Host 7.1.0.0
Viewing H5: Scroll fails
Viewing S1: Scroll fails
Viewing HL: Scroll fails

H5: Intel Pentium dual core CPU (E5200) Win 7 Pro SP1 64 bit
Viewer 7.0.2.0 Host 7.1.1.0
Not directly accessible to use Viewer, working indirectly via H4
Viewing C4: Scroll works
Viewing S1: Scroll works

S1: Intel Pentium dual CPU (E2220) Win 7 Pro 64 bit
Viewer 7.1.0.0, Host 7.1.0.0
Not directly accessible to use Viewer

HL: AMD E2-1800 APU Win 7 Pro SP1 64 bit
Viewer 7.1.0.0, Host 7.1.0.0
Viewing H5: Scroll fails
Viewing S1: Scroll fails
Viewing C4: Scroll fails

Hi Pauline
I'm getting together the info you requested, both for the machines I had already tried, and also for some others where I have not yet upgraded Viewer and Host.
I normally use stretch view, or normal view if the entire host desktop fits in the viewer window.  During data gathering I needed to use Normal view where the host desktop was bigger than the viewer window (so as to get legible text!).  In that mode, with Viewer 7..0.2.0, the scroll wheel scrolls the selected Host wiindow (e.g a browser or a document), but with Viewer 7.1.0.0 or 7.1.1.0, the scroll wheel vertically scrolls the Host desktop within the Viewer window.  This behaviour seems to be independent of the Host version in use.
Details of machine builds and Viewer and Host installs and behaviour to follow, if you still want them.
Peter.

Using viewer and host v 7.0.2.0, the mouse scroll wheel would scroll windows on the host.  Since upgrading to v 7.1.0.0, that no longer works.  
The mouse wheel *does* scroll other windows on the viewer machine, but *not* windows on the host connected to with the viewer.
This happens with two different viewers and two different hosts, all usung Windows 7.
Further upgrading to v 7.1.1.0 has not changed this behaviour.
I have not had the opportunity to revert to v 7.0.2.0 to see if the problem goes away.

Hi Polina.

My installation log, for an XP machine, on 27 March:-

27-03-2021_18:19:35#T:Installation is started #1
27-03-2021_18:19:38#T:Installation is started #2
27-03-2021_18:19:38#T:Uninstalling old version...
27-03-2021_18:19:38#T:Product code: {305B0369-6108-4910-BDFF-FE56F88634AE}
27-03-2021_18:20:05#T:msiexec exit code: 0
27-03-2021_18:20:06#T:Uninstallation successfully completed
27-03-2021_18:20:07#T:Installing...
27-03-2021_18:20:07#T:MSI file: C:\RemoteHostInstall70002(27-03-2021-18-19-17)\host7.0.0.3.msi
27-03-2021_18:20:45#T:SilentInstall: installation 70003
27-03-2021_18:20:45#T:SilentInstall: service found, removing
27-03-2021_18:20:49#T:SilentInstall: CreateService. OK
27-03-2021_18:20:50#T:SilentInstall: finished
27-03-2021_18:20:51#T:msiexec exit code: 0
27-03-2021_18:20:51#T:Installation successfully completed
27-03-2021_18:20:51#T:Installation/uninstallation is finished

And an extract from the host log for the same period (with Internet IDs xxxxxxxxxxxxx out:-

  27.03.2021---18:18:41:417 36 192.168.101.148 Access granted. Session: {959489C3-3619-4B19-AFB9-901F55D3145E}
  27.03.2021---18:19:17:870 36 192.168.101.148 Access granted.
  27.03.2021---18:19:17:933 55 192.168.101.148 Remote upgrade connection. Started. Mode: 0; Session: {959489C3-3619-4B19-AFB9-901F55D3145E}
  27.03.2021---18:19:35:073 56 192.168.101.148 Remote upgrade connection.Closed. Session: {959489C3-3619-4B19-AFB9-901F55D3145E}
  27.03.2021---18:19:56:886 34   Remote Utilities - Host 70002 is started. GMT Windows 5.1 32bit
  27.03.2021---18:19:57:261 96   Relay node: OK ID: xxxxxxxxxxxxx; Port: 5655; Try count: 1
  27.03.2021---18:19:59:808 96   Relay node redirect: OK. Relay redirect. To: 192.119.14.178
  27.03.2021---18:20:00:198 96   Relay node: OK ID: xxxxxxxxxxxxx; Port: 5655; Try count: 1
  27.03.2021---18:20:01:917 109   Fatal error. rfusclient.exe not found.
  27.03.2021---18:20:52:714 34   Remote Utilities - Host 70003 is started. GMT Windows 5.1 32bit
  27.03.2021---18:20:53:198 96   Relay node: OK ID: xxxxxxxxxxxxx; Port: 5655; Try count: 1
  27.03.2021---18:20:54:245 96   Relay node redirect: OK. Relay redirect. To: 192.119.14.178
  27.03.2021---18:20:54:636 96   Relay node: OK ID: xxxxxxxxxxxxx; Port: 5655; Try count: 1
  27.03.2021---18:21:32:120 36 192.168.101.148 Access granted. Session: {959489C3-3619-4B19-AFB9-901F55D3145E}
  27.03.2021---18:21:37:261 104 192.168.101.148 LogOff command. Session: {959489C3-3619-4B19-AFB9-901F55D3145E}

The host log includes the fatal error.

Hope that helps, Peter

Further info:  Just updated another XP Host.  This time I had not already connected to it with the Viewer before doing the update, and no user was logged onto it.  I still got the error popup, but the thing with three Host icons did not happen.  Just the one there after I had connected and logged in as a user.

On all the machines where I have updated the Host to v 7.0.0.3 from 7.0.0.2 or 7.0.0.1, using remote install with Remote Utilities security, the host pops up an error message

However, the update seems to complete, and I can connect to the host afterwards.  In the icon tray I then find two red and one blue host icons.  The blue and one red one disappear if I mouse over them, the second red is the active connection.  So it looks as if the error was not really fatal, and the remote install had a second try.  In all the cases I have checked, the file was present after the update.
All the hosts were on Windows 7 except one which was on XP
This error did not happen when I updated a 6.10. beta 4 host to 7.0.0.3.

Thar reminds me:on my XP Viewer machine at v 7.0.0.1, if I right click anywhere in either of the explorer panes in the file transfer window, the entire screen goes white.  Rather scary the first time it happened, but hitting escape key gets back to normal display.  I can't remember what happened in  v 6.10.0.0, and don't know what is supposed to happen.

Hi Conrad.

Both machines where Host didn't autostart have Avast free antivirus, as do all my other personal machines.  I have sometimes (but by no means often) had a false positive fr om it on downloading or installing or first time running new versions of Host and Viewer, but it has always let me create an exception.  In any case, I don't think it's an antivirus issue, since I can stsrt the Host manually on both machines.

I do have a rather old version of Spybot Search and Destroy on those machines, which uses a lot of CPU during startup.  Maybe that is causing the Host service to take too long responding to its start request.  I could try disabling it and see what happens.  The third machine I tried does not have Spybot S & D, and the host autostarted OK.

Other machines that I support have Avast Business AV, but that also lets me create exceptions if I get a false positive.  However, some of those machines are also slow to start for various reasons, which makes me nervous about doing a remote machine restart.  I have sometimes had to go in person to start the Host after a machine restart, or use an alternative remote access tool wh ere one is already installed.