Hi, I read serveral mailings about speed problems, but none seem to solve my problem. In our network we have a Linux box (RH7,1) configured for xdm. Xwin runs fine on the Win98 and WinNT boxes, but it's very slow on W2k.
I use this script for starting Xwin: SET MAKE_MODE=UNIX SET PATH=s:\develop\unix\cygwin\bin;s:\develop\unix\cygwin\usr\bin;s:\develop\unix\cygwin\usr\X11R6\bin;%windir%\system32;%windir%\command mount -f s:/develop/unix/cygwin / mount -f "%tmp%" /tmp SET DISPLAY=127.0.0.1:0.0 SET HOME=z:\ XWin -query 192.168.1.200 -nowinkill -unixkill -once -fp tcp/192.168.1.200:7100 On W2k it takes minutes to get de xdm login screen, while eating a lot of CPU time. Everyting you do from then is slow and CPU expensive. The W2k boxes have SP2 installed. Another strange thing is the contents of xwin.log, it only contains two lines: ddxProcessArgument () - Initializing default screens winInitializeDefaultScreens () - w 1024 h 768 On win98 I see a lot more: ddxProcessArgument () - Initializing default screens winInitializeDefaultScreens () - w 1024 h 768 ddxProcessArgument () - screen - argc: 16 i: 3 _XSERVTransmkdir: Owner of /tmp/.X11-unix should be set to root winDetectSupportedEngines () - Windows 95/98/Me winDetectSupportedEngines () - DirectDraw installed winDetectSupportedEngines () - DirectDraw4 installed winDetectSupportedEngines () - Returning, supported engines 00000017 winSetEngine () - Using user's preference: 1 winAdjustVideoModeShadowGDI () - Using Windows display depth of 16 bits per pixel winAdjustForAutoHide - Original WorkArea: 0 0 740 1024 winAdjustForAutoHide - Adjusted WorkArea: 0 0 740 1024 winCreateBoundingWindowWindowed () - WindowClient w 1018 h 715 r 1018 l 0 b 715 t 0 winCreateBoundingWindowWindowed () - Returning winInitVisualsGDI () - Masks 0000f800 000007e0 0000001f BPRGB 6 d 16 winLayerCreate () - dwDepth 16 winRandRInit () winCreateDefColormap () - Deferring to fbCreateDefColormap () winScreenInit () - returning Any ideas? Regards, Koos Vriezen
