Conference azur::mcc

    
    Susan,
    To solve the first problem (the missing bitmap), make certain there
    is a file called mcc_terminal_server_icon.dat in the directory
    pointed to by the logical mcc_icons.  Also, make sure the file has
    read access.
    
    Fred

    I reported the same problem in note 1013.  I checked the file and the
    logical.  They are both in place and the file has read access. Other
    suggestions?
    
    Thanks in advance
    
    Bob

      Does the  MCC_ICONS logical  name  point  to  the  MCC_COMMON 
      directory?   The  TSAM  installation procedure moves the file 
      MCC_TERMINAL_SERVER_ICON.DAT  to  MCC_COMMON.   If  MCC_ICONS 
      is  a  separate directory,  you  should  copy  the file  from 
      MCC_COMMON to MCC_ICONS.

      With regards to not being able to register a terminal server, 
      is this because of the icon problem,  or  is there a separate 
      problem?  If it is a separate problem, I'll need more details 
      in order to help you out.

					Lynne

In my situation, I am able to register terminal servers through the command
line/forms interface.  I did have some problems because the command line
interface commands on the bottom of page 5-4 for registering servers
included a keyword qualifier of "NAME" that was not necessary.  

I have not been able to resolve the "bitmap" problem.

Attached is some additional info that you were interested in:

$ show logical mcc_icons
   "MCC_ICONS" = "MCC_COMMON" (LNM$SYSTEM_TABLE)
1  "MCC_COMMON" = "SYS$COMMON:[MCC]" (LNM$SYSTEM_TABLE)


$ dir/prot/size mcc_icons:mcc_term*

Directory SYS$COMMON:[MCC]

MCC_TERMINAL_SERVER_ICON.DAT;1
                          3  (RWED,RWED,RWED,RE)

Total of 1 file, 3 blocks.

                
What other information can I provide?

Bob

    Perhaps the bitmap file has been corrupted somehow?   If you still
    have the TSAM kit, you may want to try to extract the icon file
    again:

    $BACKUP/SELECT=MCC_TERMINAL_SERVER_ICON.DAT MCCTSAM010.B/SAV MCC_ICONS:

    I'm not sure what else to suggest.  Can somebody who works on the
    DECwindows interface help out?

					Lynne

>>  Perhaps the bitmap file has been corrupted somehow?   If you still
>>    have the TSAM kit, you may want to try to extract the icon file
>>    again:
>>
>>  $BACKUP/SELECT=MCC_TERMINAL_SERVER_ICON.DAT MCCTSAM010.B/SAV MCC_ICONS:

Yes, try the above.  If that doesn't work, post the icon file in a reply and
we can look it.

Fred

    
    mail the icon file, or place a pointer to the file here. Please
    refrain from placing the file here. Many people print the notes file
    out on a regular basis, let's save a few trees.
    
    moderator hat on
    

    I have duely been corrected. The icon files are simple ascii files and
    not very large. Placing it in the conference should therefore not
    cause any problems.
    
    thanks for the info Fred.

Thanks for your never ending open-mindedness and flexibility!!!

    I extracted the file from the saveset and performed a DIFFERENCES
    between the 2 files.  Both files were 3 blocks and no differences were
    found.  Here is the file.
    
    Thanks for your help.
    
    Bob

#define ts_width 40
#define ts_height 40
static char ts_bits[] = {
   0xff, 0xff, 0xff, 0xff, 0xff, 0x03, 0x00, 0x00, 0x00, 0xc0, 0xfd, 0xff,
   0xff, 0xff, 0xff, 0x05, 0x00, 0x00, 0x00, 0xe0, 0x05, 0xfc, 0xff, 0x07,
   0xe0, 0x05, 0x04, 0x00, 0x04, 0xe0, 0x05, 0xf4, 0xff, 0x05, 0xe0, 0x05,
   0xf4, 0xff, 0x05, 0xe0, 0x05, 0xf4, 0xff, 0x05, 0xe0, 0x05, 0xf4, 0xff,
   0x05, 0xe0, 0x05, 0xf4, 0xff, 0x05, 0xe0, 0x05, 0x04, 0x00, 0x04, 0xe0,
   0x05, 0xfc, 0xff, 0x1f, 0xe0, 0x05, 0xf8, 0xff, 0x23, 0xe0, 0x05, 0x6c,
   0xdb, 0x42, 0xe0, 0x05, 0x92, 0x24, 0x85, 0xe0, 0x05, 0xd9, 0xb6, 0x09,
   0xe1, 0x05, 0x01, 0x00, 0x08, 0xe2, 0x05, 0xfe, 0xff, 0x07, 0xe4, 0x05,
   0x00, 0x00, 0x00, 0xe8, 0x05, 0x00, 0x00, 0x00, 0xe8, 0x05, 0x00, 0x00,
   0x00, 0xe8, 0xf5, 0xff, 0xff, 0xff, 0xe9, 0xf5, 0xff, 0xff, 0xff, 0xe9,
   0x35, 0x00, 0x00, 0x80, 0xe9, 0xb5, 0xef, 0xfb, 0xbe, 0xe9, 0xb5, 0x28,
   0x8a, 0xa2, 0xe9, 0xb5, 0xef, 0xfb, 0xbe, 0xe9, 0x35, 0x00, 0x00, 0x80,
   0xe9, 0xb5, 0xef, 0xfb, 0xbe, 0xe9, 0xb5, 0x28, 0x8a, 0xfe, 0xef, 0xb5,
   0xef, 0xfb, 0xbe, 0xe1, 0x35, 0x00, 0x00, 0x80, 0xe1, 0xf5, 0xff, 0xff,
   0xff, 0xe1, 0xf5, 0xff, 0xff, 0xff, 0xe1, 0x05, 0x00, 0x00, 0x00, 0xe0,
   0x05, 0x00, 0x00, 0x00, 0xe0, 0xfd, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff,
   0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff};
       

Bob,
Give me a call.  226-5339.

Fred

Bob and I solved this one over the phone.  We found his terminal
server icon MCC_TERMINAL_SERVER_ICON.DAT in a demo account that had
been created by the demo installation.  How it got there, we're
not really sure, but it's being looked into.

Fred

Please see note 425.45... Mr. McPhereson shines again!

Re: Note 1009.13 by TOOK::F_MESSINGER
	
	Errr.... Ummmm
	I believe that's 452.45 Fred.
                          ^^