cramer@kontron.UUCP (Clayton Cramer) (05/28/85)
Some of you may recall some negative remarks I made about Epsilon's ability to run processes in a window (in the midst of some positive remarks I made about the product as a whole). As a result of some additional information from Todd Doucet of Lugaru Software which was posted on net.micro.pc, I made another try at running C compilers in an Epsilon window. It *does* work; I found out why I originally had problems, and the reasons may be of interest to some of you who have Epsilon, or are about to buy Epsilon, and try to run it on a floppy disk system. One weakness of the manual is that is neglects to tell you that you must have COMMAND.COM available to run when you start a process in an Epsilon window. (At this point, you are probably wondering, "What? Why wouldn't it be available?" I have a 2 floppy PC, and no hard disk. Running Microsoft C V3.0 (which I'm very pleased with, incidentally) requires puttting COMMAND.COM on my RAM disk and swapping disks a lot. Perhaps because I have an ancient PC (with 16K RAMs on the motherboard, and the original ROM), Epsilon wants COMMAND.COM to be on drive A, even though the default drive is drive C.) If you try to run a process in an Epsilon window, and you get the message "exited" in the window, without the process running, this is probably the reason. In summary, Epsilon definitely works, and my problems were probably related to owning an antique PC.