Copying an Intersection Magic database

adminIntersection Magic Windows > Data

The Intersection Magic database is contained in a number of files. This article describes which of these files should be copied when moving or copying the database to a new location.
NOTE: Beginning with version 6.x of the program, there is an option called "copy" under the Utilities / Database menu. This is the preferred method of copying databases in Intersection Magic.

 Performing a full install from an update CD / diskette

adminIntersection Magic Windows > Configuration

When Intersection Magic updates are sent to users, the 'custom configuration' that was sent for the first install is not included with the update cd or diskettes. The result is that, for a network install, no data directory (containing imwuser.exe) is created, and thus the 'client' side of the install can not take place. For a local install, only the demo/tutorial is installed, there is not IMW icon or DATA directory.

 the first two characters of the CASE_ID number are removed

adminIntersection Magic Windows > Networking

Scanned images for crash records may be stored in a centralized location or on a web server and accessed when viewing a crash record in Intersection Magic. Beginning with v6.611, users may use the filter mechanism to specify the a web address or path, filename and even the extension of the image to load. This article describes some ways of using this powerful feature.

 Another worktation is READING or WRITING to this database

adminIntersection Magic Windows > Errors / crashes

Intersection Magic keeps track of users who are accessing the database. At any one time there may be many people READING from the database. However, if anyone is writing to the database, no one else may READ or WRITE at the same time. If you are attempting to READ when you get this message, then another use has opened the database for WRITING. If you attempting to WRITE to the database, then another user is READING the database. Note: This message can also be caused by the program having crashed during a READ or WRITE operation and not released its lock on the database.