help-octave
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: Octave does not start


From: Markus Mützel
Subject: RE: Octave does not start
Date: Wed, 22 Sep 2021 09:35:35 +0200

Am 21. September 2021 um 19:48 Uhr schrieb "David Remans":
> > Since you are writing about "octave.vbs", I am assuming you are using 
> > Windows. Which version of it?
> [DRE] Yes, Windows 10
>
> > How did you install Octave?
> [DRE] I ran the installer .exe file: octave-6.2.0-w64-installer.

Did you install for all users (i.e. in "C:\Program Files\...") or for the 
current user only (i.e. in your AppData folder)?

Depending on the answer to that question, you'll find an "octave.bat" file at a 
path like this one:
"C:\Program Files\GNU Octave\Octave-6.3.0\mingw64\bin\octave.bat"

Does executing that .bat file (e.g. by double-clicking) open a command line 
interface with an Octave prompt?

Additionally, you'll find the .vbs file (that looks like it's not doing the 
right thing for you) at a path similar to this one:
"C:\Program Files\GNU Octave\Octave-6.3.0\octave.vbs"

Does executing that .vbs file directly (instead of through the link in the 
start menu) open the Octave GUI for you?

> > Does starting the CLI work?
> When I select CLI I get a command screen, with a blinking cursor

Do I understand correctly? You only see a command screen with blinking cursor? 
No text at all?

> > Which anti-virus software are you using? Does it work if you temporarily(!) 
> > de-activate that software?
> Windows defender, I tried opening Octave after disabling the app & browser 
> control and the real time virus & threst protection, but so far no success.
> > Please check if your anti-virus software quarantined some of Octave's files.
> I checked, but did not find any quaranteened files
> > Are you on an administrated machine? Do the policy settings allow executing 
> > .vbs files?
> I do use a administrated machine,  I do not have a policy in place to prevent 
> .vbs scripts from running.

Some users reported that they had problems when Octave was installed in paths 
containing spaces because short file names were deactivated for them. (IIRC, 
they were able to start Octave though.)
Anyway, could you please open a CMD prompt, execute the following commands and 
show what you see? Might need to be adapted if Octave was installed to a 
different location:
C:
cd "\Program Files"
dir /x GNU*





reply via email to

[Prev in Thread] Current Thread [Next in Thread]