Conference csc32::consolemanager

22.0. "Monitor bugs, problems, quirks, etc" by VINO::DBIGELOW (Innovate, Integrate, Evaporate) Thu Sep 24 1992 23:28

Regarding the Monitor interface:

-   cm -m only suports decterms with 24 rows. Anything smaller will cause a 
     core dump. 
    
-   It will not take advantage of a larger screen. Only 24 rows appears
    to work.

-   Control C does not function properly. 
    It leaves the terminal in a sour state.
    The 'reset' command must be re-applied. 

-   No online help is available in the monitor. With hunfreds of systems, 
    it's difficult to remember all the names and their exact spelling.
    It's also tough to have all the commands committed to memory.
    
-   Got hanging hanging condition. Must reset terminal. Only way to reset was
    to shutdown CM (Which also hung) and restart.

-   'Previous' and 'Next' screen buttons don't work. During one session, 
    the previous and next buttons only moved the text 1 line.

-   Always comes up in two window mode. Why is this? My belief is that one 
    would be preferable.

-   Core dumps with just the 'set' and 'unlock' command.

-   It is impossible to 'switch' from one console to the next. If it is
    then it is not ooutlined in the man pages.

-   cm -m valid_system_name, invalid_system_name will cause a core dump.

-   Control L does nor work for refresh. Control W is incorrectly used for the
    refresh.