Language cannot be changed and drive cannot be enabled
5 posts
Hello,
As a long-time user of RAM Disk, I just tried installing RAM File System on my Win 10 Pro 64-bit machine in parallel with RAM Disk, which is running flawlessly.
I have 2 issues:
1. Language cannot be changed
To my surprise the language (my Windows language is German) cannot be switched to English, which I prefer all the way. So the bubble is in English and the GUI is German. I tried to switch to German, exit the tool, run it once again, then change to English, close, and run again, but the language preferences don't do a thing.
2. No RAM File System can be enabled
I preconfigured drive letter S: with 16384 MB, no compression, and tried to enable it. Then I get error number 1, that I can't enable RAM File System. Surprisingly, after 5 minutes drive letter S: appears in Windows Explorer, but can't be accessed.
Is there a way to resolve these issues?
Thanks in advance,
Stani
Thanks for the detailed report - it's genuinely helpful.
1. Unchangeable language issue - fixed. You found a true bug. Internally, choosing "English" was being treated the same as "follow the Windows display language", so on your German system it kept coming back to German no matter what you selected. This fix will be added in the next update.
2. Drive S activation issue (error 1, then an inaccessible S: appears) - we have just reproduced this in our tests and found the root cause. It is in the interaction between RAM File System and RAM Disk at volume mount time: when an exFAT-formatted RAM Disk volume is present, Windows loads its exFAT driver after RAM File System has started, and from that point on Windows asks exFAT first about any new RAM File System volume. That probe fails, making Windows abandon the mount altogether - which is exactly your "error number 1", and also why the drive letter appears but stays inaccessible.
Could you please confirm your RAM Disk volume is formatted exFAT? That would match our reproduction exactly.
Hi Andrew,
Thanks for taking a look at these issues.
I use RAM Disk 26.7 with the following options:
- drive letter R:
- size: 16 GB
- file system: NTFS
- flags: DT
- no image file
- empty folders are created at startup
- no advanced settings are applied
RAM Disk R: is used for Windows Temp rerouting R:\Temp\
Could the issue be in that I use RAM Disk for temp files in parallel with trying to use RAM File System?
My error 1 message in RAM File System appeared instantly, without restarting Windows. After installation of RAM File System I did not need to restart my PC, so I configured drive letter S: and tried to immediately mount S:, which failed.
Unfortunately I uninstalled RAM File System, but when you have a beta version with new fixes, I will assist you in trying the bugfixes.
Best regards,
Stani
Just an update: we've consolidated four fixes addressing the issues you reported. If you could retest the new version 26.7.1, we'd really appreciate it.
Fixes:
- Fixed: Memory-mapped file writes could be lost, resulting in empty or corrupted output.
- Fixed: Applications requiring administrator privileges would not launch from a volume.
- Fixed: Renaming or moving files across a junction onto a volume could fail.
- Fixed: Volume creation could fail when exFAT or FAT32 volumes were present.
Thanks, Andrew!
The latest version is running now in parallel to RAM Disk. I swapped the drive letters to R: for RAM File System and S: to RAM Disk, this way I now switched to testing RAM File System. Language is properly fixed. The first benchmarks via MiniTool Partition Wizard show a massive increase in speed compared to RAM Disk.
Since I don't need explicit NTFS or exFAT emulation I will soon completely switch to RAM File System :)
Thank you for your dedication and good piece of software.
Best regards,
Stani