| All Products |
||||||||||||||||||
|
|
||||||||||||||||||
| SuperCache II and SuperVolume
How to's
Fixes Informational
|
||||||||||||||||||
|
|
||||||||||||||||||
| RamDisk and RamDisk
Plus How to's Fixes Informational |
||||||||||||||||||
|
|
||||||||||||||||||
| FAQ - All Products | ||||||||||||||||||
|
|
||||||||||||||||||
| Q: | How do SuperSpeed products affect the values displayed in Task Manager? | |||||||||||||||||
| A: |
When active, SuperSpeed cache and RAM disk products will visibly impact values displayed in the "Performance" tab of Task Manager. Both memory and CPU statistics will be affected. The more work the cache or RAM disk perform, the higher the CPU utilitization. This is because our products trade CPU resources for disk resources. The memory resources for our products' caches and RAM disks are allocated from physical memory - not from the operating system's paged or non-paged kernel memory. When an allocation is made from physical memory, it directly affects the following values: Physical Memory - Available: The amount of physical memory (main memory or RAM) currently available for use. When a RAM disk or cache is created, this value will decrease by the size of the RAM disk or cache plus a smaller amount for overhead. Commit Charge - Total: The total amount of virtual memory currently allocated to programs and the operating system. Virtual memory includes physical memory allocations and memory that has been "paged out" to the paging files. When a RAM disk or cache is created, this value will increase by the size of the RAM disk or cache plus a small amount for overhead. PF Usage: This name is misleading. This value is the same as "Commit Charge - Total" above. |
Top |
||||||||||||||||
|
|
||||||||||||||||||
| Q: | Can SuperSpeed products be configured to use memory above 4 GB? | |||||||||||||||||
| A: | Yes, on all 64-bit and some 32-bit server platforms memory
allocations can be made from above 4 GB. On 32-bit platforms the boot.ini
/pae switch must be used. When memory above 4 GB is available, allocations
are taken first from physical memory addresses above 4 GB, and then from
addresses below 4 GB. The amount of memory allocated from these two "pools" can be controlled by two registry DWORD values, "Above4Gb" and "Below4Gb", respectively. Each value describes the maximum amount of memory that may be allocated, in megabytes (MB), from each "pool". Both values must be present. The values should be created in the following registry keys: For SuperCache II and SuperVolume:
For RamDisk Plus and RamDisk:
The system must be restarted for the settings to take effect. Important: By default these values are not present. Their absence indicates that allocations will be made from each pool without any driver-imposed limits. |
Top |
||||||||||||||||
|
|
||||||||||||||||||
| Q: | I have 4 GB of RAM installed but Windows only reports a little over 3 GB. Will SuperSpeed products use the memory above 3 GB? | |||||||||||||||||
| A: |
The answer to this question depends on the computer's motherboard and
how it and the operating system are configured to manage memory. SuperSpeed
products utilize only those resources the operating system recognizes
and makes available. The operating system depends on the motherboard's
chipset and BIOS to manage memory present in the system. |
|||||||||||||||||
|
|
||||||||||||||||||
| Q: | How do I order an upgrade over the internet? | |||||||||||||||||
| A: | A discount is available for upgrading from a prior version, (e.g. upgrading from RamDisk version 8.0 to 9.0). Email info@superspeed.com for pricing. | |||||||||||||||||
|
|
||||||||||||||||||
| FAQ - SuperCache II and SuperVolume | ||||||||||||||||||
|
|
||||||||||||||||||
| Q: | How do I use SuperCache II and SuperVolume with volume mount points? | |||||||||||||||||
| A: |
A volume mount point is a directory on an NTFS storage volume (the
"host") on which another storage volume (the "target")
is "mounted" or "grafted". I/O requests that reference
the mount point are no longer directed to the host volume but re-directed
to the target storage volume. Instead of thinking of a mount point as a directory that exists in the host volume's file system, it is helpful to think of it as a special path to the root directory of the target volume. The special path borrows host volume's the drive letter and directory to provide access to the target volume. In effect, the directory used as a mount point is no longer "connected" to the host volume, but rather to the target volume at that mount point. It is for this reason that Windows does not permit mounting a volume on a directory that already contains files or sub-directories as they would become inaccessible. How does this impact SuperCache II and SuperVolume? Both products cache storage volumes and both are unaware of volume mount points. Therefore, if SuperCache II is active on a host volume containing mount points, it will not cache the data of the mount point targets. To cache a target volume that is grafted onto a host volume, SuperCache II must be made active on the target. The "vfcfg" command and the storage volume's "Performance" property page support caching of volumes that are not assigned drive letters. For information about creating volume mounts points see: http://support.microsoft.com/?kbid=205524. |
Top |
||||||||||||||||
|
|
||||||||||||||||||
| Q: | How do I automate installation and uninstallation of SuperCache II and SuperVolume? | |||||||||||||||||
| A: |
Starting with version 1.0.12, the SuperCache II and
SuperVolume package provides limited support for
automated installs and uninstalls. The package can be installed and
uninstalled via a command prompt window or a script. By implementing
a script with system management software, the package can be rolled
out to remote machines. To install the package without user intervention on a system with no package currently installed, use the following command:
Where "Name" and XXXXX-XXXXX-XXXXX-XXXXX-XXXXX are the name and software license key provided by SuperSpeed LLC. Be sure to include the name in double quotes. The system must be restarted immediately after executing the command. To uninstall an installed package without user invention, use the following command:
Be sure to include the double quotes as shown. The system must be restarted immediately after executing the command. Important: The package cannot update or repair installed versions. |
|||||||||||||||||
|
|
||||||||||||||||||
| Q: | Does the "System Cache" value in Task Manager track SuperCache II or SuperVolume activity? | |||||||||||||||||
| A: | No. The "System Cache" value (under "Physical Memory (K)" on the "Performance" tab) shows the current physical memory in use and mapped to pages of open files. These mappings are managed by the operating system at the file-system driver level. Independently, SuperCache II and SuperVolume manage their caches at the storage volume device level, which is, logically-speaking, immediately below the file systems. | Top |
||||||||||||||||
|
|
||||||||||||||||||
| Q: | Are SuperCache II and SuperVolume compatible with other disk utility software? | |||||||||||||||||
| A: | Generally, yes, SuperCache II and SuperVolume
can be used along with other disk utility software without problems. However, some software, such as backup or defragmenting software, may exhibit varying degrees of incompatibility. SuperCache II and SuperVolume are implemented as a volume filter driver. When other drivers are also installed below the file system, the order in which data is processed may change, resulting in serious problems such as data corruption and/or a system crash. Therefore, we strongly recommend first testing SuperCache II or SuperVolume along with any disk utilities on a test machine or a test volume to do determine their compatibility. When a serious incompatibility is discovered, its resolution will likely fall into one of two categories: mutually exclusive installation, or a work-around. A work-around requires that extra steps be taken to assure that the two utilities work together without causing undesirable behavior. Mutually exclusive installation means the only resolution to the problem is to not have both utilities installed at the same time. An effective work-around in the case of incompatibilities between SuperCache II or SuperVolume and backup or defragmenting software, is to disable caching, perform the backup or defragmenting, and re-enable caching afterwards. If the backup or defragmenting software provides a command-line interface, the entire sequence can be scripted. |
Top |
||||||||||||||||
|
|
||||||||||||||||||
| Q: | I installed SuperCache II (or SuperVolume) and now my system fails to start. How do I fix it? | |||||||||||||||||
| A: | Certain disk management software, including some backup software, may
be incompatible with SuperCache II or SuperVolume.
When installed simultaneously, the system may hang or crash during startup.
The quickest route to making the system bootable is to disable the SuperCache
II/SuperVolume "SscVf.sys" driver. There are several possible routes to disabling the "SscVf.sys" driver. However, depending on the point of conflict, some may not be available. We suggest trying the following, in order:
Boot into "Safe Mode"
This solution requires:
Warning: this solution requires manual modification of the system registry hive.
|
Top |
||||||||||||||||
|
|
||||||||||||||||||
| Q: | When I try to configure SuperCache II or SuperVolume, I receive the message "ConnectServer(WbemService) failed. Result: 80041002h". How do I fix it? | Top |
||||||||||||||||
| A: | SuperCache II and SuperVolume provide
volume filter device management via WMI (Windows Management and
Instrumentation). If the WMI repository is corrupt, the message
"ConnectServer(WbemService) failed. Result: 80041002h" will be
returned when using the "vfcfg.exe" command-line interface, or
the "Performance" volume property page. In this case, the
repository must be repaired or rebuilt. Windows Server 2003 with Service Pack 1 and Windows XP with Service Pack 2 include tools for repairing the WMI repository. Other Windows versions can rebuild the repository by other means. Select the appropriate method for your platform: Windows Server 2003 with Service Pack 1 or later Open a command prompt window and enter:
Note: This command is case-sensitive. Enter the command exactly as shown. Windows XP with Service Pack 2 or later Open a command prompt window and enter:
Note: This command is case-sensitive. Enter the command exactly as shown. Other Windows Versions To rebuild the WMI repository, the winmgmt service must be stopped, the current repository moved or deleted, and the service restarted. To perform these steps, open a command-prompt window and enter the following commands:
For more information about repairing the WMI repository see: http://www.microsoft.com/technet/scriptcenter/topics/help/wmi.mspx#EQKAC. |
|||||||||||||||||
|
|
||||||||||||||||||
| FAQ - RamDisk Plus and RamDisk | ||||||||||||||||||
|
|
||||||||||||||||||
| Q: | How do I put a pagefile on a RAM disk? | |||||||||||||||||
| A: |
Important: Pagefile support is available with RamDisk Plus 9 running on Windows Vista or XP and RamDisk Plus 8 on Windows Server 2003 and Windows XP. |
Top |
||||||||||||||||
|
|
||||||||||||||||||
| Q: | How do I put temporary Internet files on a RAM disk? | |||||||||||||||||
| A: |
|
|||||||||||||||||
|
|
||||||||||||||||||
| Q: | How do I back up the data on my RAM disk efficiently? | |||||||||||||||||
| A: | Use RamDisk Plus.
It can be configured to automatically save a RAM disk's contents when
the system shuts down, restoring it when the system starts up. Version
8 also supports saving the contents manually or by script. For more information about saving a RAM disk's contents, see: When I try to save the RAM disk's image, I get an error. How do I fix it? |
Top |
||||||||||||||||
|
|
||||||||||||||||||
| Q: | How do I schedule automatic daily RAM disk backups? | |||||||||||||||||
| A: | Successful automatic backups of the RAM disk's contents require that
there no open handles to the RAM disk at the time each backup is performed.
(See: When I try to save the RAM disk's image, I get an
error. How do I fix it?) If the requirement for no open handles can
be met, scheduling automatic backups is a simple task. To do so:
|
|||||||||||||||||
|
|
||||||||||||||||||
| Q: | How do I speed up printing with a RAM disk? | |||||||||||||||||
| A: |
Move the print spool folder to a RAM disk.
|
Top |
||||||||||||||||
|
|
||||||||||||||||||
| Q: | How do I control the creation of the temp folder on a RAM disk? | |||||||||||||||||
| A: |
RamDisk 8.0 - The only control is to enable or disable creation of the '\temp' folder when the RAM disk itself is created. When enabled, the '\temp' folder is created immediately after the disk is formatted. Then the image is 'sealed'. Every time the machine starts up the RAM disk will start up with the contents of that image. RamDisk Plus 8.0 - You have complete control over what folders and files are present in the RAM disk when the machine starts up. First, create the RAM disk. Second, create or copy the desired folders and files to the RAM disk. Third, save the RAM disk's image. To 'seal' that image, do not select "Save at shutdown". Every time the machine starts up the RAM disk will start up with the exact same saved contents. |
|||||||||||||||||
|
|
||||||||||||||||||
| Q: | How do I make a folder on a RAM disk into a network share? | |||||||||||||||||
| A: | Just as you would any other disk or folder.
|
|||||||||||||||||
|
|
||||||||||||||||||
| Q: | How do I mount a RAM disk at a mount point? | |||||||||||||||||
| A: | RamDisk and RamDisk Plus both support
mount points. However, they are not configurable in Disk Management. Instead
you must use the command-line interface "mountvol". Open a command-prompt window and enter "mountvol". Suppose it lists a RAM disk with drive letter R: as follows:
To mount the RAM disk R: at c:\mountpoints\ramdisk enter:
Placing a file in the root of R: and placing the file in c:\mountpoints\ramdisk\ will now accomplish the same thing, as both paths point to the same object. To remove the above mount enter:
|
Top |
||||||||||||||||
|
|
||||||||||||||||||
| Q: | I applied Service Pack 2 on Windows XP and cannot set up a RAM disk. How do I fix it? | |||||||||||||||||
| A: | To fix this problem, simply uninstall RamDisk or RamDisk Plus, reboot the computer, and then reinstall the product. Note: Before uninstalling, save image files you may need. | |||||||||||||||||
|
|
||||||||||||||||||
| Q: | When I try to save the RAM disk's image, I get an error. How do I fix it? | |||||||||||||||||
| A: | Before saving the RAM disk's contents, close all applications that are
accessing it. RamDisk Plus is designed to save a static, or fixed, RAM disk image. It is not designed to backup or save dynamically changing RAM disk content. Therefore, RamDisk Plus does not permit any open handles on the disk when the save command is executed. If open handles are detected, the command will fail. (Typically an error code of 5 is returned: access denied.) See SuperVolume to automatically save dynamically changing content. Why does RamDisk Plus disallow saving the image when handles are open? To eliminate the possibility of corruption. Open file handles imply that disk data is cached and has not been written to disk. Saving a RAM disk's contents to its image file while there are handles open to it will result in a corrupt saved image. On some systems, the save operation fails even after all applications known to be accessing the RAM disk are closed. This is because other "hidden" applications or services are maintaining open handles to the disk. In this situation, an option that will allow the RAM disk's image to be saved is to forcibly invalidate these handles by dismounting the RAM disk's file system. To forcibly dismount the RAM disk's file system on Windows XP and Windows Server 2003, open a command-prompt window and enter "fsutil volume dismount R:", where R: is the RAM disk's drive letter. On Windows 2000, open a command-prompt window and enter "chkdsk R: /f" where R: is the RAM disk's drive letter. If open handles are present on the disk, the utility will prompt if you want to force a dismount of the volume. By responding Yes, the handles will be invalidated and the disk image can be saved. |
Top |
||||||||||||||||
|
|
||||||||||||||||||
| Q: | While installing RamDisk or RamDisk Plus I receive a "Stop 0x00000020" message. How do I fix it? | |||||||||||||||||
| A: | This problem is known to occur on systems running Symantec pcAnywhere 11.5 with Symantec AntiVirus 8.x or Symantec AntiVirus 9.0. The Symantec Event Handler driver (Symevent.sys) causes the problem. For further information on the problem and its resolution please see http://support.microsoft.com/default.aspx?scid=kb;en-us;905539 | |||||||||||||||||
|
|
||||||||||||||||||
| Q: | Partition Magic (8.0 or earlier) hangs when a RAM disk is present. How do I fix it? | |||||||||||||||||
| A: | Partition Magic (version 8.0 and earlier) does not "know" how to handle non-removable storage devices that do not contain a partition table. Instead of ignoring the RAM disk, Partition Magic goes into an endless loop. To run Partition Magic, you must remove all RAM disks from the system, run Partition Magic, then restore the RAM disks. Note: Before removing any disks, save the image files you may need. | |||||||||||||||||
|
|
||||||||||||||||||
| Q: | Drive Image (6.0 or earlier) hangs when a RAM disk is present. How do I fix it? | |||||||||||||||||
| A: | Some versions of Drive Image (version 6.0 or earlier) do not "know" how to handle non-removable storage devices that do not contain a partition table. Instead of ignoring the RAM disk, Drive Image goes into an endless loop. To resolve this issue, upgrade to Drive Image version 7.0 or later. | |||||||||||||||||
|
|
||||||||||||||||||
| Q: | Acronis True Image (8 or earlier) aborts or crashes the system when a RAM disk is present. How do I fix it? | |||||||||||||||||
| A: | Some versions of Acronis True Image (version 8 or earlier) do not "know" how to handle non-removable storage devices that do not contain a partition table. Instead of ignoring the RAM disk, True Image may abort or crash the system. To resolve this issue, upgrade to True Image version 9.0 or later. | Top |
||||||||||||||||
|
|
||||||||||||||||||
| Q: | Will a RAM disk make my computer faster? | |||||||||||||||||
| A: | Yes, if utilized in specific way. A RAM disk is a virtual disk in memory. This means it looks and acts like a physical hard drive, except its performance is many times faster. Although it acts like a very fast hard drive, unless something that is frequently used is stored on it, it can’t make your computer run faster. | |||||||||||||||||
|
|
||||||||||||||||||
| Q: | Can RamDisk or RamDisk Plus be used with Crusoe and/or VIA C3/Eden CPUs? | |||||||||||||||||
| A: | Yes. | |||||||||||||||||
|
|
||||||||||||||||||
| Q: | Can RamDisk or RamDisk Plus assign drive letters A: or B: to a RAM disk? | |||||||||||||||||
| A: | No. Windows reserves these drive letters for removable media devices. | |||||||||||||||||
|
|
||||||||||||||||||
| Q: | What are the names of the processes running for RamDisk or RamDisk Plus? | |||||||||||||||||
| A: | RamDisk 8.0 and RamDisk Plus 8.0 do not maintain any running processes. Except for disk management, all functionality is realized in two digitally-signed device drivers. The drivers are signed by Microsoft after meeting extensive requirements for reliability. The drivers execute in the system's kernel process. | |||||||||||||||||
![]() |
| Home | - | Site Map | - | Contact Us | - | Legal Notices | - | Privacy Policy |
U.S. Patents Nos. 5577226, 5606681, 5918244, 6370615, 6629201, 6651136, 7017013, 7039767, 7111129 and other worldwide patents pending.
Copyright © 1996-2008 SuperSpeed Software, Inc. All rights reserved.