Hi Hal Mahaffey,
>When I run the latest WinCVS's (1.1, build 7, 8, and 9), it comes up with
>this message in the command-line window:
>
> TCL is *not* available, shell is disabled
>
>When I run WinCVS 1.06, it finds Tcl just fine.
>
>I've installed Tcl 8.3.0 to no effect.
Try to use TCL 8.2 - it works.
>I notice that WinCVS 1.0.6 has a "tcl81.dll" file in it that none of the
>later versions do. When I copy the tcl81.dll file into the WinCVS 1.1
>directories, it finds it. But NOT when I copy the tcl83.dll in.
>
>If WinCVS requires tcl81.dll to be that directory, why isn't it
>distributed?
I find it odd that TCL is changing their dll names like that. That is not
really WinCvs issue - that looks to me like a TCL design flaw. The name
should not change unless there is a major difference between versions (which
I don't think is the case here). I don't think that WinCvs should distribute
the TCL dll's, TCL is an external and separate product.
BR,
Jerzy
The first thing they don't teach you at school: "Never say never".
All the issues not related to the list please send to me in private, thanks.
______________________________________________________
Get Your Private, Free Email at http://www.hotmail.com
