Rxfcv.sys is part of PrimoCache and developed by Romex Software according to the rxfcv.sys version information. Rxfcv.sys's description is 'PrimoCache Driver' rxfcv.sys is digitally signed by Shanghai Romex Information Technology Co.,Ltd. Rxfcv.sys is usually located in the 'C: Windows system32 drivers ' folder. Fancyrd.sys is part of Primo Ramdisk Ultimate Edition and developed by Romex Software according to the fancyrd.sys version information. Fancyrd.sys's description is 'Primo Ramdisk (Ult) Controller Driver' fancyrd.sys is digitally signed by SmartSource Shanghai Electronic Technology Co. Note: This is a driver-resigning version to v2.7.0, so all internal versions keep to '2.7.0' instead of '2.7.2'. Version 2.7.0 (2016-12-07) Fix bug: Incompatible issue with some network adapters in Windows 10 build 14393, resulting in BSOD at bootup or network failure. Download Romex for iOS to mit dieser App knnen Sie bequem durch das ROMEX Produktsortiment blttern.Durch die eingebaute Produktempfehlung gelangen Sie direkt zum richtigen.No Video
Romex Software Drivers
Software caching scheme that cooperates with system memory to provide data caching for disksSoftware caching scheme that cooperates with system memory to provide data caching for disks
PrimoCache is a software caching scheme that offers data caching for physical disks by cooperating with the system memory, SSDs and flash drives.
With PrimoCache you can experience a dramatic increase in system performance as it stores diks data into fast cache devices (for example the system memory). Any future request for the stored data is served right from the cache, thus a lot more faster, reducing access time.
The application offers a two-level caching architecture. The primary (level-1) cache is formed of physical memory while the secondary (level-2) cache relies on SSDs, flash drives and other similar storage devices.
You can set PrimoCache to use only one of the included cache configurations or both of them.
- 90-day trial period
- File size:
- User Rating:
- Editors' Review:
My corporate laptop has 6 GB of RAM installed, but, only sees 3 GB of logical RAM. Why? My corporate IT departmentimages laptops with the 32-bit flavor of Windows 7.
As you can see in this screenshot from my Control Panel’s System information applet, installing more memory hits a glass ceiling with Windows at ~3GB.
My laptop has 6 GB of physical RAM installed, yet my user applications have access to less than half of the physical memory!
Hacking a Solution: “Physical Virtual Memory”
Fortunately, there is a solution to this problem. It’s a hack and it uses a reasonably priced piece of 3rd party commercial software.
The solution combines a feature of Windows known as Physical Address Extensions (PAE) in tandem with a RAMDISK as the storage “disk” for the virtual memory paging file. The result is a total hack – we’re using a page file to expose the address space of physical memory. It’s “physical virtual” memory. An oxymoron if I ever heard one!
A commercial software package called Primo Ramdisk Standard by Romex Software is needed to create the Ramdisk. It’s $30/seat.
This is the only Ramdisk driver I could find that:
- Supports Windows 7
- Supports PAE
- Supports the Intel/AMD physical memory remapping (“Invisible Memory”) chipset feature (read more)
- Not flagged as a removable storage device by our corporate data loss prevention nanny software
Indeed, the performance of this hack to use “physical virtual memory” will be less than just using a 64 bit O/S with it’s address space of 264 bytes. Nevertheless, paging to a RAMDISK will always beat paging to a magnetic hard drive, and will probably beat paging to a SSD disk as well.
I speculate there are a number of very good reasons why corporate IT would deploy 32-bit over 64-bit – availability of 64-bit client software for VPNs, anti-malware, remote backup agents, remote support agents, encryption policy engines; the difficulty in recreating and testing a new image from scratch; the density of older 32-bit laptops still in use.
Caveat Emptor: You must disable hibernation mode. Hibernating sporadically crashes upon shutdown or startup when using this hack. The good news is you will not miss much. My laptop clocked faster times with a normal shutdown/startup cycle compared to the time required to enter and exit hibernation. The disk IO was just too slow to copy 6 GB of RAM contents to into and out of the C:hiberfil.sys hibernation file.
This setup was tested successfully for over one year on a Lenovo ThinkPad T410 with 6 GB of RAM (2 GB +4 GB DIMMS) as well as one year on a Lenovo T420s with 8 GB of RAM. Please test your setup. Should your machine fail to restart after following below steps, you should boot into Windows Safe Mode and disable/uninstall the RAMDISK driver and paging file.
Setup (8 steps)
Enable PAE in the Windows boot options, disable hibernation in the power options for Windows, and reboot the system.
Run the following commands in Command Prompt (cmd.exe). Note this will force a restart in 30 seconds, so save your work.
Install the commercial software Primo Ramdisk Standard by a vendor named Romex. There is a $30/seat license cost. Romex offers a 30 day free trial.
Launch the Primo Ramdisk configuration program. (“%ProgramFiles%Primo Ramdisk Standard EditionFancyRd.exe”)
Launch the dialog to configure “Invisible Memory Management”
Click the icon in the lower right corner of the configuration program that resembles an blue SD Card and a yellow wrench. On the dialog, click the “Enable IM” button. The default options worked successfully a Lenovo ThinkPad T410 (BIOS) and a Lenovo T420s (UEFI). See the Romex documentation on front-end/back-end reserve if you experience video card problems on your hardware.
Define a new RAMDISK
a) Take note of the maximum amount of available invisible memory as displayed in the lower right hand corner of the main window. This will be the size of the RAMDISK.
b) Click the “Create a new disk” toolbar button to define a new persistent RAMDISK
c) Select “Direct-IO” as the disk type. This is the faster of the two options. Also, Credant will only ignore this device type.
Romex Software Driver
d) Assign a drive letter of “Z”. This can be changed, however, a later step will need to be manually adjusted.
e) Leave “One Time Disk” unchecked to make this disk persistent across boots.
f) On the next dialog screen, enable the option for “Use Invisible Memory”. Leave all other options unchecked/disabled.
g) On the final dialog screen, select the FAT32 format and label the device “RAMDISK”.
Modify Windows’ Virtual Memory settings
a) Run “sysdm.cpl” to open System Properties
b) Open the virtual memory dialog by selecting Advanced > Performance > Settings > Advanced > Virtual Memory > Change
c) Uncheck/disable “Automatically manage paging file size for all drives”
d) Select the “C:” drive in the drive list, and select the “No paging file” option. Click the Set button.
e) Select the “Z:” drive in the drive list, and select “Custom” size of X for initial and maximum, where X is the space available listed for the drive. You may need to slightly reduce X by ~5 megabytes.
f) Click the “Set” button and confirm your settings resemble the screenshot below. Click the “Ok” button.
Hide the Z: drive from Explorer
Windows will be very annoying about the Z: drive being full. You can hide this drive from Explorer and the common dialogs with the following registry setting. Note you can still explicity access this drive with a full file path in any open/save dialog (e.g., Z:folderfile.ext). If you changed the drive letter for the RAMDISK from Z: to something else, you will need to adjust the hex value of the registry key (see TechNet for the correct hex value).
Run the following commands in Command Prompt (cmd.exe):
It’s Windows, why not throw in a reboot?
My Windows setup recommends 3 GB of virtual memory. I’d like to try upgrading my physical RAM from 6 GB to 8GB. This would let me add another gigabyte to the paging file. It would also leave another 1 GB of free space on Z:. I’m considering using this free space as a NTFS junction point with “%TEMP%” and “%SYSTEMROOT%TEMP” to make the temp folders both fast and non-persistent between reboots. (Junction points are the Windows equivalent of *nix symlinks for directories. You can use the Sysinternals utility junction.exe or the Primo Ramdisk utility to define junction points.)
I also want to test setting my IIS document root to Z: to make tests of deployment packages lightning fast (i.e., relocating the IIS document root from C:inetpub to Z:inetpub). This will make disk I/O way faster for copying scores of little image and text files. It also forces me to run an automated build/package/deploy between reboots (since Z: is wiped between reboots).