Overview

Both FileWizard Network and FileWizard Desktop products use the same engine. The difference between them is that FileWizard Desktop may only scan local disk drives and FileWizard Network can scan any drive that can be mapped to windows. All other features are identical.

FileWizard does not need clients installed on any remote system in order to scan the contents of the volume. Any volume that can be viewed in explorer can be scanned by FileWizard. In addition FileWizard can scan FTP and NFS volumes.

When FileWizard scans a volume(s) all available data is stored in a Microsoft Access database format then the data can be queried to find specific files or directories.

Licensing

FileWizard is licensed by the total volume of disk drives to be scanned, the number of servers or volumes does not matter.

Each time you scan a new volume it is added to a list and debited from the available Quota. The currently used and available quota information can be viewed in the Help menu “View License Information” option.

If a volume needs to be removed from the Quota you must contact your sales representative and volumes can only be removed from your Quota on a limited basis.

Windows Versions

FileWizard will work on Win95/98/NT/2000 with only a couple of restrictions for Win95/98.

In Win95/98 only drives that are mapped to a drive letter may be scanned. In WinNT/2000 any volume identified in Network Neighborhood may be scanned

Memory Requirements

FileWizard currently uses Microsoft Access as it’s database engine and it requires a large amount of memory to query the database. We are investigating other database engines to mitigate this but it is not yet available. As a general rule you should have RAM equal to 5 times the size of the database file filewiz.mdb located in the FileWizard install directory. For example if the filewiz.mdb file is 10 meg then 50 meg of free memory is recommended.

If there is insufficient memory your queries will still work but will take longer to complete and may appear to be “Not Responding” while your system is caching memory to disk. If you look at Task Manager and the Filewiz.exe process you will see the Memory Usage increasing and the scan progresses.

The size of the filewiz.mdb file is not determined by the size of your volume it is based on the number of Objects on the volume. The total number of Objects is the number all of files and directories.

A sample 15.7 gig scan contained 153k Objects and the filewiz.mdb file size was 17.8 meg. This would recommend at least 89 meg or about 1 meg free memory before performing a Query.

Last updated 01/10/2012