🚀 go-pugleaf

In article <eJB8o4w163w@mudos.ann-arbor.mi.us> mju@mudos.ann-arbor.mi.us (Marc Unangst) writes:
>[...]
>Also, PLEASE don't hardcode "C:\COMMAND.COM" into your program.  Not
>only does it prevent people who don't have a hard disk from using your
>program (if you think they're rare, what about people with diskless
>workstations or computers with a floppy only, who run stuff off the
>network?), but it prevents people from using an alternate command
>processor, such as 4DOS, with your program.  I'd suggest that you grab
>COMSPEC from the environment and try to load that, and only try to
>explicitly spawn COMMAND.COM if COMSPEC doesn't exist.

Maybe try grabbing SHELL next?

I run the MKS toolkit, and frankly I'd prefer it if programs grabbed
shell first, since COMSPEC is set to c:/command.com, and SHELL is set
to c:/bin/sh.exe. But this is just peculiar to my setup. When I get
command.com, I just run sh.exe on top of it, but it wastes some
memory.


--
Bitnet:                 pmrcjdb@uchimvs1
Internet:       cjdb@midway.uchicago.edu