Primo Ramdisk Known Issues List

[support]

Last Updated: 2012-06-25

#001 Direct-IO virtual disks are not compatible with VHD (Microsoft Virtual Hard Disk format) files tasks and cause system crash (Blue Screen).
Description: Right click on Disk Management (Control Panel -> Administrative Tools -> Computer Management), and click on Create VHD or Attach VHD. If you choose Direct-IO virtual disks as VHD file locations, the task of creating/attaching VHD will fail and cause system crash.
Workaround: Use SCSI virtual disks instead of Direct-IO disks.

#002 System cannot resume from hibernation if Windows pagefile.sys is set to a virtual disk which uses Invisible Memory. [Issue cannot be fixed]
Workaround: Do not set pagefile.sys to such virtual disk. Alternatively, disable hibernation.

#003 (Vista/7) Windows explorer displays wrong "Size on disk" for files on Direct-IO virtual disks.
Description: Whatever cluster size is selected for volumes of Direct-IO disks, Windows explorer always calculates “Size on disk” based on a cluster size of 512 bytes. This issue only affects the looks of the property. It doesn't affect any functionality of the file system.

#004 Windows do not assign drive letters for SCSI virtual disks after computer reboot if image/substance files for virtual disks are located on external (USB etc.) disks or Dynamic disks, or on partitions of which file systems are not same as boot file system.
Description: Such disks/partitions get ready a little later than normal disks at computer boot-up. In Windows vista/7/2008, this issue only happens on external disks.

#005 Delay Load option is greyed in Primo Ramdisk Professional/Ultimate Edition.
Description: Function has not been enabled yet.
Solution: fixed in version 5.4.0

#006 Real-Time Save option is greyed in Primo Ramdisk Professional/Ultimate Edition.
Description: Function has not been enabled yet.

#007 Drive letter will be changed when you modify virtual disk type from Direct-IO disk to SCSI disk.
Description: If you have created a Direct-IO disk and later you change it to SCSI disk via settings wizard, the drive letter may be changed after you restart the computer.
Workaround: Re-assign a drive letter for this SCSI disk via settings wizard if drive letter was changed.
Solution: fixed in version 5.6.0

[SlimShaggy]

#002 System cannot resume from hibernation if Windows pagefile.sys is set to a virtual disk which uses Invisible Memory. [Issue cannot be fixed]

Strange enough, but I've been using such a configuration for a while, and it hibernates and resumes perfectly if the ramdisk is SCSI. It does freeze when attempting to hibernate with a DirectIO ramdisk though.

[support]

#002 System cannot resume from hibernation if Windows pagefile.sys is set to a virtual disk which uses Invisible Memory. [Issue cannot be fixed]

Strange enough, but I've been using such a configuration for a while, and it hibernates and resumes perfectly if the ramdisk is SCSI. It does freeze when attempting to hibernate with a DirectIO ramdisk though.

Even sometimes you may see that it works on hibernates and resumes, it does not mean that it always works. It is risky whether you use SCSI or DirctIO ramdisk.