View Full Version : Sage Client 1.4.10 problem - frozen first frame
03-08-2004, 09:30 AM
I have this strange problem, when I start up my new sage client, I get to the first frame of whatever recorded show or live tv I want to watch and then the screen locks up and the computer freezes. This isn't just a problem in sage because when I browse to the server and try to start a video file with windows media player I get the same effect. I can view pictures and play music just fine from the client but for some reason video just wont work. This problem also doesn't happen with my other client (separate license) which has windows 2000 on it. I thought it might be the nic but installed a different one and get the same result. Has anyone else had a similar problem or a things I can check? My set up is:
Mini-itx M10000, 256megs of ram, 4gb laptop hd, laptop cd-rom, windows xp pro. I have both intervideo and cyberlink codecs installed.
03-08-2004, 10:08 AM
Sounds like a decoder issue, which decoders you you have selected in SageTV?
03-09-2004, 08:20 AM
I have cyberlink powerdvd installed and intervideo windvd installed. Neither of them seem to work. My Server and other client both seem to work fine. I thought it was the os so I reverted back to win2k and still get the same problem. Does anyone know if the M10000 has any strange video settings that need to be adjusted?
03-09-2004, 12:57 PM
When it freezes, does it lockup hard and you have to reboot it? I have a m10000 and if I used haware acceleration, it would overheat and lock. You can verify this by using Motherboard Monitor. I had to modify the case and add a fan to get it to stop locking. FYI, in my opnion, XP pro is the best OS to use with the m10000.
03-09-2004, 02:43 PM
Yes, hard lockup - that about describes it. I actually seemed to have corrected this by updating both the video driver and the bios from the via website.
03-09-2004, 04:22 PM
That bios update was courtsey of me! I contacted th Via VP concening the crappy eval message on return from s3. I sent him a bios dump and pointed out the message along with a complaint about it not being addressed since last April. That update was released a week later. Thats the only fix they implemented over the previous one. For me if was definitely a heat issue. The system reported a whole 15 degrees celcius hotter when using HW accleration. It ran fine without it. The only downside was that I could not run anything else at the same time.
03-09-2004, 05:44 PM
Thanks for making that noise falchulk, it helped me out!
vBulletin® v3.7.6, Copyright ©2000-2013, Jelsoft Enterprises Ltd.