Title: | DECmcc user notes file. Does not replace IPMT. |
Notice: | Use IPMT for problems. Newsletter location in note 6187 |
Moderator: | TAEC::BEROUD |
Created: | Mon Aug 21 1989 |
Last Modified: | Wed Jun 04 1997 |
Last Successful Update: | Fri Jun 06 1997 |
Number of topics: | 6497 |
Total number of notes: | 27359 |
Hello, A little problem. After exiting IMPM I was unable to re-enter with the following error given below. When in the original session I had only changed and saved the size of the map. I had ~50 event rules w/notification enabled running. Note, we were receiving a stream of DECnet events when I exited. help most appreciated, brad... ------------------------------------------------------------------------------ NOCMAN>manage/enterprise/inter=decw Software error: An internal error has occurred in the Iconic Map PM. %MCC-F-PM_BUG, Software error: An internal error has occurred in the Iconic Map PM. NOCMAN>mcc test mcc 0 iconicmap DECmcc (V1.1.0) MCC 0 ICONICMAP AT 13-MAY-1991 10:24:02 Test Successful
T.R | Title | User | Personal Name | Date | Lines |
---|---|---|---|---|---|
1004.1 | reboot, no effect | JETSAM::WOODCOCK | Mon May 13 1991 11:38 | 2 | |
FYI, reboot failed to clear problem... | |||||
1004.2 | re:.0 | BARREL::LEMMON | Tue May 14 1991 15:07 | 8 | |
Just curious, did you install the alarms patch? If not, install it and see if the problem is still there. If you already installed it, give me a call (226-5329). I need to track down where the error message is being displayed. /Jim | |||||
1004.3 | bad x coordinate in resource file | BARREL::LEMMON | Wed May 15 1991 13:27 | 5 | |
The map x coordinate resource in Brads MCC_RESOURCE.DAT was set to -2. He used "save current settings" to create the file. I am looking into why this happened. /Jim | |||||
1004.4 | found it | BARREL::LEMMON | Tue May 21 1991 17:51 | 6 | |
We were able to reproduce the negative x coordinate for both the management and map window. It happens (sometimes) if you save the windows position when part of the window is not on the display. This will be fixed in the v1.2 kit. /Jim |