Jim Hall said:
| Let's say you wanted to run FreeDOS EDIT every time FreeDOS boots up. | The full path to EDIT is C:\FREEDOS\BIN\EDIT.EXE, so you would create | a custom FDCONFIG.SYS that probably looked like this: | | FILES=20 | BUFFERS=20 | SHELL=C:\FREEDOS\BIN\EDIT.EXE | | For #2, see also this note at the end of the article: | | > However, there's one limitation here. Embedded systems do not usually need | > to exit back to a command prompt, so these dedicated applications don't | > usually allow the user to quit to DOS. If you manage to exit the embedded | > application, you'll likely see a "Bad or missing Command Interpreter" | > prompt, where you'll need to enter the full path to a new shell. For a | > user-focused desktop system, this would be a problem. But on an embedded | > system that's dedicated to doing only one job, you should never need to | > exit anyway. What if you use the /P switch when loading the shell? _______________________________________________ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
