🚀 go-pugleaf

<Donut> wrote:

>All labtop computers has a hibernate function which stores the current state
>of all running application at the time hibernate function activated and then
>when wake-up function activated all applications are restored and they
>continue normal operation from the state when they are forced to hibernate.
>
>How to implement such  functions; hibernate and wake-up, on application base
>in such a way that we can press a button and save the current state of the
>application and may be copy the saved state onto another computer and wake
>it up from the state when it hibernated?
>
>Any idea?

No.
You'd have to copy all of the DLLs loaded into memory that the program
relys on, as there is no guarantee that loading them again after
hybernation would put them back in the same locations.
Then, when you restore the dlls, well, they aren't registered properly
with Windows, so who knows what kind of system bugs that would
produce?

Or, before you saved the program, you would need to unload _all_ the
dlls, probably including the kernal, and all of the auto-load dlls
that load before you even get to _main(). And how would you save it
without the file i/o from the kernal?

Then there's the problem of how do you restore it? Writting a program
into executable memory isn't allowed. (Or it is? But not for long as
it's a Viral action?)

So, no. Hibernate in the Windows sense isn't going to make it.

But, all is not lost.
What you _can_ do is copy all of your data and settings to disk, and
read them back in when you restart the application. If the data is in
Global as opposed to Stack space, then the copying is easier. If you
want to come back to the same sub-screen, you'd need to mark that in
the file some how, and add the code to get back to that screen.