[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference azur::mcc

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

3187.0. "Problem to add child domains to map with v1.1" by BACHUS::FOLENS () Tue Jun 16 1992 09:10

I have the following problem with DECmcc BMS v1.1 running on a mV3100 with
VMS v5.5. 
The DNS-server resides on another system.
When I start the Iconic map with: MANAGE/ENTERPRISE/INTERFACE=DECWINDOW
the message 'file invalid' appears just before the map is displayed.
I can open a domain, create a new domain and add entity's to the map. But
when I try to add a domain child to the current domain (click on the domain
icon in the toolbox window), I get a access violation on my terminal window
from where I started mcc and the small clock is displayed on my toolbox window
untill I quit the mcc session.
The access violation is alwyas the same, i.e.:

%SYSTEM-F-ACCVIO, access violation, reason mask=00, virtual address=00000000,
PC=00297d26, PSL=03C00004

From the command language interface I have no problem at all.
All the necessary patches for v1.1 are installed (alarms, domain,kernel,...).
I have already reinstalled the whole kit, but nothing changes. Any ideas?

-Geert-

T.RTitleUserPersonal
Name
DateLines
3187.1check icon filesBARREL::LEMMONTue Jun 16 1992 12:2512
    It looks like one of your icon files has been corrupted.
    Check your logical mcc_icons and make sure it points
    to mcc_system.     
    
    Bring the toolbox up and see if any icons have a "?" in it.  If
    so, type out the file mcc_icons:mcc_<class>_icon.dat where class
    is the class of the icon with a question mark in it, try renaming
    it and see if you get the accvio.
    
    The bottom line here is one of the MCC_*_ICON.DAT files is bad.
    
    /jim 
3187.2It was a bad icon file...BACHUS::FOLENSTue Jun 16 1992 14:327
    Indeed, there was a new icon created with the paint utility ,but it was
    saved as an ddif file and not as an X11 file. This caused all the
    problems.
    Thank you for the quick answer. It was a great help to me and to the
    customer.
    
    -Geert-
3187.3One last step...DFLAT::PLOUFFEJerryWed Jun 17 1992 12:5910
Jim:

  Maybe you already intend to do this, but I'll mention it anyways so it 
  doesn't get lost in the DECmcc shuffle...

  Wouldn't it make sense to change the "file invalid" message to something more
  specific (like "Icon file xxxxxxxxx.xxx invalid") so that the user will know 
  what file needs to be replace/fixed?

                                                                       - Jerry