Cumulus Support

True - the .NET framework will take care of this.
All I have to do to get this sorted is take the local DateTime value and apply the ToUtc() method to it. Piece of cake.

Hi All,

First post… No I haven’t read that the “read here before posting” Please forgive me for any bad things.

However thought it was worth adding to this post as I resolved this issue slightly differently. Now I use a Windows XP system and I know it works for this. Don’t know and haven’t tested on Windows Vista, 7 or 8.

The aim was to have the computer start up on power resumption and run Cumulus automatically.

First thing was to set it to always power on in BIOS (this is the part of the computer that loads before anything else starts) Best to consult the motherboard manual to see how to do this one.
What this should do, is as soon as you plug the power in the back of the computer, it will turn on.
Second thing was to log into Windows with a password, automatically. The easy way out was to not have a password but this was not an option for me. The computer I use for Cumulus doesn’t have a screen connected to it and I log into it using a remote desktop session. This has to have a password in order to that.
Here is the trick. Check this Microsoft Article http://support.microsoft.com/kb/315231 for how to get around this. I undertook the method 2 option.
So thirdly was to set it to lock computer if I perhaps did a screen plugged into it. This was done by in the screen saver settings, “on resume show logon screen”. Set the idle time to say 5 min.
Last put a shortcut to start cumulus in the start-up folder of the start menu.

So mine works like this. Power fails and computer goes off. Power comes back and computer just starts up, logs in using the auto credentials, starts cumulus, then once the system is idle for 5 min, goes to screen save and will ask for a password when wake from screen saver.

Hope this helps some.

Nossis

While this might be an option for when you're running Cumulus on a PC that doesn't need strict security (what with it not being connected to a network with other users, or the Internet), it is not something one might want to do on a machine that is a domain controller, a firewall, and a host for a couple virtual servers...

I know that this is the other side of the spectrum, but it just so happens to be *my* side of the spectrum

On top of that, I would have to admit that I am considering this because... quite simply, because it can be done.