Hauppauge pvr350 tv-out and hibernate

[stu8080]

Nice one Sub, works fine. must have had IR.exe running when i tried it

[Dai]

Just like to add my thanks for this functionality.

It's great to be able to use Standby proprerly at last.

Dai

[Mikkel]

MaBo and Sub,

thanks for your great work on this. I have been away for a long time, and have not had the time to test this out, but I will as soon as I find time.

MaBo, I greatly appreciate the time you took to make a special guide for the programming illiterate (is that correct spelled??) people.

Thanks again,
Mikkel

[MaBo]

Mikkel,
yo're welcome. I like things like that...

Greetz,
MaBo

[MaBo]

Hello,
I've updated the wake.cmd file to the one below:
<table border="0" align="center" width="95%" cellpadding="0" cellspacing="0"><tr><td>Code Sample </td></tr><tr><td id="CODE">
ECHO OFF
REM This batchfile is executed in the first seconds
REM after waking the machine from hibernation.

REM This will re-activate the tv-out after hibernation
REM Version 0.3, 20040907 by MaBo
REM You can contact me at the GBPVR forums

REM changes:
REM 0.3.1: minor fixes. Now the recording service and ir.exe are
REM restarted also when restarting the pvr350 failed.
REM 0.3: now all in one file: wake.cmd
REM check whether a version of wake.cmd is already running

REM first check whether another version is running
SET checkfile=c:\syslog\wakingtvout.txt

IF EXIST %checkfile% GOTO EXIT

echo waking started > %checkfile%

REM An entry to the logfile is generated.
REM define the path to your system logfile here:
set logfile=c:\syslog\syslog.txt
REM If you don't want a logfile, please remove all lines containing
REM %logfile% in the file below

echo Wake from hibernation >> %logfile%
date /t >> %logfile%
time /t >> %logfile%
pushd "C:\Program Files\DevCon"
ECHO OFF

REM In order to restart the pvr350, it should not be in use.
REM Therefore, the remote control program has to be stopped
REM modify the path when you have not made a default install.
"C:\Program Files\WinTV\Ir.exe" /QUIT

REM Then the GB-PVR recordingservice has to be stopped.
REM This will stop any running recordings!!
REM This is assumed to be safe, as the computer has just
REM woken from hibernation/standby. So it was idle.
net stop "GB-PVR Recording Service"
REM echo Recording service stopped >> %logfile%
REM date /t >> %logfile%
REM time /t >> %logfile%

REM Then the program devcon is called to do the actual restarting
REM devcon.exe can be downloaded from microsoft.com
devcon.exe restart PCI\VEN_4444^&amp;DEV_0803
REM the entire identification of the PVR 350 was
REM in my case: PCI\VEN_4444&amp;DEV_0803&amp;SUBSYS_40000070&amp;REV_01\3&amp;61AAA01&amp;0&amp;70
REM However, the &amp;-signs posed problems.
REM By using only PCI\VEN_4444, any pvr250's are probably restarted as well.

IF ERRORLEVEL 3 GOTO SYNTAX
IF ERRORLEVEL 2 GOTO FAILURE
IF ERRORLEVEL 1 GOTO REBOOT
IF ERRORLEVEL 0 GOTO SUCCES

:SUCCES
echo pvr350 restarted succesfully >> %logfile%
date /t >> %logfile%
time /t >> %logfile%
GOTO END

:REBOOT
REM The pvr350 could not be restarted. Probably because it was in use
REM by some program. A reboot is needed.
echo The pvr350 could not be restarted. Reboot required >> %logfile%
date /t >> %logfile%
time /t >> %logfile%
REM You could add a command here to automatically reboot your machine.
GOTO END

:FAILURE
REM The pvr350 could not be restarted at all.
echo pvr350 could not be restarted succesfully >> %logfile%
date /t >> %logfile%
time /t >> %logfile%
GOTO END

:SYNTAX
REM Syntax error.
echo There is a syntax error in wake.cmd >> %logfile%
date /t >> %logfile%
time /t >> %logfile%
GOTO END

:END
REM The statements below are always performed. Even when
REM errors have occured.
REM Restart the recordingservice
net start "GB-PVR Recording Service"
REM echo Recording service started >> %logfile%
REM date /t >> %logfile%
REM time /t >> %logfile%

REM Restart remote control
START C:\Progra~1\WinTV\Ir.exe /QUIET
REM remove the checkfile to enable new restarts
REM start gbpvr.exe
del %checkfile%

popd
:EXIT
REM Commands below are performed, even when another wake.cmd is busy.
EXIT
[/QUOTE]

Only minor changes. Biggest one is that ir.exe and the recordingservice are started also when restarting the pvr has failed. Also I've inlcuded start gbpvr.exe at the end. However, I've commented it out.

Greetz,
MaBo

[MaBo]

Hi,

Quote[/b] ]Well, I've already read and posted several messages on this subject, but it appears that waiting for hauppauge to solve the problem of black-screen-on-tv-out-after-hibernate will last longer than the economic life-time of the pvr350...

I was wrong!!! I have installed the lateste hauppauge drivers recently. Now I've noticed (by accident) that when the computer wakes from hibernation and GBPVRWake is not running, the pvr35- tv-out does show a picture. In other words it appears Hauppauge has fixed the issue.

There is a minor chance that this improvement is due to the latest BIOS I've also installed, but I don't think that is true.

Nevertheless, I think I will keep on running gbpvrwake to log waking events.

Greetz,
MaBo

[stefan]

Quote[/b] (MaBo @ Nov. 19 2004,10:25)]I was wrong!!! I have installed the lateste hauppauge drivers recently. Now I've noticed (by accident) that when the computer wakes from hibernation and GBPVRWake is not running, the pvr35- tv-out does show a picture. In other words it appears Hauppauge has fixed the issue.

Hi.

Which driver was the latest when you wrote this? :-D

[MaBo]

Hi,
The ones I have installed now are:
pvr_1.18.22266_inf.zip
pvr48wdm_2.0.22287.exe
hcwSMD_5.0.22236.exe
wintv2k_4.6.22278.exe

Greetz,
MaBo

[stefan]

*doh*
I think I might have not read this properly. What I did was to remove Wake.cmd, hibernate, and then wake up. No picture (I have the same drivers as you). But now I read yuor post again and it states that GBPVRWake should not be running. So that's what I should remove? The reason I ask is that wake.cmd every so often fails to restart the pvr-350, for some reason or another. Not so wife friendly ;-)

[MaBo]

Stefan,
Well, I discovered the new drivers apparantly support hibernate because GBPVRWake was not running. However, at this moment I have GBPVRWake running to log waking events with a very simple wake.cmd file (just typing the date and time to the syslog-file I maintain). So, if the drivers work in your system like in mine, you can keep gbpvrwake running, but just modify your wake.cmd file.

In short, I do not have a diagnosis of what is going on in your system.
Greetz,
MaBo