It is unlikely that this is LogMeTT issue because LogMeTT acts just as a wrapper for TeraTerm Macros. When you run macro from LogMeTT, the macro is exported into temporary .ttl file, custom .ini file is being created and then LogMeTT starts TeraTerm by executed the Windows shell command :
- ttermpro /F="<path_to_Temp_TTL>\<custom_ini_file>" /M="<path_to_Temp_TTL>\<temp_ttl_file>"
Still, lets try to troubleshoot this. Assuming you are using LogMeTT 2.9.7; follow these steps:
1) Start LogMeTT
2) Open Windows File Explorer and goto directory Temp_TTL. This directory is located in the folder
C:\Documents and Settings\<user>\Local Settings\Application Data\LogMeTT on
Windows XP or in
C:\Users\<username>\AppData\Local\LogMeTT on
Vista and
Windows 7. Make sure Temp_TTL directory is empty, if not - manually delete all the files in it.
3) Run your macro from LogMeTT. If it does not freeze, close TeraTerm, delete the content of Temp_TTL and try again.
4) Repeat the previous step until you get "frozen" macro.
5) Check Temp_TTL folder. It should contain 2 files - one .ttl and one .ini file.
6) Open .ttl file in Notepad and make sure the Macro code is correct.
7) Compare .ini file from Temp_TTL with the default teraterm.ini file. There may be differences related to font name/size/color but SSH part should be the same.
8) Finally, open Windows Command line prompt, go to TeraTerm home directory and execute the command (make sure you have all double quotes in place):
- ttermpro /F="<path_to_Temp_TTL>\<custom_ini_file>" /M="<path_to_Temp_TTL>\<temp_ttl_file>"
Check if the macro freezes again. Repeat this step several times to collect more results.
Let us know about your findings.