Windows Vista Speech Recognition and Cygwin/X
The XWin server uses primarily hardware scan codes for interpreting the
windows WM_KEYDOWN and WM_SYSKEYDOWN messages. Unfortunately, Vista
speech recognition (WSR) doesn't bother to fill in the scancode field in
the lParam entry. Neither does SendKeys.SendWait(), which is what
Vocola 3, a recently released supplement to WSR, uses to send input to
applications.
To work around these Microsoft bugs, I modified winkeybd.c as follows:
void
winTranslateKey (WPARAM wParam, LPARAM lParam, int *piScanCode)
{
intiKeyFixup = g_iKeyMap[wParam * WIN_KEYMAP_COLS + 1];
intiKeyFixupEx = g_iKeyMap[wParam * WIN_KEYMAP_COLS + 2];
intiParamScanCode = LOBYTE (HIWORD (lParam));
to
void
winTranslateKey (WPARAM wParam, LPARAM lParam, int *piScanCode)
{
HKLdwhkl = GetKeyboardLayout(0);
intiKeyFixup = g_iKeyMap[wParam * WIN_KEYMAP_COLS + 1];
intiKeyFixupEx = g_iKeyMap[wParam * WIN_KEYMAP_COLS + 2];
intiParamScanCode = MapVirtualKeyEx (wParam,
/*MAPVK_VK_TO_VSC*/0, dwhkl);
so that the scan code is regenerated from the keycode.
An initial test appears to work. However, it is not clear to me whether
I have introduced some subtle bugs. For example, its correctness depends
on extended codes having the same scan code as the non-extended
equivalent on all keyboard layouts.
Can someone tell me if I've broken anything? Or suggest a more robust
fix? It would be nice to be able to release it rather than having a
privately distributed modification solely for Vista speech recognition.
Paul
--
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: Windows Vista Speech Recognition and Cygwin/X
Paul Loewenstein wrote:
The XWin server uses primarily hardware scan codes for interpreting the
windows WM_KEYDOWN and WM_SYSKEYDOWN messages. Unfortunately, Vista
speech recognition (WSR) doesn't bother to fill in the scancode field in
the lParam entry. Neither does SendKeys.SendWait(), which is what
Vocola 3, a recently released supplement to WSR, uses to send input to
applications.
To work around these Microsoft bugs, I modified winkeybd.c as follows:
void
winTranslateKey (WPARAM wParam, LPARAM lParam, int *piScanCode)
{
intiKeyFixup = g_iKeyMap[wParam * WIN_KEYMAP_COLS + 1];
intiKeyFixupEx = g_iKeyMap[wParam * WIN_KEYMAP_COLS + 2];
intiParamScanCode = LOBYTE (HIWORD (lParam));
to
void
winTranslateKey (WPARAM wParam, LPARAM lParam, int *piScanCode)
{
HKLdwhkl = GetKeyboardLayout(0);
intiKeyFixup = g_iKeyMap[wParam * WIN_KEYMAP_COLS + 1];
intiKeyFixupEx = g_iKeyMap[wParam * WIN_KEYMAP_COLS + 2];
intiParamScanCode = MapVirtualKeyEx (wParam,
/*MAPVK_VK_TO_VSC*/0, dwhkl);
so that the scan code is regenerated from the keycode.
diff is your friend :-)
An initial test appears to work. However, it is not clear to me whether
I have introduced some subtle bugs. For example, its correctness depends
on extended codes having the same scan code as the non-extended
equivalent on all keyboard layouts.
How about writing it in the following form, that should address that concern,
if I've understood correctly (in all cases, assuming 0 is never a valid scancode)
$ quilt diff
Index: xorg-server-1.5.3/xserver/hw/xwin/winkeybd.c
===
--- xorg-server-1.5.3.orig/xserver/hw/xwin/winkeybd.c 2009-01-05
23:50:04.0 +
+++ xorg-server-1.5.3/xserver/hw/xwin/winkeybd.c2009-01-10
21:55:40.0 +
@@ -80,6 +80,12 @@
int iKeyFixupEx = g_iKeyMap[wParam * WIN_KEYMAP_COLS + 2];
int iParamScanCode = LOBYTE (HIWORD (lParam));
+ /* WM_ key messages faked by speech recognizers don't have a scan code... */
+ if (iParamScanCode == 0)
+{
+ iParamScanCode = MapVirtualKeyEx(wParam, /*MAPVK_VK_TO_VSC*/0,
GetKeyboardLayout(0));
+}
+
/* Branch on special extended, special non-extended, or normal key */
if ((HIWORD (lParam) KF_EXTENDED) iKeyFixupEx)
*piScanCode = iKeyFixupEx;
Can someone tell me if I've broken anything? Or suggest a more robust
fix? It would be nice to be able to release it rather than having a
privately distributed modification solely for Vista speech recognition.
Well, my keyboard seems to still work with the above change. I don't think
there will be a problem including a patch like this, provided we can be fairly
confident it hasn't broken normal keyboards :-)
--
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: Regarding installation of X11 server in my Laptop with Windows Vista home basic OS
Phil Betts wrote: mallikarjun reddy wrote on Wednesday, October 15, 2008 1:02 PM:: Dear Sir, I,G Mallikarjun Reddy, am a student of B.Tech final year studying in National Institute of Technology,Warangal.I want to install Magic VLSI design tool in my Laptop which has Windows Vista Home Basic as its Operating System.So I installed Cygwin by following the instructions as given in the following site http://opencircuitdesign.com/cygwin/tcltk.html But I couldn't get X11 server installed though I followed the steps perfectly. Please give me a solution regarding this. Thanking you,in anticipation. Yours faithfully, Mallikarjun You haven't given us anywhere near enough information to let us work out what your problem is. What follows is a general procedure to follow to get X working. If you installed cygwin with DOS line endings, you would be better off cutting your losses and uninstall cygwin. Then start again using UNIX line endings. DOS line endings just cause more trouble than they are worth, and there is no good reason to use them. (The option is being removed from setup for cygwin 1.7) Next, read these links (even if X is now working): Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/ Implicit in this is a pointer to the instructions for installing Cygwin/X as recommended by the Cygwin community. If you need help from the Cygwin community, it's best to use the resources that are maintained by the community. We can't vouch for or support other sources. -- 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/
Regarding installation of X11 server in my Laptop with Windows Vista home basic OS
-- Forwarded message -- From: mallikarjun reddy [EMAIL PROTECTED] Date: Wed, 15 Oct 2008 03:32:02 +0530 Subject: To: cygwin-xfree@cygwin.com Dear Sir, I,G Mallikarjun Reddy, am a student of B.Tech final year studying in National Institute of Technology,Warangal.I want to install Magic VLSI design tool in my Laptop which has Windows Vista Home Basic as its Operating System.So I installed Cygwin by following the instructions as given in the following site http://opencircuitdesign.com/cygwin/tcltk.html But I couldn't get X11 server installed though I followed the steps perfectly. Please give me a solution regarding this. Thanking you,in anticipation. Yours faithfully, Mallikarjun -- mallikarjun -- 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: Regarding installation of X11 server in my Laptop with Windows Vista home basic OS
mallikarjun reddy wrote on Wednesday, October 15, 2008 1:02 PM:: Dear Sir, I,G Mallikarjun Reddy, am a student of B.Tech final year studying in National Institute of Technology,Warangal.I want to install Magic VLSI design tool in my Laptop which has Windows Vista Home Basic as its Operating System.So I installed Cygwin by following the instructions as given in the following site http://opencircuitdesign.com/cygwin/tcltk.html But I couldn't get X11 server installed though I followed the steps perfectly. Please give me a solution regarding this. Thanking you,in anticipation. Yours faithfully, Mallikarjun You haven't given us anywhere near enough information to let us work out what your problem is. What follows is a general procedure to follow to get X working. If you installed cygwin with DOS line endings, you would be better off cutting your losses and uninstall cygwin. Then start again using UNIX line endings. DOS line endings just cause more trouble than they are worth, and there is no good reason to use them. (The option is being removed from setup for cygwin 1.7) Next, read these links (even if X is now working): Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/ If you still have a problem, check /tmp/XWin.log for errors. If you're still no wiser, try searching the mailing list archive: http://cygwin.com/ml/cygwin-xfree/ In particular, search the archives for references to any error messages you see in /tmp/XWin.log. If XWin aborted, the error message related to this will usually be near the end of the file, so it's best to work backwards through the file. You might be suffering from http://cygwin.com/acronyms/#BLODA If you have any of the software on the list, it's important to try uninstalling it. Just disabling it is unlikely to be enough to stop such badly written software from interfering. Finally, if you're still stuck, you need to follow the instructions here: Problem reports: http://cygwin.com/problems.html In particular, *attach* the output from running cygcheck -svr. For X related problems, you should also attach /tmp/XWin.log. Phil -- This email has been scanned by Ascribe PLC using Microsoft Antigen for Exchange. -- 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: Windows Vista
Monson Hayes wrote on Sunday, August 24, 2008 12:51 PM:: [snip] Fatal server error: could not open default font 'fixed' It's pretty obvious that this is the reason it's failed, and googling for this would have found the answer. Whilst I could give you the definitive solution, it's such a frequently asked question, and I get tired of repeating myself. The answers are already out there, so I think it's up to you to do the work. If you don't know how use google to search the mail archives, try adding site:cygwin.com inurl:ml/cygwin-xfree (without the quotes) to the query. Phil This email has been scanned by Ascribe PLC using Microsoft Antigen for Exchange. -- 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: Windows Vista
On Tue, 26 Aug 2008, Phil Betts wrote: Monson Hayes wrote on Sunday, August 24, 2008 12:51 PM:: [snip] snip Fatal server error: could not open default font 'fixed' It's pretty obvious that this is the reason it's failed, and googling for this would have found the answer. Whilst I could give you the definitive solution, it's such a frequently asked question, and I get tired of repeating myself. The answers are already out there, so I think it's up to you to do the work. If you don't know how use google to search the mail archives, try adding site:cygwin.com inurl:ml/cygwin-xfree (without the quotes) to the query. Phil This email has been scanned by Ascribe PLC using Microsoft Antigen for Exchange. /snip ..by which one deduces that you've pasted the whole message from someplace. (I guess it saves your time ;-) -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net -- 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: Windows Vista
Cygwin does indeed run on 32-bit versions of Windows Vista. Don't know about 64-bit versions. In my experience, there are a few catches to getting Cygwin to work on Vista: 1. Run the Cygwin setup as Administrator and in XP Compatibility Mode. 2. I had better luck when I did the install in two stages: First, I just downloaded the packages, then I ran setup again and chose the install from local repository option. 3. After installation, run Cygwin's rebaseall command from an ash (not bash) shell. 4. When you finally run the Cygwin bash shell for real, be sure to use Vista's Run as Administrator option. 5. Also make sure that your firewall is not blocking Xwin.exe or bash.exe. FWIW, the Xming X server works just fine on Vista, and you can use Xming as your X Server when running PuTTY or many if not all of the Cygwin X-based apps. Hope this helps, Scott Monson Hayes wrote: Not sure how to reply to a thread, but here are the details of what happens when I try to run Cygwin/X. First, I would like to comment that the following was suggested: Be sure to set up $DISPLAY in your .bashrc: export DISPLAY=localhost:0.0 What is interesting, is in my installation I cannot find a .bashrc file, although I did find one in my Windows XP installation. I am told to look at the XWin.log file on my computer running Windows Vista when I get the following fatal error: A fatal error has occurred and Cygwin/X will now exit Releast 6.8.99.901-4 XWin was started with the following command llin /usr/X11R6/bin/XWin -multiwindow - clipboard -silent-dup-error The XWin.log file is: (WW) /tmp mounted int textmode _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: 1680 height: 1050 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 winMultiWindowXMsgProc - Hello winInitMultiWindowWM - Calling pthread_mutex_lock () 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 (--) 8 mouse buttons found Could not init font path element /usr/X11R6/lib/X11/fonts/CID/, removing from list! Fatal server error: could not open default font 'fixed' -- 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/ -- 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: Windows Vista
To clarify, Cygwin/X worked fine for me when I was running 32 bit Vista, but I had to resort to the XMing solution under AMD64. Kind Regards, Brian Wisti On Mon, Aug 25, 2008 at 2:24 PM, Scott Fordin [EMAIL PROTECTED] wrote: Cygwin does indeed run on 32-bit versions of Windows Vista. Don't know about 64-bit versions. In my experience, there are a few catches to getting Cygwin to work on Vista: 1. Run the Cygwin setup as Administrator and in XP Compatibility Mode. 2. I had better luck when I did the install in two stages: First, I just downloaded the packages, then I ran setup again and chose the install from local repository option. 3. After installation, run Cygwin's rebaseall command from an ash (not bash) shell. 4. When you finally run the Cygwin bash shell for real, be sure to use Vista's Run as Administrator option. 5. Also make sure that your firewall is not blocking Xwin.exe or bash.exe. FWIW, the Xming X server works just fine on Vista, and you can use Xming as your X Server when running PuTTY or many if not all of the Cygwin X-based apps. Hope this helps, Scott Monson Hayes wrote: Not sure how to reply to a thread, but here are the details of what happens when I try to run Cygwin/X. First, I would like to comment that the following was suggested: Be sure to set up $DISPLAY in your .bashrc: export DISPLAY=localhost:0.0 What is interesting, is in my installation I cannot find a .bashrc file, although I did find one in my Windows XP installation. I am told to look at the XWin.log file on my computer running Windows Vista when I get the following fatal error: A fatal error has occurred and Cygwin/X will now exit Releast 6.8.99.901-4 XWin was started with the following command llin /usr/X11R6/bin/XWin -multiwindow - clipboard -silent-dup-error The XWin.log file is: (WW) /tmp mounted int textmode _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: 1680 height: 1050 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 winMultiWindowXMsgProc - Hello winInitMultiWindowWM - Calling pthread_mutex_lock () 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 (--) 8 mouse buttons found Could not init font path element /usr/X11R6/lib/X11/fonts/CID/, removing from list! Fatal server error: could not open default font 'fixed' -- 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/ -- 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/ -- 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: Windows Vista
I still haven't been able to get Cygwin/X working under Vista yet. I was able to use XLaunch and fire off X applications from the cygwin shell. http://www.straightrunning.com/XmingNotes/ Be sure to set up $DISPLAY in your .bashrc: export DISPLAY=localhost:0.0 I'd love to know if there's a better way, though. Kind Regards, Brian Wisti On Sat, Aug 23, 2008 at 7:26 PM, Monson Hayes [EMAIL PROTECTED] wrote: I have tried to install Cygwin/X under Windows Vista, and get fatal errors when trying to run Cygwin/X. Has anyone been successful and, if so, is there documentation on how to get Cygwin running under Vista? -- 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/ -- 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: Windows Vista
Not sure how to reply to a thread, but here are the details of what happens when I try to run Cygwin/X. First, I would like to comment that the following was suggested: Be sure to set up $DISPLAY in your .bashrc: export DISPLAY=localhost:0.0 What is interesting, is in my installation I cannot find a .bashrc file, although I did find one in my Windows XP installation. I am told to look at the XWin.log file on my computer running Windows Vista when I get the following fatal error: A fatal error has occurred and Cygwin/X will now exit Releast 6.8.99.901-4 XWin was started with the following command llin /usr/X11R6/bin/XWin -multiwindow - clipboard -silent-dup-error The XWin.log file is: (WW) /tmp mounted int textmode _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: 1680 height: 1050 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 winMultiWindowXMsgProc - Hello winInitMultiWindowWM - Calling pthread_mutex_lock () 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 (--) 8 mouse buttons found Could not init font path element /usr/X11R6/lib/X11/fonts/CID/, removing from list! Fatal server error: could not open default font 'fixed' -- 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/
Windows Vista
I have tried to install Cygwin/X under Windows Vista, and get fatal errors when trying to run Cygwin/X. Has anyone been successful and, if so, is there documentation on how to get Cygwin running under Vista? -- 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: Startxwin.bat fatal error in Windows Vista
Allen Rongone wrote on Monday, May 14, 2007 8:29 PM:: I've seen this before under Windows XP and it was due to the fact that the previous user was the owner of the /tmp/.X11-unix directory and no one else had permissions to delete the X0 file nor were they able to remove this directory. I just gave Everyone Full Control to the /tmp directory and made it inheritable, that solved the problem. However, now under Vista, Everyone no longer gets propagated to the /tmp/X11-unix directory so when another user runs startxwin.bat it cannot delete the X0 file and remove the sud-directory. The usual workaround for this is to make /tmp a user mount, i.e. each user has their own /tmp. E.g.: mount -u -b $APPDATA\\tmp /tmp If that doesn't work, there's either a program already using port 6000, or your firewall/antivirus is blocking access to it. X uses port 6000 + the display number, so if another program's using port 6000, you can start X on say port 6002 with XWin :2. -- 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/
Startxwin.bat fatal error in Windows Vista
Hello, We recently received a new Dell Precision M90 laptop with Windows Vista Business version 6.0 pre-installed. I downloaded and installed the latest version of Cygwin (1.5.24) on it. Our users use it for X window access to our Unix servers, anyway, whenever a user on this machine attempts to run the startxwin.bat file they get a window that pops up and says: A fatal error has occurred and Cygwin/X will now exit. Please open /tmp/XWin.log for more information. XWin was started with the following command-line: /usr/X11R6/bin/XWin -multiwindow -clipboard -silent-dup-error I've attached a copy of the log, (along with with the output of cygcheck) but it basically says that there was fatal server error because it couldn't establish any listening sockets - Make sure an X server isn't already running. I've seen this before under Windows XP and it was due to the fact that the previous user was the owner of the /tmp/.X11-unix directory and no one else had permissions to delete the X0 file nor were they able to remove this directory. I just gave Everyone Full Control to the /tmp directory and made it inheritable, that solved the problem. However, now under Vista, Everyone no longer gets propagated to the /tmp/X11-unix directory so when another user runs startxwin.bat it cannot delete the X0 file and remove the sud-directory. Is this a Vista problem or a XWin.exe issue? And if so does anyone know a workaround? I've tried configuring the permissions every which way and no matter what I try the permissions do not get propagated to the /tmp/X11-unix directory. Thank you for your time, Allen Rongone _XSERVTransmkdir: Owner of /tmp/.X11-unix should be set to root _XSERVTransSocketUNIXCreateListener: ...SocketCreateListener() failed _XSERVTransMakeAllCOTSServerListeners: server already running Fatal server error: Cannot establish any listening sockets - Make sure an X server isn't already running Cygwin Configuration Diagnostics Current System Time: Mon May 14 12:09:45 2007 Windows Longhorn/Vista (not yet supported!) Ver 6.0 Build 6000 Path: C:\cygwin\usr\local\bin C:\cygwin\bin C:\cygwin\bin C:\cygwin\usr\X11R6\bin c:\Windows\system32 c:\Windows c:\Windows\System32\Wbem c:\Program Files\Common Files\Roxio Shared\DLLShared\ c:\Program Files\Microsoft SQL Server\90\Tools\binn\ c:\Program Files\ZipGenius 6\ c:\Program Files\wbin\ SysDir: C:\Windows\system32 WinDir: C:\Windows USER = 'root' PWD = '/home/root' HOME = '/home/root' MAKE_MODE = 'unix' HOMEPATH = '\Users\root' MANPATH = '/usr/local/man:/usr/share/man:/usr/man::/usr/ssl/man' APPDATA = 'C:\Users\root\AppData\Roaming' HOSTNAME = 'boulder1' TERM = 'cygwin' ROXIOCENTRAL = 'C:\Program Files\Common Files\Roxio Shared\9.0\Roxio Central33\' PROCESSOR_IDENTIFIER = 'x86 Family 6 Model 15 Stepping 6, GenuineIntel' WINDIR = 'C:\Windows' VS80COMNTOOLS = 'C:\Program Files\Microsoft Visual Studio 8\Common7\Tools\' PUBLIC = 'C:\Users\Public' OLDPWD = '/usr/bin' PROGRAMDATA = 'C:\ProgramData' USERDOMAIN = 'boulder1' OS = 'Windows_NT' ALLUSERSPROFILE = 'C:\ProgramData' !:: = '::\' TEMP = '/cygdrive/c/Users/root/AppData/Local/Temp' COMMONPROGRAMFILES = 'C:\Program Files\Common Files' USERNAME = 'root' PROCESSOR_LEVEL = '6' FP_NO_HOST_CHECK = 'NO' SYSTEMDRIVE = 'C:' USERPROFILE = 'C:\Users\root' PS1 = '\[\e]0;[EMAIL PROTECTED] \[\e[33m\]\w\[\e[0m\]\n\$ ' LOGONSERVER = '\\BOULDER1' PROCESSOR_ARCHITECTURE = 'x86' LOCALAPPDATA = 'C:\Users\root\AppData\Local' !C: = 'C:\cygwin\bin' SHLVL = '1' PATHEXT = '.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC' HOMEDRIVE = 'C:' PROMPT = '$P$G' COMSPEC = 'C:\Windows\system32\cmd.exe' TMP = '/cygdrive/c/Users/root/AppData/Local/Temp' SYSTEMROOT = 'C:\Windows' PRINTER = 'Adobe PDF' CVS_RSH = '/bin/ssh' PROCESSOR_REVISION = '0f06' INFOPATH = '/usr/local/info:/usr/share/info:/usr/info:' PROGRAMFILES = 'C:\Program Files' NUMBER_OF_PROCESSORS = '2' SESSIONNAME = 'Console' COMPUTERNAME = 'BOULDER1' _ = '/usr/bin/cygcheck' POSIXLY_CORRECT = '1' HKEY_CURRENT_USER\Software\Cygnus Solutions HKEY_CURRENT_USER\Software\Cygnus Solutions\Cygwin HKEY_CURRENT_USER\Software\Cygnus Solutions\Cygwin\mounts v2 HKEY_CURRENT_USER\Software\Cygnus Solutions\Cygwin\Program Options HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\mounts v2 (default) = '/cygdrive' cygdrive flags = 0x0022 HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\mounts v2\/ (default) = 'C:\cygwin' flags = 0x000a HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\mounts v2\/usr/bin (default) = 'C:\cygwin/bin' flags = 0x000a HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\mounts v2\/usr/lib (default) = 'C:\cygwin/lib' flags = 0x000a HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\Program Options c: hd NTFS
Re: Windows Vista
Brian Dessent wrote: Scott Fordin wrote: Also make sure that you run the Cygwin setup as Administrator. Eh? I just installed on Vista yesterday and all I had to do was click on setup.exe. Vista asked to run it as administrator since the executable is named setup.exe. I didn't have to do anything special. Dunno. It was the only I way I could get it to work, and I was following advice I read elsewhere. In any case, it did work when I ran it as Administrator. Are there any downsides to doing it this way? 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/
Windows Vista
Hello I am trying to install cygwin/X in Windows Vista and I get a message saying that the installation could not be completed. Is there a new version of cygwin/X for this operational system? Thanks Mariana Silva __ Mariana F. Silva Graduate Research Assistant Department of Theoretical and Applied Mechanics University of Illinois 213 Talbot Laboratory 104 South Wright Street Urbana, Illinois 61801 USA phone:(217)333-0498 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: Windows Vista
Mariana Silva wrote: Hello I am trying to install cygwin/X in Windows Vista and I get a message saying that the installation could not be completed. Is there a new version of cygwin/X for this operational system? No. The error you got is unlikely to be as a result of Vista. Try a different mirror. -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 216 Dalton Rd. (508) 893-9889 - 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/
Re: Windows Vista
Larry Hall (Cygwin X) wrote: Mariana Silva wrote: Hello I am trying to install cygwin/X in Windows Vista and I get a message saying that the installation could not be completed. Is there a new version of cygwin/X for this operational system? No. The error you got is unlikely to be as a result of Vista. Try a different mirror. Also make sure that you run the Cygwin setup as Administrator. This doesn't just mean that your user account has Administrator rights; you have to right-click the Cygwin setup.exe and then choose Run as Administrator from the pop-up menu. FWIW, I have both Cygwin and Xming on my Vista notebook. I use Cygwin when I need a real shell environment on my Vista machine. I use Xming and PuTTY when I just need an X server and an ssh session on a remote Solaris or Linux box. Both work great! Hope this helps, 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: Windows Vista
Scott Fordin wrote: No. The error you got is unlikely to be as a result of Vista. Try a different mirror. Also make sure that you run the Cygwin setup as Administrator. This doesn't just mean that your user account has Administrator rights; you have to right-click the Cygwin setup.exe and then choose Run as Administrator from the pop-up menu. Eh? I just installed on Vista yesterday and all I had to do was click on setup.exe. Vista asked to run it as administrator since the executable is named setup.exe. I didn't have to do anything special. BTW this is not X-specific so you should probably ask on the main list unless you have X related issues. Brian -- 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/
Issues with Windows Vista and X server
I'm trying to use Cygwin and especially the X server on Windows Vista. I ran into the same problems everyone did with sh.exe stalling and so on. Forcing it to an invalid keyboard rule (Start X with -xbkrules WinVista) fixed this issue for me. But after I installed the cygwin.dll version 1.5.23-2 it also worked without this keyboard rule work around. But I still have two very annoying issues right now: If I start X, it's using close to 100% of CPU. This started after I applied the new cygwin.dll patch. I let my PC run all the time and connect to it via RDP (Remote Desktop Protocol) from various RDP clients (work, home). If I now have some xterm or other X-client windows open and disconnect from my PC and reconnect later, X and all windows will be un-responsive most of the time. This happens for sure, if some other window popped up in front of the X-windows in the meantime or if the screen resolution changes (when I use a different RDP client to connect to my PC). Does anyone have any idea how to fix this? I'm using the latest patches, cygwin.dll version 1.5.23-2 and X.org base 6.8.99.901-1. Any help would be appreciated. Very Best Regards, Rainer Kraft ATA Airlines -- 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's RUN command and Windows Vista Beta 2
-Original Message- On Tue, Jun 06, 2006 at 08:22:02PM -0400, Chuck McDevitt wrote: The RUN commands that comes with Cygwin-X (\cygwin\usr\X11R6\bin\run.exe) has a problem on Windows Vista Beta 2. When I tried running Xwin.exe and ssh.exe using that RUN command on Vista, it caused a blue-screen crash of the OS. Clarification: This isn't a problem on Windows Vista Beta 2, it is a problem *with* Windows Vista Beta 2. cgf True, but there is something special about the RUN command that provokes this. I have other applications that create hidden windows, and they have no problem on Vista Beta 2. And from vbscript, I can launch programs with hidden windows, and they have no problem. I'll of course be reporting the problem to Microsoft as well, since nothing the program does should cause a crash. -- 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's RUN command and Windows Vista Beta 2
Chuck McDevitt wrote: -Original Message- On Tue, Jun 06, 2006 at 08:22:02PM -0400, Chuck McDevitt wrote: The RUN commands that comes with Cygwin-X (\cygwin\usr\X11R6\bin\run.exe) has a problem on Windows Vista Beta 2. When I tried running Xwin.exe and ssh.exe using that RUN command on Vista, it caused a blue-screen crash of the OS. Clarification: This isn't a problem on Windows Vista Beta 2, it is a problem *with* Windows Vista Beta 2. cgf snip I'll of course be reporting the problem to Microsoft as well, since nothing the program does should cause a crash. Bingo! That's Chris' point. -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 838 Washington Street (508) 893-9889 - 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/
Cygwin's RUN command and Windows Vista Beta 2
The RUN commands that comes with Cygwin-X (\cygwin\usr\X11R6\bin\run.exe) has a problem on Windows Vista Beta 2. When I tried running Xwin.exe and ssh.exe using that RUN command on Vista, it caused a blue-screen crash of the OS. Changing my scripts to use the Windows command-shell START Command instead of the run command stopped the crash from happening, but of course doesn't create the window hidden. I'd guess there is some parameter being passed to CreateProcess that didn't used to matter on XP, but now matters to Vista, and is set wrong. -- 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's RUN command and Windows Vista Beta 2
On Tue, Jun 06, 2006 at 08:22:02PM -0400, Chuck McDevitt wrote: The RUN commands that comes with Cygwin-X (\cygwin\usr\X11R6\bin\run.exe) has a problem on Windows Vista Beta 2. When I tried running Xwin.exe and ssh.exe using that RUN command on Vista, it caused a blue-screen crash of the OS. Clarification: This isn't a problem on Windows Vista Beta 2, it is a problem *with* Windows Vista Beta 2. cgf -- 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/
