All I know is that "system32" is the default
"go-to" path for many 32-bit programs. It seems to
me that many applications are hard-linked to that
directory. If you have any such candidate in your
toolchain, then "system32", and thus "SysWoW64",
are "sucked" into your PATH, whether you like it
or no
Hi,
here is some minor issue on MS Windows, did somebody experienced something
like the following?
GRASS was not starting for one student on MS Windows. The reported error
was that it cannot find some symbol/procedure in sqlite3.dll. The problem
was possible to workaround by finding another sqlit
