[GRASS-dev] [GRASS GIS] #1891: wingrass: background dosbox from regular wxgui startup
GRASS GIS
trac at osgeo.org
Sat May 4 16:47:37 PDT 2013
#1891: wingrass: background dosbox from regular wxgui startup
----------------------+-----------------------------------------------------
Reporter: hamish | Owner: grass-dev@…
Type: defect | Status: new
Priority: blocker | Milestone: 6.4.3
Component: Default | Version: svn-releasebranch64
Keywords: wingrass | Platform: MSWindows 7
Cpu: x86-64 |
----------------------+-----------------------------------------------------
Comment(by hamish):
Replying to [comment:35 neteler]:
> The current nightly winGRASS 6.4.3svn no longer starts:
>
> * wx GUI start broken- flash of dosbox only
> * old tcltk start broken - nothing happens
> * cmd mode start broken - nothing happens
>
> Only the MSYS start is functional. I don't know if this is the right
> ticket but it is BAD to break everything in after RC3.
the three you see not working start with init.bat; the msys startup is
different, it uses like 'msys.bat -c init.sh' (not exactly that, but in
effect).
I've just tried again on XP with the r56101 nightly pkg build of 6.4.3svn,
everything works fine for me.
- ''did you select the box for installing "Important Microsoft runtime
dll's"''? (again, if not selected I suspect we need an extra warning
installer page with [<Back<] [>Forward>] buttons to give the user a
second opportunity to select it)
- can you recreate from the command line to see the error message? right-
click on the menu item, look at the properties to get startup dir and
command name, open a dosbox, cd into the startup dir and paste in the
startup command.
- the only recent change to relbr64's init.bat is r56104. (which works
fine for me, and should not affect the wxGUI startup at all, so I'm
doubtful it's the cause)
or maybe there is some other dll missing. You're not using some exotic
C:\Program Files\ or Docs & Settings install location?
Helmut wrote:
> [can't test standalone cause of a nasty dll hell - aka interfering
installed
> python vs. bundled python]
at install time or run time? You should be able to change GRASS_PYTHON to
the exact c:\path\python.exe you want to use in %GISBASE%/etc/env.bat.
Hamish
--
Ticket URL: <https://trac.osgeo.org/grass/ticket/1891#comment:38>
GRASS GIS <http://grass.osgeo.org>
More information about the grass-dev
mailing list