[Coco] NitrOS-9 V3.3.0 and DriveWire

[Stephen H. Fischer]

Hi,

I have not looked at the makefiles, but is there not a way to simplify 
Boisy's efforts.

There must be common blocks of lines that could be included with a 
"#Include" preprocessor command.

I made one for Basic09, "C" of course has one.

----------------------------------------------------
PROCEDURE B_Prep
REM 89/07/23
DIM Istring,Aname,Tname:STRING[30]
DIM Iline,Aline:STRING[256]
DIM Ipath,Opath,Epath,Apath:BYTE
DIM Qstart,Qend:INTEGER

Ipath=0 \Opath=1 \Epath=2
Istring="#include "

WHILE NOT(EOF(#Ipath)) DO
READ #Ipath,Iline
Qstart=SUBSTR(Istring,Iline)
IF Qstart=0 THEN
PRINT #Opath,Iline
ELSE
PRINT #Opath,"REM ";
PRINT #Opath,Iline
Qstart=SUBSTR(CHR$(34),Iline)
IF Qstart=0 THEN
PRINT #Epath,"B_prep - MISSING start quotes"
PRINT #Epath,Iline
ERROR 56
ENDIF
Qstart=LEN(Iline)-Qstart
Tname=RIGHT$(Iline,Qstart)
Qend=SUBSTR(CHR$(34),Tname)
IF Qend=0 THEN
PRINT #Epath," B_prep - MISSING end quotes"
PRINT #Epath,Iline
ERROR 41
ENDIF
Qend=Qend-1
Aname=LEFT$(Tname,Qend)
OPEN #Apath,Aname:READ
WHILE NOT(EOF(#Apath)) DO
READ #Apath,Aline
PRINT #Opath,Aline
ENDWHILE
CLOSE #Apath
ENDIF
ENDWHILE
END

----------------------------------------------------

SHF


----- Original Message ----- 
From: "Aaron Wolfe" <aawolfe at gmail.com>
To: "CoCoList for Color Computer Enthusiasts" <coco at maltedmedia.com>
Sent: Tuesday, March 30, 2010 11:19 AM
Subject: Re: [Coco] NitrOS-9 V3.3.0 and DriveWire


So, what I've seen as I watched this thread is Boisy says it's just
too much work maintaining all these disk images (and it is, I have
seen the mountains of makefiles with my own eyes).  He needs to reduce
the number of images that he personally has been doing the work of
maintaining for all of our benefit.

Within 10 posts or some, someone just has to have every single
variation there is.  Can we reconsider this?  It doesn't solve the
problem at hand.  It's too much work for one guy to support every
possible configuration.

I see some possible solutions:

1.  Additional people skilled with *nix makefiles and OS-9 get
involved to help maintain all these disks
2.  We support only the most common configurations and provide
instructions on how those with other systems can adapt the images to
their systems.
3.  We leave it to each user to get into the CVS and make their own
disks (it's really not that hard guys).

Other solutions? Saying "I want this version" doesn't solve the problem at 
hand.

-Aaron





On Tue, Mar 30, 2010 at 1:46 PM, John W. Linville
<linville at tuxdriver.com> wrote:
> On Tue, Mar 30, 2010 at 01:31:50PM -0400, Bruce W. Calkins wrote:
>> And how difficult will it be for those with floppies to pull the
>> individual games out of the emulator "disk?"
>
> As with the suggestion about the 80track images for the OS, please
> preserve the capability to build "hardware compatible" disk images
> in the build scripts. :-)
>
> John
> --
> John W. Linville Someday the world will need a hero, and you
> linville at tuxdriver.com might be all we have. Be ready.
>
> --
> 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