[Coco] lwtools assembler difference (@Boisy)

Thu Sep 3 11:40:16 EDT 2015

I'm sorry if this email is a duplicate, but it never echoed back to me, so I assume there was an error in sending it the first time. Again, I appologize for the duplicate..

Boisy, yes, I understand what you are saying. Personally I would've been glad to help with the repo but at the time had very little knowledge of how it worked. Since then, I have learned much!

I was in no way implying anything against you in saying it was "abandoned"... maybe just a bad choice of words, but for about a year, the repo was in a state of "no activity" and would not compile (3.2.9). At the time, you were dedicating your time to other projects and had no time to work on it (we all have a life) and no one else seemed to understand the "mercurial" way of doing things, nor did anyone have LWTools experience. It seemed to be "abandoned".

 The only thing that keeps me from involving myself at the moment is my lack of knowledge of how the OS9 system internals connect (but I'm learning). I am not much of a "systems programmer", my niche seems to be more in C and building GUI systems for NitrOS9.

 But I am making a lot of headway in learning how the makefiles work and how to manipulate them to do custon builds. In my local copy of the repo, I have succeded in making custom disks and VHDs (!) for various projects and I'm currently working on a way to produce "hybrid" VHDs (RSDOS/NitrOS9) straight from the repo makefiles (90% successful). I may not know what makes the NitrOS9 system tick (yet), but I can now put the parts together and make them work for me :-)
 I'm understanding more every day of how the makefiles work and how to make them work for me.
 I'm building custom disks and VHDs for Vcc, Mess, XRoar, DW4, Becker, Coco 3, and HDBDOS. Basically "turnkey" systems for the emulators.

 I was "beta testing" every single change Tormod made to the repo and testing every disk to make sure they ran and reporting errors.. so I did take a (very small) part in trying to help in what little way that I could.

 I appologize if I seemed to be excluding you as it was your hard work that got the actual source code in the state it is in... best build ever! I actually noticed what you are referring to when I read the post "echo" after I sent it and wished I had worded it differently.

 So, in closing... I would like to personally thank Boisy for his YEARS of dedication to NitrOS9 and congradulate him on the best release we've ever had. Version 3.3.0 ROCKS!!

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: Boisy G. Pitre <coco at toughmac.com>
To: CoCoList for Color Computer Enthusiasts <coco at maltedmedia.com>
Sent: Wed, Sep 2, 2015 9:15 pm
Subject: Re: [Coco] lwtools assembler difference

Just a follow-up, I mistakenly referred to Tormod as Torsten in my email below.
Apologies. I meant Tormod.

> On Sep 2, 2015, at 7:45 PM, Boisy G. Pitre
<coco at toughmac.com> wrote:
> 
> 
>> On Sep 2, 2015, at 4:58 PM, Bill Pierce via
Coco <coco at maltedmedia.com> wrote:
>> 
>> Dave, you can thank Tormod Volden for
the condition of the repo. He came into the picture with the repo in an absolute
mess when it was all but abandoned in the midst of the switch from ToolShed to
LWTools and SVC to Mercurial and massaged it into one of the best running
releases of OS9/NitrOS9 the Coco has ever seen.
>> And thank William Astle for
the work on LWTools. LWTools has made building the repo a breeze…
> 
> Bill,
>

> Torsten certainly deserves considerable praise for picking up the pieces, and
in no way do I intend to diminish his contributions with this post. However, I
have to take issue with the way you worded your comments above.
> 
> I had been
asking for some time for someone in the CoCo community to take over the project.
Other than Robert Gault and one or two other individuals who actually made
contributions (and I thank them for that), no one bothered to even help, let
alone step up to a leadership role. It took someone from the outside (Torsten,
who has certainly earned his stripes) to come in and pick up the mantle of
leadership on the project.
> 
> Think about that for a minute… no one
ORGANICALLY from the community came forward to lead the project.
> 
> Just let
that sink in.
> 
> 
> -- 
> 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