[Coco] Drivewire and ADOS...
Bill Pierce
ooogalapasooo at aol.com
Mon Sep 30 12:25:04 EDT 2013
I'm staying out of this one LMAO
Bill Pierce
My Music from the Tandy/Radio Shack Color Computer 2 & 3
https://sites.google.com/site/dabarnstudio/
Co-Webmaster of The TRS-80 Color Computer Archive
http://www.colorcomputerarchive.com/
Co-Contributor, Co-Editor for CocoPedia
http://www.cocopedia.com/wiki/index.php/Main_Page
E-Mail: ooogalapasooo at aol.com
-----Original Message-----
From: Al Hartman <alhartman6 at optonline.net>
To: CoCoList for Color Computer Enthusiasts <coco at maltedmedia.com>
Sent: Mon, Sep 30, 2013 12:21 pm
Subject: Re: [Coco] Drivewire and ADOS...
-----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
More information about the Coco
mailing list