Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!zaphod.mps.ohio-state.edu!wuarchive!uunet!lll-winken!ames!haven.umd.edu!mimsy!nocusuhs!nmrdc1!minixug!arrakis!bert
From: bert@arrakis.nl.mugnet.org (Bert Laverman)
Newsgroups: comp.os.minix
Subject: Re: Minix-ST keyboard / mouse / clock
Message-ID: <91052210768@arrakis.nl.mugnet.org>
Date: 22 May 91 07:25:32 GMT
Organization: Alphasoft Nederland
Lines: 31

waltje@uwalt.nl.mugnet.org (Fred 'The Rebel' van Kempen) wrote:
> bert@arrakis.nl.mugnet.org (Bert Laverman) wrote:
>> Hardware level: ikbd interrupt driver
>> Driver level: /dev/kbd, /dev/mouse, /dev/joystick and /dev/rtc.
>> 
>> Looks feasable to me.
> 
> hell- you even implemented it :-)
Yeees, only to get a system that crashes on floppy use. :-(

I admit; I have a working version of the above mentioned devices (apart
from the joystick), and I even wrote a small readclock(1) that does the
same as the AT one. This will allow STers to retain date/time over
re-boots, even if they don't have a diskclock or Mega ST.
  The problem is that SCATTERED_IO requests from FS to the floppy
driver now (sometimes) seems to be messed up: bad byte counts, silly
block numbers, etc. I haven't the slightest idea how this problem
is created. Appearently it doesn't happen for Harddisk requests. Typical
situation where it goes wrong: "cp minix.img /dev/sd0". The effects range
from error messages from FS, to attempts by the floppy drive head
to escape from my drive. :-(
  I checked for interrupt problems, but that seems (no longer) to
be the cause....

Ideas anyone?

Greetings, Bert

=====================================================================
    Bert Laverman		email: bert@arrakis.nl.mugnet.org
    tel.:  +31 50 - 733587	   or: laverman@cs.rug.nl
=====================================================================