On Tuesday 07 December 2004 02:40, Charles Shattuck wrote: > I have an application where I would like to have one gforth program call > other gforth programs. I use a word like: > > s" gforth -m 1M ./interpret.fs -e go" system > > which works fine in Linux. In Windows 98SE I need to include the full > path to gforth.exe, but it still works. In Windows 2000 nothing seems > to work. I can't even get: > > s" dir" system or s" command /c dir" system > > to work. The error message is "dir: not found" or "/c: not found". > > Does anyone know the difference here between Windows 2000 and 98, and is > there a work around I can use? I haven't had a chance to try it on XP.
There was some discussion about this a few month back, don't know where it was (probably comp.lang.forth, at least not in the mailing list). The result was that we use "./$COMSPEC /c " as prefix. ./ is there to keep bash from doing something. $COMSPEC is the location of command.com (or cmd.exe on win2k?). However, something like above *should* work even without prefix, perhaps it's only lacking a ./ in front of gforth (if . is not in the search path of bash). -- Bernd Paysan "If you want it done right, you have to do it yourself" http://www.jwdt.com/~paysan/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
