HD PVR and Windows Server 2008

[jm987]

Has anyone had any success getting this combination working?
I've gone through the forums and the only thing I've found is getting bda support. (http://www.msfn.org/board/bda-tv-tun...8-t114549.html) I've done this and Sage does not show the HD PVR. I don't have any other cards to test on my server besides HD PVR's.

I've also tried installing the Arcsoft software and it shows the card in the list but it indicates that the card is not available.

Any ideas?

PS: I'm running The latest build of Sage 6.6.2

Thanks

JM

[bcjenkins]

From what I understand, this is a driver issue and Hauppage isn't supporting it.

B

[Motofreak75]

well the HD PVR is a real piece of work, IF you do the BDA mod correctly and add in/import the reg file for tuners. Then sage will see it and use it.


I had it working in Server 2008 and currently working in server 2008 R2, now that doesn't mean the tuner itself work greats. I just wish is works as advertised. But I will inform that you should install the latest drivers on a windows machine that already BDA support, vista or xp etc.. Just to ensure the HDPVR gets the latest (Linux) firmware installed. I noticed that for some reason, 2008 with BDA mods will not update the firmware and it helped my HD pvr performed a bit better.


Does the word Turd mean anything you ? but that's my opinion that tuner

[jm987]

Originally Posted by Motofreak75

well the HD PVR is a real piece of work, IF you do the BDA mod correctly and add in/import the reg file for tuners. Then sage will see it and use it.


I had it working in Server 2008 and currently working in server 2008 R2, now that doesn't mean the tuner itself work greats. I just wish is works as advertised. But I will inform that you should install the latest drivers on a windows machine that already BDA support, vista or xp etc.. Just to ensure the HDPVR gets the latest (Linux) firmware installed. I noticed that for some reason, 2008 with BDA mods will not update the firmware and it helped my HD pvr performed a bit better.


Does the word Turd mean anything you ? but that's my opinion that tuner

So what am I missing here?
I've got a vista machine X64 (primary machine) that I ran the script from to copy the required BDA drivers.
Copied the files to the Server 2008 machine to c:\
Ran the X64 script to install the bda driver support as admin. Everything seemed to be fine but it did mention one file that it couldn't copy.
I manually copied the file and registered it the same way the script does.

Is there anything different that you did that I'm missing here?
Currently have 2 HDPVR's on a WHS and want to migrate them to a new W2K8 X64 Server instead.

Thanks

JM

[Motofreak75]

Did you install desktop experience from the features add on ? thats is needed before installing the BDA files. also make sure you grab from vista x64 sp2 bda files.

[jm987]

Originally Posted by Motofreak75

Did you install desktop experience from the features add on ? thats is needed before installing the BDA files. also make sure you grab from vista x64 sp2 bda files.

Yeah that was done before installing the BDA drivers.
Checked my Vista machine and it's Vista Ultimate X64 w/ SP2
I decided to run through the process again and still getting the same results.

Unfortunately I don't have any other 64bit machines in the house, the rest of them are 32bit so I don't believe I can use those to get the BDA drivers.

Any other ideas?
BTW, this is a fresh install of Server 2008 w/ SP1
As well, all the current updates have been installed.

Thanks

JM

[Motofreak75]

After you installed the bda drivers, and rebooted, did it detect new hardware ? it should of picked up about 8 new devices. and they should be yellow in the device manager?

Once that's don,e you should reboot again. did this work ? if you didnt detect anything, then the bda install went bad somewhere.

If you want I have a copy that worked for me that I zip up for you.

[jm987]

Don't ever recall in mentioning it finding new hardware. Must of been something that didn't work properly.

I tried installing from these files as well: http://rapidshare.com/files/13949067..._2008.rar.html

But no go. Do you know what should be showing up in the device manager that indicates that BDA is installed properly?

If you could zip up the files that would be much appreciated.

JM

[Motofreak75]

http://rapidshare.com/files/27272130...erver.rar.html

I have also included bda files for Server 2008 R2 from Windows 7 x64 rtm, if you are using just using server 2008, they no need to rename anything. But if your using R2 then you need to rename the x64-R2 folder to x64


Install the bda files, reboot, then notice it detect new devices after reboot, once the new unknown devices are detected, just reboot and install/import the registry file and your done.

[jm987]

Thanks for the files but I'm still no further ahead. I've seen the 8 items in the device manager and rebooted a second time.
On the second reboot, I've tried again and still get the same result. (No capture devices in Sage)
I've loaded up graphedit and I see a few BDA sections but I'm not sure what graphs should show up here.

JM

[Motofreak75]

did you import the reg file that was posted here and over of that other forum ?

[jm987]

Here we go!!!
I ended up running these registry updates:
http://www.msfn.org/board/index.php?...=post&id=23591
It's about 30 registry adds and it fixed the problem. I'm not sure what one fixed the problem but sage now detects the HDPVR in Windows Server 2008.

I've included the file in this post in case it ever goes missing on the msfn.org forum.

Thanks!

JM

[sic0048]

JM

Would you mind giving a quick "How To"? Just the steps you took to get the BDA drivers loaded on Server 2008 and perhaps the links to the files you used. This is on my to-do list, but I haven't had a chance to do it. Your directions could literally cut hours off my installation time.

Thanks,

[jm987]

These instructions were to get the HDPVR functional on a Windows 2008 Server X64.

1. Download bdaforserver from http://rapidshare.com/files/13949067..._2008.rar.html (Motofreak75 was nice enough to provide the required bda drivers).
2. Extract the file on your Windows 2008 server in the folder c:\bdaforserver
3. Do a RunAsAdministrator on the file C:\bdaforserver2\Setup For x64\Setup BDA.bat
4. Reboot the computer
5. Some people reported they received messages of new hardware found, if you see these messages, cancel them all. Check your device manager to see if there are any items showing unknown. I saw 7 or 8 drivers with exclamation marks and this is normal but didn't see any message of new hardware found. reboot the computer again.
6. Download the reghack file from: http://www.msfn.org/board/index.php?...=post&id=23591 and extract it anywhere.
There should be about 30 reg files, double click on them all. A few of them said they couldn't be updated because they were in use, just ignore the message and continue to the next one.
7. Open SageTV and the HDPVR should be available.

Hopefully this helps you and others. I'm not sure if all steps are needed and what exactly every reg file does. It's very possible that some of these steps can be skipped or tweaked but this is the way I got it working. I haven't had the chance to do any testing besides making sure that the HD100 was able to access the channel it was on so hopefully everything else works

You should also read through the forum http://www.msfn.org/board/bda-tv-tun...8-t114549.html as it provided a great source of information.

JM

[Motofreak75]

Wima posted this code and beating imported 30 different files.

Which works for many different analog cards

Windows Registry Editor Version 5.00


[HKEY_CLASSES_ROOT\Wow6432Node\CLSID\{DA4E3DA0-D07D-11d0-BD50-00A0C911CE86}\Instance\{a799a801-a46d-11d0-a18c-00a02401dcd4}]
"FriendlyName"="WDM Streaming Crossbars"
"CLSID"="{a799a801-a46d-11d0-a18c-00a02401dcd4}"

[HKEY_CLASSES_ROOT\Wow6432Node\CLSID\{DA4E3DA0-D07D-11d0-BD50-00A0C911CE86}\Instance\{a799a802-a46d-11d0-a18c-00a02401dcd4}]
"FriendlyName"="WDM Streaming TV Audio"
"CLSID"="{a799a802-a46d-11d0-a18c-00a02401dcd4}"

[HKEY_CLASSES_ROOT\Wow6432Node\CLSID\{DA4E3DA0-D07D-11d0-BD50-00A0C911CE86}\Instance\{a799a800-a46d-11d0-a18c-00a02401dcd4}]
"FriendlyName"="WDM Streaming TV Tuners"
"CLSID"="{a799a800-a46d-11d0-a18c-00a02401dcd4}"


[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Wow6432Node\CLSID\{DA4E3DA0-D07D-11d0-BD50-00A0C911CE86}\Instance\{07dad660-22f1-11d1-a9f4-00c04fbbde8f}]
"FriendlyName"="WDM Streaming VBI Codec"
"CLSID"="{07dad660-22f1-11d1-a9f4-00c04fbbde8f}"

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Wow6432Node\CLSID\{DA4E3DA0-D07D-11d0-BD50-00A0C911CE86}\Instance\{19689BF6-C384-48FD-AD51-90E58C79F70B}]
"FriendlyName"="WDM Streaming Encoder Devices"
"CLSID"="{19689BF6-C384-48FD-AD51-90E58C79F70B}"

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Wow6432Node\CLSID\{DA4E3DA0-D07D-11d0-BD50-00A0C911CE86}\Instance\{71985F48-1CA1-11d3-9CC8-00C04F7971E0}]
"FriendlyName"="BDA Source Filters"
"CLSID"="{71985F48-1CA1-11d3-9CC8-00C04F7971E0}"

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Wow6432Node\CLSID\{DA4E3DA0-D07D-11d0-BD50-00A0C911CE86}\Instance\{71985F4A-1CA1-11d3-9CC8-00C04F7971E0}]
"FriendlyName"="BDA Rendering Filters"
"CLSID"="{71985F4A-1CA1-11d3-9CC8-00C04F7971E0}"

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Wow6432Node\CLSID\{DA4E3DA0-D07D-11d0-BD50-00A0C911CE86}\Instance\{7A5DE1D3-01A1-452C-B481-4FA2B96271E8}]
"FriendlyName"="WDM Streaming Multiplexer Devices"
"CLSID"="{7A5DE1D3-01A1-452C-B481-4FA2B96271E8}"

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Wow6432Node\CLSID\{DA4E3DA0-D07D-11d0-BD50-00A0C911CE86}\Instance\{C4C4C4FC-0049-4E2B-98FB-9537F6CE516D}]
"FriendlyName"="BDA CP/CA Filters"
"Merit"=dword:00600000
"CLSID"="{C4C4C4FC-0049-4E2B-98FB-9537F6CE516D}"

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Wow6432Node\CLSID\{DA4E3DA0-D07D-11d0-BD50-00A0C911CE86}\Instance\{FD0A5AF4-B41D-11d2-9C95-00C04F7971E0}]
"FriendlyName"="BDA Receiver Components"
"CLSID"="{FD0A5AF4-B41D-11d2-9C95-00C04F7971E0}"






[HKEY_CLASSES_ROOT\Wow6432Node\CLSID\{266EEE40-6C63-11cf-8A03-00AA006ECB65}]
@="WDM TV Tuner"

[HKEY_CLASSES_ROOT\Wow6432Node\CLSID\{266EEE40-6C63-11cf-8A03-00AA006ECB65}\InprocServer32]
@="C:\\Windows\\SysWOW64\\kstvtune.ax"
"ThreadingModel"="Both"







[HKEY_CLASSES_ROOT\Wow6432Node\CLSID\{71F96460-78F3-11d0-A18C-00A0C9118956}]
@="%Filter_XBar%"

[HKEY_CLASSES_ROOT\Wow6432Node\CLSID\{71F96460-78F3-11d0-A18C-00A0C9118956}\InprocServer32]
@="C:\\Windows\\SysWOW64\\ksxbar.ax"
"ThreadingModel"="Both"

[HKEY_CLASSES_ROOT\Wow6432Node\CLSID\{71F96461-78F3-11d0-A18C-00A0C9118956}]
@="Analog Crossbar Property Page"

[HKEY_CLASSES_ROOT\Wow6432Node\CLSID\{71F96461-78F3-11d0-A18C-00A0C9118956}\InprocServer32]
@="C:\\Windows\\SysWOW64\\ksxbar.ax"
"ThreadingModel"="Both"


[HKEY_CLASSES_ROOT\Wow6432Node\CLSID\{71F96462-78F3-11d0-A18C-00A0C9118956}]
@="WDM TV Audio"

[HKEY_CLASSES_ROOT\Wow6432Node\CLSID\{71F96462-78F3-11d0-A18C-00A0C9118956}\InprocServer32]
@="C:\\Windows\\SysWOW64\\ksxbar.ax"
"ThreadingModel"="Both"

[HKEY_CLASSES_ROOT\Wow6432Node\CLSID\{71F96463-78F3-11d0-A18C-00A0C9118956}]
@="TV Audio Property Page"

[HKEY_CLASSES_ROOT\Wow6432Node\CLSID\{71F96463-78F3-11d0-A18C-00A0C9118956}\InprocServer32]
@="C:\\Windows\\SysWOW64\\ksxbar.ax"
"ThreadingModel"="Both"

[shill]

Originally Posted by jm987

These instructions were to get the HDPVR functional on a Windows 2008 Server X64.

1. Download bdaforserver from http://rapidshare.com/files/13949067..._2008.rar.html (Motofreak75 was nice enough to provide the required bda drivers).
2. Extract the file on your Windows 2008 server in the folder c:\bdaforserver
3. Do a RunAsAdministrator on the file C:\bdaforserver2\Setup For x64\Setup BDA.bat
4. Reboot the computer
5. Some people reported they received messages of new hardware found, if you see these messages, cancel them all. Check your device manager to see if there are any items showing unknown. I saw 7 or 8 drivers with exclamation marks and this is normal but didn't see any message of new hardware found. reboot the computer again.
6. Download the reghack file from: http://www.msfn.org/board/index.php?...=post&id=23591 and extract it anywhere.
There should be about 30 reg files, double click on them all. A few of them said they couldn't be updated because they were in use, just ignore the message and continue to the next one.
7. Open SageTV and the HDPVR should be available.

Hopefully this helps you and others. I'm not sure if all steps are needed and what exactly every reg file does. It's very possible that some of these steps can be skipped or tweaked but this is the way I got it working. I haven't had the chance to do any testing besides making sure that the HD100 was able to access the channel it was on so hopefully everything else works

You should also read through the forum http://www.msfn.org/board/bda-tv-tun...8-t114549.html as it provided a great source of information.

JM

I had all but given up on this, and then I found your recent post about getting this working.. I went through all of these steps, then plugged in the HD-PVR, and let Windows check on the provided CD for drivers. Although Sage sees the HD-PVR, I get no signal..

Any advice?

[jm987]

Originally Posted by shill

I had all but given up on this, and then I found your recent post about getting this working.. I went through all of these steps, then plugged in the HD-PVR, and let Windows check on the provided CD for drivers. Although Sage sees the HD-PVR, I get no signal..

Any advice?

I still haven't migrated over my sage to W2K8 as I'm still playing with it. For whatever reason, it stopped working (might of been a recent Windows patch) but currently the server doesn't detect the HDPVR anymore. I'll be rebuilding the server next week and I'll see how it goes as trying to get the drivers to load has been futile.

You may want to create a new post and add some more details of your setup. (Server version X86 / X64) if it's fully patched, any other tuners besides HDPVR, etc.

JM

[shill]

Originally Posted by jm987

I still haven't migrated over my sage to W2K8 as I'm still playing with it. For whatever reason, it stopped working (might of been a recent Windows patch) but currently the server doesn't detect the HDPVR anymore. I'll be rebuilding the server next week and I'll see how it goes as trying to get the drivers to load has been futile.

You may want to create a new post and add some more details of your setup. (Server version X86 / X64) if it's fully patched, any other tuners besides HDPVR, etc.

JM

It's Server 2008 x64, and Windows seems perfectly happy with the hardware detection. When you had yours working, did you get a signal in Sage from the HD-PVR? Did you use the software that came with the HD-PVR to test it? Was there any configuration of the HD-PVR itself that you had to do besides providing the driver CD?

[jm987]

In my scenario, the HDPVR was detected by the device manager with the updated drivers from Hauppauge 1.5.6 I think they are at now but Sage would not see the capture device.
I had tried installing the Arcsoft software and downloading new arcsoft software but it was unable to access the card even though it showed up as a device in that software.

I had tried installing the BDA drivers (doing it myself and getting them from motofreak) but sage could still not access them. I ran across the 30 reg files from the msfn forum (http://www.msfn.org/board/index.php?...=post&id=23591) so create an account and run those files if you haven't done so then sage would detect the card. I only set it up to access the channel it was on (no tuning) and tested on my HD100 and it worked. Did you run the 30 reg files?

I had also tried testing it on my Sage Client off another computer and it wasn't working from there but didn't care as I only use the HD100's.

JM

[shill]

I downloaded the latest drivers from Hauppauge (1.5.6) and followed some other advice I saw regarding updating it from a "supported" OS to ensure the firmware was updated. Then I connected it back to the Server 2008 box and tried to install the new drivers, but it said the INF file wasn't found.

But when I checked it out in Sage, it was working! So now I just have to order a USB-UIRT, I guess, since the one that came with the HD-PVR doesn't work in Server 2K8. Almost there...