David Li Bergolis wrote:
Well, that the tray icon is mandatory to avoid problems with AV Software, that's not correct.
Look at UltraVNC, you are able to completely disable the tray icon and any notification at connection.
You can even open an integrated filemanager and transfer files from and to the host without any notification.
The host doesn't show any information at all when properly configured.
And nonetheless, AV Software don't flag it as Virus/Trojan/PUP, etc...
To be honest, UltraVNC needs an open port for ANY computer you want to control remote,
RU needs only ONE open port for the server, OK.
I really don't care about the systray icon at all, but the connection nag screen blocks any work or click at that area.
You could make a permanent and nonremovable systray icon that indicates idle, connection, errorstate, etc,...
but please remove that banner. It makes no sense for me to double annoy the host.
If it is possible with a paid version, it would be acceptable for me, although it would be a license-wise overkill,
because I'm a private user with 6 computers inside my family circle.
But I have to admit, that your price policy is really fair, so I would buy.
Is there any way to remove that banner?
It seems to be a bug, because I configured 5 computers with windows 10 and 1 computer with windows 7.
On the Windows 10 computers i can click on the "okay" button on the banner.
At my Windows 7 machine i cannot click at ANY button on that banner, neither physically, nor from remote.
I tried to reinstall RU Host with manually deleting any registry entries and any folder created (ProgramData and AppData).
That's only a problem with Windows 7. I tested it with XP, no problem at all.
My 6-year-old daughter understands almost immediately when I explain to her a mistake, sometimes with far less information.
Here, on the other hand, I explain a problem in minute detail, even with screenshots, and yet it is pretended that you don't understand what I'm talking about at all?
At the same time, everyone else here has understood exactly what is being said.
That's simply offending.
I don't expect that this error will be fixed at all, because it regards only Windows 7, that's OK for me.
I found a workaround and I posted it here for other people.
But I simply expect that an little issue will be at least called an issue inside the Software.
Jesus, it's just a bug, a fairly minor one at that, but it's a bug.
The next weekend I'll buy a license for my home, because it is still a great piece of Software and it's completely self hostable, and I support that developers.
But please for the next time.
Read the posts and don't try to take people for stupid.