Directv H25 and HDPVR/ blaster not working

[DRB]

I am having trouble using the HD-PVR with D-TV's H-25 stb. The blaster not working, it works under the blaster configue tool but not with Sage. Anyone have the same problems or a solution?

Thanks
DRB

[Beefcake550]

Infinitely easier solution is to hook up your H-25 to your LAN with the SageTV box and install the DiirecTV HTTP channel changing "driver". You'll need to give the H25 box a constant IP address in some way (either assign on the box or in your router using DHCP assignments). Then follow directions and never miss a channel change again.

[DRB]

Is this possiblable? The H25 is the small box without a ethernet port. The connection is made tru the cable. Hopefully it doesn't matter, I will research this oterwise I will have to get the H24 box.

Is this "driver" this thread? http://forums.sagetv.com/forums/show...annel+changing

Thanks
DRB

[Beefcake550]

Crap, I didn't realize that about the H25. It has to be on the network somehow. I would imagine that if you can ping the IP address assigned to the H25, you would be able to use the channel changing.

IN that thread, scroll down to Eric's posts:
http://forums.sagetv.com/forums/show...9&postcount=28
I use his stuff without problems.

[DRB]

The H25 is on the network, the connection is made tru the coax cable and channel changing works perfectly. I still have to firgue out how to lock the IP adress from changing.

However for some reason I don't get the video feed. The channel change takes place but I get no video. The blue light does not come on. Sometimes Sage thinks the change took place and other times it tells me capture error. Any ideas, could the HDPVR gone bad at the same time?

DRB

[Beefcake550]

On locking the IP address, on my H24, there is a menu where I can setup the network. You could possibly lock it there if that exists for you. If not, look into the DHCP setup that is giving out the IP addr, and, on mine at least, I can look at IP address to a MAC address.

no video is a separate problem. I would say check all connections first, but I don't have much beyond that. I'd also try out v1.5.7.0 of the drivers. I've been using them without issue.