RE: xdm question
Jeremy, Harold, All, The from parameter did the trick. I have multiple network cards in this win2k host. Thanks. -- Greetz, Wout mailto:[EMAIL PROTECTED] http://www.woutdejong.com -Original Message- From: Harold L Hunt [mailto:[EMAIL PROTECTED]] Sent: Tuesday, 28 May, 2002 14:32 To: Wout de Jong Cc: [EMAIL PROTECTED] Subject: Re: xdm question Wout, Read this: http://xfree86.cygwin.com/docs/faq/cygwin-xfree-faq.html#q-tasklist-programs- slow (be careful that part of the URL has not wrapped around... be sure to copy and paste both parts if that has happened) Also, make sure that you do not have Hummingbird SOCKS installed... I swear I wrote a FAQ entry for this, but I can't seem to find it: http://www.hummingbird.com/products/nc/socks/index.html Report your results to the [EMAIL PROTECTED] mailing list. Harold Jeremy Wilkins [EMAIL PROTECTED] said: try using Xwin -query 10.0.0.2 -from myIPAddress If you've got multiple interfaces this sometimes works better. Jeremy Wout de Jong wrote: Hi, After reading xdm howto and setting things up according to manual, I tried to use xwin -query 10.0.0.2 to contact my linux box. But only the xserver fired up, no login screen to be seen. When using xwinpro (with query switch) I got a login screen after a couple of seconds. Anybody an idea? TIA.
Re: icons not showing
The -depth parameter to XWin.exe seems enough. I can leave the screen depth at what it was (32bit) and just add -depth 24 to XWin.exe. Thanks Hrafnkell On 2002-05-30, 14:47:08 (+0100), Scott Alexander wrote: Yep a work around for this is to lower the screen depth of your windows box to 16 bit or what ever is closest normaly one down from max. - Original Message - From: Hrafnkell Eiríksson [EMAIL PROTECTED] it to connect to a redhat 7.3 box running kde 3.0. I connect via XDMCP query. The login manager works fine but when KDE is starting up text in the status dialog (starting window manager etc) is garbled (every status message is written on top of the last message) and I get no icons, not on the desktop and not on the KDE toolbar.
-xkbmap parameter not working?
Hi I can't get the -xkbmap parameter to work. I want to use it to set the keyboard layout to Icelandic. Issuing setxkbmap is from a shell after I log in works (though I have to issue it twice for some reason). I though that adding -xkbmap is to the XWin.exe command line should do the trick but it has no effect. The XFree installation on my Win2k (cygwin) host has all the xkb mapfiles in /usr/X11R6/lib/xkb/ What do I have to do to get this working? Thanks Hrafnkell
significant delay in xinit detected
Hi all, while working with kde/cygwin and xfree/cygwin I recognized a significant timeout of xinit, after starting the x server andbefore starting the x client relevant stuff. It seems that xinit goes into a timeout while waiting for the X process, because the delay does not depend on how long the xserver needs (I recognized this on a very fast machine, on which the xserver only needs 1/2 second to start). xinit waits then 5 seconds before starting the .xinitrc script. I remember on the first days on kde2 we have a similar problem with kdeinit, which was solved by Chris January. Because currently I have no idea, whats going on, is there anyone who can give a hints for this ? Regards Ralf Habacker
AmiWM Port
Title: AmiWM 0.20-pl48Url: http://www.megaservice.host.sk/AmiWM-0.20pl48-cygwin.tar.gzType: SoftwareAuthor: Diego DuarteEmail: [EMAIL PROTECTED]Date: 2002-05-30Text: The WorkBench WM ( AmigaPC) ( very very, smaller, (145kb )) AmiWM-0.20pl48-cygwin.tar.gz Description: application/compressed
RE: TWM menus don't launch xterms
--- Pille Geert (bkarnd) [EMAIL PROTECTED] wrote: Have you tried to start twm and capture its output? twm /tmp/twm.out 2/tmp/twm.err You can also check XWin.log in /tmp. __ Do You Yahoo!? Yahoo! - Official partner of 2002 FIFA World Cup http://fifaworldcup.yahoo.com
RE: significant delay in xinit detected
while working with kde/cygwin and xfree/cygwin I recognized a significant timeout of xinit, after starting the x server andbefore starting the x client relevant stuff. It seems that xinit goes into a timeout while waiting for the X process, because the delay does not depend on how long the xserver needs (I recognized this on a very fast machine, on which the xserver only needs 1/2 second to start). xinit waits then 5 seconds before starting the .xinitrc script. Looking a little deeper into the source shows that the timeout is about 15 sec, not only 5, and it seems that xinit does not recognizes the running x process. Ralf
