Suspend and resume with SageTV

[Alex0230]

I use the execute command, I think it would accomplish what you're trying to do:

C:\SageWake\SageWake.exe --noir --leadtime=120 --terminate="SageApp" --execute="C:\SageWake\startSageNoRam.bat"

In my batchfile it calls the SageTv.exe to start up the program...

[mwhitlock]

Oh yeah! That would be why. --restart means nothing to SageWake. The correct command line argument is --execute.

SageWake will wake your computer for SageTV to perform scheduled recordings as long as you don't set the --nomanual option.

[Gaurav]

will try the --execute arg tonight.
Thanks

EDIT - BTW i got the --restart argument from the examples in the documentation. Might wanna fix it.

[mwhitlock]

Thanks for the tip. It's fixed.

[Gaurav]

OK
created a batch file to invoke "Sage.exe - startup".
used sagewake --execute to invoke the batch file.
went thru three hibernate - record - hibernate cycles like a charm.

Right now I'm testing with hibernate set at 1min. Next i'll test with hibernate at 15mins. (My mobo keeps the fans on even with S3 so i have to use hibernate).

You think it'll be reliable or should I play with ramdisk ?

[Gaurav]

@#$%&@

increased the hibernate time to 10mins and the damn thing doesn't sleep anymore.

Guess i'll have to go with ramdisk as suggested elsewhere by nielm.

Any tips ?

[mwhitlock]

What mobo are you using? I've never had a problem with my computer going to sleep after the timeout set in Windows. All this talk about ramdisks. There must be something else preventing your computer from sleeping. On any semi-recently built ACPI-compliant computer, Windows handles power management timeouts, not the BIOS, so it's not that your hard disk activity is keeping your machine awake. Unless, I suppose, your ATA controller's drivers were resetting the system idle timer with every disk access, but that seems unlikely.

[Gaurav]

A7N8X-E Deluxe.
ramdisk didn't help either.
i think you're right. will do some research via filemon.

[jbuszkie]

So far so good.. I think I've got it working... I didn't need the ram disk.. I'll have to see if I miss anything and if the wife will figure out the remote power button will "power up" the computer from suspend....

I do have one issue....

I usually have diskkeeper do defragmenting late at night... Well now with sage wake it won't. Is there a way to have my computer come out of standby for a couple of hours say once a week so the defragment tool can run???

Oh.. And great tool in sagewake!!

Jim

[jbuszkie]

Originally posted by Gaurav
[B](My mobo keeps the fans on even with S3 so i have to use hibernate).

Are you sure you are in S3?? I have a a7n8x deluxe too (not my sage system) and I got it to go into s3 just fine with a little work.
When I'm in S3, there are no fans going. You might just be in S1.

Jim

[Gaurav]

Originally posted by jbuszkie
Are you sure you are in S3?? I have a a7n8x deluxe too (not my sage system) and I got it to go into s3 just fine with a little work.
When I'm in S3, there are no fans going. You might just be in S1.

Jim

Hey Jim, what work did you have to do ?
I have the bios set to "suspend to RAM" so i am assuming the suspend is S3. Is there a way to check ?

[Gaurav]

Originally posted by Gaurav
A7N8X-E Deluxe.
ramdisk didn't help either.
i think you're right. will do some research via filemon.

Well, while i was running filemon, the pc kept hibernating at 5min intervals. It had earlier not been able to sleep with 5min timeout.
I'll try again, and with a longer timeout, this evening.

I'm hoping that it will continue to behave and it was just something during my first test that kept it from sleeping.

I'm worried though that this might be sporadic and i might have to keep the timout at less than 5mins.

[jbuszkie]

Originally posted by Gaurav
Hey Jim, what work did you have to do ?
I have the bios set to "suspend to RAM" so i am assuming the suspend is S3. Is there a way to check ?

Attached (hopefully) is a program called dumppo. I believe is was a tool used by MS to test and debug some power management stuff. You might google it to get more info...

Type dumppo cap and it should list the capabilities

Type dumppo ac and it should list the ac power settings. Pay particular attention to min and max sleep. I have mine set to S3. I have a feeling that yours is set to S1.

Type dumppo ac minsleep=S3 and that should allow you to go into S3. This is only till you reboot. If that works then

Type dumppo admin minsleep=S3 and that should make it permanent.

I also did Maxsleep=s3 as well..

I think what happens with our boards (and several others) is that when we installed, the S3 option wasn't enabled in the bios so MS decided that S1 was the most we would ever do. This program will allow you to change that.

I hope this works for you...

Jim

[Gaurav]

will try it out - THANKS!

[mwhitlock]

Keep in mind that just because you set your BIOS to enable S3 doesn't mean Windows will use it. Sometimes if you have devices set to "Allow this device to bring the computer out of standby," Windows will no longer even attempt S3 because ACPI tells it that it wouldn't be able to keep that device on in S3.

As for waking your computer up to do disk defragmenting, you can simply schedule a task in Task Scheduler for some no-op program and set the task to bring your computer out of standby to perform.

[Gaurav]

apart from the fast wake up, is there any other advantage of S3 over S4 ?
I feel more comfortable with hibernate knowing that my system will be ok even if the UPS is not able to shut it down in case of a power failure.

[jbuszkie]

Originally posted by Gaurav
apart from the fast wake up, is there any other advantage of S3 over S4 ?
I feel more comfortable with hibernate knowing that my system will be ok even if the UPS is not able to shut it down in case of a power failure.

for me the speed was the major factor. Plus.. I've had more luck with S3 than with s4 in terms of issues...once I got s3 working!

Jim

[mwhitlock]

The only major difference between S3 and S4 is that S4 requires no cooperation from the hardware. To the hardware, S4 is the same as soft off. S4 is more a state of the operating system, having written the contents of RAM and processor registers to a file on the hard disk. In S3, the motherboard keeps the DRAM in slow refresh. Either should work fine for SageWake.

[buzzerbee]

I still can't get sagewake to work properly here. S3 is working perfectly now for a few weeks with sagetv running but not sagewake. as soon as I run sagewake, it won't go to sleep. mobo is epox 8RDA+. i reinstalled win after I updated the BIOS and set teh S3 setting. I can post more info if anyone is interested in trying to help me. I toyed with filemon a while but it was clear as mud to me thanks

[garyc]

One other thought relevant to this discussion -- according to M'Soft, the O/S only checks the BIOS ACPI enumeration at O/S install time. They recommend you do not change it after install. There are workarounds (e.g. "dumppo" above), but the "cleanest" method is to set the BIOS to S3 before installing XP (or 2K, or whatever).