06-23-2010, 01:34 PM
Dean Roddey Wrote:True, but what would whack the driver? Possibly some scrambled data or something could do it I guess, at least at the lower level UIRT driver level. At my level it's just a function call interface. So maybe that is why it happens. When you unload the service, it closes the UIRT level driver which would release any data. Then it would get reloaded again fresh. So maybe it's getting some scrambled data that's not being dealt with correctly, and that's whacking some control data maintained by the UIRT level driver, so it goes off into la-la land.Now that I think about it more, there is one thing that has changed in the not too distant past that might be causing this. There are several folks out there using external emitters in a zoned setup. I know I use a stereo splitter with two emitters on two different devices. Any chance of something being amok there?
As I mentioned, it's purely a function call protocol at my driver's level, I never see the actual data. I depend on the UIRT driver to make calls to me to tell me things are happening. Since my driver is mostly passive except for sending out IR commands, there's not too much it can do to screw up on the IR receiving side. It's just sitting around waiting for the UIRT to tell it something came in.
Russ...