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 / TCC/LE 10.0 build 64 uploaded

Discussion in 'Support' started by rconn, Mar 31, 2009.

  1. rconn

    rconn Administrator
    Staff Member

    Joined:
    May 14, 2008
    Messages:
    9,868
    Likes Received:
    83
    I've uploaded 10.0.64 to the web and ftp sites.

    * The binary functions now support hex values (with a leading 0x) for their offset and length values

    * RD /S - fixed a problem with quoted directory names
     
  2. dim

    dim Dimitry Andric

    Joined:
    May 31, 2008
    Messages:
    203
    Likes Received:
    0
    Confirmed fixed; RD /S now works fine again. Thanks :)
     
  3. dcantor

    Joined:
    May 29, 2008
    Messages:
    507
    Likes Received:
    3
    Thank you. That saves me a few %@EVAL[] calls.
     
  4. dcantor

    Joined:
    May 29, 2008
    Messages:
    507
    Likes Received:
    3
    I spoke too soon. This terminates with an error
    "The application failed to initialize properly (0xc0000022)."
    This happens both with TC and TCC.

    It's the same AVG error that I reported months ago with a previous build.

    I told AVG to ignore the directory, and it seems to be running okay.

    Rex, I already know you can't do anything about it -- I'm posting this here so that others are aware of it.

    However, I look forward to the next build so that I can remove the exception from AVG's processing.
     
  5. Jay Sage

    Joined:
    Jun 2, 2008
    Messages:
    284
    Likes Received:
    1
    > It's the same AVG error that I reported months ago
    > with a previous build.

    I've had so many problems with AVG (even after several rounds with their
    tech support) that I decided to just dump it. I have experienced orders
    of magnitude more problems because of anti-virus software than I ever
    have with viruses!

    One of the problem was that I could not get it to ignore the problem
    with several of the TCMD builds, and so I kept having to go back to an
    earier build (or to TCMD9 until a TCMD10 build came out that did not
    have the problem).

    -- Jay
     
  6. dcantor

    Joined:
    May 29, 2008
    Messages:
    507
    Likes Received:
    3
    You don't have to so far as to revert to an earlier build of TCMD. You can tell AVG to ignore the contents of the TCMD installation directory:

    From the AVG control windows, click Resident Shield, then Manage Exceptions, then add the TCMD installation directory path using Add Path.
     
  7. Steve Fabian

    Joined:
    May 20, 2008
    Messages:
    3,520
    Likes Received:
    4
    dcantor wrote:
    | ---Quote (Originally by Jay Sage)---
    || It's the same AVG error that I reported months ago
    || with a previous build.
    |
    | I've had so many problems with AVG (even after several rounds with
    | their
    | tech support) that I decided to just dump it. I have experienced
    | orders
    | of magnitude more problems because of anti-virus software than I ever
    | have with viruses!
    |
    | One of the problem was that I could not get it to ignore the problem
    | with several of the TCMD builds, and so I kept having to go back to an
    | earier build (or to TCMD9 until a TCMD10 build came out that did not
    | have the problem).
    | ---End Quote---
    | You don't have to so far as to revert to an earlier build of TCMD.
    | You can tell AVG to ignore the contents of the TCMD installation
    | directory:
    |
    | From the AVG control windows, click Resident Shield, then Manage
    | Exceptions, then add the TCMD installation directory path using Add
    | Path.

    I did that some time ago, and had no further trouble reports. B64 works fine
    in that directory, too. I do agree that AVG should revamp their detection
    logic, so that we could resume real virus checking in the TCMD directory...
    --
    Steve
     

Share This Page