New Hauppauge Beta Drivers for IVAC15/16 Combination

[Karen0302]

laurenglenn,

What di you mean you say you disabled the onboard audio?

Karen

[padell]

Originally posted by carlgar
I now believe most if not all of the problems were caused by an incompatable hcwi2c32.dll file. I need this file to get the Hauppauge remote to work and believe it should be included with the drivers. I was using the same version (2.7.20296.0) that I had used for the Narflex drivers. I now have version (2.8.21121.0) which I extracted from the SHS site. I have been running SageTV 1.4 for serveral hours with only 1 minor issue.

Can you explain what you mean by different versions a little more? I thought you were talking about the core drivers, but the versions don't appear to match up, and I can't find any of the other programs or drivers that seem to match those numbers....

I'm about at my wits end... I updated to the new drivers this morning, but I still get random "SageTV has encountered a problem and needs to close." messages, and I can't seem to figure out what the problem is... I'm willing to try anything.... (The good news is that I haven't had a complete lockup, ie requiring a reboot, since updating the drivers this morning...)

This is on a brand new 2.8G Intel D865GLC MB/processor combo.

Thanks,
Phil

[carlgar]

Padell, your motherboard is very close to mine so I would expect you to encounter problems like I have.
The hcwi2c32.dll file is only needed if you are trying to use the hauppauge remote. To see the version numbers I displayed, right click on the file select properties then select version.

[padell]

Thanks for the quick response!

I checked the version of that file and I have 2.7.20296.0.

So do you have a link to the latest version of that file? I found some files in one of the threads I was reading that had two standalone DLL files for the IR remote (this was one of them), but that one is also the older version....

Thanks in advance...

Phil

[carlgar]

I believe the other file you are referring is hcwutl32.dll, that file is part of the drivers.

I have attached a zipped copy of the hcwi2c32.dll file I am currently using.

[padell]

Thanks for the file. I found an updated IR installer on the SHS site, but even that one didn't have the hcwi2c32.dll file that you included. I've copied your file into my system32 directory, so we'll see how that does...

Thanks again!
Phil

[laurenglenn]

Originally posted by Karen0302
laurenglenn,

What di you mean you say you disabled the onboard audio?

Karen

I never use the onboard audio on my motherboard, so I went into the Hardware Manager and disabled my sound card. It might not have an effect, but it's what I did.

One other thing that I did which I forgot to mention was to go to http://windowsupdate.microsoft.com and install the SP1 QuickUpdate and all the updates relating to DirectX, etc.

After doing that, I had no problems with the OSD on my i865 chipset. You might want to go to that site first and try this.

There was a page on Microsoft's site that said they would fix a bug with DirectShow and TV tuner cards with SP2. Perhaps, one of these files contained the fix they talked about....

Lauren

Here are the things I updated at WindowsUpdate:

Successful Sunday, June 13, 2004 814995: Recommended Update Web site
Successful Sunday, June 13, 2004 Recommended Update for Windows XP SP1 (817778) Web site
Successful Sunday, June 13, 2004 Windows Error Reporting: Recommended Update (Windows XP) Web site
Successful Sunday, June 13, 2004 Recommended Update for Windows XP SP1 (KB822603) Web site
Successful Sunday, June 13, 2004 Update Rollup 1 for Microsoft Windows XP (KB826939) Web site
Successful Sunday, June 13, 2004 Security Update for Windows XP (KB810217) Automatic update
Successful Wednesday, June 09, 2004 Security Update for DirectX 9.0 (KB839643) Automatic update

[padell]

Well those latest IR files didn't seem to help things... I'm still getting the "SageTV has encountered an error...." messages while fast forwarding or rewinding....

I already have the latest Microsoft files, so that's not the problem.... I'll keep trying new things....

Phil

[carlgar]

I suspect that if you turn off the 350 TV-out you will see much better results. That is basically what I did. I only view program with the client software which does not know about the 350 and no problems.

[padell]

I am using the TV out on the ATI 9600SE (so in other words the 350 output is disabled in Sage). I haven't been brave enough to try the TV out on the 350... I wanted to get it 100% stable with a basic setup before I start doing anything else to complicate things... My ultimate goal is to use the DVI outpout of the 9600SE with the component video converter to connect directly to my HDTV... But again, it'll be a while before I get to that...

Phil

[carlgar]

That is interesting, maybe I am lucky I went back to SageTV 1.4 before I started most of my recordings for the night. I do recall seeing one of those error messages but thought it was related to the tv out issue.

BTW: we do have the same board, you have the Micro ATX and I have the ATX version.

[jphhughes]

I upgraded to the 1.18.21.22162 drivers and so far the system is stable using the UI output on the 350. Although I have not completely testing all of the features I am very encouraged. The process I used to upgrade was to first set Sage TV not to open. Then I ran HCWclear. Then I rebooted and when I got the new hardware found I manually directed the wizard to the folder containing the new drivers. I then re-booted and go the UI on the monitor and color bars on the TV. The colorbars dissapeared when I played live TV. However they would appear whenever I made a channel change etc. I re-read the thread on this subject and decided to reboot again and after I did that the colorbars when away and have not returned.

As I said this is peliminary but very encouraging.

P.S. If this is a fix for this problem then other should be advised.

[carlgar]

jphughes are you using the Hauppauge remote?

I am becoming more conviced that my 350 TV-out problems are related to use of that remote. Today I watched 3 PBS shows without problem and without use the remote. I then got brave with the next PBS show and did 1 skip fwd several minutes later I got the Freeze. I then restated SageTV without a system reboot, got some static for a few seconds but was able to watch show for quite a while. Just before the end of the program another freeze. I then rebooted my system and have not done any more TV out testing.

[jphhughes]

No I am not using the Hauppague remote. I use a standard ujniversal remote with USBUIRT IR receiver transmitter. So the remote may be your problem device.

[carlgar]

I just suffered a 100% CPU lockup using my client with the remote. However, after rebooting I tried the 350 TV out without using the remote. I still encountered a freeze.

SHS, can you provide a proper hcwi2c32.dll file for these drivers?

[SHS]

I belive you should be the one out web update drivers which has a ver number 2.7.20296.0

[carlgar]

Thank You, I will give it a try. However, I completely removed the remote application and the hcwi2c32.dll and still had problems. I think this is another motherboard specific issue. Will post if I see any success with this new file.

edit: I just realized this is the same as the original version I was using with the Narflex drivers. This version gave me the very worst problems.

[carlgar]

After using these drivers for a few days with the TVout on the 350 I think there are at least 3 issues that still have to be resolved. I have ruled out any problems being caused by the Hauppauge remote, I saw all of the problems with out the remote software installed and again after I started using the remote again. I am also still using SageTV 1.4 at this point.

The first two problems are very closely related and the only difference is the level of recoverly needed. I also have only encountered them when I have been skipping forward or backward. The problem is that the video will just freeze. The soft version of this problem I can resolve by sleep SageTV and then awaken it again. The hard version requires a complete reboot of my system. When I attempt to restart the video and I awaken SageTV the monitor only plays 1 or 2 seconds before stopping, I believe that is the amount of time before SageTV determines that the 350 driver is not responding. I believe these issues may be related to giving commands too fast but I have tried to allow 1 or 2 seconds between commands. I also believe I have one of the faster systems and may be more prone to this issue.

The third issue I do not believe is a direct driver issue, but I did not see it until I started using this version of the drivers. Twice, I have tried playing a program and gotten the following error message:
There was a problem with time control in Direct Show
Failed pausing the Directshow filter graph
Errcode=0x8007045d

I was able to recover using the sleep-awaken method

[padell]

I hate to say it, but I've given up on SageTV... I found that "other" options did not have any of the lockups or crashes that I was experiencing w/ Sage, so I've had to conclude that the problems are not related to driver issues, but to something in the software.

Phil

[mlbdude]

Originally posted by padell
I hate to say it, but I've given up on SageTV... I found that "other" options did not have any of the lockups or crashes that I was experiencing w/ Sage, so I've had to conclude that the problems are not related to driver issues, but to something in the software.

Phil

Can you share what other options do an OSD out of the 350? I am sure more people would like to try as well.