sageTV service in autostart mode kills my WinXP

[crusader]

Hi,

Stumbled today on this problem -- my PC after restarting went nuts. Symptoms -- everything hangs when it "gets close" to networking, e.g.:
- explorer.exe hangs on attempt to display 'Connect to' submenu menu of 'Start' menu
- Service Control panel hangs when trying to save changes to any service
- etc, etc

very strange was the fact that SageTV service was forever locked in 'Starting' mode (and it was impossible to kill it's process -- it was always in memory with just one thread stuck in some FastSystemCallRet system call, according to my ProcessExplorer)

After long session of digging around I found that everything is fine if I follow this procedure:
- set SageTV service to Manual mode (in safe mode, in normal mode everything hangs)
- restart system
- login and start SageTV from service control panel

Feels like if system starts SageTV along with other services -- it invokes some functionality before it is available and it sends OS into stupor. Problem might be connected to latest Windows Update I did few days ago.

I tried to add dependency between SageTV and Terminal Services (that in turn depends on RPC) -- did not work.

Any ideas what it might be?

[zoundz]

Not your exact problem, but I found that my XP machine was really having trouble when I had both the services and all the stuff in the startup directories starting at once.

Little freeware app called startup delayer (google it) lets you stagger the startup directory stuff to allow a little breathing room. If you really want to start the SageTV service later, you can set the service to manual and run a little bat file (use the sc command) to start the service from startup delayer.

[asc1000]

I just ran a windows update and I'm in the same boat as you are. One difference, though. The SageTV service will not start even in manual mode. :-(

[mickp]

Hey there,

This is something that I've been seeing for a long time. I'd love to know what's causing it and should probably log a support request with Sage.

You can find some previous discussion re: this problem here.

Mick.

[asc1000]

Well, I found the source of my problem. It was the JVM update (Java 6 update 18). After removing that everything started functioning like it used to including automatic SageTV service startup.

My working JVM is Java 6 update 7. Guess I'll be parking at that revision for a while...

[crusader]

Hmm... updating my Java seemed to help (it is Java 1.6.0-18_b07).

[Fuzzy]

I've found jave 1.6.0_15 seems to be most stable with pretty much everything, so I've just stuck with that. Never had any problems, so no real reason to upgrade.

[mickp]

That's interesting information re: the java versions. This has been happening for me for the past few years though so I'm not sure that is the cause of the issue I've been having.

Mick.