Hi Harold.
That is funny - although my machines both start, these are the log
entries from my NT4 (SP6) and my Win98 machine. The NT one uses
ShadowDD, the Win98 machine uses ShadowDDNL!
Both machines use the standard startx script. The only thing I changed
is -fullscreen.
Logs follow.
Tim Thomson [EMAIL PROTECTED]:
On Sun, 2002-06-16 at 02:30, Rasjid Wilcox wrote:
Strangely enough, I was planning to start work on project again
this month, and perhaps even this weekend, with my first step being
to do the script to configure XDMCP access on a 'standard' linux
Hi,
Like Uwe, I haven't added any extra parameter to XWin.exe
(I suppose that's what you meant), I'm using either the
standard startx or startxwin.sh, but I have tried to run
XWin.exe directly from a shell as well, and this was
without any parameter.
To be honest, I'm not too familiar with
Exactly. If I use -indirect I can't even make local connections to the X
server - they just seem to hang. Becaue of this I can't do a 'xhost +'
to allow connection from a remote process. So it seems I have to get the
cookie correct. Unfortunately, your explaination lost me a little. Do I
have to
On 24 Jun 2002, Nick THOMPSON wrote:
Exactly. If I use -indirect I can't even make local connections to the X
server - they just seem to hang.
This is the normal behaviour. After using xdmcp, you can only connect from
the remote machine.
Becaue of this I can't do a 'xhost +'
to allow
Hi Ago,
Thanks for your help and sorry to bug you some more - I think I'm
missing something here. I have a ~5 remote Sun Boxes on which I'd like
to pick the least busy and run some X clients. I'm sitting at a Win2k
box (mywinhost) on which I type 'Xwin.exe -indirect mysunhost'. The X
server
Announcing the first release of a new package to the Cygwin distribution:
x2x. The usefulness of this utility will become apparent to anyone with a
PC side-by-side with an *ix workstation. Simply bring up an XWindows session
on each machine, run x2x on the PC, and use your PC's mouse and
Hi,
My XWin.exe line reads:
start /B XWin :0 -from TOSHI -query mylinux -depth 16 -fullscreen
OK. So I press ctrlesc to see Windows' lower taskbar. But,
how can I do a normal exit out of Cygwin/XFree86 without terminating
Cygwin command prompt window?
Thanks,
EW
Since upgrading, Xterm will not open. Other X apps seem to work fine. I
will see a brief flicker of xterm trying to open (from my startwin.bat file)
then its gone. I'm using the wmaker WM. If I use the run command, either
nothing happens, or wmaker crashes. I've looked around a bit for any
what appears in /tmp/XWin.log ?
--- ROTTENBERG,HAL (HP-USA,ex1)
[EMAIL PROTECTED] a écrit : Since upgrading,
Xterm will not open. Other X apps
seem to work fine. I
will see a brief flicker of xterm trying to open
(from my startwin.bat file)
then its gone. I'm using the wmaker WM. If I
I have same problem on my Win2000 machine and other problem is I can't start
KDE at all. It crashes into memory vialation exception while xinit.exe
starting.
Since upgrading, Xterm will not open. Other X apps seem to
work fine. I
will see a brief flicker of xterm trying to open (from my
My apologies, for being frantic. I forgot to test my latest xfree
installation. I've installed older cygwin by with new xserver
XFree86-xserv-4.2.0-7 and XTerm work fine. So problem isn't in xserv but
somewhere in other cygwin package. I will test next KDE.
Problem solving: downgrade latest
12 matches
Mail list logo
