[Coco] Level3 and Drivewire may not work

[Bill Pierce]

Bill & Robert, have you tried putting all the dw modules in the sys memory? That way they have access to both rbf and scf. I've also wondered about the clock issue. Clock is one of the L3 modules and "I think" dw4 relies on it's clock. Can you run dw4 with a different clock other than clock_dw?
 

Bill Pierce
"Today is a good day... I woke up" - Ritchie Havens
 

My Music from the Tandy/Radio Shack Color Computer 2 & 3
https://sites.google.com/site/dabarnstudio/
Co-Contributor, Co-Editor for CocoPedia
http://www.cocopedia.com/wiki/index.php/Main_Page
E-Mail: ooogalapasooo at aol.com


 
 
-----Original Message-----
From: Bill Nobel <b_nobel at hotmail.com>
To: CoCoList for Color Computer Enthusiasts <coco at maltedmedia.com>
Sent: Wed, Dec 17, 2014 12:43 am
Subject: Re: [Coco] Level3 and Drivewire may not work


That is true Brett, but the fact remains is that in L3 SCF and RBF are split 
into 2 16k banks of thier own with no communication between the 2 as I see it 
now.  This could in time be resolved, but I am not at that point yet.

Bill Nobel

> On Dec 16, 2014, at 11:10 PM, Brett Gordon <beretta42 at gmail.com> wrote:
> 
> If the DW module in question just masks interrupts during it's
> transactions (the uber-lock), I can't logically see any serious
> problem with splitting it into separate SCF and a RBF modules.  I
> think DW also handles the reading the PC's Clock too... how would that
> fit into things?
> 
> -B
> 
> On Tue, Dec 16, 2014 at 11:48 PM, Bill Nobel <b_nobel at hotmail.com> wrote:
>> Ha, just had a thought, DW4’s modules combined could be called NFM ( or 
network file manager) in combination.  In a network sense you can have both SCF 
and RBF calls, that can happen, at any time.  DW4 seems to handle it, but there 
seems to be some incompatibility with L3.
>> 
>> Bill Nobel
>> 
>>> On Dec 16, 2014, at 10:30 PM, Bill Nobel <b_nobel at hotmail.com> wrote:
>>> 
>>> I think though it might be connected to the SCF/DWIO/RBDW relation. I could 
be wrong, but it seems Drivewire crosses the bridge between SCF protocol and RBF 
protocol, to marry the two. Mainly because DW uses serial protocol, but supports 
random block management.
>>> 
>>> Bill Nobel
>>> 
>>>> On Dec 16, 2014, at 9:11 PM, Bill Nobel <b_nobel at hotmail.com> wrote:
>>>> 
>>>> Yeah I found the same thing Robert, I tried DW4 with Becker port first 
thing and found it didn’t boot.  I noticed the same effect on other boots of 
different Image file formats.  I have converted some of them to be compatible in 
VCC, but not all.  I can’t figure out why on some of them.  Work perfect in raw 
Disk basic, but not HDBDos.
>>>> 
>>>> Bill Nobel
>>>> 
>>>>> On Dec 16, 2014, at 8:38 PM, Robert Gault <robert.gault at att.net> wrote:
>>>>> 
>>>>> Having a Level3 boot disk that works with my Coco3, MESS, and VCC, I tried 
changing the contents of OS9Boot to see if Level3 worked with Drivewire. You can 
use rb1773 instead of cc3disk so why not use rbdw and dwio?
>>>>> 
>>>>> Well the new OS9Boot, with rbdw, dwio, and /X#, booted Level3 and floppy 
access still worked. However the system crashed when trying to read /X0. Doesn't 
look good.
>>>>> 
>>>>> Robert
>>>>> 
>>>>> --
>>>>> Coco mailing list
>>>>> Coco at maltedmedia.com
>>>>> https://pairlist5.pair.net/mailman/listinfo/coco
>>>> 
>>>> 
>>>> --
>>>> Coco mailing list
>>>> Coco at maltedmedia.com
>>>> https://pairlist5.pair.net/mailman/listinfo/coco
>>> 
>>> 
>>> --
>>> Coco mailing list
>>> Coco at maltedmedia.com
>>> https://pairlist5.pair.net/mailman/listinfo/coco
>> 
>> 
>> --
>> Coco mailing list
>> Coco at maltedmedia.com
>> https://pairlist5.pair.net/mailman/listinfo/coco
> 
> 
> 
> -- 
> Brett M. Gordon,
> beretta42 at gmail.com
> 
> -- 
> Coco mailing list
> Coco at maltedmedia.com
> https://pairlist5.pair.net/mailman/listinfo/coco


-- 
Coco mailing list
Coco at maltedmedia.com
https://pairlist5.pair.net/mailman/listinfo/coco