[GRASS-dev] G7 blockers call

Hi all,

we are slowly moving towards GRASS 7 release. Recently 3rd beta has
been released. It's importnant to know what is still missing before we
start RC stage. So please report ASAP issues which you feel that they
need to be solved before GRASS 7 will be released (especially API
changes, renaming modules, parameters, everything which is impossible
to change later because of backward compatibility).

Please report this issues as 'blockers'. Other notes can be collected
on trac wiki page [1].

Thanks for collaboration! Martin

[1] http://trac.osgeo.org/grass/wiki/Grass7Planning

--
Martin Landa * http://geo.fsv.cvut.cz/gwiki/Landa

Martin,

our semester has just started and we have students downloading and installing GRASS7.0.0RC3.
So far I had two students reporting the problem with MSVCR.71.dll missing - I have added the link to the
WinGRASS_errors wiki to the course webpage so I hope that will help.
I have a visiting student who had to go through the steps listed there to get GRASS7 working, but it seemed to work fine after that.
We also have it running on several machines in the lab, but I suggest to wait few days to see whether
any serious problems are reported by students (in addition to the WinGRASS installer issue which we cannot do anything
about as far as I understand it).

Helena

Helena Mitasova
Professor at the Department of Marine,
Earth, and Atmospheric Sciences
and Center for Geospatial Analytics
North Carolina State University
Raleigh, NC 27695-8208
hmitaso@ncsu.edu
http://geospatial.ncsu.edu/osgeorel/
"All electronic mail messages in connection with State business which are sent to or received by this account are subject to the NC Public Records Law and may be disclosed to third parties.”

On Aug 22, 2014, at 8:53 AM, Martin Landa wrote:

Hi all,

we are slowly moving towards GRASS 7 release. Recently 3rd beta has
been released. It's importnant to know what is still missing before we
start RC stage. So please report ASAP issues which you feel that they
need to be solved before GRASS 7 will be released (especially API
changes, renaming modules, parameters, everything which is impossible
to change later because of backward compatibility).

Please report this issues as 'blockers'. Other notes can be collected
on trac wiki page [1].

Thanks for collaboration! Martin

[1] http://trac.osgeo.org/grass/wiki/Grass7Planning

--
Martin Landa * http://geo.fsv.cvut.cz/gwiki/Landa
_______________________________________________
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

Hi Helena,

2014-08-23 5:48 GMT+02:00 Helena Mitasova <hmitaso@ncsu.edu>:

our semester has just started and we have students downloading and installing GRASS7.0.0RC3.

please note that it's not RC but beta!

So far I had two students reporting the problem with MSVCR.71.dll missing - I have added the link to the
WinGRASS_errors wiki to the course webpage so I hope that will help.

Checking "Important Microsoft runtime libraries" in the installer
should solve this problem [1].

Martin

[1] http://grasswiki.osgeo.org/wiki/WinGRASS_errors#The_GRASS_GIS_.28winGRASS.29_exits_immediately_after_I_start_it.21

--
Martin Landa * http://geo.fsv.cvut.cz/gwiki/Landa

On Sat, Aug 23, 2014 at 3:35 AM, Martin Landa <landa.martin@gmail.com>
wrote:

> So far I had two students reporting the problem with MSVCR.71.dll
missing - I have added the link to the
> WinGRASS_errors wiki to the course webpage so I hope that will help.

Checking "Important Microsoft runtime libraries" in the installer
should solve this problem [1].

I think this issue is discussed also somewhere else since I remember

writing this somewhere already. Anyway, at least for the record, checking
the check box does not help. Getting through the 2 other suggestion on wiki
does not help either. But doing the steps from the installer manually works
(the third suggestion). This was the case on two (or more) computers
already.

Martin

[1]
http://grasswiki.osgeo.org/wiki/WinGRASS_errors#The_GRASS_GIS_.28winGRASS.29_exits_immediately_after_I_start_it.21

wenzeslaus wrote

On Sat, Aug 23, 2014 at 3:35 AM, Martin Landa &lt;

landa.martin@

&gt;
wrote:

> So far I had two students reporting the problem with MSVCR.71.dll
missing - I have added the link to the
> WinGRASS_errors wiki to the course webpage so I hope that will help.

Checking "Important Microsoft runtime libraries" in the installer
should solve this problem [1].

I think this issue is discussed also somewhere else since I remember

writing this somewhere already. Anyway, at least for the record, checking
the check box does not help. Getting through the 2 other suggestion on
wiki
does not help either. But doing the steps from the installer manually
works
(the third suggestion). This was the case on two (or more) computers
already.mention Martin

[1]
http://grasswiki.osgeo.org/wiki/WinGRASS_errors#The_GRASS_GIS_.28winGRASS.29_exits_immediately_after_I_start_it.21

_______________________________________________
grass-dev mailing list

grass-dev@.osgeo

http://lists.osgeo.org/mailman/listinfo/grass-dev

are you installing winGRASS standalone with admin rights (e.g. right click
run as admin)?

can you test it with and without "run as admin" on these win machines?

can you also test at which manually step mentioned in the wiki winGRASS is
working/not working.

the OSGeo4W-package is unfortunately a moving window...

-----
best regards
Helmut
--
View this message in context: http://osgeo-org.1560.x6.nabble.com/G7-blockers-call-tp5157820p5159968.html
Sent from the Grass - Dev mailing list archive at Nabble.com.

On Wed, Sep 3, 2014 at 6:32 PM, Helmut Kudrnovsky <hellik@web.de> wrote:

wenzeslaus wrote
> On Sat, Aug 23, 2014 at 3:35 AM, Martin Landa &lt;

> landa.martin@

> &gt;
> wrote:
>
>> > So far I had two students reporting the problem with MSVCR.71.dll
>> missing - I have added the link to the
>> > WinGRASS_errors wiki to the course webpage so I hope that will help.
>>
>> Checking "Important Microsoft runtime libraries" in the installer
>> should solve this problem [1].
>>
>> I think this issue is discussed also somewhere else since I remember
> writing this somewhere already. Anyway, at least for the record, checking
> the check box does not help. Getting through the 2 other suggestion on
> wiki
> does not help either. But doing the steps from the installer manually
> works
> (the third suggestion). This was the case on two (or more) computers
> already.mention Martin
>>
>> [1]
>>
http://grasswiki.osgeo.org/wiki/WinGRASS_errors#The_GRASS_GIS_.28winGRASS.29_exits_immediately_after_I_start_it.21
>
> _______________________________________________
> grass-dev mailing list

> grass-dev@.osgeo

> http://lists.osgeo.org/mailman/listinfo/grass-dev

are you installing winGRASS standalone with admin rights (e.g. right click
run as admin)?

can you test it with and without "run as admin" on these win machines?

I remember trying both options without success.

Anna

can you also test at which manually step mentioned in the wiki winGRASS is
working/not working.

the OSGeo4W-package is unfortunately a moving window...

-----
best regards
Helmut
--
View this message in context:
http://osgeo-org.1560.x6.nabble.com/G7-blockers-call-tp5157820p5159968.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

  can you test it with and without "run as admin" on these win machines?

I remember trying both options without success.

not sure, but I suspect some permission rights issue to execute/install the
downloaded runtimes by the winGRASS-standalone installer.

-----
best regards
Helmut
--
View this message in context: http://osgeo-org.1560.x6.nabble.com/G7-blockers-call-tp5157820p5160408.html
Sent from the Grass - Dev mailing list archive at Nabble.com.

Hi all,

On 03.09.2014 23:28, Vaclav Petras wrote:

On Sat, Aug 23, 2014 at 3:35 AM, Martin Landa <landa.martin@gmail.com
<mailto:landa.martin@gmail.com>> wrote:

    > So far I had two students reporting the problem with MSVCR.71.dll
    missing - I have added the link to the
    > WinGRASS_errors wiki to the course webpage so I hope that will help.

    Checking "Important Microsoft runtime libraries" in the installer
    should solve this problem [1].

I think this issue is discussed also somewhere else since I remember
writing this somewhere already. Anyway, at least for the record,
checking the check box does not help. Getting through the 2 other
suggestion on wiki does not help either. But doing the steps from the
installer manually works (the third suggestion). This was the case on
two (or more) computers already.

I can confirm this behavior for WinGRASS-7.0.0svn-r61783-1071.
Installing with admin priviliges and checking the box for the MS runtime
environments didn't help but copying the DLLs manually to extrabin did
the trick (as suggested in [1]).

This is a "new" behavior for me - I haven't had this problem with
winGRASS before.

Cheers,

Johannes

    Martin

    [1]
    http://grasswiki.osgeo.org/wiki/WinGRASS_errors#The_GRASS_GIS_.28winGRASS.29_exits_immediately_after_I_start_it.21

But doing the steps from the
installer manually works (the third suggestion). This was the case on
two (or more) computers already.

I can confirm this behavior for WinGRASS-7.0.0svn-r61783-1071.
Installing with admin priviliges and checking the box for the MS runtime
environments didn't help but copying the DLLs manually to extrabin did
the trick (as suggested in [1]).

which windows version (7, 8)? any antivirus software?

the winGRASS standalone installer should copy the DLLs to extrabin, see

http://trac.osgeo.org/grass/browser/grass/branches/releasebranch_7_0/mswindows/GRASS-Installer.nsi.tmpl#L943

943 CopyFiles "$TEMP\$ORIGINAL_UNTAR_FOLDER\bin\*.dll"
"$INSTDIR\extrabin"

more informations and investigations are needed ...

-----
best regards
Helmut
--
View this message in context: http://osgeo-org.1560.x6.nabble.com/G7-blockers-call-tp5157820p5160427.html
Sent from the Grass - Dev mailing list archive at Nabble.com.

On Fri, Sep 5, 2014 at 4:17 PM, Helmut Kudrnovsky <hellik@web.de> wrote:

>>But doing the steps from the
>> installer manually works (the third suggestion). This was the case on
>> two (or more) computers already.

>I can confirm this behavior for WinGRASS-7.0.0svn-r61783-1071.
>Installing with admin priviliges and checking the box for the MS runtime
>environments didn't help but copying the DLLs manually to extrabin did
>the trick (as suggested in [1]).

which windows version (7, 8)? any antivirus software?

I saw the problem with both versions. I can't check the antivirus now but
that might be causing it.

the winGRASS standalone installer should copy the DLLs to extrabin, see

the dlls are not there although the installation seems to finish correctly

Anna

http://trac.osgeo.org/grass/browser/grass/branches/releasebranch_7_0/mswindows/GRASS-Installer.nsi.tmpl#L943

943 CopyFiles "$TEMP\$ORIGINAL_UNTAR_FOLDER\bin\*.dll"
"$INSTDIR\extrabin"

more informations and investigations are needed ...

-----
best regards
Helmut
--
View this message in context:
http://osgeo-org.1560.x6.nabble.com/G7-blockers-call-tp5157820p5160427.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

Hi,

On 05.09.2014 23:57, Anna Petrášová wrote:

On Fri, Sep 5, 2014 at 4:17 PM, Helmut Kudrnovsky <hellik@web.de
<mailto:hellik@web.de>> wrote:

    >>But doing the steps from the
    >> installer manually works (the third suggestion). This was the case on
    >> two (or more) computers already.

    >I can confirm this behavior for WinGRASS-7.0.0svn-r61783-1071.
    >Installing with admin priviliges and checking the box for the MS runtime
    >environments didn't help but copying the DLLs manually to extrabin did
    >the trick (as suggested in [1]).

    which windows version (7, 8)? any antivirus software?

I saw the problem with both versions. I can't check the antivirus now
but that might be causing it.

Cannot check for Windows 8, just for 7 64bit. I'm using Microsoft
Security Essentials but it makes no difference whether it's enabled or
not. No luck even with forced administrative privileges during setup
and/or runtime. Also just checked with the newest build
(WinGRASS-7.0.0svn-r61811-1073).

I've however multiple copies of msvcr71.dll installed on my system with
the one in C:\Windows\Microsoft.NET\Framework\v1.1.4322\msvcr71.dll
being most relevant I assume.

Copying them manually in extrabin still does the trick.

Cheers,

Johannes

    the winGRASS standalone installer should copy the DLLs to extrabin, see

the dlls are not there although the installation seems to finish correctly

Anna

    http://trac.osgeo.org/grass/browser/grass/branches/releasebranch_7_0/mswindows/GRASS-Installer.nsi.tmpl#L943

    943 CopyFiles "$TEMP\$ORIGINAL_UNTAR_FOLDER\bin\*.dll"
    "$INSTDIR\extrabin"

    more informations and investigations are needed ...

    -----
    best regards
    Helmut
    --
    View this message in context:
    http://osgeo-org.1560.x6.nabble.com/G7-blockers-call-tp5157820p5160427.html
    Sent from the Grass - Dev mailing list archive at Nabble.com.
    _______________________________________________
    grass-dev mailing list
    grass-dev@lists.osgeo.org <mailto:grass-dev@lists.osgeo.org>
    http://lists.osgeo.org/mailman/listinfo/grass-dev

_______________________________________________
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

Johannes Brauner wrote

Hi,

On 05.09.2014 23:57, Anna Petrášová wrote:

On Fri, Sep 5, 2014 at 4:17 PM, Helmut Kudrnovsky &lt;

hellik@

&gt; &lt;mailto:

hellik@

&gt;> wrote:

    >>But doing the steps from the
    >> installer manually works (the third suggestion). This was the case
on
    >> two (or more) computers already.

    >I can confirm this behavior for WinGRASS-7.0.0svn-r61783-1071.
    >Installing with admin priviliges and checking the box for the MS
runtime
    >environments didn't help but copying the DLLs manually to extrabin
did
    >the trick (as suggested in [1]).

    which windows version (7, 8)? any antivirus software?

I saw the problem with both versions. I can't check the antivirus now
but that might be causing it.

Cannot check for Windows 8, just for 7 64bit. I'm using Microsoft
Security Essentials but it makes no difference whether it's enabled or
not. No luck even with forced administrative privileges during setup
and/or runtime. Also just checked with the newest build
(WinGRASS-7.0.0svn-r61811-1073).

I've however multiple copies of msvcr71.dll installed on my system with
the one in C:\Windows\Microsoft.NET\Framework\v1.1.4322\msvcr71.dll
being most relevant I assume.

Copying them manually in extrabin still does the trick.

Cheers,

Johannes

thanks for reporting.

tested here with WinGRASS-7.0.0svn-r61816-1074-Setup.exe, I can confirm that
the runtime DLLs aren't copied to the extrabin folder.

if the download of the MS runtimes in the winGRASS standalone installer is
activated, the download is correctly untared and unzipped by [1] in
C:\xxxx\normal\AppData\Local\Temp\install_msruntime

then the runtime DLLs should be copied to the extrabin folder by [2]:

CopyFiles "$TEMP\$ORIGINAL_UNTAR_FOLDER\bin\*.dll" "$INSTDIR\extrabin"

but they aren't.

from the nsis documentation (http://nsis.sourceforge.net/Docs/Chapter4.html)

"4.9.3.2 CopyFiles

[/SILENT] [/FILESONLY] filespec_on_destsys destination_path
[size_of_files_in_kb]

Copies files from the source to the destination on the installing system.
Useful with $EXEDIR if you want to copy from installation media, or to copy
from one place to another on the system. You might see a Windows status
window of the copy operation if the operation takes a lot of time (to
disable this, use /SILENT). The last parameter can be used to specify the
size of the files that will be copied (in kilobytes), so that the installer
can approximate the disk space requirements. On error, or if the user
cancels the copy (only possible when /SILENT was omitted), the error flag is
set. If /FILESONLY is specified, only files are copied.

Fully-qualified path names should always be used with this instruction.
Using relative paths will have unpredictable results.

CreateDirectory $INSTDIR\backup
CopyFiles $INSTDIR\*.dat $INSTDIR\backup"

so I can't see any obvious why file copying doesn't work...

anyone any idea?

[1]
http://trac.osgeo.org/grass/browser/grass/branches/releasebranch_7_0/mswindows/GRASS-Installer.nsi.tmpl#L935

[2]
http://trac.osgeo.org/grass/browser/grass/branches/releasebranch_7_0/mswindows/GRASS-Installer.nsi.tmpl#L943

-----
best regards
Helmut
--
View this message in context: http://osgeo-org.1560.x6.nabble.com/G7-blockers-call-tp5157820p5160573.html
Sent from the Grass - Dev mailing list archive at Nabble.com.

then the runtime DLLs should be copied to the extrabin folder by [2]:

CopyFiles "$TEMP\$ORIGINAL_UNTAR_FOLDER\bin\*.dll" "$INSTDIR\extrabin"

[...]

CreateDirectory $INSTDIR\backup

CopyFiles $INSTDIR\*.dat $INSTDIR\backup

it could be the quoting "$TEMP\$ORIGINAL_UNTAR_FOLDER\bin\*.dll" and using
wildcards for the files that is causing that file copying fails.

-----
best regards
Helmut
--
View this message in context: http://osgeo-org.1560.x6.nabble.com/G7-blockers-call-tp5157820p5160574.html
Sent from the Grass - Dev mailing list archive at Nabble.com.

Helmut Kudrnovsky wrote

then the runtime DLLs should be copied to the extrabin folder by [2]:

CopyFiles "$TEMP\$ORIGINAL_UNTAR_FOLDER\bin\*.dll" "$INSTDIR\extrabin"

[...]

CreateDirectory $INSTDIR\backup

CopyFiles $INSTDIR\*.dat $INSTDIR\backup

it could be the quoting "$TEMP\$ORIGINAL_UNTAR_FOLDER\bin\*.dll" and using
wildcards for the files that is causing that file copying fails.

I think I've found the reason causing some troubles with installing MS
runtimes, see:

http://forums.winamp.com/showthread.php?t=379253

------------------------------------------------------------
I think I've narrowed down the issue a little bit more:

in the nsis-script [1] there's the section [2] with the optional download of
these gzipped and tared files which, after unzpping and untaring, should be
copied to C:\Program Files\myprogram\subfolder.

this section calls [3] the function [4] which download [5] and unzip/untar
[6] the archive and then copies some files [7].

now for more testing, I've added some copying commands as the first action
of the nsis-installer:

    code: ;test copy files

      CreateDirectory "$INSTALL_DIR\extrabin"

      CopyFiles "C:\wd\checkdllnsis\*.dll" "$INSTALL_DIR\extrabin"

      CopyFiles "C:\wd\checkdllnsis\*.txt" "$INSTALL_DIR\extrabin"

      CopyFiles "C:\wd\checkdllnsis\*.exe" "$INSTALL_DIR\extrabin"

      CopyFiles "C:\wd\checkdllnsis\*.dll" "C:\wd\checkdllnsis\copiedf"

      CopyFiles "C:\wd\checkdllnsis\*.txt" "C:\wd\checkdllnsis\copiedf"

      CopyFiles "C:\wd\checkdllnsis\*.exe" "C:\wd\checkdllnsis\copiedf"

and all of these test files are copied.

as summary, CopyFiles doesn't seem to work, if the command is nested in a
function called in a section; but CopyFiles works, if it is in the main nsis
script and not nested in function.

intended behaviour? bug? ... should this be reported anywhere?

best
Helmut

[1] http://trac.osgeo.org/grass/browser/...aller.nsi.tmpl
[2] http://trac.osgeo.org/grass/browser/....nsi.tmpl#L966
[3] http://trac.osgeo.org/grass/browser/....nsi.tmpl#L979
[4] http://trac.osgeo.org/grass/browser/....nsi.tmpl#L900
[5] http://trac.osgeo.org/grass/browser/....nsi.tmpl#L929
[6] http://trac.osgeo.org/grass/browser/....nsi.tmpl#L935
[7] http://trac.osgeo.org/grass/browser/....nsi.tmpl#L943
------------------------------------------------------------

the solution will may be to cut download and install of the MS runtimes in
two different actions by the nsis-winGRASS-installer.

-----
best regards
Helmut
--
View this message in context: http://osgeo-org.1560.x6.nabble.com/G7-blockers-call-tp5157820p5161666.html
Sent from the Grass - Dev mailing list archive at Nabble.com.

Hi Anna,

Anna Petrášová wrote

On Fri, Sep 5, 2014 at 4:17 PM, Helmut Kudrnovsky &lt;

hellik@

&gt; wrote:

>>But doing the steps from the
>> installer manually works (the third suggestion). This was the case on
>> two (or more) computers already.

>I can confirm this behavior for WinGRASS-7.0.0svn-r61783-1071.
>Installing with admin priviliges and checking the box for the MS runtime
>environments didn't help but copying the DLLs manually to extrabin did
>the trick (as suggested in [1]).

which windows version (7, 8)? any antivirus software?

I saw the problem with both versions. I can't check the antivirus now but
that might be causing it.

the winGRASS standalone installer should copy the DLLs to extrabin, see

the dlls are not there although the installation seems to finish correctly

Anna

by r61832, r61843, r61911, r61951, r62082 I've tried to attempt to fix
installing and copying MS runtime files.

at least here on my windows box, where installing and copying MS runtimes
files previously failed, the windows standalone installer does now the job.

any chance to test standalone winGRASS7.1
(http://wingrass.fsv.cvut.cz/grass71/) above r62082?

-----
best regards
Helmut
--
View this message in context: http://osgeo-org.1560.x6.nabble.com/G7-blockers-call-tp5157820p5164138.html
Sent from the Grass - Dev mailing list archive at Nabble.com.

Johannes Brauner wrote

Hi,

On 05.09.2014 23:57, Anna Petrášová wrote:

On Fri, Sep 5, 2014 at 4:17 PM, Helmut Kudrnovsky &lt;

hellik@

&gt; &lt;mailto:

hellik@

&gt;> wrote:

    >>But doing the steps from the
    >> installer manually works (the third suggestion). This was the case
on
    >> two (or more) computers already.

    >I can confirm this behavior for WinGRASS-7.0.0svn-r61783-1071.
    >Installing with admin priviliges and checking the box for the MS
runtime
    >environments didn't help but copying the DLLs manually to extrabin
did
    >the trick (as suggested in [1]).

    which windows version (7, 8)? any antivirus software?

I saw the problem with both versions. I can't check the antivirus now
but that might be causing it.

Cannot check for Windows 8, just for 7 64bit. I'm using Microsoft
Security Essentials but it makes no difference whether it's enabled or
not. No luck even with forced administrative privileges during setup
and/or runtime. Also just checked with the newest build
(WinGRASS-7.0.0svn-r61811-1073).

I've however multiple copies of msvcr71.dll installed on my system with
the one in C:\Windows\Microsoft.NET\Framework\v1.1.4322\msvcr71.dll
being most relevant I assume.

Copying them manually in extrabin still does the trick.

Cheers,

Johannes

any chance to test standalone winGRASS7.1
(http://wingrass.fsv.cvut.cz/grass71/) above r62082?

-----
best regards
Helmut
--
View this message in context: http://osgeo-org.1560.x6.nabble.com/G7-blockers-call-tp5157820p5164141.html
Sent from the Grass - Dev mailing list archive at Nabble.com.

On Thu, Sep 25, 2014 at 9:30 AM, Helmut Kudrnovsky <hellik@web.de> wrote:

Hi Anna,

Anna Petrášová wrote
> On Fri, Sep 5, 2014 at 4:17 PM, Helmut Kudrnovsky &lt;

> hellik@

> &gt; wrote:
>
>> >>But doing the steps from the
>> >> installer manually works (the third suggestion). This was the case on
>> >> two (or more) computers already.
>>
>> >I can confirm this behavior for WinGRASS-7.0.0svn-r61783-1071.
>> >Installing with admin priviliges and checking the box for the MS
runtime
>> >environments didn't help but copying the DLLs manually to extrabin did
>> >the trick (as suggested in [1]).
>>
>> which windows version (7, 8)? any antivirus software?
>>
>>
> I saw the problem with both versions. I can't check the antivirus now but
> that might be causing it.
>
>> the winGRASS standalone installer should copy the DLLs to extrabin, see
>>
>
> the dlls are not there although the installation seems to finish
correctly
>
> Anna

by r61832, r61843, r61911, r61951, r62082 I've tried to attempt to fix
installing and copying MS runtime files.

at least here on my windows box, where installing and copying MS runtimes
files previously failed, the windows standalone installer does now the job.

any chance to test standalone winGRASS7.1
(http://wingrass.fsv.cvut.cz/grass71/) above r62082?

Great, I will try tomorrow. I need to ask someone to try it, on the
computers I have access to, it was working before. Have you identified the
problem or are you still guessing?

Thanks!

-----
best regards
Helmut
--
View this message in context:
http://osgeo-org.1560.x6.nabble.com/G7-blockers-call-tp5157820p5164138.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

hi,

Great, I will try tomorrow. I need to ask someone to try it, on the

computers I have access to, it was

working before.

Are you sure that it has ever worked? Download, unzip and untar the archive
was working, regarding installing and copying I'm not sure ...

Have you identified the problem or are you still guessing?

I've changed the logic order in the script.

-----
best regards
Helmut
--
View this message in context: http://osgeo-org.1560.x6.nabble.com/G7-blockers-call-tp5157820p5164149.html
Sent from the Grass - Dev mailing list archive at Nabble.com.

On Thu, Sep 25, 2014 at 9:59 AM, Helmut Kudrnovsky <hellik@web.de> wrote:

hi,

>Great, I will try tomorrow. I need to ask someone to try it, on the
computers I have access to, it was
>working before.

Are you sure that it has ever worked? Download, unzip and untar the archive
was working, regarding installing and copying I'm not sure ...

Sure, it was and is still working on certain computers when I check it in
the wizard.

I was wondering if the fontconfig problem I asked earlier could be somehow
related. You haven't probably experienced this problem. I will see after
the testing.

>Have you identified the problem or are you still guessing?

I've changed the logic order in the script.

-----
best regards
Helmut
--
View this message in context:
http://osgeo-org.1560.x6.nabble.com/G7-blockers-call-tp5157820p5164149.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

Hi Helmut,

On 25.09.2014 15:35, Helmut Kudrnovsky wrote:

Johannes Brauner wrote

Hi,

On 05.09.2014 23:57, Anna Petrášová wrote:

On Fri, Sep 5, 2014 at 4:17 PM, Helmut Kudrnovsky &lt;

hellik@

&gt; &lt;mailto:

hellik@

&gt;> wrote:

    >>But doing the steps from the
    >> installer manually works (the third suggestion). This was the case
on
    >> two (or more) computers already.

    >I can confirm this behavior for WinGRASS-7.0.0svn-r61783-1071.
    >Installing with admin priviliges and checking the box for the MS
runtime
    >environments didn't help but copying the DLLs manually to extrabin
did
    >the trick (as suggested in [1]).

    which windows version (7, 8)? any antivirus software?

I saw the problem with both versions. I can't check the antivirus now
but that might be causing it.

Cannot check for Windows 8, just for 7 64bit. I'm using Microsoft
Security Essentials but it makes no difference whether it's enabled or
not. No luck even with forced administrative privileges during setup
and/or runtime. Also just checked with the newest build
(WinGRASS-7.0.0svn-r61811-1073).

I've however multiple copies of msvcr71.dll installed on my system with
the one in C:\Windows\Microsoft.NET\Framework\v1.1.4322\msvcr71.dll
being most relevant I assume.

Copying them manually in extrabin still does the trick.

Cheers,

Johannes

any chance to test standalone winGRASS7.1
(http://wingrass.fsv.cvut.cz/grass71/) above r62082?

installation (including opting for downloading the MS runtimes) and
start of winGRASS 7.1 (WinGRASS-7.1.svn-r62087-1088-Setup) worked like a
charm.

Thanks for fixing it.

Cheers,

Johannes

--
Geoinformation Systems - Technische Universität Dresden, Germany