Environment
馃獰 Windows
System
Windows 11 25H2
Describe the problem
When using this convenient tool on Windows, I found that "Start SillyTavern" launches another batch file (.bat) via the call command. This causes Windows to call a new cmd.exe launcher instead of the Windows 11 Terminal.
For me, the new cmd cannot display Chinese characters correctly because it lacks a code page (chcp).
My solution was to simply add "chcp 65001 > nul" to each batch script, which sets the batch's code page to UTF-8.
Another solution is to create a new string entry named "Autorun" in the registry (regedit.exe) under "HKEY_LOCAL_MACHINE\Software\Microsoft\Command Processor" and set its value to "chcp 65001 > nul". This also solves the problem, but it's a permanent change for all cmd scripts.
I did not submit a pull request for the following reasons:
-
I am unsure if this is an isolated case I encountered.
-
I am unsure if this issue applies to other multi-language systems.
-
I'm not sure if this issue is limited to Windows 11.
Ultimately, I think submitting an issue would be good, and I believe a solution to this minor bug could be included in the documentation.
Additional info
No response
Please tick the boxes
Environment
馃獰 Windows
System
Windows 11 25H2
Describe the problem
When using this convenient tool on Windows, I found that "Start SillyTavern" launches another batch file (.bat) via the
callcommand. This causes Windows to call a new cmd.exe launcher instead of the Windows 11 Terminal.For me, the new cmd cannot display Chinese characters correctly because it lacks a code page (chcp).
My solution was to simply add "chcp 65001 > nul" to each batch script, which sets the batch's code page to UTF-8.
Another solution is to create a new string entry named "Autorun" in the registry (regedit.exe) under "HKEY_LOCAL_MACHINE\Software\Microsoft\Command Processor" and set its value to "chcp 65001 > nul". This also solves the problem, but it's a permanent change for all cmd scripts.
I did not submit a pull request for the following reasons:
I am unsure if this is an isolated case I encountered.
I am unsure if this issue applies to other multi-language systems.
I'm not sure if this issue is limited to Windows 11.
Ultimately, I think submitting an issue would be good, and I believe a solution to this minor bug could be included in the documentation.
Additional info
No response
Please tick the boxes