[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

64.0. "Reboot and XLIB error" by 8312::CURTIS (Steve Curtis - Colorado Springs) Mon Jan 30 1989 09:55

    A couple of (I think) unrelated questions.  I don't have the manuals,
    yet, so any help would be appreciated.
    
    1 - How do you reboot?  Running SYS$SYSTEM:SHUTDOWN from a DECTERM
    window causes the display manager (or is it session manager?) to quit,
    thus disabling further work on the DECTERM.  
    
    2 - I can only get one application to run from FileView.  Attempting to
    create a second apllication causes the following error 
    
    X Toolkit Error: Can't Open display
    %DWT-F-DWTABORT, xtoolkit fatal error
    
    I know this isn't much to go on.  Let me know what other kinds of
    information you need to determine the problem.
    
    Steve

T.RTitleUserPersonal
Name
DateLines
64.1LESLIE::LESLIEAndy ��� Leslie, CSSE / VMSMon Jan 30 1989 11:265
    1/ either run shutdown from a fileview DCL window, upgrade to IFT X5.2
    or use the procedure in #884 of RDGENG::COMMAND_PROCEDURES.
    
    2/ dunno

64.2Just talking to myself8312::CURTISSteve Curtis - Colorado SpringsMon Jan 30 1989 14:587
    As for #2 - the problem turned out to be a lack of global pages.  Once
    I upped the Autogen parameter, and rebooted, all was fine again.
    
    Thanks,
    Steve
    

64.3Yes you do have the manuals!!!GOROTH::MERMELLWindow PainMon Jan 30 1989 17:097
Yes you do have the manuals!!!

Use the online book reader.  Internally, the books
are available as a net kit, which you can install
on any disk that has enough room.  Customers,
though, will have to get a CD reader.

64.4XLIB error documentationSHARE::LEMONSAnd we thank you for your support.Wed Mar 08 1989 14:407
    Speaking of the online documentation, I spent � an hour searching
    through them for documentation on the XLIB error messages, without
    success.  Where are the little dears discussed?
    
    Thanks!
    tl

64.5there ain't noneDECWIN::JACKIEJackie FergusonThu Mar 09 1989 09:1932
Some of the routines list all the status return values, but this wasn't
finished in the V1 books.  Some routines can return other VMS messages
for descriptor related errors, etc.
Here's the list from the .msg file:

        .SEVERITY       WARNING

        BADPARAM        <invalid parameter encountered>
        ERROREPLY       <error reply received from server>
        NOMORE          <list of requested names has been exhausted>
        NOTFOUND        <item not found>
        PROPUNDEF       <requested property is undefined>
        TRUNCATED       <buffer too small; results are truncated>
        UNKNEVNT        <unknown event received>

        .SEVERITY       ERROR

        CANTOPEN        <cannot open display>
        INSFMEM         <insufficient dynamic memory>
        INVBUFFER       <invalid buffer number>
                                                    
        .SEVERITY       FATAL
        IOERROR         <xlib io error>
        LIBABORT        <xlib fatal error>

        .SEVERITY       ERROR
        ERROREVENT      <error event received from server>
        OBSOLETE        <obsolete xlib entry point referenced>

        .SEVERITY       INFORMATION
        NOHOSTS         <there are no hosts available to make connections>

64.6DNEAST::BOTTOM_DAVIDDeeper in DebtFri Mar 24 1989 09:2014
    I'm also having a problem and get the following error:
    
    XLIB error
    Serial 5925		Error code 8	Request code 42   minor 0
    Error text is <Bad match-parameter mismatch>
    
    I typically get this when trying to print from writer.
    
    VMS 5.1 on a 16 meg GPX
    
    any ideas or suggestions?
    
    dave

64.7DNEAST::BOTTOM_DAVIDDeeper in DebtTue Mar 28 1989 15:316
    re: .6
    it appears that XLIB.shr is missing from sys$library. How/where
    do I get a copy of this file? Or do I reinstall DECwindows?
    
    dave

64.8QUARK::LIONELThe dream is aliveTue Mar 28 1989 17:424
The image is DECW$XLIBSHR.EXE - do you have that?

	Steve

64.9DNEAST::BOTTOM_DAVIDDeeper in DebtTue Apr 04 1989 16:385
    Yes I do, (got that image name wrong at first sorry). However, I
    get occasional XLIB errors, usually when running writer.
    
    dave

64.10Any Idea's on thisVLNVAX::ELLISWed Aug 09 1989 11:1767
	The following is what I get after a mail window display is created
on my work station and try to open mail or any other folders. I can read new
mail and create/send without any problems. This comes and go's... 
I can run vue$master without any problems.
We are running SSB v5.2 on the server, and my Vaxstation II/GPX is in a 
LAVC also running SSB V5.2

DCE>set display/node=stowfd/creat

DCE>spawn/nowait/input=nl: mcr decw$mail

%DCL-S-SPAWNED, process ELLIS_1 spawned

X error event received from server: BadValue - integer parameter out of range
  
Failed request major op code 12
 X_ConfigureWindow
  
Failed request minor op code 0 (if applicable)
  
ResourceID 0xffffdd97 in failed request (if applicable)
  
Serial number of failed request 554
  
Current serial number in output stream 570

%XLIB-E-ERROREVENT, error event received from server

X error event received from server: BadValue - integer parameter out of range
  
Failed request major op code 12
 X_ConfigureWindow
  
Failed request minor op code 0 (if applicable)
  
ResourceID 0xffffdd97 in failed request (if applicable)
  
Serial number of failed request 555
  
Current serial number in output stream 570

%XLIB-E-ERROREVENT, error event received from server

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 0xffffdd96 in failed request (if applicable)
  
Serial number of failed request 559
  
Current serial number in output stream 570

%XLIB-E-ERROREVENT, error event received from server

X error event received from server: not a valid window ID
  
Failed request major op code 8
 X_MapWindow
  
Failed request minor op code 0 (if applicable)
  
ResourceID 0x50008e in failed request (if applicable)
  
Serial number of failed request 564
  
Current serial number in output stream 570

%XLIB-E-ERROREVENT, error event received from server

Dave

64.11GOSOX::RYANDECwindows MailThu Aug 10 1989 09:076
	I've seen that before, it generally means munged resources. Check
	out DECW$SYSTEM_DEFAULTS:DECW$MAIL.DAT and DECW$USER_DEFAULTS:
	DECW$MAIL.DAT and make sure nobody's messed with them...

	Mike