Thu 25 Dec 2014 01:32:52 PM UTC, comment #12:
Pushed http://hg.octave.org/mxe-octave/rev/7a6637aa3aae
|
Mon 22 Dec 2014 10:36:41 AM UTC, comment #11:
Thank you very much for the installer, John.
I downloaded the Dropbox version and installed it on a Windows 7 machine.
- Octave GUI comes up
- IL "Medium"
- No network shares at home, but I'm confident it will work
|
Thu 18 Dec 2014 02:59:00 PM UTC, comment #10:
Oh no. Dropbox is being blocked at work :-/ I'll try later.
|
Thu 18 Dec 2014 01:27:54 PM UTC, comment #9:
Try this:
https://www.dropbox.com/s/biv4im3qu987k3h/octave-3.8.2-installer.exe?dl=0
|
Thu 18 Dec 2014 01:26:28 PM UTC, comment #8:
Yes would need to build the installer.
The default for the bat runs the viewer - originally it did not, but not is needed to pass the program to run for explorer.
I will send a link to a prebuilt version on dropbox.
|
Thu 18 Dec 2014 08:07:22 AM UTC, comment #7:
Thank you for the patch.
I'm not shure how to test it. I did a build of Octave on Cygwin once, which took hours and grew the swap file to >100GB. This time, I would have to build the installer using the MXE environment, right?
Btw, the last parameter "--force-gui" is dropped with the patch. But I guess it is OK, because the default behaviour for "octave.bat" without parameter is to launch the GUI.
|
Wed 17 Dec 2014 07:19:36 PM UTC, comment #6:
Does this patch work?
(file #32687)
|
Tue 16 Dec 2014 03:56:50 PM UTC, comment #5:
The problem is well-known. Just Google for "NSIS MUI_FINISHPAGE_RUN UAC" and get more than 1000 hits.
Possible solutions found:
- Launch new Explorer process (seems most reasonable to me)
https://stackoverflow.com/questions/16555625/how-to-launch-an-executable-on-the-end-of-installation-correctly
- NSIS "UAC" Plugin (seems to be difficult to use)
http://nsis.sourceforge.net/UAC_plug-in
- NSIS "ShellExecAsUser" Plugin
http://nsis.sourceforge.net/ShellExecAsUser_plug-in
|
Tue 16 Dec 2014 03:00:47 PM UTC, comment #4:
No, this is not what I suggested. I agree with you that the installer needs admin rights (UAC) during installation.
The problem might be around makeinst-script.sh line 112
There should be some mechanism to restore Integrity Level after installation. I'm thinking of something like
The drawback here is that the user has to type his/her password again. Maybe there is some more elegant solution. I'm not the NSIS expert, unfortunately.
|
Tue 16 Dec 2014 12:07:27 PM UTC, comment #3:
So you suggest to set "RequestExecutionLevel user" (http://nsis.sourceforge.net/Reference/RequestExecutionLevel)
in makeinst-script.sh line 127 (http://hg.octave.org/mxe-octave/file/bb70aeee012e/makeinst-script.sh#l127)?
I don't use Windows but I think you're then not able to install Octave for all users. Is this intended?
Can you try the installer with RequestExecutionLevel changed?
I think not beeing able to access mapped network shares during installation is a small glitch. Can we force the Installer to not start the GUI at the End or force to close the GUI?
|
Tue 16 Dec 2014 09:38:39 AM UTC, comment #2:
Hmmm, I did a diff on the Octave installation folder, "octaverc" files etc. but nothing special here.
How about this theory:
When launching the installer, UAC is asking for confirmation (no "administrator password"). After that, the installer is running under Integrity Level = High. The installer is spawning Octave, also under Integrity Level = High.
When exiting Ocatave and launching again manually, then Integrity Level = Medium.
Citing Microsoft
Some Programs Cannot Access Network Locations When UAC Is Enabled
"This problem occurs because UAC treats members of the Administrators group as standard users. Therefore, network shares that are mapped by logon scripts are shared with the standard user access token instead of ..."
So, I would suggest that the installer has to launch Octave under "Medium" IL to fix the behaviour.
|
Mon 15 Dec 2014 10:19:25 PM UTC, comment #1:
A bit of speculation: such issues can also be caused by the installation routines invoked in Windows, or some inheritance of the installer's process properties by Octave, maybe even related by anti-malware SW.
Did you have to specify the administrator password?
Admittedly it may not be as it should, but I'm not too worried that Octave lacks a bit of functionality until after a first restart.
|
Mon 15 Dec 2014 11:02:55 AM UTC, original submission:
I just did a new installation of MXE Octave 3.8.2-4
http://mxeoctave.osuv.de/
- Uninstall previous 3.8.2-3
- Install actual 3.8.2-4
- The installer is asking "[X] Run Octave"
In this constellation, Octave will not have access to network shares. Example:
Now
- Exit Octave
- Start Octave GUI manually
It seems that when finishing the installation, but before exiting the installer tool, some prerequisite is missing to Octave to be able to mount network shares.
Seen on Windows 7 64 bit
|