I have a WinTV PVR USB2 Media Center Kit. I can get Net Radio just fine but the FM Radio just sits silent. I downloaded the required file and registered it and still no radio. Any thoughts as to what I'm missing here?
I was looking at the PVR-500 at Newegg and noticed a review which stated that there's an incompatibility with the card and AMD dual-core CPUs. The reviewer gave an email address of a Hauppauge support tech, so I wrote and tried to get some details. I think he's saying that the problem only happens with Windows XP. Has anyone had this problem? Is anyone using a PVR-500 and dual-core Athlon with Windows 2000? That's what I have, and was thinking of getting a 500, but I'd like a little reassurance. Also, I'm reading his comments as saying that they have enough boards produced that they're still going to sell them this way instead of manufacturing new ones. If you don't have a dual core you won't notice, but if you do you'll have to send the board in for a modification.
Anyway, here's what the guy said. I cut the messages back into order for readability.
bungle Wrote:> On a review at
> http://www.newegg.com/Product/Product.as...6815116628
> multiple users have stated that there are
> incompatabilities with this card and a dual core
> Athlon setup. Is this true, and what is the status
> of improved hardware and/or driver that fixes this?
> Also, do you know if this is also an issue under
> Linux (ivtv drivers)? I currently have a PVR-150 retail
> working very well on my dual-core.
Jerry Henriquez Wrote:> Hello
>
> The problem will require a Hardware modification on
> case by case basis.
> Boards would need to be sent in for the modification
> to happen. At the
> moment we are not ready to start accepting boards.
> We need the parts
> required in stock.
>
> The problem only affects Standby mode and rebooting
> after the drivers have
> been installed. We do not have confirmation or
> information on whether the
> problem affects Linux systems.
bungle Wrote:Thanks. Has the hardware modification been made to
new stock of the pvr-500 that hasn't been sold yet?
If so, is there a manufacture date where this took
effect? Or is it only specific revisions? I'm
wondering if I bought the card if there's a 100%
chance of a problem, or something less than that.
Is the problem isolated to a particular version of
Windows, like XP, or does it affect all of them? I
have Windows 2000 Pro.
What exactly happens, a lockup? Is there a
workaround, like removing the drivers to reboot?
Though since I use standby extensively that's probably
not a good option.
Thanks again for your time and comments. I'm very
happy with my current Hauppauge products, so I hope
this can be resolved.
Jerry Henriquez Wrote:Hello
Right now Hardware Modifications will only be on case by case basis.
There is no new revision of the board out there. Eventually there will be a
new artwork for the board, but we are not going to replace all the boards
in the market for new ones.
Also the problem is specifically for Windows XP, technically the
PVR-500 is not meant for Windows 2000 but for Windows Media Center
Edition. Even though the board will work on windows 2000 at the moment our
most updated drivers do not work on 2000. Engineers state that a will be forthcoming, but that has nothing to do with the current AMD Dual Core Processor problem.
When it comes to the actual problem, it only happens when you go into
standby or reboot. If you go into standby the system will not come
back. If you reboot the system will just hang. Besides that the card works
correctly.
Regards,
Jerry Henriquez
jhenriquez ~at~ hauppauge.com
Technical Support
Hauppauge Computer Works
New York
(In case you're wondering, this is a family machine and GB-PVR backend, so no I'm not crazy to have a dual core )
This plugin acts a little like Google’s own Gmail Notifier application; you cannot read the whole email but you can see if it worth logging on to your mail.
All the sudden whenever the epg updates..i get the invalid arugemetn....like when its too much data...it was working forever with 15 days epg....then i looked at i had an error saying it wouldnt store it... Now i changed it to 7 days and cleared epg and re downloaded it..and i get same error....
Howdy - I apologize if this has been described and resolved but I have been searching the forums without luck..found semi-related issues but nothing identical.
I'm using the MVP for all my playback - Net Radio Always starts OK and plays for a matter of seconds up to a few minutes after which it always locks up the net radio service. All other GBPVR functions continue to work without problem. I have to restart the gbpvr service to get net radio "back."
Using 96.12 but thus problem has been ongoing since I started using GBPVR (95.xx something).
I have:
changed buffer settings
Tried different versions of Hauppauge software
Switched out codec packs
Played with config.xml / used various permutations of:
After I install GBPVR 96.12 version, I get the .Net Framework error shown below when it tries to start up. Logs are attached. Any ideas?
When I run the previous version of GBPVR (95.16), everything works OK.
************** Exception Text **************
System.TypeLoadException: Could not load type AxWMPLib.AxWindowsMediaPlayer from assembly AxInterop.WMPLib, Version=9.0.0.3095, Culture=neutral, PublicKeyToken=null.
at xae10db17d26ba033.xbb1566157f5f8b1f.HideInset()
at xae10db17d26ba033.x86396f56243de9fb.x5337203f86c34517(String x2022b5e8d76ee693)
at xae10db17d26ba033.xbb1566157f5f8b1f.WndProc(Message& x5f8f2c40c000ab2c)
at System.Windows.Forms.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
************** JIT Debugging **************
To enable just in time (JIT) debugging, the config file for this
application or machine (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.
When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the machine
rather than being handled by this dialog.
)
