Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!zaphod.mps.ohio-state.edu!wuarchive!mit-eddie!uw-beaver!sumax!polari!rwing!nanook
From: nanook@rwing.UUCP (Robert Dinse)
Newsgroups: comp.sys.tandy
Subject: Re: Tandy 6000 floppy
Summary: initilization
Keywords: init
Message-ID: <146@rwing.UUCP>
Date: 6 Sep 90 19:50:18 GMT
References: <144@rwing.UUCP> <5656@thebes.Thalatta.COM>
Organization: Totally Unorganized
Lines: 20

In article <5656@thebes.Thalatta.COM>, campbell@Thalatta.COM (Bill Campbell) writes:
> 
> When Xenix is originally installed on the Tandy 6K/16 systems it
> asks if you are running a Model II.  If you answer yes it sets
> the drive seek rates differently since the Model II drives ran
> continuously rather than only while being used.  You could
> probably look into the initialization code on the boot floppy to
> determine what is happening and do the same thing after the
> system is installed.
> 

     The "drive" command can be used to set things back to normal. However
the original init makes no reference to /etc/drive or /xenix so I am
curious how it accomplishes this. I suspect there is a lower overhead
way to do it then to call drive and a less dangerous method than to write
kernal address space.

     Thanks for the suggestion though. As a temporary work-around I have
in my /etc/rc file: "/etc/drive wait rate=0", but I'd like that not to be
necessary so this could be a "pop-in" replacement for the original init.