Pre-Purchase Question

[trevorst]

I have downloaded the trial and am quite impressed with beyondTV. Have been using SageTv for the last 6 months because of the Client capability, this is a must for me. However I do not need live TV on the client only the abilty to watch, delete etc. recorded files.

What I have done with the trial is loaded it on both my server and client. The server has the PVR250 in it, the client has no capture device. I have been able to set the client copy to look in the directories that I record on the server. It looks like it is working fine I can view all the videos and even carries all the show info with them This would be an acceptable solution for me if:

I can run both copies on one license. The server is never used for watching only recording and storage.
There are no major issues with doing this that I have not found yet.

Any opinions/advice would be welcome.

[Cayars]

I have two licenses and have been doing this for a while. I haven't found a down side to doing this myself. The only thing I would recommend is to go into the web admin and disable downloading recording info from the server so you don't mess up your "server" assuming you use the remote recording feature.

SS has never commented on this as far as I have seen here in the forums but according to the license you should have 2 licenses if you are running the software on 2 machines.

With that said, the next version should have a true client component that works without drive mapping. Sort of the way Sage TV does it.

Carlo

[trevorst]

Run into one problem that I hope someone has the answer to. When I reboot the client my network drives don't connect. I mapped them to a drive letter and checked reconnect at logon, but they refuese to connect.
If I go to my computer and click on the drive letter they connect. But will not do it until I do. Anyone else seen this problem. Running XP Pro on both server and Client.

[m1ket]

Originally posted by trevorst
Run into one problem that I hope someone has the answer to. When I reboot the client my network drives don't connect. I mapped them to a drive letter and checked reconnect at logon, but they refuese to connect.
If I go to my computer and click on the drive letter they connect. But will not do it until I do. Anyone else seen this problem. Running XP Pro on both server and Client.

you could share the folders and use ms networking instead thats what i do

[RobertH]

trevost if you are using a wireless network with encryption and are using windows' wireless zero config (you use network properties to configure wireless instead of the card's app) then network drives will not reconnect at logon becuase the network doesnt get started until a user logson to the machine.

simple sharing also causes problems (any explorer window->tools->options->view->use simple sharing(bottom)->disable)

you should then have a user account with the same name on both computers, the account MUST have a password on it or windows will not allow you to connect remotely

ie if computer A has a user called joe, and computer B has a user called moe, then both computers need an account for both Joe and Moe and they should have the same passwords on both computers.

you can get tweakui to disable users you dont want to see on the logon screen and get it to logon by itself:
http://www.microsoft.com/windowsxp/p.../powertoys.asp

[MonsterHTPC]

Just an FYI

Another method to setting up the auto login.

Click Start, click Run, and type control userpasswords2.
Clear the Users must enter a username and password to use this computer check box.
Click Apply.
Enter the user name and password you wish to automatically log on with, and then click OK.
Click OK again and you're all done.

[trevorst]

I am already setup that way. The problem seems to be that the drives try to reconnect before the network is active. It takes a couple of seconds after boot up before the network is ready. Using Tom's method in a bat file I still can not connect if I put the bat file in the startup folder. However if I execute the bat file a couple of seconds after bootup it works fine. Seems like a bug in WindowsXP.

[TroyGates]

You could try a startup delay program like this one http://www.geocities.com/fcueto/Otros/delayrun_en.htm. It allows you to specify programs and how long after startup to launch them. So you could delay your batch file for say 30 secs after startup.

[trevorst]

Thanks Troy that works great.... Tom you should give this a try it would save having a macro button set up.