TC 8.0 Beta1 - Questions about configuration files

[HBB]

Firstly, very thanks to Mr Ghisler for the works on version 8.0 and 64 bit support especially (also thanks to the friends who spend time to check the pre-release beta versions).

To the friends who try TC8.0B1 :

Do both 32 bit and 64 bit TC are able to use :
1) same wincmd.ini and wcx_ftp.ini files (located outside of program folder)
2) same plugins (located outside of program folder)
in different machines having different operating systems (such as WinXP-32bit and Win7-64bit) by portable usage.

The answers seem to be yes according to the History file of TC8.0B1. Are the answers yes? I want to be sure.

Regards

[Sir_SiLvA]

How about using the SEARCH???

TC64Bit ofc CANT use 32Bit Plugins....

[HBB]

I searched ofcourse. Probably, I could not choose correct key words to search.

In the history file :
:
04.09.11 Added: Changed name of 64-bit program to totalcm64.exe to allow installation to the same directory as 32-bit version (64)
:

If it is so, the folder name of 64 bit plugins should be different. I did not find any warning files in the installation package.

[Sir_SiLvA]

You didnt found any warning cause from people using the tc comon sense & knowledge like 64bit prgs only using 64bit dlls & plugins...

or are you one of the guys who needs his coffee to go labeled "Attention! content is HOT!" ?

[karlchen]

Hello, HBB.

Do both 32 bit and 64 bit TC are able to use :
1) same wincmd.ini and wcx_ftp.ini files (located outside of program folder)

Yes.

2) same plugins (located outside of program folder)

Definitely no.
T.C. 8.0 beta1 32-bit can use only 32-bit plugins.
T.C. 8.0 beta2 64-bit can use only 64-bit plugins.
Yet, Christian seems to favour this approach:
Each plugin should hold the 32-bit files and the 64-bit files - the latter should have the suffix "64", and these files should be kept in a single folder.

in different machines having different operating systems (such as WinXP-32bit and Win7-64bit) by portable usage.

Whatever could be done using T.C. 7.56a, can be done using T.C. 8.0 beta1 as well.
So in case the installattion qualifies as portable, the answer is: yes.

Karl

[HBB]

Hello Karl :

Thanks for understanding and reply sincerely.

Since I don't have any idea about programming of plugins , I did not know the plugins can only be executed in system on which it is written. I wrongly expected them like codes such as vbs (I generally use plugins less and don't look at them what they are).

I have lately noticed in the history :
:
14.08.11 Added: All 64-bit plugins MUST now have '64' at the end of the extension, e.g. wcx64 (64)
:

After my post, I downloaded the version 8.0B1 and tried it (by backing up the program folder). It seems to be worked without problem for 64bit TC with the wincmd.ini of 32bit TC.

Best wishes

[MVV]

Plugins are pure DLLs, are not scripts at all. Applications may load only plugins with same bitness. When you install 32-bit plugin within TCx64, TC writes corresponding INI keys AND searches for 64-bit plugin version. If it finds one, it marks that plugin have 64-bit brother, and loads it.

However, I think TCx32 for portable use would be pretty enough, there no so much problems on 64-bit systems that require 64-bit TC, especially portable.

[HBB]

To MVV :

You wrote :

However, I think TCx32 for portable use would be pretty enough, there no so much problems on 64-bit systems that require 64-bit TC, especially portable.

I can run 32 bit applications in 32 bit environment and 64 bit applications in 64 bit environment in portable media.

I have a batch/vbs file for each program which has both 32 and 64 bit versions (This will be valid for TC from now on). The code in the batch/vbs file checks whether Windows\SysWOW64 directory exists or not and decide to run proper version of the program. Ofcourse, I always run related batch/vbs file of a program instead of running the program directly.

Regards.

[MVV]

You can do the same using just TCx32.

[HBB]

Really? How?

[MVV]

When you start script or batch from 32-bit version, it sees Windows\SysWOW64 folder too, so it can distinguish 32-bit and 64-bit version and start corresponding application.

[HBB]

Sorry MVV, I could not understand.

TC may understand the environment, but, I think it can not decide which application should be run (it does not know the exe-names and locations of 32 and 64 bit applications). Am I wrong?

How should the application/execution be defined in the script/batch?

[MVV]

When you start your script, it must know paths to 32-bit and 64-bit apps, correct?
It doesn't matter from which TC you start your script, it can check for folder Windows\SysWOW64 and start 32-bit or 64-bit application using path to it.

Code: Select all

@echo off
if exist %WINDIR%\SysWOW64 goto win_x64

:win_x32
start "" "%COMMANDER_PATH%\..\MyApp\x86\App.exe"
goto :EOF

:win_x64
start "" "%COMMANDER_PATH%\..\MyApp\x64\App.exe"
goto :EOF

This will work from both x32 and x64 TC.

[HBB]

This is same as the one that I did : The code decide which app should be run, not TC.

[MVV]

Yes, I was talking about same thing. It doesn't matter which TC do you use - x32 or x64, only script decides which app version to start.