Diacritics in Windows username break TMS Smart Setup

TMS TMS Smart Setup
1

I am trying to install TMS FNC Core and TMS FNC UI Pack using TMS Smart Setup GUI. Everything goes fine but the win64xintel version is not installed. It seems to me that the problem is the user name in diacritics, it's Ľubo, but in the LOG file it shows as ¦Żubo or ?ubo. On the second PC where I have the user name Lubo, it's all OK.

The error is:

=== Build Summary ===
[INFO ] [2026-01-19 10:23:50.768] - TMS FNC Core 4.2.2.2
[INFO ] [2026-01-19 10:23:50.768] - Delphi 13
[INFO ] [2026-01-19 10:23:50.768] - win32intel -> OK.
[INFO ] [2026-01-19 10:23:50.768] - win64intel -> OK.
[INFO ] [2026-01-19 10:23:50.768] - win64xintel -> FAILED.
[INFO ] [2026-01-19 10:23:50.768] - TMS FNC UI Pack 7.1.0.1
[INFO ] [2026-01-19 10:23:50.769] - Delphi 13
[INFO ] [2026-01-19 10:23:50.769] - win32intel -> OK.
[INFO ] [2026-01-19 10:23:50.769] - win64intel -> OK.
[INFO ] [2026-01-19 10:23:50.769] - win64xintel -> FAILED.

………..

TMSFNCCorePkg.dpk(55): error F1026: File not found: 'C:\Users?ubo\AppData\Local\TMS Setup\Temp\p\tms.fnc.core_d13_win64xintel_Release\6818EC6BFF954F2F81C5F15ED364B48C\j5o0' [C:\Users\¦Żubo\AppData\Local\TMS Setup\Temp\p\tms.fnc.core_d13_win64xintel_Release\TMSFNCCorePkg.dproj]
Done Building Project "C:\Users\¦Żubo\AppData\Local\TMS Setup\Temp\p\tms.fnc.core_d13_win64xintel_Release\TMSFNCCorePkg.dproj" (Build target(s)) -- FAILED.

Build FAILED.

"C:\Users\¦Żubo\AppData\Local\TMS Setup\Temp\p\tms.fnc.core_d13_win64xintel_Release\TMSFNCCorePkg.dproj" (Build target) (1) ->
(_PasCoreCompile target) ->
TMSFNCCorePkg.dpk(55): error F1026: File not found: 'C:\Users?ubo\AppData\Local\TMS Setup\Temp\p\tms.fnc.core_d13_win64xintel_Release\6818EC6BFF954F2F81C5F15ED364B48C\j5o0' [C:\Users\¦Żubo\AppData\Local\TMS Setup\Temp\p\tms.fnc.core_d13_win64xintel_Release\TMSFNCCorePkg.dproj]

0 Warning(s)
1 Error(s)
..........
Smart Setup Installation Troubleshooting
2

Please go through the troubleshooting steps first, then report in a separate topics what the issue is:

3

Hi,

This is currently a limitation in smartsetup, you need to install to a path with ASCII characters. The problem is that delphi command line tools are different ages and use different encodings. Specifically in Delphi 13 they started used resinator as resource compiler, and it expects a utf8 encoding. But other tools expect the machine’s windows encoding, and you get this kind of mixup. We’ve been investigating how to fix this for a while, but when we workaround one problem, we break a different thing. Not sure if we are going to be able to really get this to work, maybe we will just add a warning when you try to run from a path that has non-ascii characters. (we already give you one if you try to run from a path that has a folder starting with a dot, since that breaks delphi’s brcc32).

The workaround is simple: uninstall smartsetup, create a folder like c:\tms, and unzip tms.exe and tmsgui.exe from our portable install

Having a shorter path will also help keeping library paths smaller, which is an extra advantage.

4

Thank you for a very simple and helpful solution.

5

Rad Studio 13 64bit Modern shows a lot of errors while working. When I added TMSFNCRibbon1 to the project it could be compiled but it could not be run from the Rad Studio environment (only my environment) and it showed the error Debug Kernel is not responding. Terminate the debug process?
Invalid Process ID: 0
[00007FFAC8C8B5C3]{exceptiondiag370.bpl} Jcldebug.TJclStackInfoList + $153
[00007FFAC8C8AE88]{exceptiondiag370.bpl} Jcldebug.JclCreateStackList + $48
......
Is there any point in doing anything in this environment, what are your experiences?

6

I am not personally using the 64 bit IDE regularly, but I know it is a mixed bag. I haven't seen too many issues, but some customers do.

About the ribbon, I tried to launch a simple app with a TMSFNCRibbon from the 64bit IDE and it worked as expected. Could this be related to JclDebug?

7

I use c++ and I don't have the JCL = Jedi Code Library there.

I tried it with DELPHI and it works fine there even under DEBUG. It looks like a problem with RAD STUDIO 13(10.6.3.11) c++ version.