By registering with us, you'll be able to discuss, share and private message with other members of our community.
SignUp Now!I'm not sure what the issue is - when I go away for a while and come back, it's locked up (completely unresponsive and I have to kill it typically leaving a vew orphaned TCC.exes).
I've gone back to V10 (which luckily stayed installed even though I told it to uninstall).
What version and build of TCMD/LE, and what version of Windows?
> Take Command LE v12.00.25
> Windows 7 Professional
Build 25 is a (now expired) beta build; you should update that immediately.
Rex Conn
JP Software
Afaik the le version is free and unsupported
Sent from my Droid Incredible Verizon Wireless phone
----- Reply message -----
From: "skipaugur" <>
Date: Mon, Nov 15, 2010 2:58 pm
Subject: [Support-t-2427] Re: Take Command LE (32 bit) locking up several times a day
To: <[email protected]>
---Quote (Originally by rconn)---
Build 25 is a (now expired) beta build; you should update that immediately.
Rex Conn
JP Software
---End Quote---
I installed .35, uninstalling .25 first. It's now locked up again. I wasn't actually doing anything, I just set a few environment variables and went to lunch.
Process Explorer says: State: Wait:UserRequest (don't know if that's at all helpful).
Process Explorer says: State: Wait:UserRequest (don't know if that's at all helpful).
Not particularly, except that it's hanging inside Windows, not TCMD/LE.
Can you send me your TCMD.INI?
I'm not sure what the issue is - when I go away for a while and come back, it's locked up (completely unresponsive and I have to kill it typically leaving a vew orphaned TCC.exes).
I was *JUST* about to post a similar report!
I am running TCMD 12 64-bit edition (latest build) on Windows 7 Pro 64-bit. I had the TCMD window open, went out to get lunch, came back about 20 minutes later and the program had locked up (empty WINDOW, non-responsive). I have seen this same problem several times, only when TCMD is left open. My screen blanker (built into Windows) had kicked in, but I'm not sure if that has any bearing on the problem.
I never saw anything like this with TCMD11.
Try deleting & recreating your TCMD.INI -- the people who've reported this previously say the problem (apparently) went away with a fresh TCMD.INI.