Xref: utzoo comp.os.os9:272 comp.sys.m6809:959
Path: utzoo!attcan!uunet!husc6!bloom-beacon!tut.cis.ohio-state.edu!osu-cis!att!ihlpl!knudsen
From: knudsen@ihlpl.ATT.COM (Knudsen)
Newsgroups: comp.os.os9,comp.sys.m6809
Subject: Re: ARTICLE  (BLOB)
Summary: Non-RS floppy controller
Message-ID: <7678@ihlpl.ATT.COM>
Date: 15 Nov 88 17:01:17 GMT
References: <8811141812.AA12030@decwrl.dec.com>
Organization: AT&T Bell Laboratories - Naperville, Illinois
Lines: 28

I haven't had BLOB problems, but I figured that was because I am
very conservative (read lazy and chicken) about making new
bootfiles.  However, sometime before I got my B&B I got a Sardis
no-halt controller.  Whatever else may be said about bugs
in its driver re interrupt handling, the fact is I never had trouble
with it, even when running for a while with the B&B, which
is supposed to be very dangerous.

When I heard about the Sardis SDISK3 incampatibility with B&B,
I just made a new boot with good old CC3DISK, and gave
up the no-halt feature (only bothers me when DSAVEing to
a floppy; otherwise I never use floppies anyway).
Yes, the Sardis works fine as a vanilla controller.

The bottom line is that with plain old CC3DISK (OK, a couple
little patches here and there) I get no problems with the
Sardis controller.  This makes me wonder about the RS controllers;
I think someone mentioned them as one of the things that don't
gate SCS- properly.  And since a FD controller actually does
weirder things with the Coco bus than an HD controller (!),
maybe that's the real weak spot.

How about it, folks?  Any correlation between BLOB grief and
RS -vs- non-RS FD controller?
-- 
Mike Knudsen  Bell Labs(AT&T)   att!ihlpl!knudsen
"Lawyers are like nuclear bombs and PClones.  Nobody likes them,
but the other guy's got one, so I better get one too."