[Coco] C Compiler Executive -- Which one? One that works!

Bill Gunshannon billg999 at cs.uofs.edu
Thu Mar 28 12:08:53 EDT 2013


> or you can just do it:
>
> dmode /d1 nam=f1
> dmode /i0 nam=d1

I have never been in favor of using hacks when the correct fix is
simple.  The use of a hard coded /D1 was most likely based on the
fact that Tandy never anticipated CoCo's having hard disks.

bill

>
>
> On Wed, Mar 27, 2013 at 8:35 PM, Bill Gunshannon
> <billg999 at cs.uofs.edu>wrote:
>
>>
>> > I'm trying to get a C compiler working again after a very long time.
>> > I'm currently using a CoCo3 with a DriveWire 4 server.  The stock cc1
>> is
>> > hard coded to try to do something or other with /d1, which I do not
>> > want.  I know I once used a cc2 or some such that looked for
>> everything
>> > on /dd.
>>
>> I have installed the original Radio Shack OS-9 C Compiler on my sIDE
>> hard disk and patching it to use /dd instead of /d1 was trivial.
>>
>> bill
>>
>>
>>
>> --
>> Bill Gunshannon          |  de-moc-ra-cy (di mok' ra see) n.  Three
>> wolves
>> billg999 at cs.scranton.edu |  and a sheep voting on what's for dinner.
>> University of Scranton   |
>> Scranton, Pennsylvania   |         #include <std.disclaimer.h>
>>
>>
>>
>> --
>> Coco mailing list
>> Coco at maltedmedia.com
>> http://five.pairlist.net/mailman/listinfo/coco
>>
>
>
>
> --
> Long live the CoCo
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco
>


-- 
Bill Gunshannon          |  de-moc-ra-cy (di mok' ra see) n.  Three wolves
billg999 at cs.scranton.edu |  and a sheep voting on what's for dinner.
University of Scranton   |
Scranton, Pennsylvania   |         #include <std.disclaimer.h>





More information about the Coco mailing list