defaria@hpclapd.HP.COM (Andy DeFaria) (01/09/91)
Now that I have almost completed an simplex implementation of ksh (actually, with a lack of Un*x support, it only really does command line editing, command history, filename completion, and cut/paste with a mouse) in TP I would like to make it my system shell. I tried changing CONFIG.SYS's SHELL= and setting COMSPEC to my KSH.EXE but I often get: Invalid COMMAND.COMM, system halted. messages which are a real pain in the ... Well you know what I mean! I figure that the problem is that my TP program doesn't have the split personality the COMMAND.COM does (transient and resident parts) so my question is how do I make my TP program have a split personality. P.S. Another thing that I would need to deal with is, when my KSH becomes the system shell I might need to implement the DOS internal commands like DIR and CD 'cause I execute COMMAND.COM /C <command> to do them. Also this would be the right time to implement the ksh script language. P.S.S. Why am I writing a ksh instead of getting/buying one? 1) it's fun! 2) I'm cheap, 4) I don't have a modem to grap stuff off the freebb 3) I don't have the disc space for a vendor supplied ksh and associated baggage.