Hauppauge Nova-T 500 driver conflict on boot (1 Viewer)

[kdmcc500]

Hi,

Me again. Having sorted out my initial problem all is now working well.... (thanks Ray) except, if I shut down (as opposed to hibernate or sleep) when the PC starts again I get a driver conflict in hardware manager. Often a re-boot cures the problem but I have had to re-load the drivers on occasion to get the TV card working. I have downloaded the latest drivers from the Hauppauge site.

Just another little bug i'd like to get ironed out.

Cheers

 

[MLH01]

I obtained my drivers from New Magic here.

This page also has some information on XP SP3 issues and a workaround. It may be related to your driver problem.

Note that the Nova-T 500 has 2 different drivers depending on your model. If relatively new, use the 8MB download (Model 9910x). The model number should be on the TV card.

I am running MP 1.0.2 on Vista x64 SP2 and all is good with sleep/resume using the driver from the above link. Not the same as your setup, but I can at least say that the driver works for mine and is reported as being XP MCE/Vista (32 and 64 bit)/Vista S3 sleep compatible.

Good luck!
MLH01.

 

[kdmcc500]

I obtained my drivers from New Magic here.

This page also has some information on XP SP3 issues and a workaround. It may be related to your driver problem.

Note that the Nova-T 500 has 2 different drivers depending on your model. If relatively new, use the 8MB download (Model 9910x). The model number should be on the TV card.

I am running MP 1.0.2 on Vista x64 SP2 and all is good with sleep/resume using the driver from the above link. Not the same as your setup, but I can at least say that the driver works for mine and is reported as being XP MCE/Vista (32 and 64 bit)/Vista S3 sleep compatible.

Good luck!
MLH01.

Thanks,

I have installed the drvers from newmagic and downloaded the driver specific to my card (Mod 84109), Having only purchased the card recently I would have assumed that it would be the latest hardware release?.
It seems to be working ok with sleep/resume, (I have installed the 'standyby tool' plug as forum posts revealed a possible bug wth this card and MP power scheduler), the problem appears on a full re-boot or returning from hibernation. I'd imagine it's an XP problem so I'm hoping someone running XP has had this problem before and discovered a fix. Haven't had any replies from a hauppauge forum post as yet but remain hopefull.

May have to eventually bite the bullet and install Vista.

 

[MLH01]

Hi kdmcc500,

The fact that the problem occurs after reboot or hibernation is unusual. Most people with Nova-T 500 problems (including me when I first started) would need to do a full reboot to get the card working

If you've had any hardware changes, then it might be worth looking into unused/removed hardware that still have their drivers active. See here for more information.

The information is applicable to XP, and I have used a similar method for my Vista machine. This solved my problem of resuming from S3 sleep, but not recording anything. Apparently there was an old USB wireless network adapter driver that was conflicting with the TV card. Read the warnings near the end of the post before removing any drivers. More common ones to remove are mice, keyboards, old network adapters and old printers. By 'old' I mean no longer connected/installed.

Even if this doesn't fix the problem you have, it is still useful to remove unwanted drivers that use system resources unnecessarily.

MLH01.

 

[kdmcc500]

Thanks MLH01

I don't appear to have any unused drivers as i have just put the machine together and only installed the new hardware. But I do have a netgear USB wireless adapter connected which appears to be causing a problem with powerscheduler putting the machine to sleep, so I'll try diconnecting that for a few days and see what happens.

Kdmcc500

 

[MLH01]

I had a Netgear WN111 wireless adapter that caused me all sorts of issues with power scheduling (sleep/resume etc). This was the adapter I referred to earlier that I had troubles uninstalling the drivers - which then led me to the procedure I suggested.

I now use a Netgear WN311B wireless adapter and it is rock solid. No problems since then. Good luck with your testing

MLH01.

 

[kdmcc500]

Ah, well that narrows it down a bit then as that is exactly the adapter I'm using. (WPN111) I've just downloaded the latest drivers from netgear so I'll install that again and see how I go. Be a shame to have to replace the wifi adapter, it seems quite good.

Cheers

 

[Owlsroost]

A good source of WLAN drivers is NVISION -> Wireless LAN

Tony

 

[funkstar]

Ah, well that narrows it down a bit then as that is exactly the adapter I'm using. (WPN111) I've just downloaded the latest drivers from netgear so I'll install that again and see how I go. Be a shame to have to replace the wifi adapter, it seems quite good.

Cheers

This is the major failing with USB. There is no protection between drives, so if one set of drives does something bad, all can suffer. Or even if one driver does something that is on the edge of the spec, and again another does something similar, the whole USB subsystem can come crashing down.

Firewire doesn't suffer from this issue, makes me sad that it was never adopted as widely as USB.

 

[MLH01]

Ah, well that narrows it down a bit then as that is exactly the adapter I'm using. (WPN111) I've just downloaded the latest drivers from netgear so I'll install that again and see how I go. Be a shame to have to replace the wifi adapter, it seems quite good.

Cheers

This is the major failing with USB. There is no protection between drives, so if one set of drives does something bad, all can suffer. Or even if one driver does something that is on the edge of the spec, and again another does something similar, the whole USB subsystem can come crashing down.

Firewire doesn't suffer from this issue, makes me sad that it was never adopted as widely as USB.

Absolutely. My current wireless adapter (WN311B) is PCI-based. The old WN111 USB adapter would never initialise upon resume from S3 sleep or hibernation. I believe this caused havoc with the USB interface associated with the Nova-T 500 TV card, which ultimately resulted in no recordings after resuming from S3 sleep. WAF was quite low at that point in time

Seems that more work is needed for USB hardware (and/or drivers) to get reliable enough to use for the various power events important for HTPC use.

MLH01.