Resurrecting an old discussion - we semi regularly get users that have issues starting Octave on Windows. On occasion, we find that due to security settings, permissions issues, etc., executing a vbs file to start octave or sometimes even installing a vbs file is an issue. This used to be done by a .bat script file. There was suggestion that it could all just be part of the exe file that actually starts octave… The previous discussion was scattered amongst mailing list and bug reports. thought I’d create a new discussion here to add to the noise.
previous mailing list discussion:
“I came across bug #41074 that i think resulted in shifting from a .bat to .vbs file and seems to identify (1) no terminal window hanging around while the gui is up, (2) starting cli version in a way that still let you produce qt graphics, (3) producing the first time welcome dialog if needed.”
JWE asked if it could just be done with a separate ‘launcher’ exe, and JohnD provided one here:
Don’t think these were ever captured in a bug report. probably should be. I’d have to hunt some more to see if one was created that i missed.
a sampling of previous vbs startup/installation issues:
- Octave CLI and GUI does not open from desktop shortcut after installation on MS Windows 10
- VBS script execution blocked on Windows 10 - Super User
- Problem regarding Octave Installation
- installation - Octave GUI doesn't come up on windows 10 x64 - Super User