This version of Remote Desktop (RDT) is intended to act as a remote helper for users that require assistance but have limited capability to handle remote connections. Allowing a helper to access your computer requires a certain amount of skill in allowing an outside connection. Most casual users do not possess that ability, and it does come with a degree of risk. Therefore, I developed this helper system that allows the user to connect with an outside helper, as well as the other way around.
If a user is able to activate a listening socket to allow an outside connection, that connection must include security provisions to prevent an unauthorized hacker from gaining access. If however, the user is able to connect to the outside helper directly, there is no need for a lot of sophisticated security. You contact the helper by voice or other communication technology, and make the connection yourself which is relatively unimpeded.
The "server" term is usually reserved for the listening socket that accepts an outside connection, and the "client" term is usually reserved for the application that connects to the server. In this application however, there is only one program that can act as either the client or the server. For that reason, those sessions have been named "Helper" and "Desktop" to differentiate.
Because the remote Desktop is intended to be activated only when it is needed, there is no UserID/Password, and no facility to operate as a service. There is also no logging function. There is however a crude method of hiding individual keystrokes to prevent man-in-the-middle interception of keystrokes. If you need to leave the remote Desktop application running and awaiting a connection, you should choose an application with better security.
The IP Version will default to IPv4, the port will default to 16748, and the IP Address will default to 127.0.0.1 (IPv4 loopback). Change the IP Address to the machine that you want to connect to. Start Remote Desktop on the other machine. Check the IP Version and Port number, and don't worry about the IP Address because we are not going to use it. That machine is going to become the Remote Desktop. Click the "DeskTop" option and then click "LISTEN". The IP Address will go blank, and that system should be waiting for a connection. You can verify that with the "netstat -an" command.
Now go back to the first machine. The "Helper" option should be active, so click on the "CONNECT" button. If all goes well, you should connect with the other machine, the window will expand to 80% of the screen, and the remote screen should display. Note that the original window on the remote screen has been minimized to the Task Bar, and that the option to minimize is not available on the original window itself. That is done to discourage users from leaving the program listening on the Task Bar. When the Helper terminates the connection, the Desktop program is terminated as well.
This program is also unique in that there is no setup required. However, the information used in a successful connection is saved for the next time. Any good Helper program should be able to perform tasks that require elevation, and that particular problem still remains unresolved.
It was reported by a tester that the Desktop program did not work on a dual monitor system. Screen Width and Height was changed to the Virtual Width and Height.
Code:
ScreenL = GetSystemMetrics(76) 'Virtual Left
ScreenW = GetSystemMetrics(78) 'Virtual Width
ScreenT = GetSystemMetrics(77) 'Virtual Top
ScreenH = GetSystemMetrics(79) 'Virtual Height
At the same time, the memory allocated for the screen image was increased to account for the additional demand. The update is included as a separate post.
The discontinued Intel JPEG Library is not free to download and use.
In the past Intel's download process included a developer license but unless you have kept that original distribution package you have no rights to develop with or distribute this library. There is no legal way to obtain it anymore.
Very useful code, but in Windows XP bcrypt.dll There was a situation that couldn't be found, but there were bcrypt.dll It should be bcrypt.dll Do not support XP, how to solve this problem, thank you!
Very useful code, but in Windows XP bcrypt.dll There was a situation that couldn't be found, but there were bcrypt.dll It should be bcrypt.dll Do not support XP, how to solve this problem, thank you!
bcrypt.dll is not the only problem you will find on XP. It will not support "ws2_32.dll" as well, which is required for socket transmission.
bcrypt.dll is not the only problem you will find on XP. It will not support "ws2_32.dll" as well, which is required for socket transmission.
J.A. Coutts
I'm currently testing ws2_32.dll in an NT 4.0 VM and as far as I remember Winsock 2.0 was introduced in Win95 if not before that.
In Win 3.11 there was this hugely popular Trumpet Winsock application (the Winsock 1.0 implementation) that shimmed internet access through DOS based packet drivers -- either for ethernet controllers or PPP dial-up shims (a second one) -- that was made obsolete by Winsock 2.0 but probably not for this legacy OS.