I'm willing to test. This is an issue that has hit me, at irregular intervals, for years. Case in point: TC 16 x64 worked for a year without issue. After installing TC 17 x64 both TC 16 and 17 stop running. No other system changes were made at the time.
I'll run a Process Monitor session...
After using msconfig to perform a "diagnostic startup" with just the basic Windows devices and services running TCMD x64 starts but generates an error: Access is denied. "AttachConsole". I tried deleting TCMD.INI and that stopped the error message from displaying but TCMD x64 and TCC still...
I have a zero byte TCMD.INI in %APPDATA%\Local\JPSoft and nothing else. I'm have no plugins installed. TCC /I results in no change in behavior and I have no GPT file anywhere that I can find. I'm going to try a minimal startup and see if that helps.
When running tcc.exe from a Windows command prompt I get nothing. I've been poking at this since I posted the original message and, while using the Sysinternals Process Monitor utility I can see buffer overflow errors and then a call to \Windows\system32\WerFault.exe.
I've attached the output...
I just installed Take Command 17.00.53 x64 and now TCC no longer runs. Before installing TC 17 I had a copy of TC 16 installed and it ran perfectly. After the TC 17 installation TCC just won't run in either version.
I've uninstalled both versions and reinstalled just TC 17. No luck.
I tried...
The first time TCMD 32-bit starts I get a popup window that states "The handle is invalid. "Attache Console". Dismissing the dialogue box closes TCMD.
Starting TCMD 32-bit a second time, and subsequent times, it comes up without error and seems to work fine. Progress!
I tried 15.00.36 and TCC is still crashing when loading with no GPF file created. Any thoughts on how I might get more information to help resolve this.
I'm getting the same behavior and no GPF file is created. This is with 15.00.34 and using msconfig to pare the starting services down to the bare minimum.
I submitted the issue to Stardock's technical support. Hopefully they will be in contact. Thank you for the assistance. They might have to provide you with a copy of Windowblinds as I'm running a beta (7.30a) and not the current production release.
Bingo! Here's the .GPF file. From my, admittedly uninformed, reading of it some interaction with Stardock's Windowblinds was at fault. If someone can confirm my interpretation that's easy enough to fix and I can let file a bug report with Stardock.
No .GPF file and I'm not using any plugins. I just updated to the current build. I've noticed this issue since I updated from version 12 a month or so ago.
Running Windows 7 64-bit SP1 with all current patches with TCMD 13.04.55 x64.
The observed behavior is that the TCMD window will vanish. It seems to happen most frequently when I'm minimizing the TCMD window but it can happen at any time. I don't even have to be doing anything in the window...
I'm getting the same behavior with Windows 7 RTM. Will fixing this require changes to TCMD or Less? Any thoughts on the matter are much appreciated.
Magus
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.