Anmeldelser af Auto Shutdown (WebExtension)
Auto Shutdown (WebExtension) af Sarah Av., Andy Portmen
7 anmeldelser
- Bedømt til 1 ud af 5af Piotr, 2 år siden
- Bedømt til 1 ud af 5af Firefox-bruger 14734224, 6 år sidenCommands aren't clear... ‘CALL:PowrProf.dll SetSuspendState 0 1 0’, ...
Tip : do not copy the quote marks nor the ending comma.
I get this error after countdouwn :
If you still get this page even when the "Check Button" reports successful connection, it means the application cannot be accessed (path is not correct in the options page). If the path to the executable is correct and the native client is connected, you can debug the connection by enabling console logs.
Fix this error pls - Bedømt til 1 ud af 5af Firefox-bruger 6562376, 7 år sidenCommands aren't clear... ‘CALL:PowrProf.dll SetSuspendState 0 1 0’, ...
Tip : do not copy the quote marks nor the ending comma.
I get this error after countdouwn :
If you still get this page even when the "Check Button" reports successful connection, it means the application cannot be accessed (path is not correct in the options page). If the path to the executable is correct and the native client is connected, you can debug the connection by enabling console logs.
Native client 0.6.6 is installed, however I'm not seeing any sort of path to edit on the options page.
Tutorial page is for chrome, video tutorial is for chrome...
What should we look for into logs ?
Please fix this. (W7x64 - FF57.0.2) - Bedømt til 1 ud af 5af ziba17, 7 år sidenIt didn't work for me. only count down that count to 0 but no action! some years ago I had an add-on with the name and icon similar to the name and icon of this add-on but that years it was functional.
- Bedømt til 1 ud af 5af cec, 8 år sidenIt's not a straightforward installation, as well as the extension, other software has to be downloaded and installed.
Seems to run ok, and the clock countdown to zero, but then an error is indicated. The error suggests a path error but there is no path available to edit.
Altogether a messy extension.
Contacted the author for help.
Edit 30/9/17
No response from author - says a lot when the author doesn't respond to bug reports on his own support site.
Pretty safe to assume this extension is dead.