Hello,
I'm still working on a nice configuration, but time is lacking and there were some setbacks...
My plan is to use EventGhost as a central control point for (initially) 2 instances of winamp to bring music to two zones (using different soundcards). The computer which would run it is also used for media playback, and playing back music would leave visible windows in the userinterface (they may be minimized, but would still be there). Most control would be from a webinterface.
I'm not sure if running EventGhost as a service would allow it to launch winamp. So would this work to avoid some clutter:
1. add an account to the pc (let us call it "control"), and set the system to automatically log in to this account
2. eventghost starts on startup, so it will launch at login
3. disconnect the session by calling tsdiscon (which should not log out, but go to the user login screen to switch user)
I've tested, and when disconnecting a session, the winamp keeps playing audio. I suspect the audio device is blocked for other users, but with multiple audio devices in the system, it should be possible to "give" one device to one user. A downside would be the time for the login/lock, but the computer boots fast enough and it might be worth the benefits.
But what when I log in ? If EventGhost launches also, will there be two running instances of eventghost (one per active user)? How would it react?
Or should I prevent EventGhost from launching for all other users?
Notice: This forum has been recovered from an old backup, so some content, links, and dates may be outdated. The forum is currently read-only while we restore sign-in and registration functionality. Details
If you find this forum valuable and would like to help keep it online, donations to help cover hosting and domain costs are greatly appreciated, but never expected. You can support the forum through Buy Me a Coffee or Ko-fi. Thank you for helping preserve the EventGhost community.
If you find this forum valuable and would like to help keep it online, donations to help cover hosting and domain costs are greatly appreciated, but never expected. You can support the forum through Buy Me a Coffee or Ko-fi. Thank you for helping preserve the EventGhost community.
Would this work: auto-login/lock
- kgschlosser
- Site Admin
- Posts: 5190
- Joined: Fri Jun 05, 2015 5:43 am
- Location: Rocky Mountains, Colorado USA
Re: Would this work: auto-login/lock
You cannot run EventGhost as a service. This is because it creates a GUI when it is started. And at the current state the GUI is so interwoven into the code it's not a simple thing to separate. We have started to add some of the bits that we are going to need to be able to send information to a user interface. It is in the works. But at the moment you will have to login to the computer.
- kgschlosser
- Site Admin
- Posts: 5190
- Joined: Fri Jun 05, 2015 5:43 am
- Location: Rocky Mountains, Colorado USA
Re: Would this work: auto-login/lock
here is what you would do.
use the directions provided here
https://www.howtogeek.com/112919/how-to ... matically/
to cause the computer to login automatically when it boots.
set eventghost to startup automatically.
then create a macro with the lock workstation action and in that macro add the event Main.OnInitAfterBoot
what this will do is as soon as the computer boots it will log you in and run eventghost. and when eventghost runs it will see that it was started from boot and then lock the computer this way EG will run but the computer will be locked.
use the directions provided here
https://www.howtogeek.com/112919/how-to ... matically/
to cause the computer to login automatically when it boots.
set eventghost to startup automatically.
then create a macro with the lock workstation action and in that macro add the event Main.OnInitAfterBoot
what this will do is as soon as the computer boots it will log you in and run eventghost. and when eventghost runs it will see that it was started from boot and then lock the computer this way EG will run but the computer will be locked.
