hi
As Gil suggests also [see other email] - as soon as it starts up it tries to create a directory and to save temp data etc.
...like many apps do to create a prefs file and a cache 'environment' i believe.
I have found it's often that process that firewalls intercept as a malicious act and stop from happening.
This would mean that ishell can't generate any temp preferences etc and will fail at the initial startup process most likely. [as your's apparently does]
It is often very tricky in a networked scenario where all application created data is prevented except those from authorised apps.
Some firewalls and antivirus apps are VERY intrusive and monitor all data creation and prevent it from proceeding.
it appears that the CyberArmor 'granular' settings need to be adjusted...
It could also be the launcher being prevented from launching the main app - some firewalls prevent this - one app launching another one etc.
But in that case you would probably see the launcher start up and then fail to launch the other main project.
Can these machines definitely all run a QT mov file?
ie. is QT actually allowed to run?
I have also seen situations where QT is installed but then is not allowed to run anything.
If it is possible you need to talk directly with their IT people and get them to try and run through the usual debugging process.
- run a QT movie
- run simple ishell project to see if it;s your porject or the main app or launcher
- run another ishell project and then your ishell project to see if it's unique to your app
- run your project with the cyberarmour software temporarily turned off or suspended or set to allow apps to create sub user directories
etc
Someone needs to check the actual user settings too - to make sure the users can create data in their own directories - sometimes this can be set too severely.
It is not unheard of for users in large orgs and businesses to have virtually no ability to create data or directories except the networked default home drive.
eg. also users may not be logging into the local machine at all - but logging in as network users on a server home directory. ie. the local machine s simply a hardware client
We often see this in schools and university network setups.
These are all steps that are not really unique to ishell debugging... just IT environment debugging...
I think it's best to assume thats it's their setup if no one else is complaining.
I would take a wild guess that this is probably NOT a software issue - this is most likely an IT policy issue.
lloyd