photon
msg:1567674 | 6:13 pm on Oct 12, 2004 (gmt 0) |
If the access is via a web browser (like VNC), the accessing machine just needs to be able to run the browser. Otherwise, it will depend the software you're using.
|
eWhisper
msg:1567675 | 5:13 pm on Oct 13, 2004 (gmt 0) |
The software will be remote desktop connection for windows on an intranet.
|
photon
msg:1567676 | 5:27 pm on Oct 13, 2004 (gmt 0) |
In that case the client machine (the one accessing the remote PC) shouldn't have to be near as powerful as the specs you gave in your first post. The client is part of XP, so if your machine is running XP you're fine. There are also client versions for 98, ME, NT and 2000. The processing for your new software will be done on the remote machine, so the only real issue will be the speed of the connection on your intranet.
|
eWhisper
msg:1567677 | 6:02 pm on Oct 13, 2004 (gmt 0) |
Thanks for the info. The accessing machine is running win 2000. It's the vid card that has me wondering if it'll display right on the accessing machine - I've done many remote computer operations - just not had a program with vid specs before.
|
eWhisper
msg:1567678 | 1:04 pm on Oct 20, 2004 (gmt 0) |
The initial process is working well - just one glitch. One of the monitors I use to access the remote computer is a wide screen, yet I can't get the view to become widescreen (have those annoying black areas on the sides of the monitor). In 'display settings' for the remote computer, you're not allowed to change the display - you can only change it on the accessing computer. Any ideas how to get the remote computer to display properly on a widescreen monitor?
|
|
