Spectrum. I've found a problem with the 1.5.3.3 drivers that looks like it's been introduced since the 1.5.3.1 drivers.

If i load up DigitalWatchBDA or graphedt, start playing a channel, and then end task the digitalwatch or graphedt process using task manager then the drivers seem to end up in a bad state.

The first noticable problem is that the card becomes unusable. If you try to use DW or graphedt again then you get errors joining up the graph and cannot move to the running state. I have to reboot the computer to be able to get the card working again.

The second problem is that once the card is in this state then windows will not reboot the computer. After hitting Turn Off or Restart most programs unload and then windows just sits there as-if you never told it to shutdown. I end up having to hit reset to reboot the machine.

The only version of the drivers that i've found that this happens with are the 1.5.3.3 drivers. Other drivers i have tried which handle end tasking DW with no problem are 1.5.0.0, 1.5.1.0, 1.5.2.0, 1.5.3.0, and 1.5.3.1.

Could this also be related to the power management problem that null_pointer has outlined?
Null. is your problem present only with the most recent version of spectrum's drivers?

Nate,

No problems here. If i "end task" on DW BDA with drivers 1.5.3.3 i can start DBA up straight away fine.

Hrmmmm, ok then. It'll be interesting to see if anyone else can replicate the problem.

If it happened for every version of the drivers for me then it'd say it's my hardware configuration, but as it only happens with the 1.5.3.3 drivers then i suspect it's more likely to be a problem that other people could have too.

Guys,

Are you aware that with BDA 1.5.5.3 drivers I have a problem with the Pause button in graph edit? You can't un-pause.

http://forums.dvbowners.com/index.php?showtopic=1436&st=90#

Thanks for pointing that out bear. I'd forgotten about it. I just tried it and i get the same as you. Hitting play after being paused results in about 1/2 a second of playback (which is really only what was left in the buffer's before it was paused) and then it stalls. Stopping and starting the graph fixes it and the card is still usable so i don't think it's related to the end-task problem.

It's a bit unfortunate that that these two things both poped up in the 1.5.3.3 release which has been the first version to fix the transport stream problems in earlier versions.

Funny thing just happend, I tried your ScanChannelsBDA0100 program and did a "forced exit". Now the card behave exactly as you describe.

The forced exit thing sound like problems i was having when i first stated working on the BDA Input for DW. But that might have just been my shitty coding

I tried 1.5.3.1 and had the some problem with the getSignalStrength call not returning. This is a random problem and I can not get it to fail reliably, it will work 10 times in a row and then on the 11 time after waking from hibernate it will lock.

Once it has locked I have to reboot XP, I can reboot it though, I do not have to hard reset (reset button) like you do.