Re: 6.7.0.0 XWin w/out -nodecoration running in background doesn't display anything
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Great! Just did it with the solution mentiond by David Rothenberger. With sending XWin in the background with i managed it to only get the XWin server window. But i need to command files: a DOS batch and a sh batch. Now it run's with only on batch file like before! Thanks a lot to all! Am Freitag, 9. April 2004 18:00 schrieb Holger Krull: Sure. Call CreateProcess with appropriate flags, just like run.exe does... Thank you, that's the solution. I didn't know this program. I now can call Xwin without having an additional shell window. The needed command for me is : E:\cygwin\bin\bash.exe -c -l 'run bash -c -l CYGWIN=server Xwin.exe -query murpel -fp tcp/murpel:7100 -dpi 100 -clipboard -once ' Before someone asks, the reason for the additional bash is my whish to avoid having cygwin directorys in my windows path. So \cygwin\usr\X11R6\bin\run.exe bash -c -l Xwin.exe -query SOMENAME will probably do for everyone else. Thank you for your help Holger - -- Rudolf Kollien email: [EMAIL PROTECTED] [EMAIL PROTECTED] * Never trust a operating system you have no sources for * Buying an operating system without source is like buying a self-assembly Space Shuttle with no instructions. * -BEGIN PGP SIGNATURE- iD8DBQFAdtb/zOHTWsKaqE0RAuzqAKCKN0/IGYaiIf9Hsi40xi4ejBTZLwCfR4cg Mmh8nzqLaAHx+KgcgE15qBw= =I8Q0 -END PGP SIGNATURE-
6.7.0.0 XWin w/out -nodecoration running in background doesn't display anything
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello, i just upgraded to the new X11 (X.org) version of cygwin/X (Release 6.7.0.0-1. I use XWin to connect via XDMCP to several linux server. My previous used startup script is a MS-DOS batch file in which i fire-up XWin.exe with start XWin.exe -fp and so on. This is all ok. I get an connection and can work. But with this new X11 release i get a additional window with all the status and error messages from XWin. Until now XWin run in background when startet by the DOS start-command. When i try the new cygwin command run, as used in the sample startxdmcp.bat, i'm only can do this by supplying the -nodecoration parm. Without this param, i do not see any X-client nor the login screen from kde (in my case). Even XWin runs an has a connection to the server. I see the X in the systray, right clicking an choosing Exit reminds me that three clients connected. Shortly said: when you want to run X in a M$-Windows Window (let - -nodecorations away) then you can't run XWin in background. As i use up to 6 XDMCP connections to different linux servers with different screen sizes and resolutions, i now have 12 Windows on the desk (or taskbar, when minimized). Is there a way to get the old behavor back? Testcase: - - run XWin.exe -query HOST = you see the X in the systray but nothing else. - - run XWin.exe -query HOST -nodecorations = you get a fullscreen login screen to the server - - start XWin.exe -query HOST = you get the servers login screen in a Windooze window and an _additional_ console window with the text messages from XWin.exe - - start /b XWin.exe -query HOST = same as run XWin Regards - -- Rudolf Kollien email: [EMAIL PROTECTED] * Never trust a operating system you have no sources for * Buying an operating system without source is like buying a self-assembly Space Shuttle with no instructions. * -BEGIN PGP SIGNATURE- iD8DBQFAdaMqzOHTWsKaqE0RAjBzAJ4nmwvsiRCfJsPwd78r2V/F9B3MKgCfa/R9 1WgN4gBq5vhfKrE6ALKSbQ8= =OCSD -END PGP SIGNATURE-
Re: 6.7.0.0 XWin w/out -nodecoration running in background doesn't display anything
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello Harold, sorry, if my question sounds stupid, but... when i can't use run in a batch why there is run used in the startxdmcp.bat? It does the job as requested. But only with -nodecorations. Why can a window without border and titlebar can be used, but a normal window not? I don't want to compare to the old XFree86 (i'm glad about the new project) but once upon a time there where the same problem but was gone long ago. I will try the hint from David Rothenberger with setsid (never heared about). Sound's good. The problem is, that when the controlling window ist closed, the whole X-session gets killed. I i know my users: the will close this unneccessary window. Am Donnerstag, 8. April 2004 21:51 schrieb Harold L Hunt II: Yeah, you can't use run in the batch file... you have to use start instead. I noticed this right before the release, but I don't have a permanent solution yet. We had to switch from start to run because start doesn't prevent a DOS box from being displayed and because we switched XWin.exe from not displaying a DOS box by default to displaying a DOS box by default. The reason for this is that the new logging facility allows sending messages both to standard output and to a log file if one is opened sometime after the server starts (message have to be cached until that point since they would otherwise be lost since the log file isn't open yet). The nicest thing about this is that people running XWin -help will now see the help output instead of having to open /tmp/XWin.log to see the output. What is the permanent solution to the problem? I don't know. I think it may be time to finish writing the batch file that just launches a bash shell script, but I haven't got time to work on that today. Harold -BEGIN PGP SIGNATURE- iD8DBQFAdd0ozOHTWsKaqE0RAhnsAJ9PM2jUh0CdZIvt1sWXXgQ/MAfgkQCgoid1 K7ioTXTqK3f5Pl4V6NIg+MI= =gqaK -END PGP SIGNATURE-
Re: 6.7.0.0 XWin w/out -nodecoration running in background doesn't display anything
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 As cygwin provides a *nix-like environment, there IS a (shell) solution. Would be the first problem which couldn't worked around :-) Am Freitag, 9. April 2004 01:20 schrieb Harold L Hunt II: Rudolf Kollien wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello Harold, sorry, if my question sounds stupid, but... when i can't use run in a batch why there is run used in the startxdmcp.bat? It does the job as requested. But only with -nodecorations. Why can a window without border and titlebar can be used, but a normal window not? I don't want to compare to the old XFree86 (i'm glad about the new project) but once upon a time there where the same problem but was gone long ago. I didn't want to get into the details of what works and what doesn't work. You are right that it seems to work fine with -query, but it doesn't work with other options. I don't know what is going on, but I suspect we can probably fix it by modifying either run.exe or XWin.exe... but the other solution is to just use bash so we can do XWin instead of using start or run. Find whatever solution you need for the time being until it can be fixed properly. Harold -BEGIN PGP SIGNATURE- iD8DBQFAdem4zOHTWsKaqE0RAtEWAJ9SZPZg4ES90Bj/A/nemtWHmhZtUQCeND+G hjHezE9P/5je1My7JfyNNI0= =klTm -END PGP SIGNATURE-
