#759: r.patch non-functional in WinGRASS 6.4 svn on Vista ------------------------------+--------------------------------------------- Reporter: cmbarton | Owner: [email protected] 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 hellik):
Replying to [comment:13 glynn]: > Replying to [comment:12 hamish]: > > > sigh. what a complete pile of poo. > > +1 +1 > > For the record, I'll include a copy of the referenced MSDN article: > > [http://msdn.microsoft.com/en-us/library/aa905330.aspx] > > Someone who cares about Windows (my "caring about Windows" level just dropped by a large margin after finding out about this) might want to look into how to create a "manifest" and whether this actually solves the problem. > > Also: > > 1. Is this caused (in whole or in part) by GRASS being installed somewhere other than the "Program Files" directory? If it is, then I care even less. If there are still problems with spaces in $GISBASE, we should fix them, rather than expecting GRASS to be installed somewhere else. 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. > > 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. 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? Helmut -- Ticket URL: <http://trac.osgeo.org/grass/ticket/759#comment:15> GRASS GIS <http://grass.osgeo.org>
_______________________________________________ grass-dev mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/grass-dev
