1,852
edits
(→Octave does not start: comments on script file associations) |
(→MS Windows: Revisit the great article Nrjank :-)) |
||
Line 94: | Line 94: | ||
* Permission errors | * Permission errors | ||
: Octave on | ** '''Solution 1:''' Octave on MS Windows uses VBS scripts to start the program. You can test whether your system is blocking VBS scripts by doing the following: | ||
*# Using Notepad or another text editor, create a text file containing only the text: | **# Using Notepad or another text editor, create a text file containing only the text: <pre>msgbox("This is a test script, Click OK to close")</pre> | ||
*# | **# Save the file on your Desktop with the name {{Path|testscript.vbs}} (be sure that the editor didn't end it in .txt or .vbs.txt) | ||
*# | **# Double click the file. If scripts can run, a popup window will appear with that message. | ||
*#* If the file opens in notepad or an editor, it means it still ended in .txt. | **#* If the file opens in notepad or an editor, it means it still ended in .txt. MS Windows insecurely hides file extensions by default. To show file extensions follow [https://answers.microsoft.com/en-us/windows/forum/all/in-win10-how-to-show-the-file-extension-for/ed21ff20-cdb3-4263-9c7d-fc6ed125fc82 these instructions at Microsoft.com]. | ||
*#* If both | **#* If both {{Path|testscript.vbs}} and {{Path|octave.vbs}} open a text- or other editor, it means your MS Windows file associations have .vbs files associated with another program. To fix this, right click the .vbs file, select "Open With", select "Choose Another App", check the box that says "Always use this app to open .vbs files". Finally, select "Microsoft Windows Based Script Host" from the list. If it is not in the list, select "More apps". If still not there, select "Look for Another App on this PC" and navigate to {{Path|C:\Windows\System32\wscript.exe}}, select it, and select "Open". If {{Path|wscript}} is still not present you will need to seek assistance installing missing MS Windows components. | ||
*# | **# Try moving {{Path|testscript.vbs}} to another location, such as a {{Path|C:\temp folder}}. Additionally try to move {{Path|testscript.vbs}} in the Octave installation folder containing {{Path|octave.vbs}} and see if VBS scripts can be run there. | ||
*# | **# If {{Path|testscript.vbs}} doesn't run in any of those locations, then scripting appears to be disabled or blocked on your system. If {{Path|testscript.vbs}} runs in some locations but not others, there there may be other security permissions errors to be solved. If {{Path|testscript.vbs}} runs in the same folder as {{Path|octave.vbs}}, but directly double-clicking on {{Path|octave.vbs}} does not start Octave, then there appears to be some problem other than script permissions. | ||
** '''Solution 2:''' Consult your malware detection (a.k.a. AntiVirus) software, if files are blocked. | |||
** '''Solution 3:''' Did you install Octave on a network-drive? Do you have the execution permissions? | |||
** '''Solution 4:''' Is your computer managed by your company? Does your administrator prohibit script execution? | |||
==I do not see any output of my script until it has finished?== | ==I do not see any output of my script until it has finished?== |