The standard DRE is quite simple to use; only the basest of configuration information is necessary. When a user first decides to use DRE, he is asked to fill out some registration information. This information is shipped, via e-mail, to the DRE development team. This information is collected solely for research and statistical purposes. However, should the user be working on a workstation that is not connected to the internet, the registration will not be sent across the network. Instead, the user is asked to forward a registration file to a specific address.
This is interesting from a configuration point of view for one reason. Because the registration information is stored locally on the hard drive, it is expected to remain there for each future run. As long as the user runs DRE from the same directory, where all configuration files exist, no problem occurs. But should the user start the application from a different directory, the registration information will not be found, and the user will be prompted to register DRE again. To ensure that this does not happen, make sure that a valid registration file exists in config/reg.txt in whichever directory that the DRE is started from (for easiest result, always use the associated batch file, or always start the tool from the same directory in which it was originally installed.
One other configuration point is made. The DRE application is contained in the file DRE.jar, which is downloadable from the DRE Website. In order to operate properly, however, some cooperating .jar files are required. These files are industry standards, and downloadable from the original sources, as well as from the DRE website. These files are:
Each of these .jar files must be put into the classpath of the application. There are three solutions to this problem:
java -cp mail.jar:activation.jar DRE.manager.DRETool
Congratulations! DRE should now be fully configured and runnable on your system.