Thx for your anwser, that helps much. But there is another think, that you can maybe fix in future versions: in companies users have no admin rights for local machine mostly. so the don't have write access to c:/program files/ your programm tries to write on startup in c:/program files and wont start if it is not possible. A workaround is installing the program somewhere else where the user can write, but this is ugly. C:/program files/ should be used only for installation, after that all changes should be in user folder.
Thx for your anwser, that helps much. But there is another think, that you can maybe fix in future versions: in companies users have no admin rights for local machine mostly. so the don't have write access to c:/program files/ your programm tries to write on startup in c:/program files and wont start if it is not possible. A workaround is installing the program somewhere else where the user can write, but this is ugly. C:/program files/ should be used only for installation, after that all changes should be in user folder.
Thanks for your suggestion, I'll let the development team know about your suggestion and we will let you know when this is introduced in a future release.
Best regards,
Marc
Hi Marco,
Thanks for your suggestion, I'll let the development team know about your suggestion and we will let you know when this is introduced in a future release.
Hi Marco,
The installer is made using NSIS http://nsis.sourceforge.net. If you
want to launch it in silent mode you need to execute this command:
“[name of Prototyper’s installer].exe” /S /D=C:[route where you want
to install it, works better for shorter routes]
Best regards,
Marc
Hi Marco,
The installer is made using NSIS http://nsis.sourceforge.net. If you
want to launch it in silent mode you need to execute this command:
“[name of Prototyper’s installer].exe” /S /D=C:[route where you want
to install it, works better for shorter routes]
Best regards,
Marc
Thx for your anwser, that helps much. But there is another think, that you can maybe fix in future versions: in companies users have no admin rights for local machine mostly. so the don't have write access to c:/program files/ your programm tries to write on startup in c:/program files and wont start if it is not possible. A workaround is installing the program somewhere else where the user can write, but this is ugly. C:/program files/ should be used only for installation, after that all changes should be in user folder.
Thx for your anwser, that helps much. But there is another think, that you can maybe fix in future versions: in companies users have no admin rights for local machine mostly. so the don't have write access to c:/program files/ your programm tries to write on startup in c:/program files and wont start if it is not possible. A workaround is installing the program somewhere else where the user can write, but this is ugly. C:/program files/ should be used only for installation, after that all changes should be in user folder.
Hi Marco,
Thanks for your suggestion, I'll let the development team know about your suggestion and we will let you know when this is introduced in a future release.
Best regards,
Marc
Hi Marco,
Thanks for your suggestion, I'll let the development team know about your suggestion and we will let you know when this is introduced in a future release.
Best regards,
Marc
Hello, can the uninstaller be launched in silent mode?
Hello, can the uninstaller be launched in silent mode?
Replies have been locked on this page!