FAQs - Take Command and TCC

This page outlines some of the key questions we get about Take Command, as well as solutions to common problems.

Installation Problems - Versions 12 - 27

1. Take Command will not register

If you are getting HTTP errors, check to see that Take Command is configured to access your proxy server. (From the TCC prompt, run OPTION / Internet and enter your proxy settings.) If you cannot access your proxy server, or Internet access is completely blocked, contact us and we will send you a manual key.

You may have another application or Windows Policy blocking TCMD from accessing the Windows Registry.  Right click on the TCMD icon and select "run as administrator", and enter your registration information. If the registration is successful, you will now be able to run Take Command in non-elevated sessions.

Check to see if you have the latest versions of our software. (Click on "Download" in the menu bar above.)

Try re-registering the IsLicense50.dll by going to the command line, changing to the Take Command installation directory, and entering "regsvr32.exe /s IsLicense50.dll".

2. Take Command crashes on startup

The crash is probably occurring inside the Windows loader, before the Take Command code is executed. This is usually caused by another application attempting to inject a dll into Take Command's address space (i.e., an antivirus app, a screen manager, etc.) and the injected dll is crashing.

There are two things to try:

Turn off DEP for Take Command (control panel / system / advanced / performance settings / Data Execution Prevention) - see image:

Windows DEP dialog

If that doesn't work you'll need to find the app that's injecting the dll -- try disabling the other running applications one by one until Take Command loads successfully.

If neither of these solutions work, contact us directly for a workaround.

3. Will JP Software's products work with Windows 7, Windows 8, and Windows 10?

Take Command versions 11 - 16 support XP, Windows 2003, Vista, Windows 2008, Windows 7, Windows 8 (and 8.1), Server 2012, and Windows 10. Versions 9 and 10 will work with Windows versions through Windows 8.1, but they will not support the new Windows features introduced in Vista, Windows 7, Windows 8, and Windows 10.

Take Command version 17 supports Vista, Windows 2008, Windows 7, Windows 8.x, Server 2012, and Windows 10.

Take Command version 18 - 25 supports Windows 2008R2, Windows 7, Windows 8.x, Server 2012, and Windows 10.

Take Command version 26-37 supports Windows 10, Server 2016, and Server 2019.

Operations Questions - Versions 12 - 27

1. What Happened to 4NT?

4NT is still there. We have renamed it Take Command Console (TCC). If you want 4NT.EXE (perhaps because you have batch files requiring it), just copy TCC.EXE to 4NT.EXE.

2. How do I change the default command processor?

You can change the default command processor by going to the Control Panel / System / Advanced System Settings / Advanced / Environment Variables, and changing the value of "ComSpec" in the System Variables window.

For example, in v21 you'd change it to something like: c:\program files\jpsoft\tcmd20\tcc.exe, depending on where you installed Take Command and TCC.

3. Is Take Command completely compatible with the standard Windows CMD.EXE?

It's impossible to be 100% compatible with CMD.EXE, because

(1) Take Command has several thousand additional features, and

(2) CMD.EXE itself is incompatible with other versions of CMD.EXE.

We strive for 99.9% compatibility (generally more than CMD.EXE manages with differing versions of itself!) . There are always workarounds for the rare situation where Take Command doesn't execute a batch file in an identical way.

The best answer would be to download a 30-day fully functional trial of Take Command and test it in your own environment.

4. Is there a 32-bit version of Take Command?

The installer for Take Command v27 is 64-bit only. We will supply license keys to v25 (which includes 32-bit support & Windows 7 support) upon request.

5. Why can't I get to a full screen console in Vista, Windows 7, Windows 8, or Windows 10?

The video drivers in newer versions of Windows don't support full screen consoles. (It's not a Take Command issue; CMD.EXE won't work either.).

6. My IF statements are not working the same way since I upgraded.

The default IF behavior was changed in 8.02 to match undocumented behavior CMD.EXE -- Microsoft was distributing a number of batch files that would not work with 4NT or Take Command. (The problem was with compound commands on the IF line -- CMD.EXE will only execute the remainder of the command line if the IF test succeeds.)

If you don't intend to run any Microsoft batch files, you can restore the previous Take Command behavior by adding the line to your tcmd.ini file:


7. Why doesn't Take Command use the full size of the tab window?

Take Command can only display as many columns and rows as the largest possible console window on your system. That is determined by the screen size and the default font size in console windows. (This is a Windows limitation, not Take Command or TCC.) You can reset it by opening a console window (TCC), clicking on the icon in the upper left corner of the title bar, selecting Defaults and then Font. Select a smaller font size, save it, and close the console window. Restart TCMD, and you should be able to display a larger virtual console window.

Other Questions - Versions 12 - 27

1. Can you get me keys for earlier versions of JP Software Products?

We can sell and create keys for versions of Take Command back to Version 11. Pricing is the same as current versions.

2. If I buy a key for a JP Software product, do I get free upgrades forever?

No -- we provide major and minor updates free for 90 days after you order. If you order Extended Support with your new or upgrade order, we will provide major and minor updates free for one year.

We try to price major upgrades lower than most software companies -- upgrades are 50% of the original price.

FAQ: Windows Command Prompt. CMD Batch Files. Tabbed Windows Consoles.