Frequently Asked Questions about DiskVision

Q: What is the update policy for DiskVision?
A: Purchasing DiskVision entitles you to free minor updates for the life of the product. Minor updates are those that change the second or third version number. (For example: 1.2.3 -> 1.2.4, 1.2.4 -> 1.3.0)  In addition, all updates for one year from date of purchase are free. In other words, if you buy DiskVision today, you can upgrade to any  new version of it released up to one year from now, at no additional cost.

Q: When I try to install I get an error like "The file 'C:\Program Files\DiskVision\UNWISE.EXE' could not be opened. Please check that your disk is not full and that you have access to the destination directory. Access id denied." Why?
A: Under Windows 2000 or Windows XP, you must have administration privileges to install DiskVision. Please log in as Administrator (or another user with administrator privileges) and try again. Or, ask your administrator to install it.

Q: Why can't I see my network volume(s) in the Drive Combo Box or the File|Open menu?
A: Network volumes must be mapped to drives before DiskVision can see them. To do this, right-click on the network volume in the Network Neighborhood window, and pick "Map Network Drive…". Pick a drive in the following dialog, and click OK. You will have to restart DiskVision so that it can see the drive.

Q: Why does DiskVision show the wrong size for my hard drive?
A: Versions of Windows 95 before OSR2 (that is, release 2) cannot properly report some information on disks or partitions greater than 2GB in size. In some cases, incorrect values may be returned for volumes less than 2GB in size. The only remedies are to upgrade to Windows 95 OSR2, Windows 98, or Windows NT 4.0 or later, or to partition the drive into 2GB or smaller segments.

Q: Why does DiskVision show incorrect information for my network drive?
A: The accuracy of drive information for network volumes depends on the accuracy of the network client driver. There are known problems with the Novell NetWare drivers, for instance. You might want to try the Microsoft network client, if one is available for your network. Another option is to check the network client driver manufacturer to determine whether an updated driver is available.