Anthony Waddell's community posts

I sent the viewer side log file to support@remoteutilities.com. Cannot send host log file because I can't connect to it.

Thanks for looking into this problem.

Down for me too.

Yes, it is a specific action. It is when I click the red X to close the app. That is the only time I've seen it happen. But the frequency of it happening is random, it doesn't happen all the time.

Several times a week, the Viewer crashes with a run time error. There is a windows that pops up with the error code, but it goes away too fast for me to write the info down. But here are the two entries entered into Windows Event Viewer:

First:
Faulting application name: rutview.exe, version: 7.1.7.0, time stamp: 0x631143fa
Faulting module name: rutview.exe, version: 7.1.7.0, time stamp: 0x631143fa
Exception code: 0xc0000005
Fault offset: 0x0001093e
Faulting process id: 0x0x30A4
Faulting application start time: 0x0x1D90274AC8B3822
Faulting application path: C:\Program Files (x86)\Remote Utilities - Viewer\rutview.exe
Faulting module path: C:\Program Files (x86)\Remote Utilities - Viewer\rutview.exe
Report Id: 9b682992-fbb8-401f-97fe-6810947d6c0c
Faulting package full name:
Faulting package-relative application ID:

Followed by:
Faulting application name: rutview.exe, version: 7.1.7.0, time stamp: 0x631143fa
Faulting module name: rutview.exe, version: 7.1.7.0, time stamp: 0x631143fa
Exception code: 0xc000041d
Fault offset: 0x0028eee9
Faulting process id: 0x0x30A4
Faulting application start time: 0x0x1D90274AC8B3822
Faulting application path: C:\Program Files (x86)\Remote Utilities - Viewer\rutview.exe
Faulting module path: C:\Program Files (x86)\Remote Utilities - Viewer\rutview.exe
Report Id: c74c75ee-0477-4d08-9260-bc3dec6ed499
Faulting package full name:
Faulting package-relative application ID:

I'm running viewer 7.1.7.0 and it NEVER remembers which monitor the remote session was displayed on. I have the main panel on monitor #2 (to keep it out of the way), and when I connect to a host, the world map splash screen always opens on monitor #2, and then the remote session to the host opens on monitor #2. I then move it to monitor #1 which is where I want it. But the next time I start a session, it always starts on monitor #2.

That is not the only problem I've noticed with window placement. I'll attach a screen shot. If I use file transfer, the transfer window opens but is partially offscreen. In particular, the Close button, as you can see. Even though I move it to a better place so I can click the close button, it always opens partially off screen on subsequent uses.

Neither of these problems are a big deal, but are somewhat annoying.

What would be really cool is if I could draw on the host's screen. For example, to draw a red circle around a certain word or phrase to show the host user something important. Or the ability to highlight a particular area of the screen.

Regarding being able to move the banner to a different corner - will that include any of the 4 corners on a second attached monitor or only on monitor #1?

- Windows 10 and later: the notification can be made visible for the remote side only, and invisible on the Viewer side. We are still investigating this option, but most likely it is possible to implement.

- Ability to pick the corner in which the notification will be shown.

This means that if I am a support person (viewer) who connects to a client's computer (host), I will NOT see the notification banner? I will not be able see everything that is on my client's screen when I am asked to assist? If I can't see it, how will I be able to pick a corner for the notification to be shown?

Is my understanding correct that the paid version does not have this persistent semi-transparent connection alert? What, exactly, does the paid version have? Does it have any kind of alert at all, or does it have an alert that can be dismissed, does it have an alert that can be optional or configured by the user?

I fully agree - the host should be able to acknowledge and dismiss.