A new 350 Problem?

[Alex0230]

I have two suggestions....

First, try it in quotes:

devcon.exe restart "PCI\VEN_4444&DEV_0803&SUBSYS_40000070&REV_01\4&2E98101C&0&10F0"

Second, this will keep it clean and will work until you get a second PVR card...but you can just run the following line:

devcon.exe restart "PCI\VEN_4444"

This would restart any device matching this id class....

When you do devcon.exe find PCI\VEN_4444, only one card is returned right? This should be your 350 card....just guessing from your signature that you only have a 350 and no other tuners.

[jphhughes]

You are correct I only have on card in the Pc now and that is the 350. However I do have a 250 whihc I plan to add at a later date. But for the time being I will try you suggestions regarding the quotes and see what happens. Its getting late here !2.20Am so I will try this is the morning. thanks again for your help.

[jphhughes]

devcon.exe restart "PCI\VEN_4444" seems to work without any problem. however if I try :

devcon.exe restart "PCI\VEN_4444&DEV_0803&SUBSYS_40000070&REV_01\4&2E98101C&0&10F0"
it does not restart anything

So for the time being I will use the first command until I find the solution. Thanks again for your help.

[mls]

Some video cards also have that problem. Usually it can be fixed by changing the setting in the BIOS (if yours has the option) to reset/POST the video card when returning from standby.

Not sure if that would also reset the 350, but you could try it to find out. Can always change the BIOS setting back to whatever it was again if it doesn't work or messes up something else.

[laurenglenn]

Originally posted by Alex0230
It requires a reboot...

Actually, it doesn't. It will tell you that it needs to reboot, but you can start up Sage afterwards and it works fine. You may need to open Sage, close it, and open it up again, but you don't need to reboot.

Lauren

[Alex0230]

Originally posted by jphhughes
devcon.exe restart "PCI\VEN_4444" seems to work without any problem. however if I try :

devcon.exe restart "PCI\VEN_4444&DEV_0803&SUBSYS_40000070&REV_01\4&2E98101C&0&10F0"
it does not restart anything

So for the time being I will use the first command until I find the solution. Thanks again for your help.

Interesting, I wonder why...it's the exact id that appeared when you did a "devon.exe find PCI\VEN_4444" right? Here's what I suggest....

When you get put in your 250 card, do a "devon.exe find PCI\VEN_4444" and you should find two devices listed. At some point their ids will start to differ.

For example the 350 will look like:
"PCI\VEN_4444&DEV_0803&SUBSYS_4......"

And the 250 will look like:
"PCI\VEN_4444&DEV_0016&SUBSYS_4......"

So you should be able to just do to restart the 350 only:
devcon restart "PCI\VEN_4444&DEV_0803&SUBSYS_4"

Otherwise if you leave it the way it is now (devcon restart "PCI\VEN_4444"), both the 350 and the 250 will be restarted.

[jphhughes]

The point I was getting at in my previous message is that when I put the quote marks in the command that has &'s in them the command does not execute. If I use the "PCI\VEN_4444" which does have quotes but no &'s it works fince. As you stated in earlier replys I think that the &'s are causing the problem.

[jphhughes]

Just to let everyone know I received the following response from Hauppague Support today.

"What happens if you disable all power management? Do you have the problem
still?


Nick Russotto
Hauppauge Tech Support
Nrussotto@Hauppauge.com

Please include all previous messages when replying"

[Alex0230]

, I feel so stupid....I forgot to try that. But then again, how else would I hibernate my system if power management is disabled?

Did you respond back and say if you disable and renable the device in the device manager it fixes the problem....so it obviously appears to be a driver issue.

[jphhughes]

No I did not respond , becasue if I did go through the trouble of disabling Power management and it did work (most likley) then they would come back and say "ok then just leave power managment disabled", at which point I would be forced to say things I would regret.

Perhaps tomorrow I will be in a kinder mood and tell them it a driver problem and they need to fix it.

[jphhughes]

Hopefully my last post on this subject as it pertains to my issues.

It seems :
devcon.exe restart "PCI\VEN_4444&DEV_0803&SUBSYS_40000070&REV_01"

will restart the 350 and return no errors in my case When I put in my 250 this will not need restarting so all should be well. Thanks again everybody.

[mwhitlock]

Originally posted by Alex0230
The only problem with restarting your machine is that you need to have sage running as a service in order for it to still record your "scheduled recordings". I heard there were issues with running it as a service and have avoided that. Otherwise it will sit at the login screen waiting for someone to log it in to the OS.

In many cases, it would be acceptable to configure Windows to auto-login. You can do this easily in WinXP by executing "control UserPasswords2" from the command line. Uncheck the box labeled "Users must enter a username and password to use this computer" and when you click OK, it will prompt for a username and password to use for auto-login.

Originally posted by Alex0230
...I don't think mwhitlock specified whether or not in the "--execute" command, if the programs were run asynchronously or not.

SageWake starts programs asynchronously, so all programs in your list are started pretty much simultaneously. One thing I noticed was that in a couple of posts, you had two --execute arguments on the same SageWake command line. You can't stack them that way; the second one would overwrite the first. To execute multiple programs, place their paths in a single --execute argument, separating paths with commas.