Install path on Server vs. Client (x86)

[Flips]

I just upgraded my existing server (xp 32 bit) to a new windows 7 64 bit server.

Everything is working fine, but I seem to have an odd issue on my PC clients (not on my extender). When I load up the UI, I can only navigate to some of the menu items, but not all of them. I am not able to hit select on the majority of them. i.e, I can arrow over to detailed setup, but when I try to select it I can't. Nothing happens.

It is the same behavior on both PC clients (32bit XP). The fix was to copy my entire sage dir to program files (x86) then everything works fine. I don't understand why this is though.

Server install path: c:\Program Files (x86)\SageTV
Client install path: c:\Program Files\SageTV

Maybe I am not understanding how the SageClient.Properties files work. I thought that the properties file on the server was some sort of a default, unless the clients had their own properties file.

Also, I intially had UAC enabled on the server, but then turned it off and restarted, but that didn't fix it.

I am glad it is working, but I would rather better understand so I can fix it correctly.

Thanks,
flips

[Fuzzy]

It sounds like you copied your old properties files over. This is not ideal. On a new install, you should really configure from scratch. The fix at this point, though, would be to go through your properties files and fix all the paths that point to the Program Files folder, and instead point them to program files (x86). (You have to have sage shut down and service stopped to edit the properties files).

[Flips]

Thanks Fuzzy. the properties file on the server or the clients?

I didn't copy over the properties file on the new server installation, just the wiz.bin. The clients I didn't touch, just shut them down and started them back up. The server worked fine it was only the 32 bit xp clients. Do I need to wipe out client installations and then re-isntall them?

How is the sageclient.properties file used on the server, versus the sageclient.properties file on the client?

Currently the client properties files on the clients point to program files and the client properties files on the server point to (x86).

flips

[Fuzzy]

If you are running the server in service mode, then there are basically 4 type of properties files in question here.

1. Server's sage.properties file. This is the settings used for the backend server (handles the recordings, the guide data, etc).
2. Server's sageclient.properties file. This is the settings used for the server's local UI instance.
3. Server's clients\[MACAddress].properties file. This is the settings used for an extender/placeshifter's UI.
4. Client's sageclient.properties file. This is the settings used for the client's UI instance.

Either way, the client properties files should not have been affected by the move of the server, as they really shouldn't be accessing anything on the server by full path. however, this is likely a problem with some plugin you are using on the client (ADM perhaps) that has something mapped absolute. If you try disabling all plugins, does it correct the problems and can you navigate properly?

[Flips]

Excellent explanation. Thanks Fuzzy. You know.. it was ADM. The clients created an ADM folder in program files (x86) on the clients. I didn't know what ADM, was thinking it was some sort of Sage thing, not the dynamic menu plugin. Let me try to to fix that.

[Fuzzy]

Still sounds like a bug in ADM, if it is writing things using the server's path. Might want to let the author know about it, and what things it was writing in that path. this should not be expected behavior.

[Flips]

Looks like a known issue, that will be fixed in the next release:
http://forums.sagetv.com/forums/show...&postcount=263