Re: X server won't start in win95a

[Raymond Kwong <kwong at control dot toronto dot edu>]

Unfortunately, using "-engine 1" didn't start the X server either. I guess I
don't really know where to look to pinpoint the problem. If anyone can suggest
which files on the 2 win95 systems (the one that works and the one that
doesn't) I should compare, I'll give it another try. It sure makes one 
appreciate Linux, doesn't it!

Raymond
  
On Mon, Jun 18, 2001 at 08:02:12PM -0400, Suhaib Siddiqi wrote:
> On the Windows 95a machines with  DirectX 4, installed you can try using GDI
> blitter.  That is -engine 1, instead of 4.  Edit startxwin.bat or your
> startx script and replace -engine 4 by engine 1. If DirectX 4 is causing
> problems, you may see a GDI display.
> 
> Let us know
> 
> Suhaib
> 
> > -----Original Message-----
> > From: Raymond Kwong [mailto:kwong@control.toronto.edu]
> > Sent: Monday, June 18, 2001 2:30 PM
> > To: ssiddiqi@inspirepharm.com
> > Cc: cygwin-xfree@cygwin.com
> > Subject: RE: X server won't start in win95a
> > 
> > I installed the same set of files on the 3rd win95 machine to re-
> > assure
> > myself that the installation does work. The only thing I have noticed
> > so
> > far is that the working win95 machine did not have directX installed,
> > whereas one of the non-working win95 machines has directX version 4
> > installed. Could that have caused a problem?
> > 
> > Raymond
> > 
> > > From: Raymond Kwong [mailto:kwong@control.toronto.edu]
> > > Sent: Monday, June 18, 2001 11:28 AM
> > > To: ssiddiqi@inspirepharm.com
> > > Subject: Re: X server won't start in win95a
> > >
> > >
> > > I installed cygwin and xfree86 4.0.3 on a 3rd win95 machine. Lo and
> > > behold, this one worked! The other two still didn't. I haven't
> > figured
> > > out what is the difference between these machines. I suppose
> > > windows is
> > > so obscure that such detective work may be painstaking and
> > > time-consuming. Have you heard from anyone else who had the symptoms
> > I
> > > have, i.e. waiting for X server to accept connections? I think that
> > is
> > > the key to the mystery. Do you have any further insights?
> > 
> > 
> > Why do not you try Xfree86 4.1.0?  No I do not have any insight,
> > except that
> > your windows TCP/IP might be messed up on those two machines.  Hard to
> > say
> > anything.
> > 
> > Suhaib
> > 
> > >
> > > Raymond
> > >
> > > On 15 Jun, Suhaib Siddiqi wrote:
> > > >
> > > >
> > > >> -----Original Message-----
> > > >> From: Raymond Kwong [mailto:kwong@control.toronto.edu]
> > > >> Sent: Friday, June 15, 2001 2:32 AM
> > > >> To: Suhaib Siddiqi
> > > >> Subject: Re: X server won't start in win95a
> > > >>
> > > >>
> > > >> X server did not start with testx. I have tried both cygwin
> > > >> 1.1.8-2 and
> > > >> 1.3.1-1 without success. The only thing I have not tried is
> > > >> the newest cygwin
> > > >> and the newest xfree86. Have other people reported success
> > > >> with win95a?
> > > >
> > > > Yes, you can check mail archive.
> > > > Can you try Cygwin 1.3.2 and XFree86 4.1.0?
> > > >
> > > > Suhaib
> > > >
> > > >>
> > > >> Raymond
> > > >>
> > > >> On Thu, Jun 14, 2001 at 07:07:36PM -0400, Suhaib Siddiqi wrote:
> > > >> > Please put the attached "testx" file in /usr/X11R6/bin,
> > > >> then open a Cygwin
> > > >> > bash shell.
> > > >> >
> > > >> > Cd /usr/X11R6/bin
> > > >> >
> > > >> > Chmod 755 testx
> > > >> > ./testx
> > > >> >
> > > >> > PS: Change vtwm & to twm& if you do not have vtwm installed.
> > > >> > Remove or rename your .xinitrc and .xserverrc files.
> > > >> >
> > > >> > Let me know if server starts or not.
> > > >> >
> > > >> >
> > > >> >
> > > >> > > -----Original Message-----
> > > >> > > From: Raymond Kwong [mailto:kwong@control.toronto.edu]
> > > >> > > Sent: Thursday, June 14, 2001 5:16 PM
> > > >> > > To: cygwin-xfree@cygwin.com
> > > >> > > Subject: Re: X server won't start in win95a
> > > >> > >
> > > >> > > I didn't try them all, but I tried 640x480, and it didn't
> > > >> work. Should I
> > > >> > > try others?
> > > >> > >
> > > >> > > Raymond
> > > >> > >
> > > >> > > > What I mean by the bash prompt chaning to XWin is that the
> > > >> > > > title of the
> > > >> > > > prompt window changes to XWin. I don't mean that the
> > > >> window changes to
> > > >> > > > an X server window!
> > > >> > > >
> > > >> > > > My .xinitrc is standard:
> > > >> > > > #!/bin/bash
> > > >> > > > export DISPLAY=127.0.0.1:0.0
> > > >> > > > export PATH=.:$PATH:/usr/X11R6/bin
> > > >> > > > xterm -sb -sl 1024 -font 9x15 -e /bin/bash &
> > > >> > > > twm
> > > >> > > >
> > > >> > > > My .xserverrc is also standard:
> > > >> > > > #!/bin/bash
> > > >> > > > exec XWin -screen 0 1024x768x16 -whitepixel 255 -blackpixel
> > 0
> > > >> > > > -engine 4
> > > >> > >
> > > >> > >
> > > >> > > Did you try at lower resolution e.g. 600x800 to see if
> > > it works.
> > > >> > >
> > > >> > >
> > > >> > > Suhaib
> > > >> > >
> > > >> > > >
> > > >> > > > I have tried options such as -fullscreen, -ac, with the
> > > >> same results.
> > > >> > > >
> > > >> > > > The same setup on my windows 2000 thinkpad works fine.
> > > >> > > >
> > > >> > > > Many thanks for your fast response.
> > > >> > > >
> > > >> > > > Raymond
> > > >> > > >
> > > >> > > > On 14 Jun, Suhaib Siddiqi wrote:
> > > >> > > > >
> > > >> > > > >
> > > >> > > > >> I recently installed cygwin and cygwin-xfree 4.0.3.
> > > >> > > > >> Everything works except
> > > >> > > > >> for the X server. If I run startxwin.bat, XWin
> > > window comes
> > > >> > > > >> up but does not
> > > >> > > > >> change into the X root window. Xterm and vtwm
> > > then come up,
> > > >> > > > >> stay for a while
> > > >> > > > >> and exit. XWin window stays black and blank and does not
> > > >> > > > >> exit. I need to kill
> > > >> > > > >> it manually. There are no error messages for XWin.
> > > >> > > > >
> > > >> > > > >
> > > >> > > > > We need more info.
> > > >> > > > > post your startxwin.bat
> > > >> > > > > what are the messages displayed in DOS window when you
> > use
> > > >> > > > startxwin.bat?
> > > >> > > > >
> > > >> > > > >>
> > > >> > > > >> I also tried running startx from the bash prompt.
> > > I created
> > > >> > > > >> .xinitrc and
> > > >> > > > >> .xserverrc. When I run startx, the bash window changes
> > to
> > > >> > > > >> XWin,
> > > >> > > > >
> > > >> > > > > Never heard of a bash window chnaging to xwin??? Can you
> > > >> > > > explain what
> > > >> > > > > do you mean, a bash window can never change to xwin or
> > > >> > > > x-server window,
> > > >> > > > > whatever.
> > > >> > > > >
> > > >> > > > > Suhaib
> > > >> > > > >
> > > >> > > > >> and after
> > > >> > > > >> a little while, an error message comes up saying
> > > "waiting for
> > > >> > > > >> X server to
> > > >> > > > >> begin accepting  connections" followed by
> > > periods. If I kill
> > > >> > > > >> it by Ctrl-C,
> > > >> > > > >> an error message comes up saying "xinit, no such file or
> > > >> > > > >> directory (errno 2):
> > > >> > > > >> unexpected signal 2".
> > > >> > > > >>
> > > >> > > > >> I am still running the ancient win95a, but I am under
> > the
> > > >> > > > >> impression that
> > > >> > > > >> the X server works for all versions of win9x. It is
> > > >> > > > >> interesting to observe
> > > >> > > > >> that the win32-x11 server works (as does xvnc), but it
> > is
> > > >> > > > >> excruciatingly
> > > >> > > > >> slow. Can anyone point out where the problem lies?
> > > >> > > > >>
> > > >> > > > >> Thanks!
> > > >> > > > >>
> > > >> > > > >> Raymond Kwong
> > > >> > > > >>
> > > >> > > >
> > > >> > > >
> > > >> > > >
> > > >> > >
> > > >> >
> > > >> >
> > > >>
> > > >>
> > >
> > >