[Coco] OS-9 Library generation

Wed May 13 01:20:04 EDT 2015

First, I apologize to the group for this post, but it must be done. Fire me, ban me, or put me up on a pedestle.

Stephen, let me make myself perfectly clear I AM NOT TRYING TO MAKE ANYTHING STANDARD!!!
Quit reading things into my posts that are NOT said. you asked what compiler I was using so I told you, now you want to make an issue out of what I KNOW works for me... I do not advise people to use my compiler system, I just let them know it's there if they want to try it. As for you finding ANYTHING on your disks... GOOD LUCK with that! I could care less.

Stephen, it never fails, when someone mentions something about NitrOS9 and you make some form of derogatory comments and start calling names. I for one am SICK and TIRED of seeing it. The only person who screwed up YOUR OS9 is YOU!
NO ONE EVER told you to change a thing you were or are(??) using. If you changed something, then only you did that. NitrOS9 is NOT OS9 of 1989 and NEVER proposed to be. It was born of people wanting a faster, more stable version of OS9, and it has FAR surpassed it's original goal, regardless of your opinion of it. If you were happy with 1989 OS9 THEN USE IT. All the patches are on RTSI.

I could CARE LESS of your opinion of the NitrOS9 development or the people who do so. Until you can contribute with more than bitching and moaning about what other people are working hard to do, then I think it's best to keep your opinions to yourself. For the most part, they are unappreciated and unwanted.

You no longer even use OS9 and it's been how many years since you booted up a new version of NitrOS9?..... But yet you seem to know every bug that's there. I use NitrOS9 EVERY DAY and compile software EVERY DAY, and build a fresh copy of NitrOS9 from the repository at least monthly, and feel your antiquated source of knowledge to be as useless as a 1939 set of Compton's encyclopedias... Old, outdated and full of rumor and unproven theory.

There's a reason you get banned from forums and people lock you out of their FTPs, and you continue to prove it just about every time you post something.

BTW... "merge" was a STANDARD command on every MW OS9 release  including Level 1. If it's not on your disks, then you didnt' copy it from the masters. "Cat" was available in several forms from both Delphi and CIS as well as on the OS9UG disks, it was on most BBSs and is currently on RTSI. Cat was a standard on no-coco OS9 as it's a port of a Unix command. There are even RSDOS BASIC versions of Cat that have been around since the beginning.

Stephen, Get a life, but stay the hell out of mine and my posts!

"Stephen H. Fisher" now Ignored <click><bam><done> (finally!).

Again, I apologize to the group for this post, but I think I speak for a few if not many of us. If not? So be it. I would've sent it to Stephen private, but he would've re-posted it publically here and/or on facebook like he does everything else. So I posted it publically so I know it is in full content and not in part and taken out of context.

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/
Co-Contributor, Co-Editor for CocoPedia
http://www.cocopedia.com/wiki/index.php/Main_Page
Global Moderator for TRS-80/Tandy Color Computer Forums
http://www.tandycoco.com/forum/

E-Mail: ooogalapasooo at aol.com

-----Original Message-----
From: Stephen H. Fischer <SFischer1 at Mindspring.com>
To: CoCoList for Color Computer Enthusiasts <coco at maltedmedia.com>
Sent: Wed, May 13, 2015 12:13 am
Subject: Re: [Coco] OS-9 Library generation

I do not see either "merge" or "cat" in CMDS for my last OS-9 Level-II system. 
(1/11/1993)

OS9GEN may have been the only option back in 1986 but as you say a
40 mm cannon for very simple merges. 

Not everything on CI$ made it to Delphi.
The OS-9 Level-II new files were few and far between at the end when the Delphi
OS-9 forum was heavily dominated by the OSK folks. (Was CI$
also?)
----------------------------------- 

I would like to hear Willard's
comments about what you want to make standard. 

I was trying to make it easier
for the first time "C" programmer and present it similar to what Tandy offered.
I hope you will add your "new" (Very few changes / additions) to "my" C Compiler
project as a .dsk file.

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

One of my goals
that the inverse appears to be the dominate goal of others is to make it as
simple as possible for new users.

Yes you may have a fast great system but
think about the new user who opens up the OS-9 Manual and the "C" Compiler disk
and is told about your system and they do not match at all.

Give up, perhaps
CoCo OS-9 is not the best option for
them.

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

I have been thinking where OS-9
people could ask questions and get help.

YES, OS-9. I have an unproven theory
that there are very many out there.

1) [CoCo], too much NitrOS-9 dominated.

2) http://www.tandycoco.com/forum/ also too much NitrOS-9 dominated.

3)
Facebook, too many pictures of what was just found. Way too much traffic and not
archived which was just now a discussion on Facebook.

4) Another Forum that was
just started? Needs to be looked at to see if that might be the way to
go.

Problems, cutting the [CoConut] pie into more pieces.

I just can't handle
any more projects.

SHF

----- Original Message ----- 
From: "Bill Pierce via
Coco" <coco at maltedmedia.com>
To: <coco at maltedmedia.com>
Cc: "Bill Pierce"
<ooogalapasooo at aol.com>
Sent: Tuesday, May 12, 2015 8:19 PM
Subject: Re: [Coco]
OS-9 Library generation

...
> 
> The components to my current C compiler are
listed and well documented on my website on the "MJK C Compiler System" page.
>
I have currently discontinued use of c.prep19b, and reverted back to the old MW
c.prep because c.prep19b pukes on very long lines in the sources and allocated
memory was cut to make room for features (it's in the docs). The changes made in
my C system are as follows:
> 
...
> 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/
> Co-Contributor, Co-Editor for
CocoPedia
> http://www.cocopedia.com/wiki/index.php/Main_Page
> Global Moderator
for TRS-80/Tandy Color Computer Forums
> http://www.tandycoco.com/forum/
> 
>
E-Mail: ooogalapasooo at aol.com
> 
> 
> 
> 
> 
> 
> -----Original Message-----
>
From: Stephen H. Fischer <SFischer1 at Mindspring.com>
> To: CoCoList for Color
Computer Enthusiasts <coco at maltedmedia.com>
> Sent: Tue, May 12, 2015 9:52 pm
>
Subject: Re: [Coco] OS-9 Library generation
> 
> 
> You have the 40mm cannon
pointed in the wrong direction.
> 
> The routine I used
> to split the library I
think also wrote a text file with the names of the
> modules in the library.
>

> Facing doing a merge of 40 - 70 modules and perhaps
> doing it with several
merges hopefully using a ShellPlus script was something
> that could not be done
successfully even with a list of the modules in the
> proper order. That was the
40mm cannon pointing at the project.
> 
> As I was
> building System disks using
OS9GEN and could edit text files at that point the
> OS9GEN solution presented
itself and worked quite nicely.
> 
> All I needed to do
> was to change one
number in the "abort" module so the entire program I was
> trying to fix was
included in the "Core" dump. 
> 
> The bug made the "core" dump
> short by one
(1).  Thus constant problems looking at the "Core" dump and the
> C.Link
generated loader map. (WHAT? C.Link generates loader maps!)
> 
> I doubt if
>
you care but I have attached Abort.zip to this e-mail. Dated 7/1/1986.
> 
> I
am
> unsure if the fix is in this file but every library in use "may" have this
bug
> except the ones I made and used.
> 
> ------------------------
> 
> I do
not think
> "Make" was on my radar at that point but if the entire library
needed to be
> assembled / compiled Make would be the only way to go. I started
using "Make" as
> soon as I saw it. 
> 
> It's the use of OS9GEN with the file
list in a simple text
> file was what I wanted to add. 
> 
>
------------------------
> 
> The second phase
> of the C Complier project that
I never finished was for lack of directions from
> any direction for what to
include.
> 
> You perhaps are doing that phase, one that
> needs to be done.
There are way too many versions of libs available and no clear
> instructions.
>

> Willard just listed all the libraries available and I did not
> figure out a
plan.
> 
> http://www.tandycoco.com/forum/viewtopic.php?p=528#p528
> 
> 
>
Adding your final .dsk(s) and how you chose what to include would make the
>
project complete.
> 
> SHF
> 
> ----- Original Message ----- 
> From: "Bill
Pierce
> via Coco" <coco at maltedmedia.com>
> To: <coco at maltedmedia.com>
> Cc:
"Bill Pierce"
> <ooogalapasooo at aol.com>
> Sent: Monday, May 11, 2015 11:28 PM
>
Subject: Re:
> [Coco] OS-9 Library generation
> 
> 
>> Stephen, I using sources
to make "new"
> libraries, not fix old ones. So your 40mm cannon to kill a mouse
technique is
> useless. A makefile is much simpler and more efficient.
>> 
>>

>> 
>> 
>> 
>>
> Bill Pierce

-- 
Coco mailing
list
Coco at maltedmedia.com
https://pairlist5.pair.net/mailman/listinfo/coco