Dropping 32-bit support in Take Command & TCC?


Staff member
May 14, 2008
I'm starting on the core of the v26 update, and I'm thinking that it's time to drop x86 support in future versions. It's (considerable) extra aggravation to build, test, & create the installer code for x86, and the latest installer analytics are showing 32-bit installs hovering a bit below 2% of the total. (Most of those seem to be pirated copies in China, Russia, Iran, and a handful of other countries.)

If you have any compelling arguments why I should maintain x86 support, now's the time to present them!
Had there been a straight-forward method of installing the 32-bit version of TCC/TCMD on a 64-bit version of Windows, I would have installed the 32-bit version of TCC/TCMD.

It is fortunate that Microsoft still provides a 32-bit version of CMD EXE and a 32-bit version of PowerShell EXE on their 64-bit OS.



Staff member
May 14, 2008
Had there been a straight-forward method of installing the 32-bit version of TCC/TCMD on a 64-bit version of Windows, I would have installed the 32-bit version of TCC/TCMD.

For what possible reason? The 32-bit version is significantly slower, and can't access the 64-bit Windows directories and registry.
For these (and other) reasons:

PSHELL and out-of-process servers

PSHELL: Use 32-bit from 64-bit

32-bit out-of-process servers from 64-bit TCC via PSHELL

PSHELL switch for 32- or 64-bit

Using a 32-bit In-Process COM Server DLL from 64-bit TCC

Can 32-bit TCC be run on a system with 64-bit TCMD and TCC installed?

May 20, 2008
Syracuse, NY, USA
Had there been a straight-forward method of installing the 32-bit version of TCC/TCMD on a 64-bit version of Windows, I would have installed the 32-bit version of TCC/TCMD.
It's not hard if you have an installation on a 32-bit machine (virtual maybe?) ... just copy the install to the 64-bit machine, start it up, and register it. The first time you'll probably need to edit TCMD.INI a bit (maybe TCSTART/TCEXIT). Thereafter just don't copy those files. I'm pretty sure updating must be done on the 32-bit machine.

I have them both on Windows 10. But I have no reason to use the 32-bit one except to compare it to the 64-bit one. As Rex said, the 64-bit version is faster. Often the speed difference is only 1-2%. But for some things it can be over 10%.

Rex, is there anything internal to TCC that will tell me whether it's 32 or 64 bit?
Oct 18, 2009
These are actually some arguments against continuing to support it:

1) Some background--I work at a lawfirm where the owner insists on using a hobbyist DIY DOS database manager that was never popular, to write a database system even though she's not a programmer. Symantec abandoned the database manager in 1995, and we use an earlier version developed 1986-1991. The database manager has a proprietary file format, doesn't allow multiple tables or screen sets, has no query language, no programming language, no IDE, cannot read or write any data format other than plain ASCII, does not have strong data typing, and on and on and on. And she's not gonna get anything modern even though since mid-2014 she's been told by me and every consultant that she needs a modern Windows-based program written by a developer.

I'm 69, a lawyer with no formal I.T. training. I've told her straight out "Whenever I leave, you won't be able to find any competent I.T. person. No one under 55 knows anything about DOS--and they won't be interested in learning. Plus, any I.T. person will know that working with this stuff 2-3 years would be career suicide. "At your current job, do you work with C? No. C++? No. Java? No. SQL? No. Python? No. ..." They couldn't even list DOS on a resumé."

2) Related to that (and relevant to this topic), I've told her, "Microsoft is fully integrating Linux into Windows--but only in 64-bit Windows. They're doing it to get access to billions of lines of Linux code and hundreds of thousands of routines. Within 2 years, ... maybe 3 at most ... some client (major hospital systems) is going to tell us they've upgraded their system and we need to use a different on-line interface program--that only runs on 64-bit Windows.

"Plus, most major software vendors are no longer supporting 32-bit or already plan to phase it out. Once WSL is an integral part of Windows, within 2 major versions the software companies' developers will start using that--they won't bother writing separate equivalent routines for 32-bit versions."

3) Yes, there are "mission critical" applications that only run under 32-bit and no longer have vendor support and there is no equivalent replacement. But does that mean that a relatively small company with a narrow specialized customer base should continue manufacturing 5-1/4" floppy disk drives? Or 19" CRT monitors? Or VCR's? Or 1MB RAM sticks?

(For "You young-uns" that's one MEGABYTE sticks, not one GIGABYTE. ... Ask your grandpa ...)

And does that mean the company should continue developing and manufacturing for the customers who could get something equivalent but just "continue to hang on"?

4) Realistically, at some point Microsoft is going to stop developing and supporting 32-bit Windows. They have already publicly indicated they want to move to "Windows As A Service". Can you really see Windows 10 ver 2410 still having a 32-bit version--that can't tie in to WSL? And that's just 5 years down the line.
Oct 18, 2009
We're getting off-topic, but have you tried running it in DOSBox? I use that, with the D-Fend Reloaded frontend to run some old DOS industrial control with great success.
It's a multi-user database. She really needs to get something modern ... "ain't gonna happen" ... The basic program is garbage -- re-read the description of all the things it doesn't have.

Keep in mind--we're not talking FoxPro or dBase or Paradox, or Lotus 1-2-3, or a program that was ever somewhat popular. Even when it was under active development--"Nobody's ever heard of this! Who puts this out? Symantec has a database product??"

Continuing development of 32-bit applications and utilities for more than maybe 1-2 more versions is basically just a waste of limited development resources. Once WSL is fully integrated, any organization expecting to continue with 32-bit as a core part of its tech long term is just heading off a cliff.
Similar threads
Thread starter Title Forum Replies Date
rconn Dropping Windows 7 support in Take Command / TCC v26 Support 8
T KEYSTACK and double-double quotes dropping spaces Support 2
Peter Murschall Single-line Do-CMD is a bit uncooperative. Support 6
Joe Caverly VBEEP on 64-bit Support 3
vefatica SETP usually fails with a 32 bit process Support 4
dcantor How to? Can 32-bit TCC be run on a system with 64-bit TCMD and TCC installed? Support 6
T 32 and 64 bit simultaneous portable versions Support 2
vefatica Make FFIND a bit more friendly? Support 14
CWBillow Everything.exe - 64-bit? Support 8
S 32-bit Take Command v22 install for thumb drive Support 1
Per TCC/LE 14 64-bit won't start on Windows 10 Insider Preview 17063 (171213) Support 12
Joe Caverly SETP and 32-bit process Support 2
gworley How to? Take Command 20 64 bit vs 32 bit Support 1
mikea Documentation Consider expanding the docs for 'Everything' a bit Support 10
T 64 bit TCCLE appears to crash when opening tcc.exe from within tcc.exe window Support 7
vefatica Can a subroutine return a 64-bit integer? Support 4
M 64-bit plugins? Support 1
M An oddity that's a little bit scary... Support 6
rconn News Take Command 16.03.54 32-bit installer Support 0
rconn News Take Command 16.03.54 32-bit installer fix Support 0
MickeyF problem using COM object in VBScript from v16 x64 TCC but not from v15 32-bit TCC Support 4
JohnQSmith Installing TCMD16 on 32 bit XP Support 12
D New 64-bit install goes to Program Files x86 Support 3
F How to install 64-bit after having installed 32-bit on Win7 Support 2
Dan Glynhampton Bad link to 64 bit RC1 download Support 0
M And oddity re the 32-bit TCC on a 64-bit system... Support 4
C Advantages of 32 or 64 bit TCMD in 64 bit Windows 7 Support 3
C How to determine if system is 32 or 64 bit? Support 5
M How to? Identify 64-bit and 32-bit TCC sessions... Support 7
M WAD A bit of strangeness related to Unicode-marked file not being Unicode Support 2
M A bit of a complaint regarding @FileDate and @FileTime Support 3
K_Meinhard Take Command v13 64-bit Support 9
K_Meinhard 64-bit installer Support 3
M Another bit of weirdness.... Support 0
M A little bit of strangeness with @Char... Support 3
J CTRL-C does not work on Windows 7 64-bit Support 3
S Take Command LE (32 bit) locking up several times a day Support 14
S 64-bit version use? Support 5
S TCMD 12 64-bit locking up frequently Support 7
rconn v12 Release Build test - 32-bit fixed Support 36
Ville 64-bit command line apps invisible in TCC Support 2
gschizas TaskDialog doesn't work in 64-bit Take Command Support 1
D Settings not writting to registry in XP (32 bit) Support 10
Alpengreis Python support for 3.8.3 in TCC v26.x? Support 2
C How to? Mouse support in WSL when in Take Command Tab Support 2
N Python 3.8.2 Support in 26? Support 3
J How to? tty support in V25? Support 5
M QUERYBOX /L support seems to only partially work Support 2
rconn News Windows 7 Support Support 0
Steve Pitts REXX support - order of selection Support 2

Similar threads