[ 0 ] - switches
- [ 0.1 ] : =>App or User should create an idle/empty win service any time she starts and destroy it at non hard exit ( normal user exit, non bluescreen, EPU powwa lose or acpi shutdown ), this way App will know at any autostart if all is ok! n can handle auto connection w/o leading a fail loop.
=>User still can auto start the App by programing a new task in Task Scheduler (win start menu \ win. accessories \ TaskScheduler.exe ) for only openin' the app or write some script in ur preferred sys authorized lang to load the App & send a mouse click to the button if it's rendered.
- [ 0.2 ] : => If you have some empty RAM and can finely adjust CPU threshold and dynamic GPU n CPU cooling. U are ready to deal with virtual machines. This way you can solve all your issues cause some one like VirtualBox (accepts some functions like pause, save state, command line, autostart, seamless or windowed, send mouse or keystrokes and more)
Kn
Hi dears... hope this lines aid u in someway:
[ 0 ] - switches
- [ 0.1 ] : =>App or User should create an idle/empty win service any time she starts and destroy it at non hard exit ( normal user exit, non bluescreen, EPU powwa lose or acpi shutdown ), this way App will know at any autostart if all is ok! n can handle auto connection w/o leading a fail loop.
=>User still can auto start the App by programing a new task in Task Scheduler (win start menu \ win. accessories \ TaskScheduler.exe ) for only openin' the app or write some script in ur preferred sys authorized lang to load the App & send a mouse click to the button if it's rendered.
- [ 0.2 ] : => If you have some empty RAM and can finely adjust CPU threshold and dynamic GPU n CPU cooling. U are ready to deal with virtual machines. This way you can solve all your issues cause some one like VirtualBox (accepts some functions like pause, save state, command line, autostart, seamless or windowed, send mouse or keystrokes and more)