IMatch runs equally well from Windows 95 to Windows XP and requires only very little system resources for small (< 20,000 images) databases.
| Install size on hard disk |
 |
60 MB (approx.) |
Installable for single and
multiple users |
|
Yes |
| Number of images per database |
|
Only limited by the available hard disk space and system memory.
On a current PC, a database with up to 250,000 images works well with 256 MB RAM. For 50,000 images, IMatch requires < 64 MB RAM. |
| Number of images per folder |
|
Only limited by Windows |
| Number of images per category |
|
Only limited by available system memory. Several hundred thousand images at least |
| Maximum image size |
|
Unlimited. For editing/displaying/processing, only limited by the available system memory |
Required disk space for the
database and supplemental files |
|
Between 3% and 6% of the total size of all images. For a database holding 10 GB of image data, the database needs only between 300 and 600 MB. |
| Database technology |
|
Object-oriented RDBMS / OLAP hybrid database with transaction processing and journaling |
Property database
storage technology |
|
Compressed XML with UNICODE™ support |
Support for network-based files
and databases |
|
Yes. Drive mappings and UNC paths supported |
| Support for removable media |
|
Yes |
| Scanner Support |
|
Yes. TWAIN compatible |
| Email Support |
|
Yes. MAPI compatible |
Support for digital camera
RAW files |
|
Yes. All major vendors supported.
Support is limited due to the undocumented nature of RAW files |
| Indexing performance |
|
Between 100 images and 1000 images per minute, depending on the size and format of the input files, and the overall system performance |
| File System Monitoring |
|
Yes. Windows Explorer events application wide, file system events for the currently active folder |
| Active Suspension |
|
Yes. Shrinking IMatch to the Task Bar (Windows Tray) reduces the RAM and CPU consumption. |
