Re: Show GNU screen captions inside of mintty
On Wed, Aug 03, 2011 at 06:45:31AM +0100, Andy Koppe wrote: This has nothing to do with mintty and everything to do with screen and its configuration, unless you can show that mintty displays I didn't think it necessarily had anything to do with mintty as an application, but the TERMCAP settings it's using. Your comment did remind me that screen still reads the /etc/screenrc file even if you have a user specified configuration, so I diffed the /etc/screenrc from my Debian desktop and the Cygwin /etc/screenrc and found they were different. After replacing Cygwin's screenrc with the one from Debian, it behaved as expected. Thanks for the help, Eric -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Show GNU screen captions inside of mintty
When using mintty with GNU screen, all status messages (captions) are shown in the title bar instead of the interior of the terminal. I originally found this feature quite nifty, but now that I use an always-on caption for screen, it means that I end up losing visibility of the window title and hardstatus. What needs to be modified in order to make captions show up in the interior of mintty? Eric -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Show GNU screen captions inside of mintty
On Tue, Aug 02, 2011 at 10:58:41PM -0400, Charles Wilson wrote:
On 8/2/2011 9:30 PM, Eric Pruitt wrote:
When using mintty with GNU screen, all status messages (captions) are shown
in
the title bar instead of the interior of the terminal. I originally found
this
feature quite nifty, but now that I use an always-on caption for screen, it
means that I end up losing visibility of the window title and hardstatus.
What needs to be modified in order to make captions show up in the interior
of mintty?
Here's what I use:
hardstatus string screen %n (%t)%? [%h]%?
caption always '%{yb} %H %{k}|%L=%= %{w}%?%-Lw%45L%?%{=b bR}[%{W}%n%f
%t%?(%u)%?%{=b bR}]%{= bw}%?%+Lw%?%?%=%-30= %{k}|%{Y}%l%{k}|%{=b C}
%m/%d %c %{W}'
That does what I want, albeit not with the formatting options I'll. Could you
explain how and why that works? I like that the status messages remain in the
title bar, too. Now I just need to figure out how to do the same thing on
xterm -- keep the caption as the last line but status messages in the title
bar. Any help you could offer on that would be great as well.
Thanks,
Eric
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Show GNU screen captions inside of mintty
On Wed, Aug 03, 2011 at 12:35:10AM -0400, Charles Wilson wrote: On 8/2/2011 11:10 PM, Eric Pruitt wrote: I want, albeit not with the formatting options I'll. Could you explain how and why that works? Nope, I flushed that Domain Specific Language from my short term memory after getting it to work as I wanted. I'd just be regurgitating the Fine Manual for you...GIYF. Alright, thanks anyway. I just tweaked my screenrc and learned that mintty will always display caption as the last line of the terminal while keeping status messages in the title bar. I didn't realize screen made a distinction between the two. I'm still curious what termcap settings it's using to put the status notification in the title, though and how to toggle it. Eric -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: GNU screen not redrawing properly
On Tue, Jun 14, 2011 at 01:32:39PM +0100, Andy Koppe wrote: Ah, this invokes screen itself with TERM=screen-256color, which tells it to talk to the outside terminal as if that's another screen, which is wrong. You want to be invoking it with TERM=xterm-256color instead (which can be selected on the Terminal page of the mintty options). Screen's '-T term' option determines the TERM variable inside screen. Setting that to screen-256color to tell applications that they're running in a 256-colour enabled screen does make sense. Btw, screen emulates 256-colour mode inside a terminal that only supports 16 colours, by mapping the colours appropriately. Of course you'll still only get 16 actual colours, but it's still better than having colour requests beyond the basic 16 ignored. Andy Since Console2 is the only 16 bit terminal emulator I use, I suppose it would make the most sense to only not set xterm-256color when TERM == 'cygwin'. Thanks for the explanation, and sorry I forgot to hit group-reply on my last message. Eric -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
GNU screen not redrawing properly
When switching windows on GNU screen, the background on any unoccupied text cells fails to be redrawn for curses applications; see http://i.imgur.com/veP9B.png. I am using screen version 4.00.03, mutt version 1.5.20, Vim 7.3, and mintty 0.9.9-1 on a 32-bit Windows Vista installation. Any ideas on what could be done to fix this? The problem does not show up when using Console2 although there is an issue with it improperly detecting the terminal's height while inside of screen, but I'm not concerned with that. Eric -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: GNU screen not redrawing properly
On Mon, Jun 13, 2011 at 07:23:34PM -0400, Chris Sutcliffe wrote: On 13 June 2011 17:53, Eric Pruitt wrote: When switching windows on GNU screen, the background on any unoccupied text cells fails to be redrawn for curses applications; see http://i.imgur.com/veP9B.png. I am using screen version 4.00.03, mutt version 1.5.20, Vim 7.3, and mintty 0.9.9-1 on a 32-bit Windows Vista installation. Any ideas on what could be done to fix this? The problem does not show up when using Console2 although there is an issue with it improperly detecting the terminal's height while inside of screen, but I'm not concerned with that. Does this only occur with the Vim screen? Does executing CTRL-L in the Vim screen help? Chris -- Chris Sutcliffe http://emergedesktop.org http://www.google.com/profiles/ir0nh34d -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple This also occurs with mutt; look closely at the screenshot and you will notice that the blue header bar and blue message highlighting does not extend all the way across the terminal like it should. Ctrl+L for a manual refresh of mutt and vim does fix the problem, but I would really rather not have to do that every time. Eric -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Image fuction bug in Octave-3.2 in Vista x86
On Sat, Jun 12, 2010 at 05:17:01AM +, Marco Atzeri wrote: --- Ven 11/6/10, James Eric Pruitt ha scritto: [cut] As mentioned before, I get the error in terminal.txt (have you looked at it yet?) or something similar regardless of whether or not I have X11 installed and running or not. I've gone through 4 clean Cygwin installations trying to figure out what the problem was and I just got tired of re-downloading things. If you remove X11 from your cygwin installation, you will see that your terminal output still does not produce a crash. Yes, you are correct I do not have X11 installed (right now) but that shouldn't make octave crash and produce a dump when running the image function. Eric your code is fine and works with and without X, no crash. So I doubt it is a specific octave issue, it is more likely linked to your machine. 2 possible causes: 1) BLODA http://cygwin.com/faq/faq.using.html#faq.using.bloda 2) Dll address collisions have you tried rebaseall ? The first is obvious and it is the biggest problem working with Cygwin, specially Antivirus. I'm using Microsoft Security Essentials on both the Windows Vista host and the Windows XP virtual machine I tested Cygwin on without any problems. From the list, I have Windows Defender installed but disabled. My laptop does require the ATi Catalyst drivers. The second, as octave loads a lot of Dll's, is more easy to trigger than for simpler programs. After running rebaseall, things seem to work now. Is there a way to do some form rebase as part of my Cygwin startup? Eric -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Image fuction bug in Octave-3.2 in Vista x86
On Fri, Jun 11, 2010 at 05:31:12AM +, Marco Atzeri wrote: --- Ven 11/6/10, James Eric Pruitt ha scritto: The cygcheck output is now attached. On Thu, Jun 10, 2010 at 07:11:31PM -0500, James Eric Pruitt wrote: When using octave in Windows Vista with a fresh install of Cygwin 1.7.5, executing the image function causes octave to crash immediately and James, the cygcheck says that you are using octave-3.2.3-1 while the latest is octave 3.2.4-2, the one I tested. (in few days we will have also the 0ctave 3.2.4-3) Could you please update and check again. I updated and the problem persists. Will attach a crash dump after returning from work. Eric produce a dump. On the same machine, after being told by someone that the problem wasn't present when they ran Cygwin on their Windows XP system, I installed Cygwin on Windows XP x86 inside of a VirtualBox and upon executing octave and trying the image function, there was no crash. I am using Windows Vista x86 on an AMD Turion 64x2 processor. An output from one of the terminals in which I tried executing octave can be found at http://pastebin.com/m7SS1MwV . Aside from a fresh installation, I also copied my Cygwin installation to the virtual machine and the image function ran without producing any crashes. # Contents of stackdump: Exception: STATUS_ACCESS_VIOLATION at eip=610202F7 eax=01363188 ebx=61228FE4 ecx=7690B363 edx=00B2E950 esi= edi=0022F9FC ebp=61020A10 esp=0022C7CC program=C:\Cygwin\bin\octave-3.2.4.exe, pid 872, thread main cs=001B ds=0023 es=0023 fs=003B gs= ss=0023 Stack trace: Frame Function Args End of stack trace Regards Marco Atzeri -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Image fuction bug in Octave-3.2 in Vista x86
On Fri, Jun 11, 2010 at 05:31:12AM +, Marco Atzeri wrote: --- Ven 11/6/10, James Eric Pruitt ha scritto: The cygcheck output is now attached. On Thu, Jun 10, 2010 at 07:11:31PM -0500, James Eric Pruitt wrote: When using octave in Windows Vista with a fresh install of Cygwin 1.7.5, executing the image function causes octave to crash immediately and James, the cygcheck says that you are using octave-3.2.3-1 while the latest is octave 3.2.4-2, the one I tested. (in few days we will have also the 0ctave 3.2.4-3) Could you please update and check again. I updated and the problem persists. I have attached the octave dump, a sample output of the terminal and cygcheck.out. I do not have X11 installed on this installation of cygwin but even on the Windows XP virtual machine, this crash does not occur regardless of whether X11 is installed. Eric produce a dump. On the same machine, after being told by someone that the problem wasn't present when they ran Cygwin on their Windows XP system, I installed Cygwin on Windows XP x86 inside of a VirtualBox and upon executing octave and trying the image function, there was no crash. I am using Windows Vista x86 on an AMD Turion 64x2 processor. An output from one of the terminals in which I tried executing octave can be found at http://pastebin.com/m7SS1MwV . Aside from a fresh installation, I also copied my Cygwin installation to the virtual machine and the image function ran without producing any crashes. # Contents of stackdump: Exception: STATUS_ACCESS_VIOLATION at eip=610202F7 eax=01363188 ebx=61228FE4 ecx=7690B363 edx=00B2E950 esi= edi=0022F9FC ebp=61020A10 esp=0022C7CC program=C:\Cygwin\bin\octave-3.2.4.exe, pid 872, thread main cs=001B ds=0023 es=0023 fs=003B gs= ss=0023 Stack trace: Frame Function Args End of stack trace Regards Marco Atzeri Cygwin Configuration Diagnostics Current System Time: Fri Jun 11 16:32:52 2010 Windows Vista Enterprise Ver 6.0 Build 6002 Service Pack 2 Path: C:\Cygwin\usr\local\bin C:\Cygwin\bin C:\Cygwin\bin C:\Windows\system32 C:\Windows C:\Windows\System32\Wbem C:\Windows\System32\WindowsPowerShell\v1.0\ C:\Cygwin\lib\lapack Output from C:\Cygwin\bin\id.exe UID: 1000(User) GID: 513(None) 513(None) 0(root) 544(Administrators) 545(Users) SysDir: C:\Windows\system32 WinDir: C:\Windows USER = 'User' PWD = '/home/User' HOME = '/home/User' TRACE_FORMAT_SEARCH_PATH = '\\winseqfe\release\Windows6.0\lh_sp2rtm\6002.18005.090410-1830\x86fre\symbols.pri\TraceFormat' HOMEPATH = '\Users\User' MANPATH = '/usr/local/man:/usr/share/man:/usr/man::/usr/ssl/man' VBOX_USER_HOME = 'C:\Users\User\Configuration\VirtualBox' APPDATA = 'C:\Users\User\AppData\Roaming' HOSTNAME = 'icebox' TERM = 'cygwin' PROCESSOR_IDENTIFIER = 'x86 Family 15 Model 104 Stepping 2, AuthenticAMD' DFSTRACINGON = 'FALSE' WINDIR = 'C:\Windows' PUBLIC = 'C:\Users\Public' OLDPWD = '/usr/bin' USERDOMAIN = 'icebox' OS = 'Windows_NT' ALLUSERSPROFILE = 'C:\ProgramData' VBOX_INSTALL_PATH = 'C:\Program Files\Oracle\VirtualBox\' !:: = '::\' COMMONPROGRAMFILES = 'C:\Program Files\Common Files' USERNAME = 'User' PROCESSOR_LEVEL = '15' FP_NO_HOST_CHECK = 'NO' SYSTEMDRIVE = 'C:' LANG = 'C.UTF-8' USERPROFILE = 'C:\Users\User' PS1 = '\[\e]0;\w\a\]\n\[\e[32m\...@\h \[\e[33m\]\w\[\e[0m\]\n\$ ' LOGONSERVER = '\\ICEBOX' PROCESSOR_ARCHITECTURE = 'x86' LOCALAPPDATA = 'C:\Users\User\AppData\Local' !C: = 'C:\Cygwin\bin' ProgramData = 'C:\ProgramData' 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' SYSTEMROOT = 'C:\Windows' PRINTER = 'Microsoft XPS Document Writer' CVS_RSH = '/bin/ssh' PROCESSOR_REVISION = '6802' INFOPATH = '/usr/local/info:/usr/share/info:/usr/info:' PROGRAMFILES = 'C:\Program Files' NUMBER_OF_PROCESSORS = '2' SESSIONNAME = 'Console' COMPUTERNAME = 'ICEBOX' _ = '/usr/bin/cygcheck' HKEY_CURRENT_USER\Software\Cygwin HKEY_CURRENT_USER\Software\Cygwin\Program Options HKEY_CURRENT_USER\Software\Cygwin\setup HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExts\.edu%2fcygwin%2f HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExts\.edu%2fcygwin%2f\OpenWithList HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExts\.edu%2fpub%2fcygwin%2f HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExts\.edu%2fpub%2fcygwin%2f\OpenWithList HKEY_LOCAL_MACHINE\SOFTWARE\Cygwin HKEY_LOCAL_MACHINE\SOFTWARE\Cygwin\Installations (default) = '\??\C:\Cygwin' HKEY_LOCAL_MACHINE\SOFTWARE\Cygwin\Program Options HKEY_LOCAL_MACHINE\SOFTWARE\Cygwin\setup (default) = 'C:\Cygwin' obcaseinsensitive set to 1 Cygwin installations found in the registry: System
Re: Image fuction bug in Octave-3.2 in Vista x86
On Fri, Jun 11, 2010 at 09:51:42PM +, Marco Atzeri wrote: --- Ven 11/6/10, James Eric Pruitt ha scritto: +, Marco Atzeri wrote: --- Ven 11/6/10, James Eric Pruitt ha scritto: The cygcheck output is now attached. On Thu, Jun 10, 2010 at 07:11:31PM -0500, James Eric Pruitt wrote: When using octave in Windows Vista with a fresh install of Cygwin 1.7.5, executing the image function causes octave to crash immediately and James, the cygcheck says that you are using octave-3.2.3-1 while the latest is octave 3.2.4-2, the one I tested. (in few days we will have also the 0ctave 3.2.4-3) Could you please update and check again. I updated and the problem persists. I have attached the octave dump, a sample output of the terminal and cygcheck.out. I do not have X11 installed on this installation of cygwin but even on the Windows XP virtual machine, this crash does not occur regardless of whether X11 is installed. Eric Eric, I am a bit puzzled. image is a test function to plot a test image on the X11 screen using gnuplot. It's not just for testing. I was using it in this cellular automata physics simulator. Please excuse the messy code; http://pastebin.com/17KXGzZa . On my Debian Linux installation of Octave and gnuplot, the script runs fine although right now it runs nearly instantly as I don't have any timer breaks. Octave can work without the Xserver, but you can not plot without it running. Without X11, I have on my XP : octave:1 image warning: X11 DISPLAY environment variable not set warning: loadimage is obsolete and will be removed from a future version of Octave; please use imread instead Marco As mentioned before, I get the error in terminal.txt (have you looked at it yet?) or something similar regardless of whether or not I have X11 installed and running or not. I've gone through 4 clean Cygwin installations trying to figure out what the problem was and I just got tired of re-downloading things. If you remove X11 from your cygwin installation, you will see that your terminal output still does not produce a crash. Yes, you are correct I do not have X11 installed (right now) but that shouldn't make octave crash and produce a dump when running the image function. Eric -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Cygwin Octave / Octave Forge image functions
Whenever I use any of the image functions in Octave, it begins to spew out a bunch of exceptions. I have an X server running and the DISPLAY environment variable set but it doesn't make a difference. Sample output can be found at http://pastebin.com/m7SS1MwV but here is the stack dump and en excerpt from the output (Note, I'm running Cygwin 1.7.5 on Windows Vista x86): # Dump output Exception: STATUS_ACCESS_VIOLATION at eip=610202F7 eax=01363188 ebx=61228FE4 ecx=7690B363 edx=00B2E950 esi= edi=0022F9FC ebp=61020A10 esp=0022C7CC program=C:\Cygwin\bin\octave-3.2.4.exe, pid 872, thread main cs=001B ds=0023 es=0023 fs=003B gs= ss=0023 Stack trace: Frame Function Args End of stack trace # Octave output octave:1 image warning: loadimage is obsolete and will be removed from a future version of Octave; please use imread instead 2 [main] octave-3.2.4 2644 exception::handle: Exception: STATUS_ACCESS_VIOLATION 569 [main] octave-3.2.4 2644 open_stackdumpfile: Dumping stack trace to octave-3.2.4.exe.stackdump ... ... error: popen2: process creation failed -- Resource temporarily unavailable -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Cygwin Octave / Octave Forge image functions
On Thu, Jun 10, 2010 at 08:57:35PM +, Marco Atzeri wrote: --- Gio 10/6/10, James Eric Pruitt ha scritto: Whenever I use any of the image functions in Octave, it begins to spew out a bunch of exceptions. I have an X server running and the DISPLAY environment variable set but it doesn't make a difference. Sample output can be found at http://pastebin.com/m7SS1MwV but here is the stack dump and en excerpt from the output (Note, I'm running Cygwin 1.7.5 on Windows Vista x86): no such problem on my 1.7.5 on Win XP. I tested it on a Windows XP Virtual Machine I'm running and it did not give me that error. I guess I will file a report after all. Thanks, Eric Problem reports: http://cygwin.com/problems.html what about to follow this instruction ? Regards Marco -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Image fuction bug in Octave-3.2 in Vista x86
When using octave in Windows Vista with a fresh install of Cygwin 1.7.5, executing the image function causes octave to crash immediately and produce a dump. On the same machine, after being told by someone that the problem wasn't present when they ran Cygwin on their Windows XP system, I installed Cygwin on Windows XP x86 inside of a VirtualBox and upon executing octave and trying the image function, there was no crash. I am using Windows Vista x86 on an AMD Turion 64x2 processor. An output from one of the terminals in which I tried executing octave can be found at http://pastebin.com/m7SS1MwV . Aside from a fresh installation, I also copied my Cygwin installation to the virtual machine and the image function ran without producing any crashes. # Contents of stackdump: Exception: STATUS_ACCESS_VIOLATION at eip=610202F7 eax=01363188 ebx=61228FE4 ecx=7690B363 edx=00B2E950 esi= edi=0022F9FC ebp=61020A10 esp=0022C7CC program=C:\Cygwin\bin\octave-3.2.4.exe, pid 872, thread main cs=001B ds=0023 es=0023 fs=003B gs= ss=0023 Stack trace: Frame Function Args End of stack trace -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Image fuction bug in Octave-3.2 in Vista x86
The cygcheck output is now attached. On Thu, Jun 10, 2010 at 07:11:31PM -0500, James Eric Pruitt wrote: When using octave in Windows Vista with a fresh install of Cygwin 1.7.5, executing the image function causes octave to crash immediately and produce a dump. On the same machine, after being told by someone that the problem wasn't present when they ran Cygwin on their Windows XP system, I installed Cygwin on Windows XP x86 inside of a VirtualBox and upon executing octave and trying the image function, there was no crash. I am using Windows Vista x86 on an AMD Turion 64x2 processor. An output from one of the terminals in which I tried executing octave can be found at http://pastebin.com/m7SS1MwV . Aside from a fresh installation, I also copied my Cygwin installation to the virtual machine and the image function ran without producing any crashes. # Contents of stackdump: Exception: STATUS_ACCESS_VIOLATION at eip=610202F7 eax=01363188 ebx=61228FE4 ecx=7690B363 edx=00B2E950 esi= edi=0022F9FC ebp=61020A10 esp=0022C7CC program=C:\Cygwin\bin\octave-3.2.4.exe, pid 872, thread main cs=001B ds=0023 es=0023 fs=003B gs= ss=0023 Stack trace: Frame Function Args End of stack trace Cygwin Configuration Diagnostics Current System Time: Thu Jun 10 19:24:27 2010 Windows Vista Enterprise Ver 6.0 Build 6002 Service Pack 2 Path: C:\Cygwin\usr\local\bin C:\Cygwin\bin C:\Cygwin\bin C:\Windows\system32 C:\Windows C:\Windows\System32\Wbem C:\Windows\System32\WindowsPowerShell\v1.0\ C:\Cygwin\lib\lapack Output from C:\Cygwin\bin\id.exe UID: 1000(User) GID: 513(None) 513(None) 0(root) 544(Administrators) 545(Users) SysDir: C:\Windows\system32 WinDir: C:\Windows USER = 'User' PWD = '/home/User' HOME = '/home/User' TRACE_FORMAT_SEARCH_PATH = '\\winseqfe\release\Windows6.0\lh_sp2rtm\6002.18005.090410-1830\x86fre\symbols.pri\TraceFormat' HOMEPATH = '\Users\User' MANPATH = '/usr/local/man:/usr/share/man:/usr/man::/usr/ssl/man' VBOX_USER_HOME = 'C:\Users\User\Configuration\VirtualBox' APPDATA = 'C:\Users\User\AppData\Roaming' HOSTNAME = 'icebox' TERM = 'cygwin' PROCESSOR_IDENTIFIER = 'x86 Family 15 Model 104 Stepping 2, AuthenticAMD' DFSTRACINGON = 'FALSE' WINDIR = 'C:\Windows' PUBLIC = 'C:\Users\Public' OLDPWD = '/usr/bin' USERDOMAIN = 'icebox' OS = 'Windows_NT' ALLUSERSPROFILE = 'C:\ProgramData' VBOX_INSTALL_PATH = 'C:\Program Files\Oracle\VirtualBox\' !:: = '::\' COMMONPROGRAMFILES = 'C:\Program Files\Common Files' USERNAME = 'User' PROCESSOR_LEVEL = '15' FP_NO_HOST_CHECK = 'NO' SYSTEMDRIVE = 'C:' LANG = 'C.UTF-8' USERPROFILE = 'C:\Users\User' PS1 = '\[\e]0;\w\a\]\n\[\e[32m\...@\h \[\e[33m\]\w\[\e[0m\]\n\$ ' LOGONSERVER = '\\ICEBOX' PROCESSOR_ARCHITECTURE = 'x86' LOCALAPPDATA = 'C:\Users\User\AppData\Local' !C: = 'C:\Cygwin\bin' ProgramData = 'C:\ProgramData' 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' SYSTEMROOT = 'C:\Windows' PRINTER = 'Microsoft XPS Document Writer' CVS_RSH = '/bin/ssh' PROCESSOR_REVISION = '6802' INFOPATH = '/usr/local/info:/usr/share/info:/usr/info:' PROGRAMFILES = 'C:\Program Files' NUMBER_OF_PROCESSORS = '2' SESSIONNAME = 'Console' COMPUTERNAME = 'ICEBOX' _ = '/usr/bin/cygcheck' HKEY_CURRENT_USER\Software\Cygwin HKEY_CURRENT_USER\Software\Cygwin\Program Options HKEY_CURRENT_USER\Software\Cygwin\setup HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExts\.edu%2fcygwin%2f HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExts\.edu%2fcygwin%2f\OpenWithList HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExts\.edu%2fpub%2fcygwin%2f HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExts\.edu%2fpub%2fcygwin%2f\OpenWithList HKEY_LOCAL_MACHINE\SOFTWARE\Cygwin HKEY_LOCAL_MACHINE\SOFTWARE\Cygwin\Installations (default) = '\??\C:\Cygwin' HKEY_LOCAL_MACHINE\SOFTWARE\Cygwin\Program Options HKEY_LOCAL_MACHINE\SOFTWARE\Cygwin\setup (default) = 'C:\Cygwin' obcaseinsensitive set to 1 Cygwin installations found in the registry: System: Key: c5e39b7a9d22bafb Path: C:\Cygwin c: hd NTFS152624Mb 30% CP CS UN PA FC d: cd N/AN/A e: fd FAT32 7770Mb 4% CPUN RADON z: hd FAT255Mb 93% CPUN CHAT C:\Cygwin/ system binary,auto C:\Cygwin\bin/usr/bin system binary,auto C:\Cygwin\lib/usr/lib system binary,auto cygdrive prefix /cygdrive userbinary,auto Found: C:\Cygwin\bin\awk Found: C:\Cygwin\bin\awk - C:\Cygwin\bin\gawk.exe Found: C:\Cygwin\bin\bash.exe Found: C:\Cygwin\bin\bash.exe Found: C:\Cygwin\bin\cat.exe Found: C:\Cygwin\bin\cat.exe Found: C:\Cygwin\bin\cp.exe Found: C:\Cygwin\bin\cp.exe Not Found: cpp (good!) Not Found: crontab Found: C:\Cygwin
