From: Suresh G. <sgo...@ya...> - 2008-09-04 03:18:17
|
>>Quoting Earnie > Quoting Suresh Govindachar <sgo...@ya...>: >>Quoting Earnie >>> Quoting Suresh Govindachar <sgo...@ya...>: >>>>> >>>>> This appears to be an environment issue. How are you starting MSYS? >>>>> Or are you using some other bash? What is the output of ``which ls''? >>>> >>>> Bash is started with a shortcut that has the command: >>>> >>>> C:\opt\msys\1.0\bin\bash.exe --rcfile c:\home\suresh\.bashrc >>> >>> Where did you get bash.exe? >> >> From the MinGW site -- I have been using this MinGW, MSYS and bash >> for a year or so with no issues. The lack of output started a few >> days ago. > > So, what changed on your system? Did you install any hardware > components; like a camera? Yes, I installed a camera (Logitech), its software and some additional video related software (such as videolan vlc and QuickTime). > >>> What happens if you open a Windows command window and >>> execute c:\opt\msys\1.0\msys.bat? >> >> c:\home\suresh>c:\opt\msys\1.0\msys.bat >> Cannot find the rxvt.exe or sh.exe binary -- aborting. >> Press any key to continue . . . >> >> However, sh.exe does exist: >> > > Create a ``shortcut'' and set Target C:\opt\msys\1.0\msys.bat > and Start in with C:\opt\msys\1.0\bin, save the short cut and > then click on it. This pops up a window with yellowish background that seems to have a working bash. >> c:\home\suresh>dir c:\opt\msys\1.0\bin\*sh.exe >> Volume in drive C has no label. >> Volume Serial Number is B879-566C >> >> Directory of c:\opt\msys\1.0\bin >> >> 09/27/2007 09:44 AM 567,296 bash.exe >> 01/02/2003 08:05 AM 11,264 rsh.exe >> 08/08/2006 07:49 AM 567,296 sh.exe >> 01/02/2003 08:05 AM 734,208 ssh.exe >> 4 File(s) 1,880,064 bytes >> 0 Dir(s) 47,383,117,824 bytes free >> >> c:\home\suresh> >> >> I then tried the following from a cmd window: >> >> C:\opt\msys\1.0\bin\bash.exe --rcfile c:\home\suresh\.bashrc >> >> and the bash I got seems to work correctly. So it could be that >> something in Windows is not allowing the shortcut to work anymore. >> The env in this bash has TERM set to cygwin. > > This is different than what you stated orginally. But again, > what changed on your system? I don't understand the part about my having stated something different -- what have I stated now and what different thing did I state earlier? >> The windows env from within a cmd window: >> >> c:\home\suresh>set >> ALLUSERSPROFILE=C:\Documents and Settings\All Users >> APPDATA=C:\Documents and Settings\sgovinda\Application Data >> CLASSPATH=.;C:\Program Files\Java\jre1.6.0_03\lib\ext\QTJava.zip >> CommonProgramFiles=C:\Program Files\Common Files >> COMPUTERNAME=XP-SGOVINDA2 >> ComSpec=C:\WINDOWS\system32\cmd.exe >> FP_NO_HOST_CHECK=NO >> HOMEDRIVE=U: >> HOMEPATH=\ >> HOMESHARE=\\ad-campbell2\users\sgovinda >> Include=C:\SYBASE\INCLUDE >> Lib=C:\SYBASE\LIB >> LOGONSERVER=\\CHM-DC1 >> NUMBER_OF_PROCESSORS=1 >> OS=Windows_NT >> Path=c:\opt\perl\site\bin;c:\opt\perl\bin;C:\Program >> Files\Common >> Files\OTG;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\P >> rogram >> Files\ATI Technologies\ATI Control >> Panel;C:\SYBASE\DLL;C:\SYBASE\BIN;c:\opt\uu\usr\local\wbin;C:\opt\gtk\ >> 2.0\bin;C:\opt\Smart Projects\IsoBuster;c:\opt\gnupg;C:\Program >> Files\QuickTime\QTSystem\ >> PATHEXT=.pl;.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.PSC1 >> PROCESSOR_ARCHITECTURE=x86 >> PROCESSOR_IDENTIFIER=x86 Family 6 Model 9 Stepping 5, GenuineIntel >> PROCESSOR_LEVEL=6 >> PROCESSOR_REVISION=0905 >> ProgramFiles=C:\Program Files >> PROMPT=$P$G >> QTJAVA=C:\Program Files\Java\jre1.6.0_03\lib\ext\QTJava.zip >> SESSIONNAME=Console >> SonicCentral=C:\Program Files\Common Files\Sonic Shared\Sonic Central\ >> SYBASE=C:\SYBASE >> SystemDrive=C: >> SystemRoot=C:\WINDOWS >> TEMP=c:\temp >> TMP=c:\temp >> USERDNSDOMAIN=AD.MC.COM >> USERDOMAIN=MERCURY >> USERNAME=sgovinda >> USERPROFILE=C:\Documents and Settings\sgovinda >> windir=C:\WINDOWS >> XCHAT_WARNING_IGNORE=true >> >> c:\home\suresh> >> >> "which ls" outputs nothing. Using the full path to ls >> (/c/opt/msys/1.0/bin/ls.exe) outputs nothing: >>> >>> ~$ /c/opt/msys/1.0/bin/ls.exe >>> ~$ pwd >>> /home/suresh >>> ~$ >>> >>> The environment: >>> >>> ~$ env >>> XCHAT_WARNING_IGNORE=true >>> HOMEPATH=ad-campbell2\users\sgovinda >>> APPDATA=C:\Documents and Settings\sgovinda\Application Data >>> TERM=cygwin >> >> TERM=cygwin looks suspicious. >> TERM=msys or TERM=xterm should be better. >> aside> John Clizbe (not I) said that he too sees "TERM=cygwin aside> if [he] start[s] in a cmd window (with --norxvt)" aside> aside>> That isn't what you said before. >> > Do commands work in the command window after you start MSYS with >> > c:\opt\msys\1.0\msys.bat? >> >> msys.bat does not work (see above). >> >> > Also, which OS are you using? >> >> Windows XP Professional, Version 2002, Service Pack 2. >> >> I rebooted the machine and started bash from the shortcut and issued >> ls as the very first command; it worked; but issuing ls again >> outputted nothing. Hasn't worked since that first time. >> > > Something on your system is causing this. What changed? If > nothing changed then you should run memory diagostics? Hope it isn't an issue with memory! --Suresh |