[Coco] NitrOS9 Sources

[Bill Pierce]

I have no idea why that last message listed part of it twice LOL
AOL mail.. gotta love it

Bill P

Music from the Tandy/Radio Shack Color Computer 2 & 3
https://sites.google.com/site/dabarnstudio/
Bill Pierce
ooogalapasooo at aol.com




-----Original Message-----
From: Bill Pierce <ooogalapasooo at aol.com>
To: coco <coco at maltedmedia.com>
Sent: Mon, Mar 11, 2013 5:36 pm
Subject: Re: [Coco] NitrOS9 Sources



Bill,
On the NitrOS9 sources, the sources in the repo will NOT compile on a coco 
without a lot of modification. I have personally tried importing these sources 
to use various parts for various reasons. You may find a couple here and there 
that will assemble with a minimal amount of changes but for the most part, they 
are written for the cross-assembler. In the sources, there are conditionals for 
Coco 1, 2, & 3, Atari Libra09, Dragon 64 & Alpha and FPGA. And then there's the 
conditionals for all the different hardware setups.
 
To answer your questions on the Microware sources, you must search back throgh 
the message archives. This was discussed not too long ago and it was said that 
the machine the sources were on was basically destroyed.

On the NitrOS9 sources, the sources in the repo will NOT compile on a coco 
without a lot of modification. I have personally tried importing these sources 
to use various parts for various reasons. You may find a couple here and there 
that will assemble with a minimal amount of changes but for the most part, they 
are written for the cross-assembler. In the sources, there are conditionals for 
Coco 1, 2, & 3, Atari Libra09, Dragon 64 & Alpha and FPGA. And then there's the 
conditionals for all the different hardware setups.
 
To answer your questions on the Microware sources, you must search back throgh 
the message archives. This was discussed not too long ago and it was said that 
the machine the sources were on was basically destroyed.
As for Microware, they are well aware of the NitrOS9 repo.
As I said, search the back message database and you'll see all the info on 
Microware/RadiSys/RealTimeSystems.
Just search for the subject "os9 has a new owner"
Matter of fact, here's a link to the view the thread

http://comments.gmane.org/gmane.comp.hardware.tandy.coco/64839

This may giveyou some idea what's going on
Bill P

Music from the Tandy/Radio Shack Color Computer 2 & 3
https://sites.google.com/site/dabarnstudio/
Bill Pierce
ooogalapasooo at aol.com




-----Original Message-----
From: Bill Gunshannon <billg999 at cs.uofs.edu>
To: CoCoList for Color Computer Enthusiasts <coco at maltedmedia.com>
Sent: Mon, Mar 11, 2013 4:56 pm
Subject: Re: [Coco] NitrOS9 Sources



>
> Bill,
> The answer your question on why all the NitrOS-9 code is in assembler is a
> simple one. There is no OS-9 C cross compler. There's been several
> attempts at it, but the best was (I think) a flaky RSDOS (read non-OS-9,
> non-position independant).

But there is the OS9 C Compiler.

>                            Also, another reason is that most of the
> original OS-9 modules were written in asm. These were disassembled to get
> the sources as the original sources are assumed to be non-existant.

Doesn't that make this a derivitive of OS9 and therefore not free?

And why are the original sources thought to be non-existant?  Did
MicroWare actually say that before their demise?  There were other
derived products like CD-RTOS that had to have copies of the sources.
Copies must exist somewhere.

> Disassembling a program written in C is a nightmare. I will personall
> testify to that.

I've never tried it but I can imagine it is pretty much impossible.
Even disassembling assembler is often more a task than most would think.

> I too would love to see some of this code in C. But in the long run, using
> assembly makes for the fastest, most efficiant code anyway.

I figured efficiency came into the equation somewhere.  :-)

>                                                            If you notice,
> any program included in the NitrOS-9 repository that was originally
> written in C is either copied directly to the disk (compiled) or broken
> down into "FCB"s and "FDB"s of the binary program dump and assembled as a
> module like a BASIC program pokes data into memroy to make a machine
> language program.

Yeah, I really don't understand the point of this last one.  If all
you have are binaries turning them into meaningless sources seems
rather counterproductive.

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

 

--
Coco mailing list
Coco at maltedmedia.com
http://five.pairlist.net/mailman/listinfo/coco