cygwin/x with Vista
Hi, I am wondering if there is a version for Windows Vista because I have installed the current version, the installation process finished correctly, but cygwin/X didn't work. Maybe, I should install that version on different way, could you send me your comments? Regards, Sodel -- Sodel Vazquez-Reyes The University of Manchester PhD Student (Room: H12) E-mail: [EMAIL PROTECTED] -- 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/
Re: cygwin/x with Vista
Sodel Vazquez-Reyes schrieb: I am wondering if there is a version for Windows Vista because I have installed the current version, the installation process finished correctly, but cygwin/X didn't work. There is no version for Vista. X11 from cygwin has problems with Vista (search the archive) some have workarounds and some don't. If nothing helps try Xming. -- 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/
Re: Windowmaker not open bash properly
Larry Hall (Cygwin X) wrote: Scott Mohnkern wrote: Larry Hall (Cygwin X) wrote: Scott Mohnkern wrote: Apologies, I was following the format of other questions I'd seen here. Attached is cygcheck.out The other server was Xvision, which was part of an automatic install of Cradle 5.5.x You (no longer?) have Cygwin in your path. You're picking up the Nutcracker/MKS tools now. Fix your path and give a quick run through of the rest of your environment to clean up any issues. Two that caught my eye are $HOME and $TERM are now incorrectly set. If you can find where Nutcracker/MKS sets these and remove/avoid them, you'll have better luck working with Cygwin. That appears to have solved most of it. Removing the nutcracker entries and putting cygwin and cygwin bin in the path got me up and running. It doesn't appear to be pulling my profile up correctly when I open up bash (It's defaulting to a different $HOME but I can probably figure out where that is set) It's probably in your system-level environment, which you can access from the Windows control panel System applet. Good luck. That's definitely it I'm pretty sure it's an environment variable that got messed with. Cradle during install set $SHELL to nutc without telling me, and I'm 90% sure that's what caused Windowmaker to choke. Now I just need to figure out which of these other system variables need to go, and which ones I need to put back in. Scott -- 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/
Re: unable to open display 6 times when I try to run any X apps from xterm
I have uninstalled window's firewall (which was disabled before) and uninstalled the virus software (AVG). Still not working. Can't use xhost or any X program except xterm without getting 6 errors of - Can't open display. I'm a little confused about the response since the output I showed was from an xterm started using startxwin.bat which launches X before starting xterm which is an X app? I have been using this configuration for over 2 years on this box and it suddenly stopped working. I can't seem to locate xstartwin. Where can I find it? Any other suggestions or insight into what could be causing this? What is the meaning of 6 errors when I try to execute xhost? Thank you in advance! -greg Here is my /tmp/XWin.log; _XSERVTransmkdir: ERROR: euid != 0,directory /tmp/.X11-unix will not be created. (II) XF86Config is not supported (II) See http://x.cygwin.com/docs/faq/cygwin-x-faq.html for more information winAdjustVideoModeShadowGDI - Using Windows display depth of 32 bits per pixel winAllocateFBShadowGDI - Creating DIB with width: 1920 height: 1200 depth: 32 winInitVisualsShadowGDI - Masks 00ff ff00 00ff BPRGB 8 d 24 bpp 32 null screen fn ReparentWindow null screen fn RestackWindow InitQueue - Calling pthread_mutex_init InitQueue - pthread_mutex_init returned InitQueue - Calling pthread_cond_init InitQueue - pthread_cond_init returned winInitMultiWindowWM - Hello winInitMultiWindowWM - Calling pthread_mutex_lock () winMultiWindowXMsgProc - Hello winMultiWindowXMsgProc - Calling pthread_mutex_lock () 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 (--) Setting autorepeat to delay=500, rate=31 (--) winConfigKeyboard - Layout: 0409 (0409) (--) Using preset keyboard for English (USA) (409), type 4 (--) 3 mouse buttons found Could not init font path element /usr/X11R6/lib/X11/fonts/CID/, removing from list! Could not init font path element /usr/X11R6/lib/X11/fonts/100dpi/, removing from list! winInitMultiWindowWM - pthread_mutex_lock () returned. winInitMultiWindowWM - pthread_mutex_unlock () returned. winMultiWindowXMsgProc - pthread_mutex_lock () returned. winMultiWindowXMsgProc - pthread_mutex_unlock () returned. winInitMultiWindowWM - DISPLAY=127.0.0.1:0.0 winProcEstablishConnection - Hello DetectUnicodeSupport - Windows NT/2000/XP winProcEstablishConnection - winInitClipboard returned. winClipboardProc - DISPLAY=127.0.0.1:0.0 winInitMultiWindowWM - XOpenDisplay () returned and successfully opened the display. winMultiWindowXMsgProc - XOpenDisplay () returned and successfully opened the display. winClipboardProc - XOpenDisplay () returned and successfully opened the display. -greg -- 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/
Re: unable to open display 6 times when I try to run any X apps from xterm
[EMAIL PROTECTED] wrote: I have uninstalled window's firewall (which was disabled before) and uninstalled the virus software (AVG). Still not working. Can't use xhost or any X program except xterm without getting 6 errors of - Can't open display. I'm a little confused about the response since the output I showed was from an xterm started using startxwin.bat which launches X before starting xterm which is an X app? I have been using this configuration for over 2 years on this box and it suddenly stopped working. Sounds like this is the key. What's new to the system since it stopped working. You mentioned initially that you have DISPLAY set in your startxwin.bat. Don't recall off-hand whether that's in there by default (and I'm not at a machine that has Cygwin-X installed). If you added this, I suggest removing it. -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 216 Dalton Rd. (508) 429-6305 - FAX Holliston, MA 01746 -- 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/
