From: Paul G. <pga...@at...> - 2002-11-19 00:28:46
|
Got it Earnie. Thanks for the consideration on the virus stuff...though I am pretty secure here it is definitely appreciated. Paul G. > Can someone please test this on a non NT platform and provide the > results? I named it .txt to avoid the "You have a virus attached" > spam. :) So, rename it appropriately. > > Thanks, > Earnie. > |
From: Paul G. <pga...@at...> - 2002-11-19 02:56:20
|
> Can someone please test this on a non NT platform and provide the > results? I named it .txt to avoid the "You have a virus attached" > spam. :) So, rename it appropriately. No problem, Earnie. Here are the results. Some initial results: under Win98SE, when @echo off is enabled (not remarked), produces the following error: "File not Found" Msys prompt (rxvt) launches. Additional information and commentary. Baseline description: Shortcut I am using to start Msys already has environment setting (cmd line) manually defined within the shortcut itself as follows: c:\windows\command.com /E:4096 /c D:\MSYS\1.0\MSYS.BAT No errors occur. -- end "baseline" description Hmm...just noticing something (from Earnies' msys.bat.txt): ... if "%COMPSPEC%" == "" set COMSPEC=command.com start %COMSPEC% /e:4096 /c %0 GOTO: _Resume %0 %1 %2 %3 %4 %5 %6 %7 %8 %9 goto EOF ... ... Did you want "compspec" for some reason, Earnie? If I eliminate, ie. change "compspec" to "comspec": eg. ... ... if "%COMSPEC%" == "" set COMSPEC=command.com start %COMSPEC% /e:4096 /c %0 GOTO: _Resume %0 %1 %2 %3 %4 %5 %6 %7 %8 %9 goto EOF ... ... ... ...and re-enable @echo off the following occurs: "File not found" Error goes away. (attached file has been modified to "comspec" from "compspec") Another test (shortcut): If I change c:\windows\command.com /E:4096 /c D:\MSYS\1.0\MSYS.BAT** (this is my "baseline" for windows shortcut under Win98SE). to: D:\MSYS\1.0\MSYS.BAT** (this is original Msys prompt cmd line format) ** CMD LINE within Msys (desktop) shortcut under Win98SE. shows new errors: Out of Environment Space File not found rxvt/msys prompt does launch w/o "Out of Environment Space" error appearing again during normal Msys/rxvt prompt operations/session. "Out of Environment Space" and "File not found" errors do recur whenever Msys is launched using "original" msys.bat shortcut (cmd line) format. For now I will revert to my working Msys shortcut where the cmd line format looks like this: c:\windows\command.com /E:4096 /c D:\MSYS\1.0\MSYS.BAT (my "baseline" definition) Paul G. ps. not sure if it is appropriate here, but will throw it out here anyway. I realize that the install program is limited in terms of what it can do with some things, specifically when it comes to differentiation between Operating Systems. I also realize that the msys.bat.txt proposal is an attempt to bypass the install package limitations, and I appreciate the time and effort that you are putting into Mingw and Msys in general, Earnie. I appreciate the time and energy that we are all, those who post to this list, putting into Mingw and Msys. |
From: Earnie B. <ear...@ya...> - 2002-11-19 13:14:45
Attachments:
msys.bat.txt
|
Paul G. wrote: > Hmm...just noticing something (from Earnies' msys.bat.txt): > > ... > if "%COMPSPEC%" == "" set COMSPEC=command.com > start %COMSPEC% /e:4096 /c %0 GOTO: _Resume %0 %1 %2 %3 %4 %5 %6 %7 %8 %9 > goto EOF > ... > ... > > > Did you want "compspec" for some reason, Earnie? > > If I eliminate, ie. change "compspec" to "comspec": > Thanks, Paul, change accepted. > eg. > ... > ... > if "%COMSPEC%" == "" set COMSPEC=command.com > start %COMSPEC% /e:4096 /c %0 GOTO: _Resume %0 %1 %2 %3 %4 %5 %6 %7 %8 %9 > goto EOF > ... > ... > ... > > > ...and re-enable @echo off the following occurs: > > "File not found" Error goes away. > > (attached file has been modified to "comspec" from "compspec") > > Another test (shortcut): > > If I change > > c:\windows\command.com /E:4096 /c D:\MSYS\1.0\MSYS.BAT** (this is my > "baseline" for windows shortcut under Win98SE). > > to: > > D:\MSYS\1.0\MSYS.BAT** (this is original Msys prompt cmd line format) > > ** CMD LINE within Msys (desktop) shortcut under Win98SE. > > shows new errors: > > Out of Environment Space > File not found > So, you still see this error; but, > rxvt/msys prompt does launch w/o "Out of Environment Space" error appearing > again during normal Msys/rxvt prompt operations/session. > you start a command shell environment anyway? > "Out of Environment Space" and "File not found" errors do recur whenever Msys is > launched using "original" msys.bat shortcut (cmd line) format. > I've attached a new version with your fix and another small change. Is this better? Earnie. |
From: Luke D. <cod...@ho...> - 2002-11-21 00:08:42
|
Okay I have it working now... ----- Original Message ----- From: "Earnie Boyd" <ear...@ya...> To: <min...@li...> Sent: Tuesday, November 19, 2002 9:14 PM Subject: Re: [MinGW-dvlpr] Updated msys.bat needs a windows 95/98/ME test. > > I've attached a new version with your fix and another small change. Is > this better? > > Earnie. > ---------------------------------------------------------------------------- ---- > @echo off > rem Copyright (C): 2001, 2002 Earnie Boyd > rem mailto:ea...@us... > rem This file is part of Minimal SYStem > rem http://www.mingw.org/msys.shtml > rem > rem File: msys.bat > rem Revision: 2.0 > rem Revision Date: April 17th, 2002 > > rem DON'T CHANGE the value of CYGWIN. > rem Ok. Go ahead change it. Just don't cry on my list if you do. > set CYGWIN="nowinsymlinks notty notitle binmode nontsec nontea nosmbntsec" This should go after the _WindowsNT label. > > rem ember to set the "Start in:" field of the shortcut. > rem A value similar to C:\msys\1.0\bin is what the "Start in:" field needs > rem to represent. > > rem ember value of GOTO: is used to know recursion has happened. > if "%1" == "GOTO:" goto %2 > > rem ember command.com only uses the first eight characters of the label. > goto _WindowsNT > > rem ember that we only execute here if we are in command.com. > :_Windows > > if "x%COMSPEC%" == "x" set COMSPEC=command.com > %COMSPEC% /e:4096 /c %0 GOTO: _Resume %0 %1 %2 %3 %4 %5 %6 %7 %8 %9 > goto EOF > > rem ember that we execute here if we recursed. > :_Resume > for %%F in (1 2 3) do shift > > rem ember that we get here even in command.com. > :_WindowsNT > > if "x%MSYSTEM%" == "x" set MSYSTEM=MINGW32 > if "%1" == "MSYS" set MSYSTEM=MSYS > > if NOT "x%DISPLAY%" == "x" set DISPLAY= > > rem Setup the default colors for rxvt. > if "x%MSYSBGCOLOR%" == "x" set MSYSBGCOLOR=White > if "x%MSYSFGCOLOR%" == "x" set MSYSFGCOLOR=Black > if "x%MINGW32BGCOLOR%" == "x" set MINGW32BGCOLOR=LightYellow > if "x%MINGW32FGCOLOR%" == "x" set MINGW32FGCOLOR=Navy > if "%MSYSTEM%" == "MSYS" set BGCOLOR=%MSYSBGCOLOR% > if "%MSYSTEM%" == "MSYS" set FGCOLOR=%MSYSFGCOLOR% > if "%MSYSTEM%" == "MINGW32" set BGCOLOR=%MINGW32BGCOLOR% > if "%MSYSTEM%" == "MINGW32" set FGCOLOR=%MINGW32FGCOLOR% > > if EXIST bin cd bin I found that this command doesn't work in Win98. To test for the existence of a directory you must do: if exist bin\nul cd bin > if EXIST rxvt.exe goto startrxvt > if EXIST sh.exe goto startsh > > echo Cannot find the rxvt.exe or sh.exe binary -- aborting. > pause > exit 1 There is no "exit" command in command.com, so you should use "goto EOF" instead. I realise this should have been tested long ago. > > rem If you don't want to use rxvt then rename the file rxvt.exe to something > rem else. Then sh.exe will be used instead. > :startrxvt > start rxvt -sl 2500 -fg %FGCOLOR% -bg %BGCOLOR% -sr -fn Courier-12 -tn msys -e /bin/sh --login -i > exit > > :startsh > start sh --login -i > exit > The same for these two exits. > :EOF > Luke |
From: Earnie B. <ear...@ya...> - 2002-11-21 00:22:34
|
Luke Dunstan wrote: > Okay I have it working now... > > ----- Original Message ----- > From: "Earnie Boyd" <ear...@ya...> > To: <min...@li...> > Sent: Tuesday, November 19, 2002 9:14 PM > Subject: Re: [MinGW-dvlpr] Updated msys.bat needs a windows 95/98/ME test. > > > >>I've attached a new version with your fix and another small change. Is >>this better? >> >>Earnie. >> > > > > ---------------------------------------------------------------------------- > ---- > > > >>@echo off >>rem Copyright (C): 2001, 2002 Earnie Boyd >>rem mailto:ea...@us... >>rem This file is part of Minimal SYStem >>rem http://www.mingw.org/msys.shtml >>rem >>rem File: msys.bat >>rem Revision: 2.0 >>rem Revision Date: April 17th, 2002 >> >>rem DON'T CHANGE the value of CYGWIN. >>rem Ok. Go ahead change it. Just don't cry on my list if you do. >>set CYGWIN="nowinsymlinks notty notitle binmode nontsec nontea nosmbntsec" > > > This should go after the _WindowsNT label. > Thanks, Luke. This can actually be removed for 1.0.8, the user settings are ignored and my settings are perminate. Earnie. |
From: Earnie B. <ear...@ya...> - 2002-11-23 19:18:55
|
Luke Dunstan wrote: > Okay I have it working now... > >> >>echo Cannot find the rxvt.exe or sh.exe binary -- aborting. >>pause >>exit 1 > > > There is no "exit" command in command.com, so you should use "goto EOF" > instead. I realise this should have been tested long ago. > What command.com are you executing? The following works for me on the Win98 I dug out of the basement. <foo.bat> echo off echo Hello from foo exit 1 </foo.bat> I even tried this with interesting results <bar.bat> @echo off @echo Hello from bar @exit 1 </bar.bat> Are you sure exit doesn't work for you? Earnie. |
From: Manu <ma...@wa...> - 2002-11-23 21:05:58
|
Earnie Boyd wrote: > Luke Dunstan wrote: > > Okay I have it working now... > > > >> > >>echo Cannot find the rxvt.exe or sh.exe binary -- aborting. > >>pause > >>exit 1 > > > > > > There is no "exit" command in command.com, so you should use "goto EOF" > > instead. I realise this should have been tested long ago. > > > > What command.com are you executing? The following works for me on the > Win98 I dug out of the basement. > > <foo.bat> > echo off > echo Hello from foo > exit 1 > </foo.bat> > > I even tried this with interesting results > > <bar.bat> > @echo off > @echo Hello from bar > @exit 1 > </bar.bat> It works for me as well. I tried also: <foo.bat> echo Hello from foo exit 1 echo Hello again </foo.bat> I don't see "Hello again", so I suppose that it works. --- C:\Dev\Msys-Dev-1.0.8\1.0>echo Hello from foo Hello from foo C:\Dev\Msys-Dev-1.0.8\1.0>exit 1 --- I tried msys.bat version 1, with the typo corrected, version 2 and also a version 3 with Luke's changes, the three bat files seems to work fine, even with "C:\DEV\MSYS-D~1.8\1.0\MSYS.BAT MSYS" in my "msys.pif". I'm running Windows 98 4.10.1998 French. Manu. |
From: Luke D. <cod...@ho...> - 2002-11-24 05:18:53
|
Yes, I was mistaken. When the script was not able to find sh.exe, I was seeing "File not found" errors appearing _after_ the message "Cannot find the rxvt.exe or sh.exe binary -- aborting.", so I thought that it was somehow getting past the "exit". The actual problem is that the first invocation does: %COMSPEC% /e:4096 /c %0 GOTO: _Resume %0 %1 %2 %3 %4 %5 %6 %7 %8 %9 goto EOF The "File not found" occurs here: rem Many thanks to Randy W. Sims <RandyS@ThePierianSpring.org>. ... rem 2002.11.19 Paul Garceau <pga...@at...> The silly shell tries to open files called RandyS@ThePierianSpring.org and pga...@at... and naturally can't find them. If you also try: rem foo>bar ...an empty file "bar" is created. Since you put mailto:ea...@us..., maybe we encountered this before but I don't remember. Luke ----- Original Message ----- From: "Manu" <ma...@wa...> To: <min...@li...> Sent: Sunday, November 24, 2002 5:08 AM Subject: Re: [MinGW-dvlpr] Updated msys.bat needs a windows 95/98/ME test. > Earnie Boyd wrote: > > > > Luke Dunstan wrote: > > > Okay I have it working now... > > > > > >> > > >>echo Cannot find the rxvt.exe or sh.exe binary -- aborting. > > >>pause > > >>exit 1 > > > > > > > > > There is no "exit" command in command.com, so you should use "goto EOF" > > > instead. I realise this should have been tested long ago. > > > > > > > What command.com are you executing? The following works for me on the > > Win98 I dug out of the basement. > > > > <foo.bat> > > echo off > > echo Hello from foo > > exit 1 > > </foo.bat> > > > > I even tried this with interesting results > > > > <bar.bat> > > @echo off > > @echo Hello from bar > > @exit 1 > > </bar.bat> > > It works for me as well. > > I tried also: > <foo.bat> > echo Hello from foo > exit 1 > echo Hello again > </foo.bat> > > I don't see "Hello again", so I suppose that it works. > --- > C:\Dev\Msys-Dev-1.0.8\1.0>echo Hello from foo > Hello from foo > > C:\Dev\Msys-Dev-1.0.8\1.0>exit 1 > --- > > I tried msys.bat version 1, with the typo corrected, > version 2 and also a version 3 with Luke's changes, > the three bat files seems to work fine, even with > "C:\DEV\MSYS-D~1.8\1.0\MSYS.BAT MSYS" > in my "msys.pif". > > I'm running Windows 98 4.10.1998 French. > > Manu. |
From: Earnie B. <ear...@ya...> - 2002-11-24 12:58:08
|
Luke Dunstan wrote: > Yes, I was mistaken. When the script was not able to find sh.exe, I was > seeing "File not found" errors appearing _after_ the message "Cannot find > the rxvt.exe or sh.exe binary -- aborting.", so I thought that it was > somehow getting past the "exit". The actual problem is that the first > invocation does: > > %COMSPEC% /e:4096 /c %0 GOTO: _Resume %0 %1 %2 %3 %4 %5 %6 %7 %8 %9 > goto EOF > > The "File not found" occurs here: > > rem Many thanks to Randy W. Sims <RandyS@ThePierianSpring.org>. > ... > rem 2002.11.19 Paul Garceau <pga...@at...> > > The silly shell tries to open files called RandyS@ThePierianSpring.org and > pga...@at... and naturally can't find them. If you also try: > > rem foo>bar > > ...an empty file "bar" is created. Since you put mailto:ea...@us..., > maybe we encountered this before but I don't remember. > Yes we've seen this before. Thanks for finding it. Earnie. |
From: Manu <ma...@wa...> - 2002-11-24 14:10:50
|
Earnie Boyd wrote: > Luke Dunstan wrote: > > Yes, I was mistaken. When the script was not able to find sh.exe, I was > > seeing "File not found" errors appearing _after_ the message "Cannot find > > the rxvt.exe or sh.exe binary -- aborting.", so I thought that it was > > somehow getting past the "exit". The actual problem is that the first > > invocation does: > > > > %COMSPEC% /e:4096 /c %0 GOTO: _Resume %0 %1 %2 %3 %4 %5 %6 %7 %8 %9 > > goto EOF > > > > The "File not found" occurs here: > > > > rem Many thanks to Randy W. Sims <RandyS@ThePierianSpring.org>. > > ... > > rem 2002.11.19 Paul Garceau <pga...@at...> > > > > The silly shell tries to open files called RandyS@ThePierianSpring.org and > > pga...@at... and naturally can't find them. If you also try: It was because of a line break after "start rxvt ... Courier-12 -tn", isn't it. I've been confused by this when copied/pasted the text into a bat file: start rxvt -sl 2500 -fg %FGCOLOR% -bg %BGCOLOR% -sr -fn Courier-12 -tn msys -e /bin/sh --login -i ^ line break pollution. Manu. > > rem foo>bar > > > > ...an empty file "bar" is created. Since you put mailto:ea...@us..., > > maybe we encountered this before but I don't remember. > > > > Yes we've seen this before. Thanks for finding it. > > Earnie. > > > > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > _______________________________________________ > MinGW-dvlpr mailing list > Min...@li... > https://lists.sourceforge.net/lists/listinfo/mingw-dvlpr |
From: Earnie B. <ear...@ya...> - 2002-11-24 15:12:59
|
Manu wrote: >>> >>>The silly shell tries to open files called RandyS@ThePierianSpring.org and >>>pga...@at... and naturally can't find them. If you also try: >> > > It was because of a line break after "start rxvt ... Courier-12 -tn", isn't it. > I've been confused by this when copied/pasted the text into a bat file: > > start rxvt -sl 2500 -fg %FGCOLOR% -bg %BGCOLOR% -sr -fn Courier-12 -tn > msys -e /bin/sh --login -i > ^ line break pollution. > The file was attached so you should have just saved the attachment. Luke is correct, I've had the problem before. Earnie. |
From: Paul G. <pga...@at...> - 2002-11-20 13:21:11
|
[snip] > > Did you want "compspec" for some reason, Earnie? > > > > If I eliminate, ie. change "compspec" to "comspec": > > > > Thanks, Paul, change accepted. Glad I could help. > > > eg. > > ... > > ... > > if "%COMSPEC%" == "" set COMSPEC=command.com > > start %COMSPEC% /e:4096 /c %0 GOTO: _Resume %0 %1 %2 %3 %4 %5 %6 %7 > > %8 %9 goto EOF ... ... ... > > > > > > ...and re-enable @echo off the following occurs: > > > > "File not found" Error goes away. > > > > (attached file has been modified to "comspec" from "compspec") > > > > Another test (shortcut): > > > > If I change > > > > c:\windows\command.com /E:4096 /c D:\MSYS\1.0\MSYS.BAT** (this is > > my "baseline" for windows shortcut under Win98SE). > > > > to: > > > > D:\MSYS\1.0\MSYS.BAT** (this is original Msys prompt cmd line > > format) > > > > ** CMD LINE within Msys (desktop) shortcut under Win98SE. > > > > shows new errors: > > > > Out of Environment Space > > File not found > > > > So, you still see this error; but, > > > rxvt/msys prompt does launch w/o "Out of Environment Space" error > > appearing again during normal Msys/rxvt prompt operations/session. > > > > you start a command shell environment anyway? Yup! rxvt/msys prompt launches. > > > "Out of Environment Space" and "File not found" errors do recur > > whenever Msys is launched using "original" msys.bat shortcut (cmd > > line) format. > > > > I've attached a new version with your fix and another small change. > Is this better? Turns out that the following errors are now being reported using the attached msys.bat.txt file during ms-dos prompts' life. (echo is off) and using original CMD line settings (as provided in Msys install). Out of Environment Space File not Found File not Found (errors noted recur for every test except when ms-dos prompt cmd line includes environment settings -- in that case, only a single error occurs: File not Found) some "grinding" (aka: processing) seems like Win98SE is working really, really hard ms-dos prompt hangs out a bit rxvt/msys prompt launches ms-dos prompt closes normally So, rxvt/msys prompt launches just fine. Msystem is set to Mingw32. Paul G. |
From: Luke D. <cod...@ho...> - 2002-11-20 14:13:07
|
>From: "Paul G." <pga...@at...> >Reply-To: min...@li... >To: min...@li... >Subject: Re: [MinGW-dvlpr] Updated msys.bat needs a windows 95/98/ME test. >Date: Wed, 20 Nov 2002 05:21:15 -0800 > > [snip] > > I've attached a new version with your fix and another small change. > > Is this better? > >Turns out that the following errors are now being reported using the >attached msys.bat.txt file during ms-dos >prompts' life. (echo is off) Paul, could you try turning echo on to see where the errors occur? >and using original CMD line settings (as provided in Msys install). > > Out of Environment Space I don't know why I didn't notice this before :). It is caused by attempting to set CYGWIN too early in the script. > File not Found > File not Found I don't know about these errors and I haven't tried running this yet on Win98 but hopefully I will be able to soon. > > Paul G. Luke _________________________________________________________________ Help STOP SPAM with the new MSN 8 and get 2 months FREE* http://join.msn.com/?page=features/junkmail |
From: Paul G. <pga...@at...> - 2002-11-20 23:07:29
|
> > > > > [snip] > > > I've attached a new version with your fix and another small > > > change. Is this better? > > > >Turns out that the following errors are now being reported using the > >attached msys.bat.txt file during ms-dos prompts' life. (echo is off) > > Paul, could you try turning echo on to see where the errors occur? With echo on, no errors occur, at least not that I can detect. Will double check just to be certain. Paul G. > > >and using original CMD line settings (as provided in Msys install). > > > > Out of Environment Space > > I don't know why I didn't notice this before :). It is caused by > attempting to set CYGWIN too early in the script. > > > File not Found > > File not Found > > I don't know about these errors and I haven't tried running this yet > on Win98 but hopefully I will be able to soon. > > > > > Paul G. > > Luke > > > _________________________________________________________________ Help > STOP SPAM with the new MSN 8 and get 2 months FREE* > http://join.msn.com/?page=features/junkmail > > > > ------------------------------------------------------- > This sf.net email is sponsored by: To learn the basics of securing > your web site with SSL, click here to get a FREE TRIAL of a Thawte > Server Certificate: http://www.gothawte.com/rd524.html > _______________________________________________ MinGW-dvlpr mailing > list Min...@li... > https://lists.sourceforge.net/lists/listinfo/mingw-dvlpr |
From: Paul G. <pga...@at...> - 2002-11-20 23:54:19
|
[skip] > > > File not Found > > File not Found These last two only occur if echo is set to off. They do not occur if echo is set to on. One more thing to note: If multiple pause commands are in the .bat fiile the errors do not occur. Now, this File not Found error, and this is pure speculation/theory at this point, could be caused by an internal file conflict within the OS when it tries to open a file that has already been opened at least once prior to when a File not Found error occurs. Considering that there are at least three ms-dos prompts launched before rxvt/msys prompt is actually opened, this is a very real possibility. (see "shift" directive, ie. "for %%F in (1 2 3) do shift") theory: first ms-dos prompt (command.com), Out of Environment Space error generated (known error -- can confirm it is caused by Cygwin being set too early in first command.com generation) second ms-dos prompt (command.com) launched: No Out of Environment Space error File not Found error is generated third ms-dos prompt (command.com) launched: No Out of Environment Space error File not Found error is generated I realize it is likely a long-shot on my part, but at this point I have to remember what someone said long ago. When all of the probable causes are eliminated, there is only one alternative, consider the improbable.. > > I don't know about these errors and I haven't tried running this yet > on Win98 but hopefully I will be able to soon. Ok. Paul G. |