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

TCC 10.0.0.57: Crash on launch in Secur32.dll

Discussion in 'Support' started by Spire, Mar 1, 2009.

  1. Spire

    Joined:
    Jun 20, 2008
    Messages:
    2
    Likes Received:
    0
    I've just installed the trial version of Take Command 10.0.0.57 under Windows Vista Home Premium (32-bit), and every time I try to start TCC I get the following crash:
    There is no TCC.INI file.

    Is this a known problem? What can I do to get it working?
     
  2. rconn

    rconn Administrator
    Staff Member

    Joined:
    May 14, 2008
    Messages:
    9,870
    Likes Received:
    83
    Spire wrote:

    It's not a TCC problem. TCC doesn't load secur32.dll, so it's being
    loaded by something else and injected into TCC's address space (probably
    an antivirus app or a video / desktop manager).

    A quick Google search shows lots of identical secur32.dll errors with
    other apps; a common cause seems to be the Google Toolbar and/or
    Desktop. If you're running one of those, try disabling it and see if
    TCC.EXE loads successfully.

    (There would never be a TCC.INI file, but there should be a TCMD.INI
    file, unless you don't have write access to your disk.)

    Rex Conn
    JP Software
     
  3. Spire

    Joined:
    Jun 20, 2008
    Messages:
    2
    Likes Received:
    0
    After some trial and error, I've discovered what triggers the crash: It's when TCC is launched by AutoHotkey via a keyboard shortcut.

    AutoHotkey is an open-source utility that allows one to write simple or complex automation scripts that can be executed by pressing keyboard shortcuts.

    I have a simple script that launches TCC when I press Win+4. (Why "4"? I wrote it many years ago, back when TCC was called 4NT.) It's when I launch TCC via this script that I get the instant crash in Secur32.dll; when I launch TCC normally (via the Windows Start menu), it works just fine.

    What I'm wondering is why out of the many programs I launch via AutoHotkey -- including many past versions of TCC and 4NT -- this new version of TCC is the only one what triggers this crash.

    I plan to ask about this on the AutoHotkey forum as well, but I'm wondering if you can offer any ideas as to why this has suddenly started happening.
     
  4. rconn

    rconn Administrator
    Staff Member

    Joined:
    May 14, 2008
    Messages:
    9,870
    Likes Received:
    83
    Spire wrote:

    No idea -- since TCC isn't crashing (secur32.dll is) nor is it calling
    secur32.dll in the first place, I don't have much to go on.

    Do you get a TCC.GPF file after the crash? If you do, send that to me;
    it might point to *why* secur32.dll is being called. (If not, the crash
    would be happening in secur32.dl when it was loaded by the Windows
    loader, and before any of the TCC.EXE code is executed.)
     

Share This Page