Xwin error

[Suhaib Siddiqi]

XIO:  fatal IO error 104 
(Connection reset by peer) on X server ":0.0"       
after 0 requests (0 known processed) with 0 events remaining.
 
Is the 
X-server booting?  Are you getting X-desktop or is the X-server dying 
immediately on startup.
 
Suhaib
 

  -----Original Message----- From: TRIKKALIOTIS Nikolaos 
  [mailto:Nikolaos.Trikkaliotis@serfrance.fr] Sent: Tuesday, June 27, 
  2000 8:17 AM To: Suhaib Siddiqi Subject: Re: Xwin 
  error
  I use WinNT 4.0 SP6a.
  
    ----- Original Message ----- 
    From: 
    Suhaib Siddiqi 
    To: cygwin-xfree@sourceware.cygnus.com 
    
    Sent: Tuesday, June 27, 2000 2:04 
    PM
    Subject: RE: Xwin error
    
    You should figure out what should be the next 
    error?  How should I know?
     
    Win95/98 are not supported for XWin, dues to 16 bit 
    crap behind the glorious desktop... it cann handle surface lock and unclocks 
    
    of 
    x-server without crashing win9x.
     
    Suhaib
     
    
      -----Original Message----- From: cygwin-xfree-owner@sourceware.cygnus.com 
      [mailto:cygwin-xfree-owner@sourceware.cygnus.com] On Behalf Of 
      TRIKKALIOTIS Nikolaos Sent: Tuesday, June 27, 2000 7:48 
      AM To: cygwin-xfree@sourceware.cygnus.com Subject: 
      Xwin error
      
      What is the next error ???
      ======================
       
      scheduling timer: Invalid argument _XSERVTransmkdir: Owner of 
      /tmp/.X11-unix should be set to root pwin->width = 
      00000500 pwin->height = 00000400 pwin->paddedWidth = 
      00000a00 pwin->bitsPerPixel = 00000010 calling 
      winAllocateFramebufferMemory
       
      +===============================+ | Direct Draw Init 
      Failed       | | Error=88760078(unknown 
      error) | +===============================+
       
      XIO:  fatal IO error 104 (Connection reset by peer) on X server 
      ":0.0"       after 0 requests (0 known 
      processed) with 0 events 
  remaining.