#re: 51244
2 messages in this thread
I am working on a number of improvements to Matt Dillion's Cshell which will
address some problems. In the mean time the current shell uses a buffer for
the copy command that is as the file or as large as memory will allow. Quite
efficient. I have copied large files from one drive to another and watched the
light on the source drive go out BEFORE the light on the destination drive went
on! I think I can fix it so that It will not ask for the destination disk
until after it has read in the data form the source disk. Not shure. If not it
only involves one excess disk swap 😉
I have a friend who does software development on a one drive, 512K system!?! so
I know he, if no one else will appriciate the changes. BTW he uses the shell
now and loves it.
jim powell
I just downloaded ver. 2.05 of the shell, so I haven't had time to play with it
much. Not being a Unix user, it's taking some getting used to, but on the
whole it's behaving fairly well. I just ran into a program that wouldn't run
under it. In fact, when the shell is loaded, you can't even run this program
from it's icon on the Workbench. The program is a file viewer that a friend of
mine wrote, so maybe I'll get him to take a look at the shell source and see
what's going on.