RE: windows installer - vbs vs bat startup script

[JohnD]

> Message: 2
> Date: Tue, 25 Aug 2020 11:53:01 -0400
> From: Nicholas Jankowski <jankowskin@asme.org>
> To: octave maintainers mailing list <maintainers@octave.org>
> Subject: windows installer - vbs vs bat startup script
> Message-ID:
>       <CABNpfR-A-
> GJdExxbuA0yCtWhnvaKzWpEU0wP006j9D4PrimO7A@mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
> 
> working through a user issue on startup trouble that is tied to an (as yet
> unsolved) inability to execute vbs scripts[1][2], a comment was made "why
> do you need VBS for something as simple as setting path and environment
> variables and starting a program? A simple batch script will do it and is
> guaranteed to work. If you would like to avoid a black CMD window see this
> post [3]"
> 
> I came across bug #41074 [4] 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.  i seem to recall there being something else but it escapes me, I
> don't know if it made any other setup steps easier.
> 
> thanks to the history of windoze security issues, using a vbs may be
> problematic for some users, with the usual result of "octave doesn't
> start". Were there other reasons for shifting to the .vbs that I'm missing
> above? Is there a workaround for someone who just can't run a vbs file for
> some reason?  I hate to suggest reverting to the 'include .bat as a backup'
> model, but is that the only method that would work for them?
> 
> [1]
> https://octave.discourse.group/t/octave-cli-and-gui-does-not-open-from-
> desktop-shortcut-after-installation-on-ms-windows-10/112
> [2]
> https://superuser.com/questions/1579906/vbs-script-execution-blocked-on-
> windows-10
> [3]
> https://superuser.com/questions/62525/run-a-batch-file-in-a-completely-
> hidden-way
> [4] https://savannah.gnu.org/bugs/?41074
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <https://lists.gnu.org/archive/html/octave-
> maintainers/attachments/20200825/b8e34f84/attachment.html>
> 

So which solution on [3] did you mean for hidden batch file ? 

>From memory I think the only reason for shifting to the .vbs was because it 
>was the only solution that appeared to not flash a cmd console on startup, or 
>hide the octave first use dialog 

The vbs file was only ever intended on running from the windows shortcuts or 
from clicking on the file - not for running in scripts where the .bat file 
should be used. The bat file is also the one that is run when octave is called 
in pkg installs etc

The .bat file is installed by default just appears in the bin folder rather 
than at top level so is available if needed. 

But if there is a solution that doesn’t require the .vbs that works then we can 
change it