═══ 1. Keys Help For Objects ═══ ┌────────────────────┬────────────────────┐ │Key Name │Key Function │ ├────────────────────┼────────────────────┤ │F1 │Help │ ├────────────────────┼────────────────────┤ │F10 │Menu │ ├────────────────────┼────────────────────┤ │PgDn │Scroll listbox │ │ │forward. │ ├────────────────────┼────────────────────┤ │PgUp │Scroll listbox │ │ │backwards. │ └────────────────────┴────────────────────┘ ═══ 2. List Objects Overview ═══ Additional help is available for: o General o Listbox o Refresh o Register o Deregister o Verify o Exit ═══ 2.1. General Help For Objects ═══ Applications installed on your system which create new WorkPlace Shell objects, register these objects to the operating system. In effect, these objects become extensions of the WorkPlace Shell. When OS/2 boots up, it tries to locate and load these registered DLL files associated with these registered objects. Many programs do not provide a de-install feature. Simply erasing these files do not remove the hooks within the operating system. In some cases, you cannot delete the files until the objects are deregistered. Therefore, this program was written to help you clean up after a product as been deleted from your system. It can also be used by program developers creating new objects. Objects can be registered and deregistered as required while you develop objects. Another useful feature, is the ability to move a product from one disk drive to another. One example, is the IBM Workframe/2 product. It uses WorkPlace Shell integration. Simply copying the files to another drive does not properly connect the operating system to your changes. You can display the current settings, write them down, deregister the classes, then re-register the classes pointing to the appropriate drive. ═══ 2.2. Listbox (List of Classes) ═══ The listbox shows the list of the classes or objects registered to the WorkPlace Shell. Items starting with "WP" are part of OS/2 and cannot be manipulated by this program. As you move the selection cursor over the items in the list box, you will see the registered DLL file name in the status area at the top of the window. ═══ 2.3. Refresh ═══ Refresh can be selected from either the menu or the push button. It simply goes out to the system and re-reads the currently registered list of objects (classes) and displays them in the list box. ═══ 2.4. Register ═══ Use either the register push button or the register menu item to register a new class or object to the WorkPlace Shell. You would only need this option if you were creating new objects or if you are moving objects from one drive to another and the drive was coded in the DLL file name. Note: If a DLL name is not fully qualified with the drive and path, then it is located via the LIBPATH in the CONFIG.SYS. You do not have to enter a fully qualified name if you are in the LIBPATH. Some products install using a fully qualified name. If you move these products to another drive, then you will need to de-register and then register these objects specifying their new locations. ═══ 2.5. Deregister ═══ Use the deregister push button or menu item to remove the object from the WorkPlace Shell. Note that you cannot deregister any object or class which beings with "WP". These are part of the WorkPlace Shell and cannot be manipulated by this application. Note: Once an item has been deregistered, you must shut down and re-boot OS/2 before the operating system will release the files. ═══ 2.6. Verify ═══ The verify push button will bring up the verify window. The purpose of verify is to check your hard disk to see if the selected .DLL file is stored on the drive. If it is, then it is likely that you should not deregister the object. If the .DLL file is not found, then it is a good candidate to be deregistered from your system. ═══ 3. Register Help ═══ ═══ Dummy ═══ The registration process allows you to register a new object (class) to the WorkPlace Shell. Code support for the new object is provide by a DLL file. This DLL file is loaded by the operating system during boot or as required. To register a new object, you must provide a new class name and the DLL file which provides the code support. Additional help is available for: o Class Name o DLL Name o OK o Cancel ═══ Dummy ═══ ═══ 3.1. Class Name ═══ The class name is the internal object name. Each class has a name and an associated DLL file name to support the object. Both items are required for registration. Note: There is no validity checking on the location of the DLL file name. If you enter it wrong, the system will not be able to locate the DLL file during boot up. It will not cause the system to fail to boot, but the supporting code for the object will not be in the system. ═══ 3.2. DLL Name ═══ The DLL name is the file name of the DLL file which provides the object support within the WorkPlace Shell. It can be a fully qualified path name with drive or it may be just the filename. If you do not fully qualify the DLL name, then OS/2 uses the LIBPATH in the CONFIG.SYS to locate the object's DLL. Note: There is no validity checking on the location of the DLL file name. If you enter it wrong, the system will not be able to locate the DLL file during boot up. It will not cause the system to fail to boot, but the supporting code for the object will not be in the system. ═══ 3.3. OK ═══ Selecting the OK button, will start the registration process of a new or relocated object. ═══ 3.4. Cancel ═══ Selecting the Cancel button, will abort the registration process. No changes are made to the system. ═══ 4. Verify Help ═══ ═══ Dummy ═══ Additional help is available for: o General o Drives o Search o Stop o Exit ═══ Dummy ═══ ═══ 5. Deregister Help ═══ ═══ Dummy ═══ Click the "Yes" button to deregister the object or class from the system. Click the "No" button to take no action. More... Note: Once an item has been deregistered, you must shut down and re-boot OS/2 before the operating system will release the files. ═══ Dummy ═══ ═══ 5.1. General Help For Verify ═══ The verify process searches the selected drives for the .DLL file. If it is found, then it is likely that the object is still in use and should not be deregistered. If it cannot be located, then it is a good candidate to be deregistered from the system. The search will stop once the first occurrence of the DLL file is located. You control what drives are searched and you may terminate the search early with the "Stop" button. You can run multiple scans at the same time by opening multiple copies of the verify window. ═══ 5.2. Drives Check Boxes ═══ This group of check boxes will contain a item for each drive starting with Drive C:. By default the last drive is not selected as it is assumed that this is a CDROM drive. Check the drives you wish to search. Note: It is recommended that you search all drives except the CDROM when performing the search. ═══ 5.3. Search Button ═══ Clicking this button begins the search on the selected drives. It is an error to have no drives selected. You can stop the search once it has begun by clicking the "Stop" button. ═══ 5.4. Stop Button ═══ The "Stop" button will interrupt or abort the currently running search. ═══ 5.5. Exit Button ═══ Press the Exit button to terminate or close the window. ═══ 6. Product Registration ═══ If you like the software, you can register it to entitle you to be notified of updates and to report problems with the product. The current registration price is $20.00. You can register the product by: o Mail (requires check or credit card information) Taylor Made Systems PO Box 180096 Mobile, Alabama 36618 There is certain information needed for registration: o Company o Name o Address o Phone