dillon@CORY.BERKELEY.EDU (Matt Dillon) (05/05/86)
I don't know why, but it doesn't work... it comes up and all that, but the does strange things, and dies when you exit. You must execute shell from a CLI. (note here that the thing that executes the startup-sequence IS a CLI, of course. In fact, when programming, I hardly ever use the workbench... I don't even bother to bring it up. Sorry if this has caused confusion. -Matt
sdl@MITRE-BEDFORD.ARPA (Steven D. Litvintchouk) (05/06/86)
I don't know why, but it doesn't work... it comes up and all that, but the does strange things, and dies when you exit. OK, I promise to run your Shell V2 only from the CLI! However, just for the record, I want to reiterate that the *only* problem I had in running Shell V2 from the Workbench (by mousing an associated icon) was the inability of the Shell to pass the location of a named file to built-in programs, unless the entire pathname (including the drive) was given for the file. I haven't experienced any other problems. When exiting Shell V2 run from Workbench, I find that the window closes cleanly, and everything else on the Workbench is fine....no crashes or anything. I compiled my copy of Shell V2 using Lattice C and Workbench 1.1. Perhaps Aztec C is the culprit.... Steven Litvintchouk MITRE Corporation Burlington Road Bedford, MA 01730 (617)271-7753 ARPA: sdl@mitre-bedford UUCP: ...{allegra,decvax,genrad,ihnp4,philabs,security,utzoo}!linus!sdl