Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/5/84; site steinmetz.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!bellcore!decvax!mcnc!ncsu!uvacs!edison!steinmetz!davidsen
From: davidsen@steinmetz.UUCP
Newsgroups: net.micro.pc
Subject: fast xtals in AT / Sidekick
Message-ID: <645@steinmetz.UUCP>
Date: Sat, 1-Feb-86 15:39:48 EST
Article-I.D.: steinmet.645
Posted: Sat Feb  1 15:39:48 1986
Date-Received: Mon, 3-Feb-86 05:37:57 EST
References: <236@bnrmtv.UUCP>
Reply-To: davidsen@kbsvax.UUCP (Davidsen)
Organization: GE CRD, Schenectady, NY
Lines: 30
Keywords: fast xtals, Sidekick
Summary: 


I would encourage anyone who has a problem with the floppy drives and a fast
clock to look at all the sources of the problem carefully before slowing down.
I had some of these problems (9 MHz) and tried some patches and stuff without
much luck. I finally found that Sidekick was the cause (or at least part of the problem), since taking it out turned hard failures into perfect operation. 

Since Sidekick also craps up the operation of DOS functions 6 and 7 (direct
read), I'm not too unhappy taking it out. To prove that it does this, write a
program with DEBUG doing:
	a100
	mov	ah,7
	int	21

	g=100,104
With Sidekick out, the values of ALL keys are passed back to the program. With
Sidekick, ^P toggles the printer, ^S stops output, ^Q starts output, and ^C
kills the program. Nobody ever used those keys in an editor, huh? Borland gets
by this in their editor by bypassing the DOS completely and going to the
hardware. This is acceptable in a program for the PC, but making DOS fail is
not!
-- 
	-bill davidsen

	seismo!rochester!steinmetz!--\
       /                               \
ihnp4!              unirot ------------->---> crdos1!davidsen
       \                               /
        chinet! ---------------------/        (davidsen@ge-crd.ARPA)

"It seemed like a good idea at the time..."