Version of TCMD that does not use the registry for keys, etc

[Péter Köves]

I seem to remember that there is a version of TCMD that doesn't leave tracks in the registry. I tried searching but couldn't find it. Didn't need it before, but as the workplace locks down, I do now.Could somebody point me in the right direction? Thanks.

 

[rconn]

Version of TCMD that does not use the registry for registration keys, etc

> I seem to remember that there is a version of TCMD that doesn't leave
> tracks in the registry. I tried searching but couldn't find it. Didn't
> need it before, but as the workplace locks down, I do now.Could
> somebody point me in the right direction? Thanks.
>

If you're referring to v11, you don't need a separate version. V11 will
attempt to write the registration info both to the registry and to a
"TakeCommand11.key" file in the installation directory. When it loads, v11
will look first in the registry and then for the key file. See
"Registration" in the help for more details.

(Note that if you're using Vista or Windows 7 and you want to use the key
file, you cannot install Take Command in the "\program files" directory, as
Windows will not allow apps to write there unless the app was started with
full administrator rights.)

Rex Conn
JP Software

 

[Péter Köves]

If you're referring to v11, you don't need a separate version. V11 will
attempt to write the registration info both to the registry and to a
"TakeCommand11.key" file in the installation directory. When it loads, v11
will look first in the registry and then for the key file. See
"Registration" in the help for more details.

Hmm... That's not what I need though. I don't want TCMD to write to the registry even if it has permissions (I want it to be "invisible"). So let me ask it this way. If I copy a TCMD installation from elsewhere to a computer (where it has been uninstalled and registry entries removed) together with the key file ... will it leave the registry alone?

 

[rconn]

> Hmm... That's not what I need though. I don't want TCMD to write to the
> registry even if it has permissions (I want it to be "invisible"). So
> let me ask it this way. If I copy a TCMD installation from elsewhere to
> a computer (where it has been uninstalled and registry entries removed)
> together with the key file ... will it leave the registry alone?

TCMD only tries to write to the registry when you enter your registration
info. If you don't do that, and you have a takecommand11.key file with your
registration info, it will leave the registry alone.

Rex Conn
JP Software

 

[dim]

On 2010-04-22 01:21, rconn wrote:

>> Hmm... That's not what I need though. I don't want TCMD to write to the
>> registry even if it has permissions (I want it to be "invisible"). So
>> let me ask it this way. If I copy a TCMD installation from elsewhere to
>> a computer (where it has been uninstalled and registry entries removed)
>> together with the key file ... will it leave the registry alone?
> ---End Quote---
> TCMD only tries to write to the registry when you enter your registration
> info. If you don't do that, and you have a takecommand11.key file with your
> registration info, it will leave the registry alone.

It looks like it still registers the ISLicense40.dll file, which writes
to HKEY_CLASSES_ROOT, otherwise the registration stuff cannot work.

TCmd also automatically writes some preferences to HKEY_CURRENT_USER.

E.g. to remove any registry traces afterwards, you would need to:
- Run regsvr32.exe /u %TCMDPATH%\ISLicense40.dll
- Delete HKEY_CURRENT_USER\Software\JP Software

 

[Péter Köves]

Thanks. I think this latter is OK. Presumably all I need is for TCMD not to show up as an installed application.