How to Move UniMaint to a New Location Since you cannot have UniMaint Uninstall or Reinstall itself, I have been asked to describe how to move UniMaint manually and that is the purpose of this document. Before you do anything you should have both a Desktop Backup of your Desktop and a Portable Backup of your Desktop. The Desktop Backup is for safety and the Portable Backup will be needed to modify the WPS Objects. There are three problems: 1. The files and directories themselves. 2. The UniMaint and UniWatch references in the OS2.INI file or the private UniMaint INI file. 3. The WPS Objects. Moving the Files to a new Directory The only problem with the files themselves is that the AcsAgent.DLL file is in use if the UniMaint WPS Object is registered. Therefore, the Object must be deregistered before the files can be moved or copied. Here is the procedure: 1. Without UniMaint or UniWatch running, run AcsTest with -Z on the parameter line. The run should end with a message box telling you that the WPS Class is deregistered. 2. Before you restart UniMaint, copy the entire UniMaint directory to the new location. The UniMaint and UniWatch entries in the INI Files Since UniMaint will be used to handle this modification and it is not possible to modify the INI file that is in use, a new INI file should be used. Here is the procedure: If you do not have a SET UNIMAINT= entry in the config.sys file then the UniMaint settings are in the OS2.INI file so you would do the following: 1. Add a SET UNIMAINT= entry to your current config.sys pointing to an INI file, lets say UniMaint.INI in the new UniMaint directory. This file will not exist at this point and do not create it. Also do not reboot until you have finished the entire set of UniMaint modifications. 2. Open the OS2.INI file, select the Uni Maintenance application, then use the Action/Copy/Selected Application ot copy it to the INI file in 1. above. The target file need not exist, it will get created. 3. Do the same for the UniWatch application if you are using UniWatch. 4. Use the Recover/Translate INI file function to open the newly created INI file and modify all instances of the old directory to the new directory. If you have a SET UNIMAINT= entry in your config.sys then you have already copied the UniMaint INI file from the old location ot the new location since I am assuming you have the UniMaint INI file in the UniMaint directory. Therefore, you only need to do the following: 1. Modify the SET UNIMAINT= to refer to the new location. 2. Use the Recover/Translate INI file function to open the copy in the new directory and modify all instances of the old directory to the new directory. The WPS Objects Just to be sure that the WPS Agent Class is not registered before you reboot you should run AcsTest with -Z on the parameter line again. You should now reboot. Start UniMaint by double clicking on the EXE in the new location. Do you use the WPS program icons until you get them fixed below. You are now using the UniMaint files in the new location and the UniMaint INI file that is in the modified SET UNIMAINT= entry in the config.sys file. You can now restore the UniMaint Folder and it will automatically modify all of the EXE and startup directory information to point to the new location. However, before you do this it is important that the Portable Restore no be able to find the old files. Here is the procedure: 1. Get rid of the old location by zipping the entire contents of the old UniMaint directory to a singe zip file and then deleting the directory. 2. Bring up the Portable Restore and use the generation you created above which should have been done just before you started this procedure. 3. Make sure the Existing Objects Menu item is set to Replace Existing Objects. 4. Select the UniMaint Folder and Restore it. This will fix all of the WPS Program entries and point them all to the new location. 5. Exit UniMaint and reboot. You should now be able to fully use UniMaint in the new location.