This is the mail archive of the
cygwin-xfree@cygwin.com
mailing list for the Cygwin XFree86 project.
RE: xinit working (no more startxwin.bat)
- To: Piers Haken <piersh at friskit dot com>
- Subject: RE: xinit working (no more startxwin.bat)
- From: Tzafrir Cohen <tzafrir at technion dot ac dot il>
- Date: Sat, 21 Jul 2001 21:34:27 +0300 (IDT)
- Cc: <cygwin-xfree at cygwin dot com>
On Sat, 21 Jul 2001, Piers Haken wrote:
> I'm sharing the solution I found to a problem I was having. My problem
> was twofold:
>
> 1) startxwin.bat wasn't working because the 'start xterm' and 'start
> twm' commands are executed before the 'Xwin'process has had a chance to
> fully start the server. The startxwin.bat should, in theory, wait until
> the X server is running before proceeding to start any clients, but of
> course there's no way to do this effectively with cmd.exe. This is
> precisely what xinit is supposed to do.
I'm not sure that your diagnostics is correct here. This batch file seems
to work for people (my personal observasion: WorksForMe)
But If there's no way to do it with cmd.exe which is probably a slightly
better shell than lsh, but not more than that) then do it with bash.
Since I know linux better, I modified that batch file to set some
envionment vars and run 'startx'. And then I put all the clients I want in
~/.xinitrc and if I want to modify the server arguments I use ~/.xserverrc
. In your case the xserverrc file should contain (If I understand you
currectly):
XWin.exe -screen 0 800x600x32 -engine 4
--
Tzafrir Cohen
mailto:tzafrir@technion.ac.il
http://www.technion.ac.il/~tzafrir