Hi!

Tried to install BDA version of WebScheduler and so installed Spectrums BDA drivers.
Got graphedit to render a graph, albeit without active movie window showing anything (probably because of my age-old Matrox Mystique sans overlay, etc.), but WebScheduler cannot be persuaded to tune to both 7 and 8 Mhz bandwidth channels, which unfortunately we have here in Berlin.
Any solutions?

TIA

Try this - cludgy, but should work.

Take your working WebScheduler directory, and copy it (and all subdirs) to a new directory - say WebScheduler8MHz. Edit server.prop to get it running on a different port, and start it up.

Assuming that you can either tune or manually add the 8MHz channels, you've at least got a workaround.

I'm surprised that you can't get it to tune both - assuming you've edited data\stationdata.list, for example, or entered a channel by hand.

However, you can quite happily have multiple WebSchedulers running in parallel (even as multiple services, if you have a look at the service.conf files) - I've done this to have both the WDM and BDA versions running at the same time.

BJ

Hi BJReplay!

Thanks for all your input and suggestions. At least someone took note.
Seems strange that you are the only one to bicker with the issue at hand - I mean, come on, this is really serious.
In the present state the BDA-version is almost unusable here in Berlin perhaps even in the rest of Germany (don't really know whether 7 Mhz are necessary because those channels are within the VHF band, so it could be a Berlin-only problem, but I wouldn't count on it as I believe I latched onto it on this forum that there is at least one Australian station transmitting something with a 6(!) mhz bandwidth - so the whole issue could easily come back to haunt others as well...)
Your ideas unfortunately do not address the root cause of the problem (thanks anyway, really!), because it's not an issue with WebScheduler per se, it's an issue with Spectrum's BDA driver (or, perhaps, there's a bug in Microsoft's BDA subsystem).
At present the bandwidth somehow seems to be hardcoded into the driver! (I truly hope I'm wrong on that one!)
Of course, I fiddled with the forceBandwidth key - but whether I delete the whole key or enter "0" - it inevitably reverts to 7 Mhz kind of scanning/frequency locking. Then, of course, I did run Webscheduler's channel scanning twice, once with a 7 Mhz setting and then again with an 8 Mhz setting. This garnered me all the necessary data for every channel - alas, the presence of this information cannot do away with the driver's apparent 'inborn 7 Mhz nature', which can only be altered rather drastically by changing it to an '8 Mhz nature' - which at the end of the day doesn't win you anything.
[rant] I'm sorry that I sound annoyed, but a search on this forum elicited just one rather cryptic remark which wasn't clarifying anything.
So, an issue like that should really receive somewhat more attention than just one post (thanks again BJReplay!) in 3 and an half days (with 91(!) people taking a look on it, to boot)!
Tell me I'm a moron and/or that I made a clerical blunder somewhere, tell me that the issue is known but, unfortunately, at present nobody has a solution, tell me 'Oh that's strange and interesting, but I cannot test this anyway as we in Australia have only 8 Mhz channels - so how should I possibly ever be able to help you?', tell me 'it's all Microsoft's fault', tell me 'only 7 Mhz count', tell me 'only 8 Mhz count', tell me 'who needs 7 Mhz anyway' - just tell something! [/rant]

PS: I took the tedium of really installing/unistalling the drivers with an appropriately edited thbdatun.inf file - so, just to make sure, I didn't bypass anything by just editing the registry directly (though, of course, the net result should have been the same - but just in case...) . All of this was done on a freshly formatted partition with an equally freshly installed Windows XP. Finally I cross-checked with another Windows 2000 system. So, I really tried....
By the way, another post on this forum, incidentally my very first one here, hasn't received any answer at all, which, at least in my books, is no good either!

As you have discovered Spectrum's drivers can be hardcoded to use a particular bandwidth setting by editing the .inf file before installation or they can follow whatever the API sets. This was necessary to deal with a long standing Microsoft bug in bdasup.sys that did not call set_Bandwidth() in the drivers. This may or may not have been fixed in XP / SP2 and/or DirectX 9.0c ~~~ It is apparently fixed in "Symphony" (MCE2005/6)...

The IDVBTLocator::put_Bandwidth() method allows the BDA Architecture to set the bandwidth on a per request basis, so it is technically possible to change the bandwidth on a channel by channel basis. There is no real guarentee that this will work with the current BDA Architecture implementation ~~~

I am not sure whether the current implementation of WebScheduler BDA stores a per channel bandwidth setting.

I am really not impressed with your attitude. This is free software developed by null_pointer, who has put a lot of time and effort into making it available. Not only that it is Open Source so that you can take it and modify it yourself if you want it to do something extra. If you want professional support then go and buy a commercial product and pay for the support level you seem to expect

Be more grateful

As JoeyBloggs has said WS does set the Bandwidth, WS does everything it can to adher to the BDA standard, if the standard is broken there is not a lot I can do though, check out the following source:

http://cvs.sourceforge.net/viewcvs.py/dvb-...1.1&view=markup

Do a search for for following text:
"Create a new locator and set it values"
and you will see the code in question.