Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site sdcarl.UUCP
Path: utzoo!linus!philabs!cmcl2!seismo!harvard!talcott!panda!genrad!decvax!ittatc!dcdwest!sdcsvax!sdcc3!sdcarl!andy
From: andy@sdcarl.UUCP (Andrew Voelkel)
Newsgroups: net.micro.pc
Subject: dos exec call (help)
Message-ID: <225@sdcarl.UUCP>
Date: Tue, 23-Jul-85 01:55:13 EDT
Article-I.D.: sdcarl.225
Posted: Tue Jul 23 01:55:13 1985
Date-Received: Fri, 26-Jul-85 04:12:25 EDT
Organization: Computer Audio Research Lab, UCSD, San Diego, Calif.
Lines: 25

I am considering the possibility of writing some subset of what looks like
a unix "shell" (really just a history mechanism to cut down on repeated
long command lines), since queries as to the existence of such a facility
have been unsuccessfull. I have read the description of the dos EXEC call
in the tech reference manual and in Norton's "programmers guide". I'm
still a bit confused and remember some discussion about the subject a 
while back. Could someone help me out with a more thourough description,
and maybe an example of use? Are there tragic flaws to prevent such a
scheme from working at all? I figure there must be stumbling blocks or
someone would have succeeded at doing something like this already.

Another question:
	I am using the Mark Williams C compiler to port software written
under Unix. They often read binary input from stdin. Such input is often
cut off in the middle of a file (presumably because we run into a end of
file character). Friends have run into this problem also. Is it really
true that one cannot read binary input from stdin (a file), or is this
a problem unique to the Mark Williams Compiler?

Thanks in advance to any answers?


-- 
	Andrew Voelkel
	{ucbvax,ihnp4,akgua,hplabs,sdcsvax}!sdcarl!andy