Following community recommendations, I downloaded AIM Toolkit from SourceForge for its Windows 11‑compatible ramdisk feature. The tool is concise, handy and works well.
As a Chinese user, I found the original built‑in Chinese localization incomplete. I've translated and supplemented the language resources. The revised file is attached.Includes both Simplified‑Chinese and Traditional‑Chinese language files.
@w77 As a regular user, I stick to the default "Virtual" for Memory Type. While Virtual supports dynamic memory allocation, the documentation states "Large‑page is only available for dynamic memory allocation". This appears inconsistent.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thanks for this update. It will be integrated in the next release. However, I restored the line breaks you removed in tchinese.txt. They are important if I have to make a change in all the language files.
About the memory types:
The dynamic memory allocation is an extension ("proxy") to the driver, located in RamDyn.exe.
Like the driver, it supports virtual and physical (AWE) memory allocation, but also large page which is another type of physical memory. Large page is handled by the extension but not the driver itself.
Thanks for pointing this out and restoring the line‑breaks.
I failed to do a thorough check before submitting the file. I now understand line‑break positions need to be consistent for your batch‑editing workflow.
For future updates I will double‑check both line breaks and terminology.
Also, if there are doc changes or new features before a release, please notify me ahead of time.
I can update the translations so the localization stays fully aligned with the software, preventing mismatched text after release.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thanks. With Imdisk Toolkit, I spent hours to contact each translator (with sometimes different channel communication) and then verify there was no bug for each file received... This was too much work for me, so I stopped that with AIM Toolkit.
Now, I let translators propose new translation or update.
That said, it may take a while before a new translation is required. The next version will focuse on the issue described here, with the use of DevIoDrv in RamDyn as new communication method with the driver. Not a big rewrite, but still rather difficult...
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I totally understand the heavy workload with translators.
Take your time with the DevIoDrv change for RamDyn.
I'll watch for updates and update Chinese localization when new texts arrive.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Following community recommendations, I downloaded AIM Toolkit from SourceForge for its Windows 11‑compatible ramdisk feature. The tool is concise, handy and works well.
As a Chinese user, I found the original built‑in Chinese localization incomplete. I've translated and supplemented the language resources. The revised file is attached.Includes both Simplified‑Chinese and Traditional‑Chinese language files.
@w77 As a regular user, I stick to the default "Virtual" for Memory Type. While Virtual supports dynamic memory allocation, the documentation states "Large‑page is only available for dynamic memory allocation". This appears inconsistent.
Thanks for this update. It will be integrated in the next release. However, I restored the line breaks you removed in tchinese.txt. They are important if I have to make a change in all the language files.
About the memory types:
The dynamic memory allocation is an extension ("proxy") to the driver, located in RamDyn.exe.
Like the driver, it supports virtual and physical (AWE) memory allocation, but also large page which is another type of physical memory. Large page is handled by the extension but not the driver itself.
Thanks for pointing this out and restoring the line‑breaks.
I failed to do a thorough check before submitting the file. I now understand line‑break positions need to be consistent for your batch‑editing workflow.
For future updates I will double‑check both line breaks and terminology.
Also, if there are doc changes or new features before a release, please notify me ahead of time.
I can update the translations so the localization stays fully aligned with the software, preventing mismatched text after release.
Thanks. With Imdisk Toolkit, I spent hours to contact each translator (with sometimes different channel communication) and then verify there was no bug for each file received... This was too much work for me, so I stopped that with AIM Toolkit.
Now, I let translators propose new translation or update.
That said, it may take a while before a new translation is required. The next version will focuse on the issue described here, with the use of DevIoDrv in RamDyn as new communication method with the driver. Not a big rewrite, but still rather difficult...
I totally understand the heavy workload with translators.
Take your time with the DevIoDrv change for RamDyn.
I'll watch for updates and update Chinese localization when new texts arrive.