Thanks for the suggestion. I just gave it a try. However, if I put
fossil in SysWOW64, cmd.exe fails to find it at all.
Kind regards,
Philip Bennefall
On 2014-06-11 15:39, Jan Nijtmans wrote:
2014-06-11 15:31 GMT+02:00 Philip Bennefall <phi...@blastbay.com>:
I am not sure if this should be considered an issue with Fossil or Windows
itself, but if I put fossil.exe in a path such as C:\Windows\system32 in
order for it to be found whenever I type fossil in a command prompt, it
fails whenever it tries to fork. It works fine to invoke it when running
commands such as open, commit etc, but try running a command like ui and the
problem appears. The reason I am expecting it to work is because fossil.exe
is in fact in a directory stored in the path environment variable.
Again, not sure if this is really a Fossil issue but I wanted to run it by
you just in case.
No, this is not a fossil issue. The directory C:\Windows\system32 is meant
for 64-bit executables if you are on a 64-bit Windows system, but fossil
is a 32-bit executable. The C:\Windows\system32 directory is
invisible to 32-bit applications. You should place fossil.exe in
C:\Windows\SysWOW64 in stead, then it should work.
Regards,
Jan Nijtmans
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
