- Jan 16, 2001
- 31,528
- 3
- 76
OK, so I spent $110 on a really nice KVM (IOGear GCS84A) that I opened up, but never hooked up.
I plan on holding onto it for awhile.
Anyway, per the recommendations of many astute fellow ATers, I DL'd VNC and installed it. It works perfectly. No BSODs (my biggest fear) no, screen stuttering (as long as you dont' try to game over VNC, which it's not designed for anyway) and no other maladies to speak of.
My only beef is that it is not intended for use by idiots, er, first-time users like ME, that don't know what the diff b/t "client mode" and "listen mode" are.
It would be nice if it came with a README that was lableled "How to setup VNC on your machines" and gave you a step by step. It does not.
But, but, but after about an hour of fiddling, setting the passwords, etc, I now can control my server and my second box from my main rig. I can run programs, browse, even shut down and restart, remotely! (Yes, I am a newb to this...let me be happy with my little thimblefull of knowledge, OK?)
The only catch is that the box you want to control must already be in a Windows environment (I know zilch about Unix/Pennix/Hystrenix or those other OS's you Wizards use) in order to control it.
IOW, if you must reboot the system remotely, the following conditions apply:\
1. You must be able to access the CTRL-ALT-DEL on the remote box
2. When it reboots, the box cannot have a BIOS password installed, b/c you can't "type it" over the LAN b/c the box isn't in Windoze already
Other than that, it really rocks. I have not explored all the options and tricks inside it yet....basically, it took me awhile to get it up and running to begin with
but it rocks.
Takes up virtually no resources/CPU time while running...I couldn't be happier. Thanks guys.
Anyway, per the recommendations of many astute fellow ATers, I DL'd VNC and installed it. It works perfectly. No BSODs (my biggest fear) no, screen stuttering (as long as you dont' try to game over VNC, which it's not designed for anyway) and no other maladies to speak of.
My only beef is that it is not intended for use by idiots, er, first-time users like ME, that don't know what the diff b/t "client mode" and "listen mode" are.
It would be nice if it came with a README that was lableled "How to setup VNC on your machines" and gave you a step by step. It does not.
But, but, but after about an hour of fiddling, setting the passwords, etc, I now can control my server and my second box from my main rig. I can run programs, browse, even shut down and restart, remotely! (Yes, I am a newb to this...let me be happy with my little thimblefull of knowledge, OK?)
The only catch is that the box you want to control must already be in a Windows environment (I know zilch about Unix/Pennix/Hystrenix or those other OS's you Wizards use) in order to control it.
IOW, if you must reboot the system remotely, the following conditions apply:\
1. You must be able to access the CTRL-ALT-DEL on the remote box
2. When it reboots, the box cannot have a BIOS password installed, b/c you can't "type it" over the LAN b/c the box isn't in Windoze already
Other than that, it really rocks. I have not explored all the options and tricks inside it yet....basically, it took me awhile to get it up and running to begin with
Takes up virtually no resources/CPU time while running...I couldn't be happier. Thanks guys.
