AssetX打不开
- Thread starter dopa
- Start date
Translated to English:
I installed version 3.3 of AssetX, but after installing it won't open and it shows that it has stopped working
and shows a column of
error codes like Application Error
Exception in module AssetX.exe EReadError at 00027D87.
Error reading RichEdit1.Lines.Strings: RichEdit line insertion error.
Try running the application as Administrator. This is a requirement for older applications such as AssetX, and PEV's Tools such as Images2TGA and PM2IM.
Or has the software stopped working?
Moderator comment:
Post translated by using Google Translate. Only post in English unless you are in a language specific forum.
That is possible. Have you tried reinstalling again?
Can you post in English, please? This is an English-speaking forum and it's helpful for all of us. There are is a forum available for Chinese speakers here:
Can you post in English, please? This is an English-speaking forum and it's helpful for all of us. There are is a forum available for Chinese speakers here:
Sorry, comrade, this is my first time using the Trainz forum to express my opinions.I've already tried that, and I installed all the scripts and other versions, but the prompt about the above transmitted code and the software being deactivated still appears.
Welcome to the forums. We try our best to assist users. The author of AssetX program passed away a few years ago and there's no longer any support for it.
I'm sorry if I couldn't help you, perhaps someone else will know the answer.
And here's your answer from another forum on the same subject.
The program no longer works with Windows 11 Pro and I will go out on a limb and say that this is Windows 11 in general.
It was working for me a few days ago in Win 11 Pro with a few minor issues. Since then I’ve had a major Windows update that may have broken it. I haven’t checked since I’m away from home and won’t be back until the end of the month.
That's possible. The last update was a security update. Enjoy your travels.
lackoo11111
Active member
I found a solution to run the software on Windows 11 x64 .
Settings > Time & Language > Language & Region > Administrative language settings > Change system locale
Then uncheck the box for Beta: Use Unicode UTF-8 for worldwide language support and restart your PC.
Settings > Time & Language > Language & Region > Administrative language settings > Change system locale
Then uncheck the box for Beta: Use Unicode UTF-8 for worldwide language support and restart your PC.
Dinorius_Redundicus
kuid 68213
My PC uses Windows 11 Home edition. AssetX has worked well for years and as recently as yesterday.
Bro, I know how to solve it. For Windows 11, go to Time & Language -> Language & Region -> Windows Display Language. There's an option for the language of non-Unicode programs; change that to English (United States) and it should run normally. This is a language encoding issue, probably caused by the Chinese language encoding not being considered during the design process. It's unrelated to memory, compatibility, or whether it's running in administrator mode. Most people on this forum are foreigners; their operating systems don't handle Chinese characters, so they can't reproduce our problem. I only discovered this by accident today.
Moderator comment:
Post translated by using Google Translate. Only post in English unless you are in a language specific forum.
Moderator comment:
Post translated by using Google Translate. Only post in English unless you are in a language specific forum.
Last edited by a moderator:
If you had a major upgrade for Windows 11, like 23H2 and lower become upgraded to 24H2 and newer, some things on some titles were not working as before after. Some may have been fixed, cannot say for sure if this one was ever relayed about the internet to get fixed.
AssetX works in my version of Win11 Pro which is 25H2. I'd be surprised if AssetX ever had any support for unicode and, given it is unsupported, nothing will change.
I still use AssetX on a daily basis and have written a couple of AXM macros to add/delete/modify any new or revised config tags. The help system, written in English, is quite good for explaining that.
N3V's config builder is very good for its purpose and I sometimes use it in conjunction with AssetX.
Post #11 above looks suspiciously like an AI generated post to me, or am I just paranoid?
I still use AssetX on a daily basis and have written a couple of AXM macros to add/delete/modify any new or revised config tags. The help system, written in English, is quite good for explaining that.
N3V's config builder is very good for its purpose and I sometimes use it in conjunction with AssetX.
Post #11 above looks suspiciously like an AI generated post to me, or am I just paranoid?
这种目前只在简体中文Windows操作系统被报告出现，因为微软在简体中文中文操作系统中采用GBK编码格式而非ASCII，GBK使用双字节编码方式，可能在编程不当的情况下出现内存溢出导致程序崩溃
目前中国香港特别行政区和中国台湾省以及日本和韩国尚未出现报告，但中国香港特别行政区和中国台湾省的繁体中文Windows操作系统使用的BIG5编码格式、日本使用的Shift_JIS编码格式以及韩国使用的EUC-KR编码格式同样可能同样出现相同问题，但我未进行测试
目前看来更换非Unicode编码为英语（美国）为较简便解决方式，此操作能强制让AssetX使用ASCII编码从而解决此问题，彻底解决可能需要对原版软件重新编译强制使用UTF-8为标准字体编码格式以解决此问题，但鉴于原作者已经仙逝，可能需要社区创作者进行软件逆向工程以解决
This issue has only been reported in the Simplified Chinese version of the Windows operating system so far. Microsoft uses the GBK encoding format instead of ASCII in the Simplified Chinese version of the operating system. GBK uses a double-byte encoding method, which may cause memory overflow and program crashes if the programming is incorrect.
So far, no reports have been made in Hong Kong Special Administrative Region of China, Taiwan Province of China, Japan, and South Korea. However, the Traditional Chinese Windows operating system in Hong Kong and Taiwan uses the BIG5 encoding format, while Japan uses the Shift_JIS encoding format and South Korea uses the EUC-KR encoding format. These encoding formats may also have the same problem, but I have not tested them.
At present, changing the non-Unicode encoding to English (United States) seems to be a relatively simple solution. This operation can force AssetX to use ASCII encoding and solve the problem. A complete solution may require recompiling the original software to force the use of UTF-8 as the standard font encoding format to solve the problem. However, since the original author has passed away, it may require community creators to perform software reverse engineering to solve it.
因为我是一个中国人，题主提问时也是采用中文提问，我选择直接使用中文进行回复，然后社区管理员为了保证“社区和谐”使用谷歌翻译（翻译中文是一坨屎）进行了强制转换，导致其看起来可能像一个AI的回复AssetX works in my version of Win11 Pro which is 25H2. I'd be surprised if AssetX ever had any support for unicode and, given it is unsupported, nothing will change.
I still use AssetX on a daily basis and have written a couple of AXM macros to add/delete/modify any new or revised config tags. The help system, written in English, is quite good for explaining that.
N3V's config builder is very good for its purpose and I sometimes use it in conjunction with AssetX.
Post #11 above looks suspiciously like an AI generated post to me, or am I just paranoid?
顺便说一下，谷歌翻译在中国有一个别名叫谷歌生草机，在中国视频网站Bilibili上甚至有一批人专门制作视频展示一句话在用谷歌翻译多次转换后有多么荒谬的脱离句子原意来逗人发笑
Because I am a Chinese person and the questioner asked the question in Chinese, I chose to reply directly in Chinese. Then, the community administrator, in order to ensure "community harmony", used Google Translate (which translated the Chinese into a mess) to force a conversion, making it look like an AI's response.
By the way, Google Translate has a nickname in China called "Google’s ‘grass-growing’ translation machine". On the Chinese video website Bilibili, there is even a group of people who specifically make videos to show how absurdly far a sentence can deviate from its original meaning after being translated multiple times by Google Translate, just to make people laugh.