Sat 25 Jan 2014 09:54:40 PM UTC, comment #13:
Excellent, thanks for your testing and feedback.
|
Sat 25 Jan 2014 05:28:07 PM UTC, comment #12:
The shortcuts created during the installation work as intented.
So, as of 3.8 the human element of this issue is removed and thus solved.
Tested through wine and windows 8.
|
Thu 23 Jan 2014 05:50:26 PM UTC, comment #11:
This is the closest thing we have to an "official" binary release of Octave 3.8.0 for Windows currently, please download and install if you can and let us know if it resolves this issue:
http://octave.osuv.de/3.8/windows/
|
Thu 23 Jan 2014 03:12:00 PM UTC, comment #10:
I did not notice the new version since it is not yet downloadable. When a (official) binary package comes out, I will check if the problem still persists.
I suppose now that an installer is baked into the package (an presumably automatic shortcut creator) the issue will be solved, but will have to install it once to be certain.
|
Wed 22 Jan 2014 02:22:16 AM UTC, comment #9:
I'm not sure what you're saying in comment #8. There have been significant improvements in the Octave 3.8.0 binary build for Windows. Are you able to test the installer to see if the problem in this report has been solved? Thanks.
|
Tue 21 Jan 2014 05:58:57 PM UTC, comment #8:
After exploring what this bug was all about I concluded that a windows installation was needed to check it.
The problem still persists. Bar the changed version numbers tha directory structure is still the same as are the instructions. Details are in the original submission.
This applies at least to the mingw-packaged version.
|
Tue 21 Jan 2014 03:00:57 AM UTC, comment #7:
Thanks for following up. I'll close this bug as invalid. Please feel free to report any further bugs you may encounter.
|
Mon 20 Jan 2014 10:00:51 PM UTC, comment #6:
Original reporter here. I no longer have access to a Windows installation so I cannot check the state.
Kudos for trying to solve such an old problem.
|
Sun 19 Jan 2014 10:31:28 PM UTC, comment #5:
Has this bug been dealt with? Does the MXE installer of Octave 3.8.0 for Windows resolve the issues in this bug report?
|
Mon 28 May 2012 09:20:52 AM UTC, comment #4:
Ok, back after a long pause.
First of all I'll answer the question: no, explorer does not crash or lag after the paths are set up correctly.
Secondly, I could not get it to crash again when changing the .lnk file properties. What explorer does do is take so long to open the .lnk files when the paths are wrong that it will claim to be 'not responding'. After it's sweet time it will respond and one can change the paths.
To reiterate the problem, the default .lnk files do not match the readme instructions because of the extra folder (\Octave3.6.1_gcc4.6.2\).
Maybe just add the extended path to the link files so octave will work without touching any of the .lnk files if you extract the package to the suggested path.
|
Mon 30 Apr 2012 09:20:51 AM UTC, comment #3:
I don't have the access to a windows pc I can play araound at the moment, but I'll check it out when I get the chance.
- Driim
|
Fri 27 Apr 2012 05:40:20 AM UTC, comment #2:
OK, I will fix the readme and descritption in octaveforge download page on next release.
I do not know what might be the problem with the .lnk files. Are .lnk related explorer crashes happen also after the target,startup and icon paths are properly set ?
Nitzan
|
Wed 25 Apr 2012 06:53:08 PM UTC, comment #1:
Nitzan, do you want to take a look at this?
|
Wed 25 Apr 2012 06:48:01 PM UTC, original submission:
The instruction file Octave3.6.1_gcc4.6.2_readme.txt tells the user to create a directory and extract all the files to that directory (abbreviated <octave-dir>).
Then it advises to change the .lnk file directories to the format of <octave-dir>\bin\octave.exe.
The proble is that when you extract the files it creates an additional directory in the user's created directory (in this case Octave3.6.1_gcc4.6.2\). So the correct form for the .lnk file change would be <octave-dir>\Octave3.6.1_gcc4.6.2\bin\octave.exe
Also the start-in diorectory needs to be <octave-dir>\Octave3.6.1_gcc4.6.2, or the paths wont work.
Lots of student have had issues with this.
Also, for some reason opening the .lnk files properties takes an extra-ordinate amount of time or might ecen crash explorer.exe, though that is most likely just a windows bug, but one that might have to taken into consideration.
I.e. it might be wiser to omit the .lnk file altogether and give more precise instructions on creating the lnl-files.
|