Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.3 Unisoft-Cosmos; site micropro.UUCP
Path: utzoo!watmath!clyde!bonnie!akgua!whuxlm!harpo!decvax!ucbvax!ucdavis!lll-crg!well!micropro!edg
From: edg@micropro.UUCP (Ed Greenberg)
Newsgroups: net.micro.pc
Subject: Re: Sidekick vs. Microsoft C
Message-ID: <170@micropro.UUCP>
Date: Fri, 18-Oct-85 16:40:11 EDT
Article-I.D.: micropro.170
Posted: Fri Oct 18 16:40:11 1985
Date-Received: Mon, 21-Oct-85 00:38:35 EDT
References: <962@vax2.fluke.UUCP> <298@graffiti.UUCP>
Reply-To: edg@micropr.UUCP (edg)
Distribution: net
Organization: MicroPro Int'l Corp., San Rafael, CA
Lines: 23

In article <298@graffiti.UUCP> peter@graffiti.UUCP (Peter da Silva) writes:
>Sidekick won't run when MS-DOS is currently executing, to avoid re-entrancy
>problems. The BIOS is re-entrant, but MS-DOS isn't. gets and fgets both must
>use MS-DOS call #whatever-it-is to read a line of text, instead of doing it
>character-at-a-time in the BIOS as other programs do. You can get the same
>result by invoking Sidekick at certain times in COMMAND.COM.
>...
>Workaround #2: Write your own gets() function, using getch(), and do all the
>erase and kill processing yourself

Or try this...  Sit in a loop until a character becomes available, THEN
call fgets (or whatever) to get the string.  When a Sidekick hit
happens, you're not in DOS.  If you are filling out the command line,
and you try to bring up SK, you will still get the five beeps, but
that's much more appropriate than getting them at the beginning of the
line.
					-e


-- 
Ed Greenberg; MicroPro International Corp. (disclaimer)
UUCP: {hplabs,dual,glacier,lll-crg}!well!micropro!edg
AT&T: 415-499-4096