DeskWatcher updated to V0.08
Thomas Milius (7848) 116 posts |
My first commercial RISC OS application DeskWatcher has been updated to version 0.08. DeskWatcher is a screen sharing program. This means that with DeskWatcher you can show the content of the screen of a RISC OS based computer on another In V0.08 a couple of errors have been corrected and some new features have been added - Fixed opponent license Invers connection means that a client can provide the connection port to which the server can connect to. This is useful to avoid changes at the firewall at server side for remote support. You can obtain detailed information about DeskWatcher from the homepage of my company http://www.stader-softwareentwicklung-gmbh.com.de/indexE.htm or the German version http://www.stader-softwareentwicklung-gmbh.com.de/index.htm section RISC OS Software There you can also download the manual. Update from V0.07 to V0.08 is free of charge for existing users. Prices are as follows
After clarification of a couple of questions in context of Brexit my company is VAT registered in UK from 1st April 2021 onwards. In case you have questions about the program please contact me by e-mail: Verwaltung@stader-softwareentwicklung-gmbh.com.de Best Regards Thomas Milius |
|||||||||||||||||||||||||||||||||||
David J. Ruck (33) 1635 posts |
This looks good as a RISC OS to RISC OS screen sharing using the OS APIs could be much more efficient than porting an existing desktop sharing protocol, such as RDP or VNC. However it is up against VNC which although slow does work well, and is free. I would have thought that a lower initial cost would have created a smaller bar to purchase, especially as the manual describes quite a few areas which could be improved upon (security, encryption, automatic font transferring, etc), which could be paid for upgrades. I’m glad there was a section on licencing in the manual on the website, as I wouldn’t have been able to work it out otherwise, perhaps worth putting this on the website more predominately. However the main issue for me is I control my RISC OS machines from Linux boxes rather than each other, so need to use a common protocol like VNC, rather than something which is RISC OS to RISC OS only. |
|||||||||||||||||||||||||||||||||||
David Feugey (2125) 2709 posts |
DeskWatcher is really fast. In fact, most of the time, you won’t see the difference with the local WIMP. For now, the only problems I can see is a jumpy cursor (could be solved with a “local cursor option”), and some crash when leaving a session if Messenger is running on the server side. The memory use is quite high too on the server side, but I suspect it’ll be better later :) But I agree that to compete with TeamViewer, it should have a model with: |
|||||||||||||||||||||||||||||||||||
Raik (463) 2061 posts |
We have try “Invers Connection”. |
|||||||||||||||||||||||||||||||||||
andym (447) 473 posts |
I have also used the Invers connection, in a real world situation, and it worked perfectly. This was between my 72mbps connection and the other computer, connected to self-described ‘flaky’ broadband. Bit of a pause whilst it drew the initial screen and then it was very usable! Didn’t try file transfer though. About 200 miles! |
|||||||||||||||||||||||||||||||||||
Steve Pampling (1551) 8170 posts |
Latency will be in milliseconds Coventry to Worcester via Perry Bar, Birmingham < 10ms (even on a Virgin MPLS) Worst part in the scenario you are discussing = RO network stack. |
|||||||||||||||||||||||||||||||||||
WPB (1391) 352 posts |
I recently purchased DeskWatcher for the purpose of providing remote support to my father who also uses RISC OS. I can say that my experience so far is really excellent. No need for him to make any changes to his network setup at his end because he uses the “Invers” connection. And Thomas’s support has been fantastic. Highly recommended! |