SoftPerfect Support Forum
Show all posts by user
Re: RAM File System and Minifilters
7 days ago, by Andrew in RAM Disk & RAM File System Forum
It should work with any antivirus, not only Defender. With this option Windows attaches no file system filters to the volume at all, and that is how practically every antivirus scans files on access. Protection that doesn't rely on a file system filter, such as checks when a program starts, still applies.
Re: RAM File System and Minifilters
7 days ago, by Andrew in RAM Disk & RAM File System Forum
Good news: Windows does accept it. A RAM FS volume can tell Filter Manager that it is a trusted Dev Drive with no trust record, and Filter Manager then attaches no filters to it at all, antivirus included. We only borrow that part of the mechanism, so the volume does not otherwise behave as a Dev Drive. There is a test build for you to try. It installs over the current version. After a reboot o
Re: RAM File System and Minifilters
13 days ago, by Andrew in RAM Disk & RAM File System Forum
Unfortunately it doesn't quite work that way. InstanceSetupCallback belongs to each minifilter, not to the file system underneath it. When Filter Manager offers a new volume to Defender or any other filter, it's that filter's own callback that decides whether to attach, and RAM File System has no say in it. A file system has no supported way to tell Windows which filters may attach to its volumes.
Re: Information about changes in pre-releases
14 days ago, by Andrew in WiFi Guard Forum
Sorry, that's not something we can do. Pre-releases are one-off builds made for the users who reported a specific problem; what each such build fixes/changes may be contained in a private support ticket, not just on the public forum. The vast majority of our support communications are private. Normally people post on the forum only when they believe their message can be of benefit to all other use
Re: Product name accuracy: it detects devices in all networks, not just Wi-Fi
14 days ago, by Andrew in WiFi Guard Forum
Wi-Fi Guard does have the ability to scan wired and wireless networks, but its name purposefully has two words: Guard is what it does, Wi-Fi is where most of the guarding happens. Surreptitious plugging into someone's Ethernet is not a frequent occurrence. So in practice an unknown device turning up uninvited is almost always on Wi-Fi. Scanning a wired network segment as well as Wi-Fi isn't th
Re: Suggestion: indicate the OS/hardware that new release affects
14 days ago, by Andrew in RAM Disk & RAM File System Forum
That's a fair point and we'll make it clearer from now on. For RAM FS 26.9 specifically: it was the first release to support macOS, and the macOS build arrived with the full feature set of the Windows version. That's what the first line means. Everything else listed under 26.9 is a change to the Windows version only, which is why some of it reads as already being there. Future changelogs will s
Re: Suggestions for ramfsctl CLI
24 days ago, by Andrew in RAM Disk & RAM File System Forum
Adding those to create would really just turn it into auto add plus mount. The main window and autosave both work from a volume's stored settings: the window lists them, and the saver reads them to know which folder to write back to and how often. create deliberately stores nothing, so there's nothing for either of them to find, and a create that stored its settings would be exactly auto add follo
Re: Suggestions for ramfsctl CLI
25 days ago, by Andrew in RAM Disk & RAM File System Forum
I went through the source on that one. The check that produces the busy error is identical in versions 26.8.1 and 26.9, and the only thing 26.9 changed about it actually makes it more permissive. So neither the upgrade nor your script is at fault: something had your folder open this time that didn't last time. Worth knowing though, and it makes the whole thing moot: auto add is a one-off. The r
Re: Suggestions for ramfsctl CLI
26 days ago, by Andrew in RAM Disk & RAM File System Forum
Glad it helps! Regarding create, no it is still the one-off that stores nothing, so it has no autosave and doesn't show in the main window. mount is the one to use, and having several projects is fine. Give each project its own letter once ramfsctl auto add P 8G ProjectA manual autosave period=300 source=C:\Work\ProjectA ramfsctl auto add Q 8G ProjectB manual autosave period=300 source=C:\Wor
RAM Disk doesn't retain its window size - Fixed
28 days ago, by Andrew in RAM Disk & RAM File System Forum
Thanks for the report. You came across a genuine bug: the main window was being resized to a fixed default width every time it was shown, which is why it reset on launch, on a language change, and also when restored from the tray. We have just fixed this small oversight. Please download the latest build and install over your current version. It now remembers the size between runs, along with th
Re: RAM FS lifetime statistics
30 days ago, by Andrew in RAM Disk & RAM File System Forum
That's a fair way to think about it, and it isn't an unreasonable thing to ask for in principle. Let me explain where we draw the line, because it isn't arbitrary. We're deliberately sparing with switches. An option is permanent once it exists: it has to be honoured in the driver, kept working across every Windows build, documented, tested and supported for years. A few dozen individually reaso
Re: VirusTotal shows trojan detections
4 weeks ago, by Andrew in RAM Disk & RAM File System Forum
There are no trojans in any of our products. What you are seeing is a false positive. It is a common erroneous flag for this class of software. Why it happens: RAM Disk and RAM File System both install a kernel driver, which heuristic and machine-learning malware detection engines treat as inherently suspicious. They can flag a new build simply for its reputation ("freshness" rather t
Re: RAM FS lifetime statistics
4 weeks ago, by Andrew in RAM Disk & RAM File System Forum
There's no switch for it in either product, which is why you couldn't find a registry key. The counting is built into the driver. It costs practically nothing though. Each read or write bumps a couple of counters in a per-CPU slot, with no locks and no atomic operations, so it doesn't even register against the memory copy it's counting. A background thread adds those slots up once a second and
Re: RAM FS lifetime statistics
4 weeks ago, by Andrew in RAM Disk & RAM File System Forum
Thank you for reporting the error. We recently moved to a new installer builder, which changed how a 32-bit installer finds the Windows system folder from script code. This led to the new interface talking to the old driver, which knows nothing about the new reset command. Hence Error 1. It is now rebuilt as a 64-bit installer, so fresh downloads are unaffected. In you case, you don't need to r
Re: Suggestions for ramfsctl CLI
4 weeks ago, by Andrew in RAM Disk & RAM File System Forum
Both are implemented in version 26.9, released today. ramfsctl mount <letter> mounts a volume from its stored recipe, the same one auto add creates, so size, source and autosave do not have to be repeated on the command line the way create requires. Pair it with manual on the auto add line and the volume never mounts at boot, only when you call mount: ramfsctl auto add V 8G Work manual a
Re: Example of how to use Telnet
4 weeks ago, by Andrew in Network Scanner Forum
The Telnet object went away because Python made it redundant. Remote Python arrived in v25.8 and it runs a real CPython installation rather than an interpreter, so socket and anything you install with pip are already available to a script. There is no longer much point in us wrapping a protocol in a custom object. Set one up under Options → Remote Python. The dialog tells you whether an interpr
Re: Suggestions for ramfsctl CLI
5 weeks ago, by Andrew in RAM Disk & RAM File System Forum
Good news: what you describe is exactly what Folder Mirroring does, added in version 26.8.1. No scripting needed, the driver does the whole swap itself. In the Add Volume dialog, click Use a source folder instead and pick your project folder, tick Save changes at shutdown, and in Advanced tick Save changes every (minutes) if you want periodic write-back. That is the power loss protection you wa
Re: Memory reclamation speed in SoftPerfect RAM Disk
5 weeks ago, by Andrew in RAM Disk & RAM File System Forum
Good news: in RAM Disk version 26.7 we shortened the reclaim delay considerably. Memory freed by deleting files now comes back within about 10 to 15 seconds on NTFS, where previously it took around 70 seconds. On exFAT it takes a little longer, roughly half a minute, because Windows does not report deleted blocks through TRIM on an exFAT volume, so the driver scans the allocation bitmap itself and
Re: Compliments to SoftPerfect RAM Disk software
5 weeks ago, by Andrew in RAM Disk & RAM File System Forum
Thank you for the kind words! We do put a lot of care into RAM Disk and have further plans for its development and improvement. If you ever get any ideas or suggestions, simply post them here - and we'll take a look. Welcome aboard, and enjoy our software!
Re: RAM FS indexing with Voidtools "Everything"
6 weeks ago, by Andrew in RAM Disk & RAM File System Forum
The automatic NTFS entry is what gets in the way. Here is our test setup: RAM FS sits on drive Z and Everything keeps adding Z to its NTFS list because the volume reports itself as NTFS. Even if you can't remove it there, you can tell Everything to ignore it. There are two changes to make in Tools - Options: Indexes - NTFS: select the RAM FS drive in the list of local NTFS volumes, then untick
Re: Windows tweaks for increasing RAM FS performance
6 weeks ago, by Andrew in RAM Disk & RAM File System Forum
The same applies to RAM Disk, at it also keeps its data in locked physical memory, so none of those three keys would change anything for it, and the advice above about what you put on the volume is the same. One thing that is more effective than any registry key: if you are on a multi-socket machine (with several CPU sockets), set the NUMA node under Advanced in the Add/Edit Disk dialog, so the
Re: RAM FS lifetime statistics
6 weeks ago, by Andrew in RAM Disk & RAM File System Forum
Those numbers are real, and TB is exactly what CrystalDiskMark produces on a RAM FS volume. It doesn't just write the test file once and then stop. Instead, it hammers the volume for the full measurement time of every single test, so the real extend of test data has very little to do with whether you picked 1 GB or 8 GB. We measured it here, using the same DiskSpd engine CrystalDiskMark drives,
Re: Windows tweaks for increasing RAM FS performance
6 weeks ago, by Andrew in RAM Disk & RAM File System Forum
Your understanding in correct, and the short answer is that there are no Windows registry keys worth touching for the RAM File System. The reason is in how it works. RAM FS keeps all file data and metadata in nonpaged kernel memory, which Windows never pages out and never runs through memory compression, so disabling the paging executive or memory compression changes nothing for it. It also byp
Re: RAM FS lifetime statistics
7 weeks ago, by Andrew in RAM Disk & RAM File System Forum
It could be an interesting metric, noted for a future update. On a related note, RAM FS was designed from the start to minimise SSD writes, both for disk longevity and performance. Periodic and shutdown saving to an image file only writes the changed data in 2 MB blocks, rather than rewriting the whole image. Folder mirroring works the same way: only changed blocks within a file are written bac
Re: RAM FS lifetime statistics
7 weeks ago, by Andrew in RAM Disk & RAM File System Forum
You're right, and thank you - that's a genuine bug, which we've now reproduced and identified here. The counters are updated by a background task that periodically adds up the traffic of the mounted volumes. While a dismount was being attempted, the volume briefly dropped out of that sum, and when the attempt was refused and the volume came back, its traffic was added a second time. So you were
Re: RAM FS lifetime statistics
7 weeks ago, by Andrew in RAM Disk & RAM File System Forum
No, unmounting itself shouldn't add anything. The numbers should climb only when a process reads or writes files on a RAM FS volume - that's all they measure. Unmounting shouldn't subtract anything either: when a volume goes away, its data is gone, but the totals already counted should stay where they are, since they're a lifetime record of I/O rather than a picture of what's currently mounted.
Re: RAM FS lifetime statistics
7 weeks ago, by Andrew in RAM Disk & RAM File System Forum
Both numbers are lifetime totals for all your RAM FS volumes, accumulated since installation. They survive dismounts and reboots, so they only ever go up. Processed X MB of data - all file data that has passed through RAM FS volumes: reads and writes. Saved your storage from Y MB of additional wear - only the writes. Without RAM FS, storing those files on a physical drive would mean those by
7 weeks ago, by Andrew in RAM Disk & RAM File System Forum
Thank you for the feedback - the two things you noticed are connected, so let me explain how it works and what we'd suggest. Why the chosen source folder itself doesn't appear on the RAM FS drive When you create a volume with a source folder, e.g. C:\Test, that folder itself becomes the volume. Your C:\Test is set aside and is replaced with a link pointing at the RAM FS drive. So C:\Test\rep
RAM FS doesn't see that the drive letter is already used by VMware Shared Folder - Fixed
7 weeks ago, by Andrew in RAM Disk & RAM File System Forum
Thank you for the clear steps and the screenshot - it reproduced here exactly. With shared folders switched off in VM, the mapping stays remembered. Windows Explorer still shows it, and it reclaims the letter as soon as sharing is switched back on, but no device answers on that letter, so the usual Windows checks reported the letter as free and allowed RAM FS to offer it. In the latest buil
'Display Speed in Taskbar' re-enables itself on process start - Fixed
7 weeks ago, by Andrew in NetWorx Forum
Thanks for the detailed report. This looks like a bug, not anything you did. NetWorx still carries a one-time migration from the old taskbar deskband to the current widget. At startup it asks the shell whether the legacy deskband is still showing; if so, it hides it and switches the widget on, saving that to the database. That save is the problem - it can overwrite your own setting on every lau