[Coco] Drivewire and ADOS...
Brian Blake
random.rodder at gmail.com
Mon Sep 30 12:38:42 EDT 2013
On 9/30/2013 12:21 PM, Al Hartman wrote:
>
>
> -----Original Message----- From: Aaron Wolfe
>
>> I suspect the issue is that HDBDOS and ADOS cannot "coexist"... This is
>> probably true of any two DOS roms, and very likely the same issue would
>> effect users of HDBDOS for the SuperIDE and other flavors of HDBDOS
>> or the
>> RGBDOS it came from. Likely this applies to every DOS although I am
>> not an
>> expert on such things. Apparently ADOS has had facilities for
>> dealing with
>> this situation since long before HDBDOS or DriveWire existed.
>
> Most likely true. Which further backs up the point that this must be
> documented on the Drivewire site.
>
>> I believe the most helpful approach will be to provide documentation
>> that
>> explains the role and scope of the DriveWire software clearly, so that
>> users will understand the demarcation. This way hopefully their first
>> place common sense will take them to the correct project for support.
>
> It would be less work, more useful, and more effective to have it on
> the Drivewire site in a client troubleshooting section.
>
> Why are you trying to make more work for everybody?
>
> -[ Al ]-
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco
We all know what opinions are like, right? How about this: try
presenting your point, and accepting it if not everybody sees it your way?
I don't have a dog in this fight, so to speak, but here's a suggestions:
Ask Allen Huffman for permission to create a page on CoCoPedia for the
DriveWire and you can create the page you think Aaron and everyone else
should be doing.
I'm not trying to be snide, condescending, or any other type of
smartass. I'm being serious.
I happen to agree with Al on some things, but, I also see Aaron's point
as well - it IS a hobby and very few make money at all from the CoCo
these days. If they can provide the resources we all benefit from and a
few basic tips on how to get started, maybe the rest of the community
should take notes, and create an easy to use getting started manual the
laymen can understand. I'll contribute whatever I can - hell, if Allen
doesn't think it should be on CoCoPedia, I'll host it on my website.
There's already a test wiki there I was playing with earlier this year;
just didn't see any reason to have two coco based wiki's out there...
Brian
More information about the Coco
mailing list