Replying to [comment:16 hellik]:
> IMHO "right click and ''run as administrator''" for installing a
software in WinVista/Win7 is the "normal" way to install software on the
Windows-box (i have to do this on all WinVista/Win7-out-of-the-box-
machines, that i know, and for all kind of softwares (opensource and
proprietary) and often noted in README-files etc. for the software).
>
> Helmut
It doesn't matter what is considered a "normal way". If installator fails
to create direcotry for file extraction, then there is no reason why to
continue and not fail with error message. It doesn't matter what is the
root of failure (insufficent rights, read-only file system, disk full
etc.). Still hint about "run as admin" or "check free disk space" would be
nice.
Replying to [comment:17 helena]:
> I just got a report that when GRASS is installed under C:\Program Files
> "Add vector" causes python.exe to crash for WinGRASS64 r41105 and
WinGRASS65 r41099.
> [[BR]]
>
> There is no problem if it is installed under C:\Grass64.
> The feedback that I am getting from WinGRASS users here is that they
prefer GRASS installed under
> its own directory, such as C:\Grass64.
> I have no opinion on this as I am not a Windows user and I can imagine
that the preferences
> would differ for users with different backgrounds, but maybe the
previous approach under C:\GRASS... was less problematic?[[BR]]
>
> Helena
is this still valid with the actual nightly builds of wingrass?
Replying to [comment:21 hellik]:
> Replying to [comment:17 helena]:
> > I just got a report that when GRASS is installed under C:\Program
Files
> > "Add vector" causes python.exe to crash for WinGRASS64 r41105 and
WinGRASS65 r41099.
> > [[BR]]
> >
> > There is no problem if it is installed under C:\Grass64.
> > The feedback that I am getting from WinGRASS users here is that they
prefer GRASS installed under
> > its own directory, such as C:\Grass64.
> > I have no opinion on this as I am not a Windows user and I can imagine
that the preferences
> > would differ for users with different backgrounds, but maybe the
previous approach under C:\GRASS... was less problematic?[[BR]]
> >
> > Helena
>
> is this still valid with the actual nightly builds of wingrass?
>
> Helmut
before closing the ticket, can someone with a non-english copy of Windows,
which puts a space in the translation of "C:\Program Files", try
installing there? does it work ok now?
Replying to [comment:23 hamish]:
> before closing the ticket, can someone with a non-english copy of
Windows, which puts a space in the translation of "C:\Program Files", try
installing there? does it work ok now?
>
>
> Hamish
in a german win7-box, AFAIK c:\Programme is only an alias for C:\Program
Files.
as i remember correctly, this ticket was an issue with the windows-UAC.
I've changed then the behaviour of the wingrass-installer that the
windows-UAC-user interaction starts automatically.
Apologies to the Windows dev folks for not posting these earlier. Here are the links to the Federal Desktop Core Configuration guidelines ( mandatory for US federal government computers using Windows XP and Vista. I think Win 7 is still in the pipe ) for secure desktop computing.
Main things to remember, 1) application does not require administrative access to run. 2) application does not use system directories( i.e. Windows or Program Files) for user data/ temp files.
The opinions I express are my own and are not representative of the official policy of the U.S.Fish and Wildlife Service or Dept. of the Interior. Life is too short for undocumented, proprietary data formats.
Replying to [comment:24 hellik]:
> Replying to [comment:23 hamish]:
> > before closing the ticket, can someone with a non-english copy of
Windows, which puts a space in the translation of "C:\Program Files", try
installing there? does it work ok now?
> >
> >
> > Hamish
>
> in a german win7-box, AFAIK c:\Programme is only an alias for C:\Program
Files.
>
> as i remember correctly, this ticket was an issue with the windows-UAC.
I've changed then the behaviour of the wingrass-installer that the
windows-UAC-user interaction starts automatically.
>
> best regards
> Helmut