Re: still no Xwin

2004-11-09 Thread Alexander Gottwald
On Tue, 9 Nov 2004, Bijell, Jens wrote: > Hello Alexander, > > I have an Identical problem with cygwin/X and I can´t get it to work. > the packages seem to be properly installed. > It is that damned XWin.exe he can´t find. > Do you have a clue on that? - do not mail me personally. Write to the c

Re: still no Xwin

2004-05-25 Thread Alexander Gottwald
Allen H. Nugent wrote: > This is a repeat posting (I forgot to reset the 'Subject' last time, so Why not just reply to the previous message. That way I can easily keep track of what was already suggested and I don't have to search the mailbox for some messages from Allen H. Nugent. > maybe the m

Re: still no Xwin

2004-05-24 Thread Igor Pechtchanski
On Tue, 25 May 2004, Allen H. Nugent wrote: > This is a repeat posting (I forgot to reset the 'Subject' last time, so > maybe the message was overlooked). I have been unable to use the > application that depends on Xwin (and which I need to complete my thesis) > for 2 weeks, now, so I am going to

still no Xwin

2004-05-24 Thread Allen H. Nugent
This is a repeat posting (I forgot to reset the 'Subject' last time, so maybe the message was overlooked). I have been unable to use the application that depends on Xwin (and which I need to complete my thesis) for 2 weeks, now, so I am going to have to be a pest until it I can get Xwin to run.

Re: STILL no Xwin

2004-05-20 Thread Alexander Gottwald
Allen H. Nugent wrote: > I just tried reinstalling the whole X11 package set. Same result! Please start a bash shell and check if /usr/X11R6/bin is in the $PATH variable. Also check if /usr/X11R6/bin/cygX11-6.dll is existing bye ago NP: Oomph! - Goldenes Herz -- [EMAIL PROTECTED] http://w

Re: STILL no Xwin

2004-05-19 Thread Allen H. Nugent
On Tue, 18 May 2004, Allen H. Nugent wrote: > It seems Setup _did_ install the new Xorg after all. But, it still won't > run. After navigating to the top directory, I tried two ways to invoke XWin > and got two bad results: > > $startxwin.bat > ==> causes a 'Run.exe' window that says: >