This is the mail archive of the
cygwin-xfree@cygwin.com
mailing list for the Cygwin XFree86 project.
RE:XWin works on Win2K but not on some WinXP clients
- From: Alexander Gottwald <Alexander dot Gottwald at s1999 dot tu-chemnitz dot de>
- To: "'cygwin-xfree at cygwin dot com'" <cygwin-xfree at cygwin dot com>
- Date: Mon, 10 Nov 2003 22:27:46 +0100 (MET)
- Subject: RE:XWin works on Win2K but not on some WinXP clients
- References: <BC1489C260F5D611A6A400508BB0929303AE7183@XCGVA007>
- Reply-to: cygwin-xfree at cygwin dot com
Woellert, Kirk D. wrote:
> MIT-SHM extension disabled due to lack of kernel support
> XFree86-Bigfont extension local-client optimization disabled due to lack of
> shared memory support in the kernel
> (==) winConfigKeyboard - Layout: "00000409" (00000409)
> (EE) No primary keyboard configured
> (==) Using compiletime defaults for keyboard
> Rules = "xfree86" Model = "pc101" Layout = "us" Variant = "(null)" Options =
> "(null)"
> winPointerWarpCursor - Discarding first warp: 637 481
> winBlockHandler - Releasing pmServerStarted
> winBlockHandler - pthread_mutex_unlock () returned
> winDeinitClipboard - Noting shutdown in progress
> winDeinitMultiWindowWM - Noting shutdown in progress
> winDeinitClipboard - Noting shutdown in progress
> winDeinitMultiWindowWM - Noting shutdown in progress
> winDeinitMultiWindowWM - Noting shutdown in progress
> winDeinitClipboard - Noting shutdown in progress
> winDeinitMultiWindowWM - Noting shutdown in progress
There is no evidence why xdmcp failed. Is a firewall (even the winxp builtin)
present? Can you check the xdm logfiles on the server? Maybe they contain
some information why you can't get access.
@Harold: Are the winDeinitClipboard and -MultiWindowWM messages ok? I
assume they are called even if the -multiwindow and -clipboard parameters
are not supplied.
NP: Enya - Shepherd Moons
--
Alexander.Gottwald@informatik.tu-chemnitz.de
http://www.gotti.org ICQ: 126018723