Dear all, Recent experience show that scripts do not behave after wake up from hibernation: In FrameMaker a document is open and one of my scripts (FMmarkers) is used heavily to check and correct index markers. I need to interrupt work now and hibernate the system After waking up the sysstem next day I want to continue work and for that purpose restart the script from the menu. But some functions are damaged I save all open documents and restart FM The script now behaves as it should Can anyone confirm this behaviour - or have an explanation what's going wrong?

K.Daube

Community Expert

Question

The danger of hiberation for scripts

Forum|Forum|3 years ago
March 18, 2022
1 reply
126 views

Dear all,

Recent experience show that scripts do not behave after wake up from hibernation:

In FrameMaker a document is open and one of my scripts (FMmarkers) is used heavily to check and correct index markers.
I need to interrupt work now and hibernate the system
After waking up the sysstem next day I want to continue work and for that purpose restart the script from the menu.
But some functions are damaged
I save all open documents and restart FM
The script now behaves as it should

Can anyone confirm this behaviour - or have an explanation what's going wrong?

Scripting

This topic has been closed for replies.

Bob_Niland

Community Expert

The Hibernate feature appears to be disabled (not visible to Users) by default in Win10 (Win10 Pro/64 here). It's necessary to drill down (as Admin) in some dialogs to make it available again. And then, about every 3rd Windows Update, it gets turned back off. I suspect that MS knows something they aren't willing to admit.

I use hibernate routinely, but I've seen enough issues in FM (and other apps), that I perform a re-boot before doing any serious work in any application.

Apart from the bugs people see, MS may be deprecating Hibernate because, unlike shut-down & Sleep, it prevents Updates.

K.Daube

Author

Community Expert

Thanks Bob for Your comment. I use the hibernation feature only to 'preserve' the current environment with all the open windows to remind we, where I disrupted my work. And I do not use the Windows Start thingy (my Win account seems to be admin)

but an AutoHotKey script which issues the hibernate command and also logs the time. Also the time of wake-up (and type of) is logged.

But yes, there are also other effects than the one reported here. For example, very often after wake-up FM does not execute CTRL+xx shortcuts and I need to use the context dialogs to go further (even CTRL+s does not work in these cases).

Concerning reboot: normally I shut down Windows completely in the evening and boot completely. So the last two days look like this in my system log (the 1391st start since I installed Win10 in October 2019):

Thu 2022-03-17 16:32:38	Starting 1391  OS: 21H1 Build: 10.0.19043.1586
Thu 2022-03-17 18:07:37	; ;	Force hibernate
Thu 2022-03-17 18:07:44	; ;	Suspend 4
Fri 2022-03-18 10:03:55	; ;	Resume 7
Fri 2022-03-18 10:03:56	; ;	Resume 18
Fri 2022-03-18 11:05:28	Ordinary Close	; ;	Shut down
Fri 2022-03-18 16:44:00	Starting 1392  OS: 21H1 Build: 10.0.19043.1586
Fri 2022-03-18 16:56:39	Start	; ; Win open dialogue huge for a short time, then it settles - is it gone?
Fri 2022-03-18 17:14:03	Start	; ; custom scaling was on (234) - don't know what/who set it
Fri 2022-03-18 17:20:15	Logging	; ; Resetting to 100% did not help: any Win open dialogue blinks in full screen size (3440x1440) until it is finally displayed correctly
Fri 2022-03-18 17:28:21	Logging	; ; I did this: if the dialog is finally open in correct size, double click in the header line to maximise it to the screen size; then double click again to restore correct size. This seems to have cleared the problem.

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.

Scanning file for viruses.

This file cannot be downloaded