When I start using cygwin.bat, it merely starts up a bash in a simulated unix env in an XP cmd window. Then I have to run startxwin.sh, which starts my cygwin-x server on display 0.0.
After which I rlogin to real unix machines, setenv DISPLAY mysillylaptop:0.0, to run graphical apps which throw Xwindows onto my cygwin-x server. If I ever dared close my unabashedly bash XP cmd window, all my X client windows would disappear. The question that trebor(robert?) asks is "Can we close the XP cmd window, without killing the local X server process?" because he probably started using cygwin.bat. But if he started cygwin-x by clicking directly on Drive:\<cygwin-home>\usr\X11R6\bin\startxwin.bat, he would get an error msg, "cygwin1.dll not found". What he needs to do is, Right click My Computer to append Drive:/<cygwin-home>/bin/ to his system path. Now he would be able to click directly, Drive:\<cygwin-home>\usr\X11R6\bin\startxwin.bat , and be a rather happy camper (provided he knows how to set up his XP system path). -----Original Message-----Trebor Sreyb wrote: >Is there some way to run startx without opening a >cygwin shell window? Or, alternatively, to exit the >shell window after the X window manager has >successfully started? > >Otherwise, I find myself having to leave open a cygwin >shell window that is used for nothing other than >kicking off startx - that window just sits there. > >This is only a nuissance (adds an extra icon to the >task bar), but if there's another way I'd like to >know. > >I use cygwin on Win XP SP2. > Doesn't your startxwin.bat file accomplish this? -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
