Windows 7 test fix

Mar 27, 2009
3
0
The beta build 66 works with my Windows 7. Released build 67 does not.

But typing 'exit' does not close TCC - I have to click on the 'x' of the Window or Tab to close TCC.
 

rconn

Administrator
Staff member
May 14, 2008
12,404
152
Martin wrote:

> The beta build 66 works with my Windows 7. Released build 67 does not.

I didn't put the Windows 7 code into build 67, because nobody ever
responded about whether it was working for them with the test build.


> But typing 'exit' does not close TCC - I have to click on the 'x' of the Window or Tab to close TCC.

With build 66 (known issue) or build 67?

Rex Conn
JP Software
 
Apr 30, 2009
17
0
With the RC widely available this week is there any chance this might be re-released? I saw in another thread that the Windows 7 fix wasn't included in later releases due to lack of feedback.


I've uploaded a test build of Take Command 10.0.65 to the ftp beta area (ftp://jpsoft.com/beta/tcmd.exe). This has an experimental workaround for a Windows 7 bug when starting apps; those of you having trouble with Take Command or TCC and Windows 7 please try this build and let me know if it solves your problem.
 

dim

Dimitry Andric
May 31, 2008
205
1
Netherlands
On 2009-05-04 19:41, Magus wrote:

> With the RC widely available this week is there any chance this might be re-released? I saw in another thread that the Windows 7 fix wasn't included in later releases due to lack of feedback.

FWIW, build 67 works fine here on Windows 7, build 7100, x64. Both
TCC.exe and TCmd.exe start up fine, and seem to work correctly, as far
as I have tested.
 
May 2, 2009
10
0
Would install for me on a clean install of Win7 build 7100 x64. However on first run the program would hang not showing the dialog to enter registration details. However manually adding the registration details into the registry allows it to run.
 

dim

Dimitry Andric
May 31, 2008
205
1
Netherlands
On 2009-05-05 14:03, paraglider wrote:

> Would install for me on a clean install of Win7 build 7100 x64. However on first run the program would hang not showing the dialog to enter registration details. However manually adding the registration details into the registry allows it to run.

As far as I know, the registration information for Take Command 10 is stored in a file, not in the registry (except for the ASProtect stuff, if you run a trial version). Since the registration file goes in the Take Command installation directory by default, you may not be able to write it if your process is not "elevated", e.g. run with administrative privileges.

So you could try to run tcc.exe or tcmd.exe as administrator, and see if that allows you to register properly.
 
May 2, 2009
10
0
I am running it as an administrator. Also Everyone user has full control to the install directory and subdirectories. Problem has now returned.

I think the problem is tcc. If I run tcc directly all I see is a blinking cursor. I don't see the registration lines.
 
May 4, 2009
2
0
This has an experimental workaround for a Windows 7 bug when starting apps; those of you having trouble with Take Command or TCC and Windows 7 please try this build and let me know if it solves your problem.

I have tried both the test build and the release version of Take Command on Windows 7 RC, and they don't seem to work. What happens, I run it, I can see tcmd.exe in the process list, but tcc.exe is not running, I have to end the tcmd.exe process.
 

rconn

Administrator
Staff member
May 14, 2008
12,404
152
> ---Quote (Originally by rconn)---
> This has an experimental workaround for a Windows 7 bug when starting
> apps; those of you having trouble with Take Command or TCC and Windows 7
> please try this build and let me know if it solves your problem.
> ---End Quote---
> I have tried both the test build and the release version of Take Command
> on Windows 7 RC, and they don't seem to work. What happens, I run it, I
> can see tcmd.exe in the process list, but tcc.exe is not running, I have
> to end the tcmd.exe process.

The test build was *not* for RC1. In RC1, Microsoft broke several Windows
APIs; it's going to take a little while to find workarounds.

Rex Conn
JP Software
 
May 4, 2009
2
0
The test build was *not* for RC1. In RC1, Microsoft broke several Windows
APIs; it's going to take a little while to find workarounds.

Alright then, no problem, was just a fyi, guess you already knew. I think Microsoft likes keeping you busy :)
 
Similar threads
Thread starter Title Forum Replies Date
thorntonpg windows 11 Support 12
vefatica Windows 10 themes Support 0
J Take command does not start on Windows 10 Support 3
D How to? Windows Key-Left and Windows Key-Right Support 9
Joe Caverly PYTHON from Microsoft Windows Store Support 2
D Open Windows 10 Photos app from command line Support 11
vefatica Windows Terminal ... Pop-up location Support 1
Joe Caverly Windows Terminal and @SELECT Support 13
vefatica Console popup windows don't work correctly Support 0
D Layout debugger windows Support 2
L LIST's pop-up search loses focus in a Windows Terminal window Support 15
nickles ANSI Colors Windows 7 no longer working Support 6
S Windows Server version not being detected correctly in TCMD 26RC2 Support 9
D Which is the latest version for Windows XP? Support 2
rconn News Windows 7 Support Support 0
Joe Caverly Windows Size is 80x0 Support 2
rconn Dropping Windows 7 support in Take Command / TCC v26 Support 8
G Taskbar Windows 10 Support 7
T Windows Terminal Support 2
Joe Caverly Windows Sensor Support 5
vefatica Windows 10 and line wrapping selection? Support 6
fishman@panix.com New Problem with later Windows 10 Support 10
CWBillow Upgrade Windows 10's effect on TCMD and TCC Support 3
T Take Command v21 on Windows Server Support 1
Bill de Haan "Sensitive Privilege Use" in Windows security auditing Support 7
Joe Caverly Create Windows Jobs and optionally attach processes to a job Support 17
Joe Caverly What version and Windows OS are you using? Support 3
A Windows 10 This app can't run on your PC Support 2
G 4NT on Windows 10 Support 3
vefatica Undesired scrolling in Windows 10 enhanced console. Support 2
vefatica Windows 10 version number? Support 6
vefatica How do I see Windows 10's ANSI in action? Support 3
A List windows with titles matching given pattern? Support 2
M New "pinned" attribute (since Windows 10 1709) Support 6
Emilio III TCMD Tab titles on Insider Windows Support 2
kb6ojs Want to start TCMD v20 with every Windows 10 bootup Support 3
E Cannot paste dollar sign into TCC on Windows 10 1803 Support 7
M TCC incorrect dir output since Windows 1803 Support 6
G Version 20.11 installed on Windows 10 problems Support 9
fishman@panix.com TCC v22 & the Windows 10 Console Support 5
Per TCC/LE 14 64-bit won't start on Windows 10 Insider Preview 17063 (171213) Support 12
I tcmd versus tcc in Windows 10 Support 2
Dick Johnson DrawBox now broken in Windows 10? Support 6
CWBillow Editing in the root directory of windows 10 Support 6
CWBillow Clearing out the Windows Temp folder Support 2
H New command not working well in Windows 7 Support 4
H _winver shows 6.1 on windows 7 Support 7
Joe Caverly Windows x64 Support 4
mscheuner TCMD 20 on Windows 10 - always loosing its settings Support 1
fishman@panix.com Windows Installer failing again... Support 6

Similar threads