Copied from the chat:
- seltzdesign
Quick question: Are there any resources/turorials/forum posts you know about concerning running Gamma in an exhibiton environment where you have a dedicated computer that has to start up/shutdown on its own, start VL in fullscreen, etc.? Thanks
- tebjan
sebescudie has recommended chataigne as an automation tool. I would also be interested in his latest review and whether he would still recommend it.
- boris.vitazek.stx
from my experience its important to pick pc with bios that has scheduled start, you can shutdown with gamma, otherwise I did not have any problems of starting gamma and not having app fullscreen, but that would be probably even better if you compile the app
- lecloneur
you need to start VL or start the app you exported from VL ?
- catweasel
I use a vvvv or VL app to do it and to watchdog the patch, simply UDP heartbeat to check if the process is alive, if it isn’t kill it and relaunch. I did have a vvvv in contribs I think, I can try and find my VL if you like?
-
As boris says the most important thing is the wake on alarm and power on on power loss in the bios
-
catweasel
WatchDog.zip (47.9 KB)
-
Its not pretty, but it works :) You can export it to exe too.
-
lecloneur
just curious how/why the process wouldn’t be running anymore ?
- seltzdesign
Excellent info, thanks everyone. I’ll check out the WatchDog file! It will be a .exe running for quite a while (a few years). It would turn off every evening and then start again in the morning. I saw something about Deep Freeze, where basically the harddisk is more or less locked and it can somewhat guarantee that nothing is ever changed or updated (looking at you, Windows).
- lecloneur
normally there isn’t any reason why a process would stop, I’ve got some installation running made with Gamma the only problem was the Windows defender eating the .exe file just when I was about to copy it on the computer
-
also put the .exe on startup app with auto fullscreen (for stride) and it’s been running smoothy so far
-
a scheduled restart help to flush memory also
-
motzi
seltzdesign
Excellent info, thanks everyone. I’ll check out the WatchDog file! It will be a .exe running for quite a while (a few years). It would turn off every evening and then start again in the morning. I saw something about Deep Freeze, where basically the harddisk is more or less locked and it can somewhat guarantee that nothing is ever changed or updated (looking at you, Windows).
I’ve had good experiences with the BIOS timer boot thing and turning off every night.
I also tried the UWF feature available windows enterprise (deep freeze/ram overlay of disks), but it was rather not successful due to windows always trying to update (which at some point caused huge traffic as downloaded updates were always lost on restart and then redownloaded). I’d be curious if someone has a way of configuring windows in a way that it behaves nicely with that feature…
- lecloneur
normally there isn’t any reason why a process would stop, I’ve got some installation running made with Gamma the only problem was the Windows defender eating the .exe file just when I was about to copy it on the computer
in beta times i had it sometimes that the process would crash (with a notification window), but would not be autokilled. having a watchdog lets you check if the process is still alive and not a zombie. so a watchdog is a good idea imho.
- motzi
in one of the long running installations i used the windows “aufgabenplanung” (taskplanner?) to define tasks when to boot the application. defining tasks there it allows you to run them also from commandline/executor which i called from the watchdog. it allowed a little more fine grained control when to start the application than when just using batch-files (and it will be logged in the windows event viewer). it felt to me that it is a clean “windows way” of doing stuff, but there is no particular advantage in my opinion to using just batch-files in autostart…
- chk
all these hints are too valuable to be buried in the chat :/ what about taking care of documenting them in the gray book (in the best practices section) or at least create a forum topic out of it?
- sebescudie
Wow sorry just seeing I was mentioned here : yes, I’m still using Chataigne for startup/monitoring/watchdog purposes on installations, works like a charm.
I also use it for project specific stuff (state machines, timeline, inter app communication) if needed, but it’s always there at least for the whole startup, watchdog and monitoring stuff