id,summary,reporter,owner,description,type,status,priority,milestone,component,version,resolution,keywords,cc,cpu,platform 2213,Windows startup broken,jbrauner,grass-dev@…,"Hi GRASS developers, I downloaded and installed the weekly snapshot today (built on the revision 59215) and was provided with the following error message during startup: ""ERROR: GRASS GIS seems to be already running. Exiting."" I digged a little bit and found that since the very recent 59210 revision, the following statement: if 'GISBASE' in os.environ: sys.exit(_(""ERROR: GRASS GIS seems to be already running. Exiting."")) (see http://trac.osgeo.org/grass/browser/grass/trunk/lib/init/grass.py?rev=59210#L1227) breaks the successful start under Windows (both winGRASS weekly build and osgeo4w). Possible reason: For the winGRASS install, the GISBASE env variable is set by the grass70svn.bat (which I think is created here: http://trac.osgeo.org/grass/browser/grass/trunk/mswindows/GRASS-Installer.nsi.tmpl) which sets this variable for Windows before calling the Python startup script. Thus, startup always has to fail. Commenting the if clause out in the Python script did the trick for a successful start (I believe the if clause was introduced for a reason though ;-)). For the osgeo4w install, the GISBASE env variable is set by the env.bat (which I think is created here: http://trac.osgeo.org/grass/browser/grass/trunk/mswindows/osgeo4w/env.bat.tmpl) which sets this variable for Windows before calling the Python startup script. Thus, startup always has to fail. Commenting the if clause out in the Python script did the trick for a successful start (I believe the if clause was introduced for a reason though ;-)). Please let me know if I can help any further. Cheers and keep up the good work, Johannes ",defect,closed,major,7.0.0,Startup,svn-trunk,fixed,,jbrauner,Unspecified,MSWindows 7