Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!uunet!seismo!mcnc!rutgers!labrea!decwrl!pyramid!voder!wlbr!pete From: pete@wlbr.EATON.COM (Pete Lyall) Newsgroups: comp.sys.m6809 Subject: Re: os9 level II development kit Message-ID: <1099@wlbr.EATON.COM> Date: Mon, 27-Jul-87 12:10:07 EDT Article-I.D.: wlbr.1099 Posted: Mon Jul 27 12:10:07 1987 Date-Received: Tue, 28-Jul-87 05:43:23 EDT References: <26@abvax.icd.ab.com> Reply-To: pete@wlbr.UUCP (0000-Pete Lyall) Organization: Eaton IMS, Westlake Village, CA Lines: 39 Keywords: os9 development C In article <26@abvax.icd.ab.com> harmon@abvax.icd.ab.com (Larry Harmon) writes: > > Does anyone know if Tandy is still planning to release a >"development kit" for os9 level II in the coco 3? If so when? >I have been using the old C compiler, which can run four times faster under >level II, but I sure wish new definition header files and i/o function >libraries were available. A vi type editor supporting 80 column and >ed functionality would be a blessing too. I have been using "tsedit" >in a 32 column window to edit and compiling in another 80 column window. The >ability to look at compiler errors then switch back to the editor is >great, but having to use the old 32 column screen is a hinderance. I think >the coco3 could be a usefull low cost developnemt machine if the right tools >could be obtained. Does anyone have a good development setup they could >describe? > Yes - to my knowledge, there will still be a developer's kit. A few nice surprises in it too... among them, a 6809 version of 'Make', and the RMA assembler as opposed to the ASM assembler. Also, DEFS files and '.h' files, although I understand that *some* DEFS files have been mistakenly omitted. I'm sure there will be a way to obtain them. Re: an 80 coulmn 'vi' type editor, Bob Santy has just posted patches to the OS9 Forum for the Tsedit package to use 80 columns, etc. You must also have the utility Ipatch (Install-Patch - also written by Santy, as well as MakPatch form a very nice patch writer/applier toolkit.). If we (comp.sys.m6809) can agree on a method for posting, I will happily post Ipatch/Makpatch and the Tsedit patches. I should bring up the fact that we have been using a utility called "ar" for well over a year now, and it has become our standard method of packaging and compressing files. It is similar in *concept* to MS-DOS's ARC. I would prefer the following scenario: a) Post a UUENCODED version of 'ar' to the net. With docs, of course. b) Post UUENCODED 'ar' formatted files for all future submissions. For the curious, yes - I have source to 'ar', and I believe am free to distribute it.