we have a Windows Terminal Server at Beuth University of Applied Sciences. Students log into it from client computers.
Only the first one starting Kojo by the Start menu succeeds. For all subsequent trials we only see a second-lasting hourglass, which diappears without a message. After exiting the first Kojo instance, another instance can be started.
As we do not know this behavior from other Java applications we suppose the little kojo.exe to be guilty.
In the Kojo2\bin directory there is a shell script for starting Kojo. It collects all .jar files from Kojo2/lib.
Do you have an equivalent script as Windows batch file for trying a workaround?
Or how could we diagnose, why only the first Kojo instance can start?
Thank you very much,