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

Conference bulova::decw_jan-89_to_nov-90

Title:DECWINDOWS 26-JAN-89 to 29-NOV-90
Notice:See 1639.0 for VMS V5.3 kit; 2043.0 for 5.4 IFT kit
Moderator:STAR::VATNE
Created:Mon Oct 30 1989
Last Modified:Mon Dec 31 1990
Last Successful Update:Fri Jun 06 1997
Number of topics:3726
Total number of notes:19516

142.0. "Fileview crash and burn?" by ASD::LOW (I'm the IRS) Tue Feb 07 1989 11:55

    I'm having trouble getting fileview running.  When I log
    in, I get my terminal window, icon box and session manager
    box.  If I start fileview, I get a "starting fileview"
    message.  About 20 seconds later, the fileview window
    tries to pop up, then instantly vanishes, taking the 
    icon box (and the window manager) with it.  I checked my
    process quotas against the DECwindows release notes, and they 
    seem OK.  I'm running on a MVII (9 meg) on a MIVC running
    VMS 5.1 and SDC DECwindows.  Anyone have a clue as to what
    might be happening?  Is there a log file I can look at?
    (dec$sm.log has next to nothing in it...)
    
    Thanks,
    
    Dave
    

T.RTitleUserPersonal
Name
DateLines
142.1What is your sylogin.com and login.com doing?OIWS20::BRYSONTue Feb 07 1989 16:327
What are you doing in your SYLOGIN.COM and LOGIN.COM?  Is there any error
messages in the Session Manager message box?  Does the problem only exist
with your account or do all accounts on the system exhibit this behavior?

David

142.2STAR::BENSONTue Feb 07 1989 16:469
    Remember that you can't execute an INQUIRE in LOGIN.COM if you're
    running FileView - but this isn't normally the symptom you get if
    you do. Try define DECW$VUE_OUTPUT to point to a file before starting
    FileView - the session manager will then use this as SYS$OUTPUT for the
    FileView process, and you may get some interesting info there.
    
    Tom
    

142.3No dice...RAYBAN::LOWI'm the IRSWed Feb 08 1989 09:1175
    I tried defining DECW$VUE_OUTPUT as a filename, and the file
    was never even created.  I got the "STARTING FILEVIEW" message,
    the screen "twitched", and the icon box went away...
    
    When I try and run vue$master with my server set to my
    workstation, I'm greeted by a host of error messages,
    listed below.  I also get similar messages when trying to
    run most DECwindows applications, so I suspect it's a 
    "setup" problem.  My login.com and the systems SYLOGIN.COM
    do not contain any inquire statements.  I don;t have a 
    decw$login in my login directory.  Do I need it?
    
    Thanks!
    
    Dave
    

$ set display/create/node=0/transport=local
$ run sys$system:vue$master
X error event received from server: BadValue - integer parameter out of range
Failed request major op code 1
 X_CreateWindow
  
Failed request minor op code 0 (if applicable)
  
ResourceID 0x0 in failed request (if applicable)
  
Serial number of failed request 34
  
Current serial number in output stream 40

%XLIB-E-ERROREVENT, error event received from server
X error event received from server: not a valid window ID
Failed request major op code 28
 X_GrabButton
  
Failed request minor op code 0 (if applicable)
  
ResourceID 0x20000e in failed request (if applicable)
  
Serial number of failed request 38
  
Current serial number in output stream 40

%XLIB-E-ERROREVENT, error event received from server
X error event received from server: not a valid window ID
Failed request major op code 28
 X_GrabButton
  
Failed request minor op code 0 (if applicable)
  
ResourceID 0x20000e in failed request (if applicable)
  
Serial number of failed request 39
  
Current serial number in output stream 40

%XLIB-E-ERROREVENT, error event received from server
X error event received from server: not a valid window ID
Failed request major op code 18
 X_ChangeProperty
  
Failed request minor op code 0 (if applicable)
  
ResourceID 0x20000e in failed request (if applicable)
  
Serial number of failed request 46
  
Current serial number in output stream 75
.
.
.

     

142.4A few suggestionsSTAR::BROUILLETTEWed Feb 08 1989 11:2822
    
    There are a couple of things to do:
    
    1. Put the define of decw$vue_output in decw$login.com.  The session
    manager is looking for that logical in the process name table of the
    session manager process.  ( This will be fixed in the next release).
    
    2. I suspect that the log file will show the same output as running
    vue$master interactively.   I have seen these error messages when
    neither vue$library or decw$system_defaults logical names are defined. 
    This can happen if you change the definition of lnm$file_dev to bypass
    the decw$logical_names table.  Have you done that?
              
    3. Check that the logical name decw$system_defaults passes through
    sys$library.  Check that the file sys$library:vue$defaults.dat exists
    and has a protection w:re.   
    
    4. Check that the logical name vue$library exists, and that there are
    com files in that directory with the protection w:re
    
    

142.5That hit the spot!ASD::LOWI'm the IRSWed Feb 08 1989 14:039
    .4 did the trick.  In SYLOGIN.COM, lnm$file_dev was defined in
    the process table, and did not include the decw$logical_names
    table.  Adding the decw$logical_names table did the trick...
    
    Thanks!
    
    Dave