As the title says, I don't think this is a problem that can be solved simply by using telnet or at time.
1. First, let me describe a certain thing, because I don't know what to call it. For example, the program run remotely with telnet or at time is in one space, while what a user logged into the zombie machine locally sees is in another space.
2. The 2 spaces are different.
3. Getting to the point, I have a remote monitoring software package in hand, made in VB. It is not the kind of monitoring method that first takes screenshots and then transfers them to a picture control; instead it reads memory directly, compresses it, and transmits it.
4. When I remotely use telnet or at time to run the server-side software, the client sees nothing but a black screen. But if I log in locally and run the server-side software directly (either by double-clicking or running it with a DOS command), the client can monitor normally.
5. It feels like two users are using one computer at the same time, and the two have their own separate interfaces, but the user I use with telnet and the locally logged-in user are actually the same.
6. How can this problem be solved? My own line of thinking is: make the program run remotely with telnet or at time be in the same space as the local login space.
1. First, let me describe a certain thing, because I don't know what to call it. For example, the program run remotely with telnet or at time is in one space, while what a user logged into the zombie machine locally sees is in another space.
2. The 2 spaces are different.
3. Getting to the point, I have a remote monitoring software package in hand, made in VB. It is not the kind of monitoring method that first takes screenshots and then transfers them to a picture control; instead it reads memory directly, compresses it, and transmits it.
4. When I remotely use telnet or at time to run the server-side software, the client sees nothing but a black screen. But if I log in locally and run the server-side software directly (either by double-clicking or running it with a DOS command), the client can monitor normally.
5. It feels like two users are using one computer at the same time, and the two have their own separate interfaces, but the user I use with telnet and the locally logged-in user are actually the same.
6. How can this problem be solved? My own line of thinking is: make the program run remotely with telnet or at time be in the same space as the local login space.
