1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Take Command / TCMD/LE 9.02.156 uploaded

Discussion in 'Support' started by rconn, Apr 25, 2009.

  1. rconn

    rconn Administrator
    Staff Member

    Joined:
    May 14, 2008
    Messages:
    9,732
    Likes Received:
    81
    For those of you who haven't upgraded to v10 yet, I've uploaded build 156 of Take Command 9.02 to the web and ftp sites.

    * Fixed a Windows API bug that sometimes caused ^Break to exit TCMD

    * Fixed a compatibility problem with some console apps not receiving ^C

    * Fixed a problem with filename completion from the path crashing if you have an extremely large number of matching files
     
  2. Matt

    Joined:
    Jan 15, 2009
    Messages:
    16
    Likes Received:
    0
    This version doesn't seem to install correctly, stating perl510 is missing. Them it doesn't seem to remove correctly (from the control panel) so it won't let me reinstall build 154 stating a newer version is currently installed. Any ideas on how I can get build 154 re-installed?


     
  3. rconn

    rconn Administrator
    Staff Member

    Joined:
    May 14, 2008
    Messages:
    9,732
    Likes Received:
    81
    Matt wrote:

    Either turn off Perl support in your TCMD.INI or install Perl 5.10.

    I can't reproduce the problem with removing it from the control panel.
    (That would be a Windows bug rather than a TCMD issue.)

    I've reuploaded 9.02 linked with Perl 5.8.

    Rex Conn
    JP Software
     
  4. Matt

    Joined:
    Jan 15, 2009
    Messages:
    16
    Likes Received:
    0
    I guess I should have been more explicit. Windows XP (SP3). I downloaded and installed Activestate Perl 510.
    Then installed build 156, so it seems to work now.

    What I meant before is that removing via the control panel worked but when I tried to install build 154 it said a newer version was already installed. So, to me, uninstalling via the control panel did not work because your installation program looked for and found (where ?) a reference of some kind to build 156 so it would not install 154. How did we get to this point with such a technical product that it refuses to install even though that's what I wanted and what I told it to do? I guess it knows better than me what I want to (or should) do. You should have announced that you finally figured out an implementation of your mind reading parser (installer) that you've mentioned over the years.

    Matt


     
  5. rconn

    rconn Administrator
    Staff Member

    Joined:
    May 14, 2008
    Messages:
    9,732
    Likes Received:
    81
    Matt wrote:


    That's normal Windows Installer behavior. It's possible to change that
    so that any version will overwrite any other, but that would also mean
    that autoupdate would no longer work.

    Rex Conn
    JP Software
     

Share This Page