Intersection Magic provides a mechanism for “pushing” configuration and master support files (schematics, charts, gis, scripts, and other misc files) from a server to each local installation. This mechanism only works when a full network install is used. This article provides a checklist to follow if this mechanism isn’t working.
This check list is to be used for those users which already have a full network install. Please contact Pd’ Programming at this time to find out how to obtain a full network install.
The following is a list of requirements (a checklist) for this feature to function properly.
- _Config.upd must be in a directory called DATA which is beneath the imw.exe being called. (i.e. If you run imw.exe locally from c:magicimw.exe it will not work. The shortcut “target” must be a network path i:magicimw.exe*).
- The data directory must hold a valid set of configuration files. This includes a critical file called cityid.txt which is sort of a ‘flag’ indicating that indeed this is a configuration directory. cityid.txt must travel with the rest of the config files anywhere they are placed.
- The local imw.INI file has an entry in the [filenames] section called “MasterConfig”. This entry must either:
- not exist
- have no value to the right of the equal sign
- point to your network master data directory (I.e. MasterConfig=i:magicdata*)
- The local imw.INI has an entry in the [updates] section called “Config”. In order for an update to occur, this value must either:
- not exist
- be older than the value in the _config.upd on the network.
- The network _config.upd has an entry [general] section called “Lastupdate”. In order for an update to occur, this value must exist, and it must be newer than the value in the local imw.ini.
- When all of items 1-4 are set up correctly, on start up, Intersection Magic will check each of the files in the network data directory to see if it is newer than the corresponding file on the local drive. If a newer file is found on the network, or if no corresponding local file is found, the file will be copied to the local drive.
- One exception to step 5, is that if a file called imw.ini is found, it will not be copied. Rather, each item in the file will be examined and the corresponding value in the local imw.ini file will be set to match it. Thus, the local file will only be updated rather than replaced.
- In addition. If any files are found in sub-directories of the server’s data directory, those files will be copied and sub-directories created as needed on the local drive.
*For example purposes, we are using “i” as the network drive letter.
0 out Of 5 Stars