From: Robert S. <rob...@gm...> - 2003-05-02 19:02:57
|
From: "John Adcock" <Jo...@ad...> > > Thus, the driver must be HARDCODED for each area which has different > > settings for these two parameters. > > Hardcoded is a bit strong, but these have to be set via some other means, > like the registry for example. An can't simply be set via the api which > I agree with Robert is very silly. I did try adding registry access for > these parameters expecting something like this coming up. I'll try a bit > harder. Hmm, I would not go through such workarounds. IIRC, the IBDA_DigitalDemodulator device interface *does* work properly and is able to pass down the DVB-T parameters. So instead of modifying the driver, I would suggest either modifying the application to pass down these parameters through the device interface, or replacing the DVB Network Provider, whose task it is to do that in the first place (but which Microsoft's DVB-T NP apparently neglects to do). Regards, -- Robert Schlabbach e-mail: rob...@gm... Berlin, Germany |