Hi,
at two MS Windows machines we had a problem that installation of MS runtime libraries during GRASS installation failed. GRASS was not able to run then even though installer linked at GRASS wiki [1] says that libraries are installed.
At least at one of the machines the error in GRASS installer log was something like “HTTP 404 Not found”. However, downloading the file manually works (I determined the URL from installer source code [2]). Then we run the the exe files and copied dlls as the installer is doing [3]. And GRASS works.
Of course, on other computer on the same network the download works well. Do you have the any idea why download would fail? Antivirus? The computers have different system configuration but the antivirus program might be the same.
Also do you think that the steps from the installer should go to the wiki [1]. The tar.bz2 would be bit unfortunate in this case and we might want to ask for adding there zip/7z too.
Thanks,
Vaclav
[1] http://grasswiki.osgeo.org/wiki/WinGRASS_errors#The_winGRASS_program_exits_immediately_after_I_start_it.21
[2] http://trac.osgeo.org/grass/browser/grass/trunk/mswindows/GRASS-Installer.nsi.tmpl#L973
[3] http://trac.osgeo.org/grass/browser/grass/trunk/mswindows/GRASS-Installer.nsi.tmpl#L938
> Do you have the any idea why download would fail?
The computers have different system configuration
some possible issues:
- osgeo-server down?
- winGRASS-standalone installing without admin rights?
- no right to download from internet?
- ...
I've seen there is now:
http://download.osgeo.org/osgeo4w/x86/release/msvcrt/msvcrt-1.0.1-12.tar.bz2
27-Jun-2014 12:09 12M
the installer source points to:
974 StrCpy $ARCHIVE_NAME "msvcrt-1.0.1-11.tar.bz2"
this should be changed in trunk and in all branches.
Also do you think that the steps from the installer should go to the wiki
[1].
maybe yes, but doubling of packages on the server should be avoided IMHO.
-----
best regards
Helmut
--
View this message in context: http://osgeo-org.1560.x6.nabble.com/Installing-MS-DLLs-failed-because-of-404-tp5149036p5149075.html
Sent from the Grass - Dev mailing list archive at Nabble.com.
At least at one of the machines the error in GRASS installer log was
something like "HTTP 404 Not found".
http://en.wikipedia.org/wiki/HTTP_404
The 404 or Not Found error message is a HTTP standard response code
indicating that the client was able to communicate with a given server, but
the server could not find what was requested.
[...]
A 404 error should not be confused with "server not found" or similar
errors, in which a connection to the destination server could not be made at
all. A 404 error indicates that the requested resource may be available
again in the future; however, the fact does not guarantee the same content.
-----
best regards
Helmut
--
View this message in context: http://osgeo-org.1560.x6.nabble.com/Installing-MS-DLLs-failed-because-of-404-tp5149036p5149076.html
Sent from the Grass - Dev mailing list archive at Nabble.com.
On Tue, Jul 1, 2014 at 2:57 PM, Helmut Kudrnovsky <hellik@web.de> wrote:
> Do you have the any idea why download would fail?
> The computers have different system configuration
some possible issues:
- osgeo-server down?
- winGRASS-standalone installing without admin rights?
- no right to download from internet?
- ...
As I wrote manual download worked. So, osgeo sever is fine and general
download works as well that's why my guess was some strange
security/antivirus settings but I don't know how to prove or disprove this.
(My first guess was problem with server because of 404 but it was easy to
disprove.)
On Tue, Jul 1, 2014 at 2:57 PM, Helmut Kudrnovsky <hellik@web.de> wrote:
> Also do you think that the steps from the installer should go to the wiki
> [1].
maybe yes, but doubling of packages on the server should be avoided IMHO.
The guide is there but I don't want to see the user struggling with
unpacking tar.bz2 on MS Window. zip or 7z would be helpful. It might be
convenient to have both. The package is >12 MB, so size is the issue?
http://grasswiki.osgeo.org/wiki/WinGRASS_errors#The_GRASS_GIS_.28winGRASS.29_exits_immediately_after_I_start_it.21
The guide is there but I don't want to see the user struggling with
unpacking tar.bz2 on MS Window. zip or 7z would be helpful.
7zip can unzip and untar tar.bz2. so if you have installed 7zip, you can do
this.
The package is >12 MB, so size is the issue?
I would say manpower; there are 1-2 persons maintaining OSGeo4W base
packages.
-----
best regards
Helmut
--
View this message in context: http://osgeo-org.1560.x6.nabble.com/Installing-MS-DLLs-failed-because-of-404-tp5149036p5149095.html
Sent from the Grass - Dev mailing list archive at Nabble.com.
On Tue, Jul 1, 2014 at 5:03 PM, Helmut Kudrnovsky <hellik@web.de> wrote:
>The guide is there but I don't want to see the user struggling with
unpacking tar.bz2 on MS Window. zip or 7z would be helpful.
7zip can unzip and untar tar.bz2. so if you have installed 7zip, you can do
this.
Excellent. I was not aware of that. Added to the wiki.
http://grasswiki.osgeo.org/wiki/WinGRASS_errors#The_GRASS_GIS_.28winGRASS.29_exits_immediately_after_I_start_it.21
>The package is >12 MB, so size is the issue?
I would say manpower; there are 1-2 persons maintaining OSGeo4W base
packages.
I can understand that. Since 7-Zip (which is open source) can handle it, I
don't see any problem with tar.bz2 (especially when it is now noted in the
guide).
http://grasswiki.osgeo.org/wiki/WinGRASS_errors#The_GRASS_GIS_.28winGRASS.29_exits_immediately_after_I_start_it.21
-----
best regards
Helmut
--
View this message in context:
http://osgeo-org.1560.x6.nabble.com/Installing-MS-DLLs-failed-because-of-404-tp5149036p5149095.html
Sent from the Grass - Dev mailing list archive at Nabble.com.
_______________________________________________
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev