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 10:02:33 +0200

Am 22. September 2021 um 09:43 Uhr schrieb "David Remans":
> HI Markus,
> 
>  See comments below. Unfortunately Gui does not show Yet.
> 
> Best regards,
> 
> David Remans
> 
> 
> -----Original Message-----
> From: Markus Mützel <markus.muetzel@gmx.de> 
> Sent: woensdag 22 september 2021 09:36
> To: David Remans <D.Remans@tradinco.com>
> Cc: help@octave.org
> Subject: RE: Octave does not start
> 
> 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)?
>               [DRE] First I installed for all users, now I installed for 
> current user only, I get the same behaviour.
> 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?
>               [DRE] Yes this works fine, I get a command Prompt with text in 
> it

That is good news. So, Octave per se seems to work. But for some reason the GUI 
doesn't start.

Some GUI related packages have been updated in our build system for Windows 
since Octave 6.3.0 has been released. Could you please check if a nightly build 
from octave.space works for you?
https://buildbot.octave.space/#/download


> 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?
>               [DRE] No it does not solve the problem
> > > 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?
>               [DRE]   Yes I do not see any text on my screen

So, there might be two unrelated issues here:
1. The GUI doesn't open.
2. The .vbs file doesn't open the CLI.


> > > 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*
>               [DRE] I did, see attached (second) screenshot
> 

If I'm not mistaken, you forgot to add the asterisk at the end of the last 
command. Could you please execute the command as shown?

At the installation location that you've shown in the last screenshot, the 
corresponding commands would be:
C:
cd "\Users\d.remans\AppData\Local\Programs"
dir /x GNU*





reply via email to

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