I am in the process of switching to Linux Mint (an Ubuntu derivative), after over a year of frustration with Windows 10. As I've been using Take Command and its predecessors for 30 years, I have numerous tools and batch files that rely on it, notably the ones I use to build my Web site. I expect...

Thanks, Alpengreis. ColorTool does work. Also, there is (sane) logic to changing the color scheme, as explained here. If I weren't using a dark-blue background for TC, I likely would have noticed only that the colors are clearer against the standard black background. The real problem was that...

First, thanks to all of you for the quick response. Changing the color palette seems insane to me. But I don't know if Microsoft is insane, or if I'm the insane one for my inability to recognize and be grateful for Microsoft's improvements. This isn't the first insane thing I've encountered in...

I recently built a new computer that runs Windows 10, to replace an old machine that ran Windows 7. I moved the TCMD.INI file from the old machine to the new after installing Take Command 24. TCMD.INI specifies "Bright White on Blue" as its standard color for TCC. The background was the correct...

As an alternative, would it be possible for the installer to display a message advising the user to uninstall the later version if they really want to downgrade? Yes, I did figure out that I needed to uninstall. But it would have saved some unnecessary aggravation and wasted time if I didn't...

Oops... I didn't see Rex's post about "Bad 17.00.66". The version now on the server is 64, though I had no way of knowing that. I downloaded it and ran the installer, which aborted with an error message about a newer version already installed. I had to uninstall Take Command entirely before I...

I updated from 17.00.64 to 17.00.66 using "Check for Updates." The update appears to have installed correctly. When I restarted Take Command, I got this error message: Error on line 1 of C:\Users\xxxx\AppData\Local\JPSoft\TCMD.INI: Invalid item name "Key=No" It also looked like it ignored my...

I just installed version 17 (from the "all downloads" page, as the "news" page link is version 16!). Thanks for finally making the use of control-C consistent with the rest of Windows world, thereby fixing a significant nuisance. Assuming I don't run into any significant problems with 17...

That's not directly relevant, since I was talking about uncompressing GZipped log files from my Web site. But I'll give the new compression options a try. When I compared the ZIP from version 11 with a Zip utility that had compression settings, the latter at maximum was better. I'll have to try...

That's exactly what caused the problem! I've had COPY and MOVE aliased with /r and DIR aliased with "*dir /Ou /H" since the 4DOS days, so I didn't even think of that. I suspect I'll end up using the TCDIALOG approach (with a less cumbersome alias) rather than changing the ancient aliases. Is...

I just upgraded to TCC 13 from version 11. I notice that the new /= option does not work with DIR, COPY, or MOVE, even though the help file says that's a valid option. But /= does bring up a dialogue box with ZIP, UNZIP, VIEW, and ATTRIB. With DIR /= I get the message TCC: (Sys) The parameter...