|
Hardware Support Discussions related to using various hardware setups with SageTV products. Anything relating to capture cards, remotes, infrared receivers/transmitters, system compatibility or other hardware related problems or suggestions should be posted here. |
|
Thread Tools | Search this Thread | Display Modes |
#1
|
||||
|
||||
Rage Pro Turbo issues???
OK.
I have a Rage Pro 128 Turbo with an unknown ammount of memory. I have it installed in a Duron 1100 machine and am attempting to get SageClient to run as a test. The client runs and connects to the server but when you hit TV, it changes the graphics and then closes. A error is left which shows the following: An unexpected exception has been detected in native code outside the VM. Unexpected Signal : EXCEPTION_ACCESS_VIOLATION occurred at PC=0x197412A7 Function=DllUnregisterServer+0x297 Library=C:\Program Files\Frey Technologies\Common\myasyncflt.ax Current Java thread: at sage.BasicVideoFrame.initializeMediaFile0(Native Method) at sage.VideoFrame.a(Unknown Source) - locked <04AF4968> (a java.lang.Object) at sage.VideoFrame.if(Unknown Source) at sage.VideoFrame.access$000(Unknown Source) at sage.VideoFrame$1.run(Unknown Source) at java.awt.event.InvocationEvent.dispatch(Unknown Source) at java.awt.EventQueue.dispatchEvent(Unknown Source) at sage.UIManager$1.dispatchEvent(Unknown Source) at java.awt.EventDispatchThread.pumpOneEventForHierarchy(Unknown Source) at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source) at java.awt.EventDispatchThread.pumpEvents(Unknown Source) at java.awt.EventDispatchThread.pumpEvents(Unknown Source) at java.awt.EventDispatchThread.run(Unknown Source) Is this because tha card does not have th necessary features or memory? Or is there another issue??? -Stan |
#2
|
||||
|
||||
I just found out that the card has only 8MB of memory. Thats probally it....
-Stan |
#3
|
||||
|
||||
8MB should work did install MPEG2 decoder drv
|
#4
|
||||
|
||||
Yes,
I successfully installed PowerDVD & verified playback.... -Stan |
#5
|
||||
|
||||
Are you running Windows XP Pro?
__________________
Jeffrey Kardatzke Founder of SageTV |
#6
|
||||
|
||||
Yes,
XP Pro here... and on the server. The laptop client which IS working fin is XP home.... -Stan |
#7
|
||||
|
||||
Has anyone gotten the SageTVClient to stream video on Windows XP Pro?
__________________
Jeffrey Kardatzke Founder of SageTV |
#8
|
||||
|
||||
ALL,
Jeff and I have traded emails and logs and tracked the problem down to an issue which was NOT related to the video card at all. The issue had to do with me specifing the server by IP (not name) and this somehow go confused by SageTV. My workaround was to edit the hosts file and add in the ip addresses and names of the machines on the network. All seems fine now. BTW Jeff has fixed the problem for the 1.3 release. For what its worth, the SageTV client with the Rage Pro Turbo 8MB on a Duron 1100 needs about 60% of the CPU time to play. FYI -Stan |
#9
|
||||
|
||||
Jeff - I had video on the client when I was testing this last month, with both server and client running XP Pro. That was back with the first client version before it was made public.
Edit after reading Shodge's last post, I was connecting client to server via computer name, not IP number. So that would explain it. |
#10
|
||||
|
||||
This problem had nothing to do with XP Pro. It's just that the people that tried connecting from work were all using XP Pro. And the machine name on your home LAN will not resolve correctly from your PC at work. That's where the problem was. For the 1.3 release it's been fixed. (not 1.3.7)
__________________
Jeffrey Kardatzke Founder of SageTV |
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
|
|