RE: xinit working (no more startxwin.bat)

[Suhaib Siddiqi <ssiddiqi at inspirepharm dot com>]

> -----Original Message-----
> From: Piers Haken [mailto:piersh@friskit.com]
> Sent: Saturday, July 21, 2001 11:42 AM
> To: cygwin-xfree@cygwin.com
> Subject: RE: xinit working (no more startxwin.bat)
> 
> >
> > huh?  I am not sure what are you doing?
> >
> 
> 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.

Startxwin.bat is a sample file.  If you are on a Win9x/ME it can happen that
batch files will execute xterm and other xclients before server is fully up
and running.... that is because Win 9x/ME DOS shell is too slow to be useful
for something good.

But anyway.. you did not answer which OS you are using?

> 
> 2) xinit wasn't starting the server correctly on my system due to the
> error I posted.
> 

That is not a real solution... you are making a too many links to batch
files

Xwin-start.bat --> X --> xwin.  

Execute Xwin directly from batch file.


Suhaib

> So I posted a workaround just in case anyone else was having that
> problem. Maybe if you'd read my post instead of just biting my head
> off,
> you might have the answer to your question above.
> 
> Ouch.
> 
> Piers.