[Coco] DECB development under OS9

[James Jones]

Library functions may use system calls, most notably stdio. Also, "cstart"
(the outer layer that does setup and then calls main, and cleans up after
it returns) will use system calls or call things using system calls--main()
expects to see stdin, stdout, and stderr FILE structures in place. You may
have to roll your own cstart; I forget the C standard nomenclature for an
environment that doesn't assume you have an OS to help out, but one of
those.

On Fri, May 11, 2018 at 10:14 PM, Dave Philipsen <dave at davebiz.com> wrote:

> Thanks for the comments guys.  Anyone care to comment upon whether an OS9
> C program with minimal system calls could theoretically be
> patched/converted to run under DECB?  I’m thinking it might even be able to
> be run unpatched if you simply created an add-on that serviced the SWI in
> DECB. Of course, there would be a lot of system calls that simply wouldn’t
> make sense under DECB but it would seem like the stdin/stdout stuff could
> be made to work among some others.
>
> Just an idea I was thinking of...
>
> Dave
>
> > On May 11, 2018, at 6:44 PM, L. Curtis Boyle <curtisboyle at sasktel.net>
> wrote:
> >
> > CocoSDC emulates the real thing, so I believe it will work fine with
> RSDOS as well (and Dave specifically asked about using it with CocoSDC). I
> think I actually tried it a long time ago too.
> >
> > L. Curtis Boyle
> > curtisboyle at sasktel.net
> >
> >
> >
> >> On May 11, 2018, at 5:40 PM, Bill Pierce via Coco <coco at maltedmedia.com>
> wrote:
> >>
> >> Curtis, RSDOS only works with real disks and emulations of the wd1773.
> It will not work with DW4 or HDB/RGB dos partitions/dsks. Robert Gault's
> "HRSDOS" will do all of them. It's what I based the MShell RSDOS read/write
> code on.
> >>
> >>
> >>
> >>
> >>
> >> Bill Pierce
> >> "Charlie stole the handle, and the train it won't stop going, no way to
> slow down!" - Ian Anderson - Jethro Tull
> >>
> >> My Music from the Tandy/Radio Shack Color Computer 2 & 3
> >> https://sites.google.com/site/dabarnstudio/ <https://sites.google.com/
> site/dabarnstudio/>
> >> Co-Contributor, Co-Editor for CocoPedia
> >> http://www.cocopedia.com/wiki/index.php/Main_Page <
> http://www.cocopedia.com/wiki/index.php/Main_Page>
> >>
> >> E-Mail: ooogalapasooo at aol.com <mailto:ooogalapasooo at aol.com>
> >>
> >>
> >>
> >>
> >>
> >> -----Original Message-----
> >> From: L. Curtis Boyle <curtisboyle at sasktel.net <mailto:
> curtisboyle at sasktel.net>>
> >> To: CoCoList for Color Computer Enthusiasts <coco at maltedmedia.com
> <mailto:coco at maltedmedia.com>>
> >> Sent: Fri, May 11, 2018 6:13 pm
> >> Subject: Re: [Coco] DECB development under OS9
> >>
> >> I think the RSDOS utility will do this already, so you could set that
> up in a script to copy to/from a DECB disk image directly.L. Curtis
> Boylecurtisboyle at sasktel.net> On May 11, 2018, at 4:02 PM, Dave Philipsen
> <dave at davebiz.com> wrote:> > I have a possible project that I'd like to
> get a little input on.  I would like to use NitrOS9 as my development
> platform for programs that will run under DECB.  The reason for this is
> that NitrOS9 is well suited in that it has plenty of disk space and several
> assembler options available.  It would be easy to include the headers
> inside of the source code for compatibility with the DECB LOADM format as
> I've already done this with a cross assembler under DOS/Windows.  I'm not
> really keen on the idea of having to develop on a PC, transfer the output
> file via drivewire to the CoCo, and test.> > I have a CoCo3 with 512K and I
> have CoCoSDC that has disk images for booting NitrOS9 as well as images for
> DECB.  What I was thinking is that I could write a utility program that
> runs under NitrOS9 that would allow me to copy files back and forth to one
> of the DECB disk images on the CoCoSDC. Maybe it has already been done.
> Has anyone ever attempted this?  If not, is there anyone who would want to
> give me a little advice on how, theoretically, it might be done?> > I see
> there is a low level driver for the cocosdc and I'm wondering how difficult
> it would be to mount a DECB disk image and access the image as another
> drive under NitrOS9.  I realize that because of the difference in disk
> format the drive would not be natively read/writeable from NitrOS9 but as
> long as all of the virtual sectors were accessible then I could write a
> program to access the data/programs in the DECB file system.  So I guess
> I'm asking whether it would be feasible to mount one or more DECB disk
> images on the CoCoSDC as virtual drives; /SD1, /SD2, etc.> > This would
> allow me to write a program under NitrOS9, assemble it, copy the DECB
> format binary to the correct DECB image on the CoCoSDC, then reboot the
> computer
> > a
> >> nd test the program out in DECB. Another idea I have which would be an
> add-on to this would be a way to actually compile a NitrOS9 C program and
> either trap or replace the system calls and have the program usable under
> DECB.  I know this is a bit of a stretch but it might be possible if only
> certain limited system calls were used from the C program.> > > > Dave> > >
> -- > Coco mailing list> Coco at maltedmedia.com <mailto:Coco at maltedmedia.com>>
> https://pairlist5.pair.net/mailman/listinfo/coco <
> https://pairlist5.pair.net/mailman/listinfo/coco>> -- Coco mailing
> listCoco at maltedmedia.comhttps <mailto:listCoco at maltedmedia.comhttps>://
> pairlist5.pair.net/mailman/listinfo/coco
> >>
> >> --
> >> Coco mailing list
> >> Coco at maltedmedia.com <mailto:Coco at maltedmedia.com>
> >> https://pairlist5.pair.net/mailman/listinfo/coco <
> 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
>