[Coco] Updated KenTon SCSI drivers for OS-9?

[Boisy G. Pitre]

Allen, Bob, et al:

No SCSI driver for the CoCo that I know of uses the SCSI 
disconnect/reconnect feature, so that is not the problem.  I'm not sure 
what Allen is seeing.  It could be a SCISYS issue, it could be 
SuperDrivers, it could be hardware.  What's interesting is that Allen 
describes the lock-up as an inactive keyboard, though the CLEAR key 
still causes the cursor to blink.  This tells me that control is stuck 
in the driver with interrupts unmasked.  This usually points to an 
infinite loop in the driver that is not encountering an exit condition.
--
Boisy G. Pitre
E-Mail: boisy at boisypitre.com
Mobile: (337) 739-7584
Web: www.boisypitre.com

On Sep 15, 2004, at 6:28 PM, Bob Devries wrote:

> Al said:
>> Bob, what do you mean by "disconnect/reconnect"?
>
> That is a bus phase, where the disk drive is disconnected from the 
> SCSI bus
> in the middle of a transaction, and is later re-connected to continue. 
> I
> dunno if the coco SCSI systems use it, though.
> Boisy, you got a comment on that?
> --
> Regards, Bob Devries. Dalby, Queensland, Australia.
> Faith isn't faith until it's all you're holding on to.
> http://e4god.com/freeblogs/bdevries/
>
>
> ----- Original Message -----
> From: <alsplace at pobox.com>
> To: <coco at maltedmedia.com>
> Sent: Thursday, September 16, 2004 1:41 AM
> Subject: Re: [Coco] Updated KenTon SCSI drivers for OS-9?
>
>
>> Bob, what do you mean by "disconnect/reconnect"?
>>
>> I keep suspecting it is a conflict from SCSISYS and whatever IDE 
>> driver
>> I try to use (Glenside, or now SuperDrivers).  I recall SCSISYS had
>> some cache thing with an 8K block that got banked in and out, but it
>> seems it would either always work, or always fail if that were the 
>> case.
>>
>> Also, if I boot from the SuperDrivers disk then load the Kenton stuff
>> (SCSISYS and k0, my descriptor -- Kenton drive 0), it works.  But if I
>> boot from the NitrOS9 image Mark put on my hard drive and load the
>> SCSI, it hangs.  So it's got to be a simple combination of modules.
>>
>> Now, if I could just do this the correct way -- build a proper boot
>> using the provided scripts -- maybe I'd be in better shape, but I
>> modified a bootlist that included the SuperDrivers and removed the 
>> SCSI
>> stuff there I did not need (Sx descriptors, lltc3 sub-driver) and 
>> added
>> the scsisys and k0, and it also did not work.
>>
>> So it's got to be something about how those drivers use memory.  The
>> weird thing is, it may work -- copying files happily for HOURS --
>> before it hangs.
>>
>> I will be trying to get the unsupported, non-tested, "might work but 
>> if
>> your drive dies it's your fault" KenTon driver from Boisy and see if
>> that fixes me up.  ELse I'll write my own -- Boisy's driver module
>> makes even me look at it and say "hey, I could write a hard disk
>> driver!" :-)
>>
>>      -- ALlen
>>
>>
>> -- 
>> Coco mailing list
>> Coco at maltedmedia.com
>> http://five.pairlist.net/mailman/listinfo/coco
>>
>
>
>
> -- 
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco
>