WAD Latest TCMD won't start.

May 20, 2008
11,288
95
Syracuse, NY, USA
I haven't started TCMD in a while, maybe a couple of updates. The recent one won't start here (even with no INI, START, or EXIT files). I get "TakeCommand has stopped working" (details below) and no GPF file. I tried XP-compatibility and it got a little further the first time (asking if it was OK to write to the registry) ... then it crashed similarly.

Code:
Problem signature:
  Problem Event Name:    APPCRASH
  Application Name:    tcmd.exe
  Application Version:    14.0.2.36
  Application Timestamp:    503ed28a
  Fault Module Name:    tcmd.exe
  Fault Module Version:    14.0.2.36
  Fault Module Timestamp:    503ed28a
  Exception Code:    c0000005
  Exception Offset:    0040e3c8
  OS Version:    6.1.7601.2.1.0.256.48
  Locale ID:    1033
  Additional Information 1:    6e20
  Additional Information 2:    6e202ab67437ef41a4dabce957adb59b
  Additional Information 3:    9176
  Additional Information 4:    917604371a90886e5d972d6afc943d5f
 
May 20, 2008
11,288
95
Syracuse, NY, USA
So I tried to do a (Programs and Features) repair of "Take Command 14.0". That resulted in two message boxes:
Code:
Windows cannot find 'C:\Users\vefatica\AppData\Roaming\JP Software\Take Command 14.0\updates\Update\tcmd.exe'. Make sure you typed the name correctly, and then try again.
followed by a "Fatal Error" message box. I don't think that file ever existed.

Then I noticed that I don't even have an "AppData\Roaming\JP Software\Take Command 14.0 14.02.36" directory (thinking I should have one since that's the version I'm using). And I found an August 29 (build 36) TCMD.MSI in "AppData\Roaming\JP Software\Take Command 14.0 14.02.35".
 

rconn

Administrator
Staff member
May 14, 2008
12,316
148
I haven't started TCMD in a while, maybe a couple of updates. The recent one won't start here (even with no INI, START, or EXIT files). I get "TakeCommand has stopped working" (details below) and no GPF file. I tried XP-compatibility and it got a little further the first time (asking if it was OK to write to the registry) ... then it crashed similarly.

That address isn't inside TCMD.EXE. (At least not in the 32-bit version -- did you switch to Windows x64?)

You've either got something attaching itself to TCMD, or your Windows has gotten a bit wonky. Did you try deleting the TCMD registry entry (HKCU\Software\JP Software\Take Command 14.0)?
 
May 20, 2008
11,288
95
Syracuse, NY, USA
I'm still with Win7/32. Here it is again after deleting that registry key. FWIW, no TCCs were started. DUMPBIN shows the image base at 0x00400000 which would put that address in TCMD.EXE.

Code:
Problem signature:
  Problem Event Name:    APPCRASH
  Application Name:    tcmd.exe
  Application Version:    14.0.2.36
  Application Timestamp:    503ed28a
  Fault Module Name:    tcmd.exe
  Fault Module Version:    14.0.2.36
  Fault Module Timestamp:    503ed28a
  Exception Code:    c0000005
  Exception Offset:    0040e3c8
  OS Version:    6.1.7601.2.1.0.256.48
  Locale ID:    1033
  Additional Information 1:    6e20
  Additional Information 2:    6e202ab67437ef41a4dabce957adb59b
  Additional Information 3:    9176
  Additional Information 4:    917604371a90886e5d972d6afc943d5f
 
May 20, 2008
11,288
95
Syracuse, NY, USA
P.S. If that is really an offset (from 0x00400000), it's still in the image.
Code:
400000 image base (00400000 to 00836FFF)
I have no other indications of Windows being wonky!
 
May 20, 2008
11,288
95
Syracuse, NY, USA
When I run it in WinDbg, I get this (over and over, at least several tens of times).
Code:
0:000> g
(6ac.48c): Access violation - code c0000005 (first chance)
First chance exceptions are reported before any exception handling.
This exception may be expected and handled.
eax=000000b6 ebx=00821f5e ecx=0000004b edx=10151b80 esi=0082f6f4 edi=0080b600
eip=0080e3c8 esp=01afe9fc ebp=01b5fee4 iopl=0        nv up ei pl nz na po nc
cs=001b  ss=0023  ds=0023  es=0023  fs=003b  gs=0000            efl=00010202
tcmd!CallHtmlHelp+0x3ebfd8:
0080e3c8 64ff32          push    dword ptr fs:[edx]  fs:003b:10151b80=????????
0:000> g
(6ac.48c): Access violation - code c0000005 (!!! second chance !!!)
eax=000000b6 ebx=00821f5e ecx=0000004b edx=10151b80 esi=0082f6f4 edi=0080b600
eip=0080e3c8 esp=01afe9fc ebp=01b5fee4 iopl=0        nv up ei pl nz na po nc
cs=001b  ss=0023  ds=0023  es=0023  fs=003b  gs=0000            efl=00010202
tcmd!CallHtmlHelp+0x3ebfd8:
0080e3c8 64ff32          push    dword ptr fs:[edx]  fs:003b:10151b80=????????
 
May 20, 2008
11,288
95
Syracuse, NY, USA
It starts fine for me, under both XP and 7; I don't think this is a bug. Suggest you completely uninstall Take Command and reboot before reinstalling.
(Well, there goes my 104 days of uptime.) A reboot didn't help. But a subsequent uninstall/re-install did. TCMD starts now. It's too bad "Repair" didn't work!
 
May 20, 2008
11,288
95
Syracuse, NY, USA
No -- your offset is 0x40e3c8 *from* offset 0x400000 (i.e., 0x80e3c8), which is way outside the TCMD.EXE image.
According to DUMPBIN, the image extends to 0x836FFF. And 0x80e3c8 is less than 0x836FFF. And 0x80e3c8 is exactly where the VS debugger said the violation was. Hmmm! After the re-install, DUMPBIN says the image extends to 0x832FFF (that previous 0x836FFF was copied right from DUMPBIN's output!).
 

rconn

Administrator
Staff member
May 14, 2008
12,316
148
(Well, there goes my 104 days of uptime.) A reboot didn't help. But a subsequent uninstall/re-install did. TCMD starts now. It's too bad "Repair" didn't work!

You insisted (repeatedly) that I disable the "Repair" capability, because you didn't want the .MSI files remaining on your system after installation.
 
May 20, 2008
11,288
95
Syracuse, NY, USA
You insisted (repeatedly) that I disable the "Repair" capability, because you didn't want the .MSI files remaining on your system after installation.
Huh? I complained about **old** MSI files hanging around and never asked that "Repair" be disabled. And they're still hanging around anyway (new and old)!

Code:
v:\> ffind /a /s c:\tcmd.*
C:\Users\vefatica\AppData\Roaming\JP Software\Take Command 13.04 13.04.63\install\779AB05\tcmd.msi
C:\Users\vefatica\AppData\Roaming\JP Software\Take Command 14.0 14.00.28\install\D1A3D56\tcmd.msi
C:\Users\vefatica\AppData\Roaming\JP Software\Take Command 14.0 14.00.29\install\19C1FA4\tcmd.msi
C:\Users\vefatica\AppData\Roaming\JP Software\Take Command 14.0 14.00.30\install\68DC674\tcmd.msi
C:\Users\vefatica\AppData\Roaming\JP Software\Take Command 14.0 14.00.31\install\014E2B9\tcmd.msi
C:\Users\vefatica\AppData\Roaming\JP Software\Take Command 14.0 14.00.32\install\E512FBF\tcmd.msi
C:\Users\vefatica\AppData\Roaming\JP Software\Take Command 14.0 14.01.33\install\264BD79\tcmd.msi
C:\Users\vefatica\AppData\Roaming\JP Software\Take Command 14.0 14.02.35\install\CA5CBE7\tcmd.msi
C:\Users\vefatica\AppData\Roaming\JP Software\Take Command 14.0 14.02.36\install\070978E\tcmd.msi

When I say "remove old versions" they should go. Only the most recent one should stay. And "Repair" (as it is) doesn't look for an MSI file; it looks for an EXE.

Code:
Windows cannot find 'C:\Users\vefatica\AppData\Roaming\JP Software\Take Command 14.0\updates\Update\tcmd.exe'. Make sure you typed the name correctly, and then try again.
 
May 20, 2008
11,288
95
Syracuse, NY, USA
And the installer does keep a tcmd.exe (only one, the latest one), right where you might expect it! But the "Repair" option doesn't look for that one (see my previous post).

Code:
c:\windows\installer\{f016b878-65a0-48e9-8a9d-eeb71070978e}> d
2012-09-16  21:31        <DIR>    .
2012-09-16  21:31        <DIR>    ..
2012-09-16  21:31        106,838  TakeCommand.exe
2012-09-16  21:31        106,838  tcmd.exe

Those two files are identical. Are they really both needed?
 

rconn

Administrator
Staff member
May 14, 2008
12,316
148
And the installer does keep a tcmd.exe (only one, the latest one), right where you might expect it! But the "Repair" option doesn't look for that one (see my previous post).

Code:
c:\windows\installer\{f016b878-65a0-48e9-8a9d-eeb71070978e}> d
2012-09-16  21:31        <DIR>    .
2012-09-16  21:31        <DIR>    ..
2012-09-16  21:31        106,838  TakeCommand.exe
2012-09-16  21:31        106,838  tcmd.exe

Those two files are identical. Are they really both needed?

I don't have anything to do with that; Windows Installer is creating & saving them for some unknown reason. Neither of them are a "real" tcmd.exe (or a real .EXE, for that matter). Judging by the other 6,589 files in my \windows\installer subdirectories, I suspect they're icon/shortcut files.
 
Similar threads
Thread starter Title Forum Replies Date
rfaquino Automated download of the latest TCMD build Support 9
thorntonpg What is the latest version of everything Support 1
D Which is the latest version for Windows XP? Support 2
C Del /W999 2gbFile.ext / latest build / Win7 x64 / MSE / Everything Support 5
A Latest TCC/LE install broken Support 1
MickeyF where to view the latest JPSoft newsletter? Support 0
S Documentation Webpage not showing latest V15 build Support 0
S How to? Set the timestamp of ZIP command built archive to match latest member Support 8
C Latest TCMDx64 fails on XP Pro x64 Support 1
H Latest installer Support 0
B Virus in latest update? Support 4
C Latest not pasted Support 0
vefatica Tray min'd TCMD and ACTIVATE Support 6
C How to? starting TCC/TCMD v25 Support 2
CWBillow TCC and TCMD in Powershell Support 6
kb6ojs How to? "Specified Account Already Exists" error installing TCMD v27 Support 12
CWBillow TCMD Colors Support 8
Jay Sage Issues With TCMD File Explorer Support 0
C Last TCMD that supports win 7? Support 5
gentzel TCMD background color confusion Support 6
R Upgrade TCMD 19 to TCC 26 Support 1
Alpengreis Remaining TCMD background process (v26) ... Support 19
S Windows Server version not being detected correctly in TCMD 26RC2 Support 9
G TCMD crash when copy Support 3
Joe Caverly DrawVLine results different in TCMD tab and detached TCC Support 11
Alpengreis [TCMD v25.00.24] Small space problem with the DE translation in Prefs-GUI Support 1
Alpengreis [TCMD v25.00.24] Problem with copy and paste and the # char via mouse in TCC Support 6
Jay Sage TCMD Crashes with "tctoolbar /c /r file" Support 5
nikbackm TCMD 25 - Unregister older TCMD version Support 2
G Documentation on TCMD.INI Support 9
R New Clear Buffer in TCMD Home Menu Support 2
CWBillow Back up TCMD tabs Support 2
CWBillow Upgrade Windows 10's effect on TCMD and TCC Support 3
DrusTheAxe TCMD 24.02.49 x64 crashed due to DivideByZero :-( Support 4
A After update to 24.02.49, helpfile tcmd.chm hangs when opened Support 0
David McClelland TCMD 24 & Perl - perl thinks it's own executable is ...\TCMD24\TCC.EXE??? Support 3
dcantor How to? Can 32-bit TCC be run on a system with 64-bit TCMD and TCC installed? Support 6
W pdir returns diff results between tcc and tcmd - one is an error msg Support 5
vefatica What's TCMD's problem with ^e[0m? Support 13
CWBillow TCMD PowerShell Tab elevated Support 6
A How to? Copy+Paste in TCMD tabs with Ctrl-Shift-Ins? Support 5
vefatica TCMD output invisible on Win10 Support 22
J Moving from TCC v22 to TCMD v24 issues Support 3
RChrismon How to? Copy TCMD.INI to New Version Support 7
rps TCMD OPTIONS dialog Support 2
rps TCMD Tabs priority option setting Support 0
D Can we fix the scaling for TCmd? Support 14
CWBillow TCMD Tab Defs Support 4
A How to? TCMD Configuration Dialog: 'Smooth Scrolling' Option missing? Support 1
A Fixed [23.0.22]: TCMD crashes shortly after start, TCC keeps running in background Support 6

Similar threads