Thanks for the suggestions but I now suspect that it's something odd I was doing. I exited J and re-started it and fixed a looping include and the problem went away. The "looping include" was a script including a script that included the original script - this normally gets handled OK but I think this may have been related to the problem. However, I was unable to re-create it with a simple example. I'll try uncommenting what I fixed to see if it re-occurs.
On Sun, Jul 25, 2010 at 12:29 AM, David Ward Lambert <[email protected] > wrote: > Many moons ago Microsoft had "command" and "cmd" programs. These > treated paths and privileges differently. Or it could have been some > sort of options. I'd say try the script using cmd, and try it again > using command. One of these may work. In the other you'll have to > write C:\Progra~1\sixcha~1\j.exe > Hope this helps. > > On Sun, 2010-07-25 at 12:00 +0800, [email protected] > wrote: > > Windows command shell doesn't recognize "C:\Program Files"? > > ---------------------------------------------------------------------- > For information about J forums see http://www.jsoftware.com/forums.htm > -- Devon McCormick, CFA ^me^ at acm. org is my preferred e-mail ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
