------------------------------------------------------------------------------
 OD-90228                         SUGGESTION                       "PRIDE"-IF
------------------------------------------------------------------------------
 MAY 12, 1997                   RELEASE  1.2.0                        PAGE  1

       ****************************************************************
       *                 MI-10029 DEREGISTER UTILITY                  *
       ****************************************************************


 REQUIRED DATE- OPEN          USER PRIORITY WEIGHT-  75    RANKING-  0029
 DATE RECEIVED- APR 28, 1997  REQUEST STANDING  - REVIEW   AS OF- MAY 12, 1997
                              TYPE- MOD/IMP

 DESCRIPTION-

        IBM Supplied De-Registering Utility
        I haven't really gotten the hang of using Templates yet -
        but one thing I know - there sure are a lot of them.  And
        programs are always installing templates on their own.  One
        problem with Templates (aside from bloating the OS2.INI file)
        is that they needlessly eat up system memory.  What's needed
        is an IBM utility to de-register (and possibly RE-register)
        templates.  I'm thinking of a shredder like object, or maybe
        more like a trash can object, that's placed in the Template
        folder.  The user would simply drag a Template to this object
        to have it de-registered and disappear.  To get the object
        RE-registered, the user opens up the trash, and retrieves the
        object he needs.  Either that, or a bullet item on the
        RMB cascading  menu that toggles "De-Registered/Registered,"
        with maybe the ICON getting an X on it (or the int'l "NO"
        symbol) when deregistered.

        ATTRIBUTES:

        LOW Value
        Desired next FIXPACK

        Submitted by:

        Mike Palmer
        Phoenix, AZ, USA
        mppalmer@aol.com

                           * * * END OF OUTPUT * * *

PLEASE SEND US YOUR COMMENTS! on the priority rankings or any of the suggestions included; send e-mail to the Editor at: TimB1557@aol.com