DM2000 Setup

There are two available types of Data Master 2000 setup: automatic InstallShield installation and a set of *.zip archives containing separate DM2000 components. If you have downloaded full DM2000 distribution kit (dmsetup.zip), just unpack it to the temporary folder, run setup.exe and follow instructions that appear on the screen (see readme.txt for more details).

If you download DM2000 as a set of *.zip files, you will not find special installation programs or *.inf files in these archives. However, all installer functionality is integrated into dm2000.exe application itself (for build #10.6.0.84 or later). All you need to do after unpacking archives to the selected folder is to run dm2000.exe and perform some optional manual setup (use Options|Setup command to display DM2000 Setup dialog box).

Installation.

  1. OLE registration. If you use Windows 98 you may need to install Microsoft script control OCX (msscript.ocx) included in dm2000.zip archive. Unpack this file into installation folder and click "Script control" button to perform registration. Note that this step is required only if Script window menu item (Options|Script window) is not available. Also you can download newest version of this control from Microsoft web site (see Links page). If you want to use DM2000 MetaBase you should register property page server (proppage.dll) included in mbshell.zip. Just click appropriate button. If there's no files named msscript.ocx and proppage.dll in the installation folder these buttons will be disabled. Note that DM2000 launch standard regsvr32.exe application to perform COM server registration.

  2. MetaBase provider registration. Provider DLL connects property page server (or dm2000.exe application) to the metadata storage. Only text-file provider (proptext.dll) is supplied with DM2000, but you can easily create additional providers (source code of Interbase connector is included in the metabase.zip archive). After you select provider file, DM2000 will try to launch rundll32.exe to register selected provider library. See MetaBase User's guide for more information about DM2000 MetaBase.

  3. Create file associations. You should create file associations if you want to open files in DM2000 from the file managers like Windows Explorer. Note that you may have several different extensions for your data files: input file type description and click "Data files" button several times for every extension. If you check "Create link to property page" flag and MetaBase have been installed, additional property pages will be displayed in file properties dialog box invoked from the file managers.

Uninstallation.

To uninstall DM2000 completely you should make the same steps but in reverse order (use Uninstall tab):

  1. Delete file associations. Select file type from the list and click "Delete" button to remove appropriate file association.

  2. MetaBase provider deregistration. Select provider library and click "Delete" button to deregister provider DLL.

  3. OLE deregistration. Note that in addition to DLL servers (msscript.ocx and proppage.dll) you should deregister dm2000.exe application itself.

  4. Delete DM2000 registry key. This button allows you to safely remove [\HKU\software\RRR\DM2000] registry key and all its subkeys.

After uninstallation complete, just close application and delete installation folder and all files in it.

Note that you must have administrative rights to perform software installation under Windows NT/2000.

Update.

In addition to the "clean" installation, you may manually update DM2000 components when their new versions will be available (see News page for a list of latest updates). In the most cases you may simply replace files with the newest ones; executable files provide additional feature - file version stamp, or build number (see "Version" property page on the File Properties dialog box). However, sometimes registry configuration information or toolbars layout (saved in the toolbars.bin file) may be discarded. 

Notice that starting from build #10.6.0.98 DM2000.exe application have special feature for automatic online update check: select "Check Updates" command from the Help menu to download special XML file from the DM2000 home page (your computer must be online, otherwise old cached version may be used instead of remote file). If this file downloaded successfully, DM2000 extracts build number of the latest online version, compares it with current version and displays the results. Of course, the only information DM2000 transmits over Internet during this operation is standard HTTP "GET" request, just like browse any web page; actually, it uses MSIE/MSXML to access the remote file.

System requirements.

All components of DM2000 were developed and tested under both Windows 98 and Windows 2000. Minimal hardware requirements (as for Windows 98 itself) are 486DX2-66 processor with 16MB RAM and 800x600x8bpp SVGA. It is strongly recommended that you upgrade your system to MSIE5 - some features will not work correctly with MSIE4. See readme.txt for additional information about compatibility and known installation issues.

DM2000 installation takes approximately 1-5 Mbytes of disk space, depend on installed components. It is not recommended to run this application from the remote computer because Windows cannot correctly create OLE objects when machine is down.