Periodic lockups in the 2.2.5 beta

[abbott_m]

I've been experiencing periodic lockups of the the GUI. Some details of my setup are:

Intel Mobo
2.93Ghz Celeron processor
NVidia GEForce GX5700LE
Intervideo decoder
Sage 2.2.5 beta
Java 1.5

I've been running the software as a service but I don't let it start up automatically, rather I start it from a batch file using "net start SageTV". There are no client computers conecting to the system, just the one system.

The lockups I'm getting only effect the client running on the system and only then in the menu system when switching between various videos. Basically the CPU goes to 100% for about 2-3 minutes and then returns to 0% but from then on the menu system allows no further input and doesn't take anything from either the mouse or the remote.

I was running the Cayars STV but noticed some errors in the logs directly related to that so I went back to the standard STV but had a lockup again even after that.

When the lockups occur I can just go to task manager and kill the client and restart and everything is back to normal with no problems with wiz.bin getting corrupted or even current recordings being interrupted.

Any ideas on this, the wife is starting to get irritated

Mike

[rwc]

I had/have the same problem...Cayers, et. al...the only solution I found was to not run the service

[abbott_m]

I certainly am open to that but my only concern is that so far i've not had my wiz.bin corrupted by this lockup behavior. If I run it without the service and it locks up am I going to have the wiz.bin get hosed?

[abbott_m]

One further question, when running without service mode, does cayars v17 run ok now?

[rwc]

Cayers 17 runs for me

rwc

[AWS]

You know what worked for me, in terms of the service running and client auto starting after a boot? My problem was that if I set the service to autostart and the UI to autostart, then my UI would start before the service and then would not load my STV (Cayars16 at the time). So then I used the "net start SageTV" batch file method...didn't like having to do that. Then I just had the service auto start and disabled the auto start of the UI (setting in Sage) and now it auto starts everything (the service and UI) like it should. It's wrong, but it works somehow.