MP 1.5 - Volume won't change (1 Viewer)

[mm1352000]

It did cross my mind that this could be a problem with the TBS driver (and so MP might suffer the same bug), but in the end I reluctantly concluded that there was probably a more fundamental problem, as evidenced by the TBS card in the 1x PCI-Express slot disappearing from "Device Manager" on wake from sleep. This might also be a driver problem, but it is clearly not related to any specific media-center software. If it is a motherboard BIOS problem, I don't feel justified in badgering TBS for a fix (I won't know whether it is a motherboard problem until I try the two TBS cards in a different motherboard, something that I cannot do at present).

You might be able to workaround the problem by using a script and devcon to disable the driver before standby/hibernate and re-enable it after resume.

I take it you don't have this problem on cold boot?

 

[CyberSimian]

You might be able to workaround the problem by using a script and devcon to disable the driver before standby/hibernate and re-enable it after resume.

That is an interesting suggestion (one that had not occurred to me before). At the moment I don't see how it could be automated, but I think that I can try it manually first, to see if it would provide a solution. If it does, then it would be worth trying to arrive at an automated solution.

I take it you don't have this problem on cold boot?

Correct; on cold boot both TBS cards are present and available for recording.

-- from CyberSimian in the UK

 

[CyberSimian]

You might be able to workaround the problem by using a script and devcon to disable the driver before standby/hibernate and re-enable it after resume.

I have finally got around to trying this, but sadly without success. I used "DEVCON /?" to see what actions it supported, and it looked as though the DISABLE and ENABLE actions were the ones that I wanted. I used the FINDALL action to find the device instance ids for the two TBS cards, and then tried DISABLE. It responded with this:

The devices are ready to be disabled. To disable the devices, restart the devices or reboot the system.

Rebooting the system completely negates the point of using DEVCON, so I tried the RESTART action, and it responded with this:

The devices are ready to be restarted. To restart the devices, reboot the system.

So DISABLE and ENABLE do not provide a viable solution. I notice from your post that you said disable the driver, so I had another look at the DEVCON actions to see if any would do that, but I could not find any. This is on Windows Vista 32-bit (I don't know whether that makes a difference; perhaps DEVCON supports more actions on Windows 7 or 8).

Am I using DEVCON wrongly, or is disable/enable without rebooting simply not possible? Thanks.

-- from CyberSimian in the UK

 

[mm1352000]

Hello CyberSimian

That's certainly not how I remember it working.
Are you executing devcon with admin privileges?

mm

 

[CyberSimian]

Are you executing devcon with admin privileges?

I had another go at this. First, I reset my system to its usual configuration (one tuner card enabled, the other disabled), and rebooted.

From my "normal" command window I then tried to enable the disabled tuner, and that worked! By accident, I happened to have Windows Media Center open but minimised, and when I maximised it, WMC displayed a window saying that it had detected a new tuner and did I want to set it up? I said NO.

I then right-clicked my command-window shortcut and selected "Run as administrator". It opened a new window with (presumably) administrator privileges. I tried to disable the tuner previously enabled, but as before it wanted me to reboot to allow the disablement to take effect.

-- from CyberSimian in the UK