Take Command v13 64-bit

Hi Rex,

there a hitch in the x64 installer. After answering the license
agreement, the "yes, uninstall older versions" and the install path
etc., I get another safety warning (Do you want to execute this
file). If I agree, TCMD is ostensibly successfully installed. Trouble
is, its nowhere to be found :-). Even Everywhere can't find it.
Staring TCMD from the last installer page opens only the SysWOW64
directory.
Best regards,

* Klaus Meinhard *
<www.4dos.info>
 

rconn

Administrator
Staff member
May 14, 2008
12,356
150
there a hitch in the x64 installer. After answering the license
agreement, the "yes, uninstall older versions" and the install path
etc., I get another safety warning (Do you want to execute this
file). If I agree, TCMD is ostensibly successfully installed. Trouble
is, its nowhere to be found :-). Even Everywhere can't find it.
Staring TCMD from the last installer page opens only the SysWOW64
directory.
<WWW.4DOS.INFO>

Not reproducible here. Try uninstalling the old v13 beta first and then install the public beta and see if that makes a difference.
 
Hallo rconn,


> ---Quote (Originally by K_Meinhard)---
> there a hitch in the x64 installer. After answering the license
> agreement, the "yes, uninstall older versions" and the install path
> etc., I get another safety warning (Do you want to execute this
> file). If I agree, TCMD is ostensibly successfully installed.
> Trouble
> is, its nowhere to be found :-). Even Everywhere can't find it.
> Staring TCMD from the last installer page opens only the SysWOW64
> directory.


> Not reproducible here. Try uninstalling the old v13 beta first and
> then install the public beta and see if that makes a difference.

No difference. The 64bit version wasnt installed at all.

But it _may_ be an installer problem. I have noticed other
installer-related problems since then, and I'll try a system restore
at some later time.

herzliche Grüße,

Klaus Meinhard
 
Hallo rconn,


> Still not reproducible here, but there's only a couple of possible
> places that Windows Installer could be going astray. I've uploaded
> a test build (tcmdx64.zip) to the ftp beta site; try downloading,
> unzipping & installing that build and let me know if it behaves
> differently.

Small difference. I get no 2nd safty warning. But at the end (Start
TCMD...) SysWOW64 is opened and no TCMD13x64 directory is found. But
see my other post. It may be an installer problem on my system.

herzliche Grüße,

Klaus Meinhard
 
Hallo Rex,

I tried (unsuccessfully) to get to the bottom of this. I took the
following steps:

I installed TCLE13x64 and TCCLE13x64 successfully. The only thing I
noticed was an unusual second safety warning (do you really want to
run...) when the proper installation (after answering all questions)
started for TCCLE13x64. So installation of 64-bit programs into
Program Files seems to be generally okay.

I (again) tried to install TCMD13x64, latest build 14. Same luck as
before: I get a the second safety warning before actual installation
(the same one I get when I start the file, and installation aborts
when I answer no), then there's a blank console window shortly opening
before the end, installation says it finished successfully, but
there's no directory or files containing TCMD13x64. Selection of
running TCMD or README opens the SysWOW64 dir in Explorer.

I then extracted and set up the files manually. No problem. I then run
TCMD13x64 setup again, and it now seems to find the installation and
offers to uninstall. It doesn't, however. After a seemingly successful
uninstall all files are still there.

So what is the difference between the TCMDLE and the TCMD
installation?

This is on Vista 64-bit, all updates, german language version, no UAC.

I then tested this on a Windows7x64 machine, UAC enabled, german
language, where I get another warning at the end of the install prep
(Do you want that this program changes settings ...) and installation
runs okay as expected.

Seems I might have to upgrade my Vista machine...


herzliche Grüße,

Klaus Meinhard
 

rconn

Administrator
Staff member
May 14, 2008
12,356
150
> I (again) tried to install TCMD13x64, latest build 14.

I think you have the same problem (Windows Installer x64 bug) as a couple of
other users. The problem is not in the new builds, it's in the old build
(12 and earlier) when uninstalling. Build 14 has to uninstall 12, and
that's where it's displaying that message & console window -- and failing.
The 32-bit Windows Installer does not seem to have the problem (nor do other
x64 users), so it seems to be Windows Installer version specific. (I added
a workaround for build 13+ so it wouldn't make the offending script call
when uninstalling.)

The only way around it is to remove the build 12 & earlier versions from
your system. Delete everything on disk (especially including any saved .msi
files), and scrub the registry of any v13 x64 traces. (There will be a lot
-- the Windows Installer adds them everywhere!)
 
Hallo Rex,


> The only way around it is to remove the build 12 & earlier versions
> from your system. Delete everything on disk (especially including
> any saved .msi files), and scrub the registry of any v13 x64
> traces. (There will be a lot -- the Windows Installer adds them
> everywhere!)

I am pretty sure there wasn't a prior build of version 13 x64 on that
system. I had only installed the x86.

I guess I'll see what the next update will do - will it update the now
existing version build 14 correctly?

herzliche Grüße,

Klaus Meinhard
 
Jun 2, 2008
376
2
Newton, MA
On 9/6/2011 9:56 AM, rconn wrote:

> I think you have the same problem (Windows Installer x64 bug) as a couple of
> other users. The problem is not in the new builds, it's in the old build
> (12 and earlier) when uninstalling. Build 14 has to uninstall 12, and
> that's where it's displaying that message& console window -- and failing.

I finally built up the courage to try getting rid of build 12. A Windows
update had already created a restore point.

I located the directories in the Program Files areas (both 32-bit and
64-bit) and renamed the directories that referenced Take Command 13.
Then I fired up the Registry Editor (regedit) and ran through it using
two search strings: "take command 13" and "tcmd13". I searched for the
strings in the keys, values, and data. Whenever I found something, I
deleted the single item if there were items for other programs in the
same key or the entire key, and I deleted the parent key when it
appeared that the entire key had been created just for Take Command 13
(for example, for all the subcomponents such as the language dlls,
ide.exe, etc.). As Rex said, there were a lot of keys!

With some trepidation, I rebooted the computer (I once destroyed a
computer when trying hopelessly to get rid of Norton Internet Security
and had to start over with a new hard disk). Thankfully, it booted up
without any apparent problem. The Control Panel "Programs and Features"
tool no longer showed Take Command 13 -- a good sign. And build 14
installed and is now running fine. Whew.

-- Jay
 
Similar threads
Thread starter Title Forum Replies Date
rconn News Take Command v13.03.50 Released Support 0
rconn News Take Command v13.03.45 Released Support 0
M "V(iew)" command does not work at all for me in V13... Support 6
Dmitry L. Kobyakov How to? How to remove the record of the old version of the Take Command? Support 7
D Can alias pass parameters to for command? Support 3
samintz How to? Search for %(command) in Help? Support 1
T VIEW only works from command line Support 14
rconn News Take Command / TCC / CMDebug / TCC-RT v28 Released Support 0
T Take Command 28: Lua reports version 5.4.0 (5.4.3 expected) Support 0
Jay Sage WAD Possible Bug With OPTION Command With @FILE Support 5
rconn News Take Command / TCC / CMDebug / TCC-RT 27.01.24 uploaded Support 0
J Take command does not start on Windows 10 Support 3
vefatica `Back quotes` - command line vs. batch file Support 5
Jay Sage WAD Failure of Alias Command with /Z Option Support 14
Phileosophos Is there any way to open the Take Command options dialog from the command line? Support 8
Phileosophos Command-line Editing Shortkeys That Fail Support 6
fpefpe How to? free (internal) command Support 0
rconn News Take Command / TCC / CMDebug / TCC-RT 27.01.23 uploaded Support 0
T How to? retain command history across reboot? Support 6
rconn News Take Command / TCC / CMDebug / TCC-RT v27.01 Build 22 Uploaded Support 0
Jay Sage Bug With Flow Control and/or Command Grouping Support 2
GermanDirk How to? EVENTLOG Command with simple User Rights not functional Support 4
Jay Sage Take Command Is Too Fast! Support 4
Jay Sage Comparison of IF with Command Group and IFF Support 6
D Open Windows 10 Photos app from command line Support 11
rconn News Take Command / TCC / CMDebug / TCC-RT 27.0.21 uploaded Support 0
rconn News Take Command / TCC / CMDebug / TCC-RT 27.0.20 uploaded Support 0
U Can not get/start Take Command gui Support 1
rconn News Take Command / TCC / CMDebug / TCC-RT 27.0.19 Support 0
S Increasing Font Point Size in Command Tabs Support 2
mfarah Fixed The DATE command produces the wrong error message. Support 1
vefatica Command name mix-up Support 3
FreezerBurnt "Missing SETLOCAL" when initializing Visual Studio Command Prompt. Support 9
E How to? Closing desktop created by DESKTOP command Support 10
rconn News Take Command / TCC / CMDebug / TCC-RT v27.0.18 Support 0
K Take Command fox XP? Support 7
Joe Caverly Documentation Replace internal command with LIBRARY command Support 0
fpefpe How to? command echo in title line/bar Support 2
U Command help on file names Support 5
vefatica Command line DO with no closing parenthesis? Support 9
vefatica Command history search is off Support 7
H How to? How can I say "if the command separator is not ~ then setdos /C~" Support 8
N Command execution slows down in TCC Prompt after a while Support 6
R Long commands retrieved from command history have blank line when wrapped Support 20
jpeni Take Command Language Examples Support 1
rconn News Take Command / TCC / CMDebug / TCC-RT 26.02.41 Uploaded Support 0
fpefpe winfr command Support 4
Dmitry L. Kobyakov Fixed The SETARRAY /R command works incorrectly with cyrillic files Support 2
M Selecting test "off by one" problem in Take command Support 4
Dmitry L. Kobyakov Documentation Error in the Help: the WINDOW command Support 0

Similar threads