[GRASS-dev] Re: [GRASS GIS] #759: r.patch non-functional in WinGRASS 6.4 svn on Vista

GRASS GIS trac at osgeo.org
Sat Jan 9 19:30:59 EST 2010


#759: r.patch non-functional in WinGRASS 6.4 svn on Vista
------------------------------+---------------------------------------------
  Reporter:  cmbarton         |       Owner:  grass-dev at lists.osgeo.org
      Type:  defect           |      Status:  new                      
  Priority:  critical         |   Milestone:  6.4.0                    
 Component:  Raster           |     Version:  6.4.0 RCs                
Resolution:                   |    Keywords:  r.patch, wingrass        
  Platform:  MSWindows Vista  |         Cpu:  Unspecified              
------------------------------+---------------------------------------------
Comment (by glynn):

 Replying to [comment:15 hellik]:

 > in my case (i don't anything about the original report), i don't install
 the WinGrass-installer, i'm building WinGrass in the osgeo4w-stack which
 is installed in C:\OSGeo4W. this path is proposed by the osgeo4w-
 installer.

 I'm inclined to say "take this up with the OSGeo4W people". I don't think
 that anyone here is in a position to change what's in the OSGeo4W
 installer.

 > > 2. Is this relevant:
 {{{
 Note   The "User Account Control: Detect application installations and
 prompt for
 elevation" setting must be enabled for installer detection to detect
 installation
 programs. This setting is enabled by default and can be configured using
 the
 Security Policy Manager snap-in (secpol.msc) or with Group Policy
 (gpedit.msc).
 }}}
 > > I.e. if you disable that setting, does the problem go away?
 > >
 > > If it does, then "problem solved", IMNSHO.
 >
 > i've disabled this option, but there is no difference, the problem
 resists.

 In that case, the error isn't what I initially assumed.

 > the actual WinGrass-Installer proposes to install WinGrass to c:\Grass.
 So maybe, like mentionend in the ms-document that c:\Program Files is a
 "safe" site, the WinGrass-Installer should be changed to install the
 application into c:\Program Files\Grass to exclude this possible source of
 problems? Maybe this should be tested before Grass64-release?

 Apart from issues related to UAC, we shouldn't be assuming that the person
 installing GRASS has "Create Folder" access on "C:\". Typically, members
 of the "Power Users" group have "Create Folder" access for the
 `%ProgramFiles%` directory, which allows them to install normal
 applications, but anything beyond that may require Administrator status
 (and on a network, most users typically don't have Administrator status).

-- 
Ticket URL: <http://trac.osgeo.org/grass/ticket/759#comment:17>
GRASS GIS <http://grass.osgeo.org>


More information about the grass-dev mailing list