configuring GBPVR from another machine

[tomper]

Hi

I have a dedicated windows xp machine running GBPVR. As it has no keyboard or mouse (it's just connected to the TV and the network) if I need to change any settings in GBPVR I use remote desktop to log into the machine and then, because RD leaves the pc on the login screen when one logs off, I have to trigger a reboot in order to get the machine to auto-login and start GBPVR.

Also, using remote desktop is useless for trouble shooting because it doesn't support VRM9.

Is there a more convenient way of configuring GBPVR from another machine on a network?

Thanks
Tom

[HarryH3]

I use UltraVNC to access my server. http://www.uvnc.com It takes over the existing console session instead of the rather stupid "kill the console session and start a remote session" mode that Remote Desktop uses (unless you're remoting into one of Microsoft's server OS'es.) I seem to remember that it doesn't pass video well, but I don't recall the details. You can peruse the forums on their site to learn more.

[mikeh49]

When I used UltraVNC on lower powered GBPVR machines (analog days), it was great for configuring, but indeed did not do video. I didn't even try to get video working, and this was a couple of years ago, so it might be possible or better now. ATM, I use a wireless keyboard and mouse that I keep in a drawer in the bedroom. Got it for about $20 last year on Black Friday. I prefer it to the remote technique.

[liteswap]

Another vote for UltraVNC, which has been doing the biz here at Liteswap Towers for years....

[martint123]

Another Ultravnc user who is happy with it. (and sub has used it remotely for debugging in the past and worked very well).

If I fire up pvrx2 on the server I get a blank window with uVNC, but going into properties on the server side and unticking the video hook driver it then will display the whole lot. Snag with this is something I have to ask it to refresh the screen as chunks can go "missing".

[tomper]

Thanks for the replies.

UltraVNC sounds like the way to go.

Although I did find a partial solution using Remote Desktop.

RD (with a bit of hacking) allows for concurrent logins so I can log in under a different user name without terminating the existing session and from there I can run the config utility. Then, to get the changes to take effect, I can use the remote to exit GBPVR and then restart it.

Unfortunately saving doesn't automatically restart the recording service (presumably because it's running under a different account) so some settings would probably still need a reboot (or a mouse hooked up to the PVR).

[ACTCMS]

I use RDC. I login using the same user name. To exit, I just close the RDC window.

If for any reason I need to reboot, I use Start, Run, shutdown -r -t 2

[kayleigh]

I use RDC. I login using the same user name. To exit, I just close the RDC window.

If for any reason I need to reboot, I use Start, Run, shutdown -r -t 2

Ditto... I just close the RDC window. If I need to reboot, I'll open Task Manager. (Right-click the task bar and select Task Manager. There's a Shut Down option in the menu, and select Reboot. It'll give you a message that you won't be able to reach the remote computer until it's back up. Click the OK button.)

I have a similar setup on my GB-PVR computer (no local keyboard or mouse, all scheduling and streaming done through the web interface), and an automatic login starts GB-PVR services at reboot.

I use the same automatic login ID to log in remotely to the console (mstsc /console or mstsc /admin at the Run line of your remote computer, depending on the version of Remote Desktop Client you're using), and just close the session when you're done... don't log out, or you'll kill the GB-PVR processes! It'll give you a message that your session will still run (blah, blah), but that's really what you want.

P.S.: If you run the shutdown command remotely, use shutdown \\gbpvrcomputername -r -t 2 where, gbpvrcomputername, is the name of your GB-PVR computer, -r, tells it to reboot, and -t 2, tells it to do this in 2 minutes. Leave off -t 2 if you want to reboot right away.