[Coco] CoCo Hardware License Re: eBay madness?

Sun May 8 23:55:07 EDT 2011

A wiki could be handy for collection various tips and tricks.

This was a cool idea but seems unmaintained:

http://www.cocopedia.com/wiki/index.php/Main_Page

The NitrOS9 wiki is quite good but specific to OS9 of course:

http://sourceforge.net/apps/mediawiki/nitros9/index.php?title=Main_Page

A general wiki for all things coco would be cool but would only be
valuable if the various coco experts out there contributed their
knowledge.  I suppose someone could try to glean nuggets from this
list, the archives do contain a goldmine but the mine is deep and dark
and the canary often doesn't look too well.

As for a "coco license"... as a ham I can assure you the primary
reason we have and want licensing is because radio is a hobby that
effects other people (wouldn't be too useful if it didn't).  the
graduated licensing system basically starts you off with a license
that only lets you potentially annoy people in your local area, then
you upgrade to a license that lets you annoy people over long
distances, and finally you can get a license to annoy internationally.
 Each requires significantly more effort than the previous, to filter
out those who either intentionally or unintentionally would cause
trouble to others.

 Since breaking your coco really doesn't effect anyone else, I'm not
sure a license is appropriate.  Now.. posting to the mailing list,
maybe thats a different story :)

2011/5/8 Luis Fernández <luis46coco at hotmail.com>:
>
> I agree with you
>
> I myself am an expert on some issues and other rookie
>
> What I'm determined to do is to sort the information as it is scattered
> in many place sand in the list are treated very specific points
>
> Novices can not post a lot and generally scary, because it novice,
> you make a mistake and posted beaten tracks, I remember a posting of mine
> about a prize won from the list, and it was one year old, lol
>
> and many other errors
>
>
> but I'm afraid to ask how much memory does my computer, do not you do not find like asking if I have 64 or 32k, lol
>
> The idea is to order the coconut things that can be used
>
> are scattered in hundreds of pages and not very coherent
>
> I'm trying to change that
>
>> CC: coco at maltedmedia.com
>> From: mike at bcmr3.net
>> Date: Sun, 8 May 2011 18:36:45 -0400
>> To: coco at maltedmedia.com
>> Subject: Re: [Coco] CoCo Hardware License Re: eBay madness?
>>
>> I'll take the test as soon as a good study guide is made available! The certification would have to be printed on a DMP, tractor feed of course. :)
>>
>> I'm one of those trying to learn more about the coco and ML programming. This list has been a great source of information and the general discussions have generally been enlightening. It's clear that we have a big collection of experts and the rest of us tend to lurk. There is a big divide between the skill sets. We all have limits on our time and schedules. You can't blame folks for asking for answers, and you can't blame others for growing weary if some of the questions. However, if you are weary, you can choose not to answer. If you're feeling generous, help out.
>>
>> I think many of us fantasize about some mass education project on the CoCo, but this isn't likely for previously stated reasons. We all do what we can.
>>
>> This list certainly has room for varying opinions, suggestions, and answers.
>>
>> Now, who will be my mentor?? :)
>>
>> Cheers,
>> -Mike
>>
>> On May 8, 2011, at 6:14 PM, Brian Blake <random.rodder at gmail.com> wrote:
>>
>> > Maybe I'm reading too much into this, but, it's either irony, coincidence,
>> > or your not so subtle way of telling me 'you shouldn't have opened the case
>> > in the first place' that your message came right after I posted a note on
>> > the list about the CoCo I'm currently working on.
>> >
>> > Anyway...
>> >
>> > So... what are you proposing? Coming up with a test a CoCo user should have
>> > to take prior to opening up a CoCo? Like schematic reading 101? Or soldering
>> > basics (yeah, it's not 'the bigger the blob, the better the job)?
>> >
>> > It's interesting how folks get a CoCo and find out there are problems with
>> > it, then ask for help with it due to unfamiliarity with the machine, or they
>> > really have no earthly idea of the problem and are hoping it's an easy fix.
>> > I thought that's what a hobbyist group was for - helping new and old members
>> > alike. As for other users, who have more than one CoCo, what's the problem
>> > with them using one to experiment with to try to learn more about how it
>> > works? Especially if they've fixed another part on the same machine before.
>> >
>> > As for setting 'guidelines' for someone before they take on a task on their
>> > beloved CoCo they themselves paid money for, I think that's one sure way to
>> > get people to leave the CoCo community. Most people here posting questions
>> > very willingly admit their limitations, and by trying to enforce a community
>> > edict on what they should and shouldn't do with the things they paid money
>> > for seems like an elitist slap in the face.
>> >
>> > I would think it's a foregone conclusion that anyone who's going to attempt
>> > a 6309 swap will not be using a hammer and chisel to remove the 6809. Nor is
>> > it necessary to use tin-snips when removing the four memory chips when doing
>> > a 512k upgrade. However, there's nothing wrong with an FAQ of various
>> > projects so someone knows what types of skills and tools to have on hand for
>> > a given project. What type of soldering/de-soldering tools, ESD protection,
>> > electronics vise, multimeter, 50 or 100MHz o'scope, etc... Have you ever
>> > soldered anything before? Resistors? Capacitors? IC socket? Can you tell the
>> > value of a resistor by it's color code? Do you know the difference between
>> > standard caps and electrolytic? Do you know what a base, emitter and
>> > collector is, and where they are most likely to be found? Now it's getting
>> > into basic electronics, but, where do you draw the line?
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> > On Sun, May 8, 2011 at 5:13 PM, Steve Bjork <6809er at srbsoftware.com> wrote:
>> >
>> >> You could always build your own digital to analog joystick interface for
>> >> less than $10.
>> >>
>> >> Yes, I know not everyone could build their own.  But maybe that should be
>> >> your test on your hardware skills?  I watch too many CoCo users open up a
>> >> CoCo and only to make things a lot worse.  Maybe you need a License before
>> >> you work on a CoCo?
>> >>
>> >> Hear me out.  HAMs are another hobbyist group (and FCC) that require a
>> >> license to get on the air.  They do this so everyone knows how share the air
>> >> waves without causing problems.  As part of this, you need the skills to
>> >> keep the equipment in tune and running well.
>> >>
>> >> Well, License idea maybe a bit too strong.  But we should come with a few
>> >> guidelines for our fellow CoCo users on what hardware skills are needed for
>> >> taking on a hardware task on our beloved Coco.
>> >>
>> >> After all, there are very few WORKING CoCos left out in the wild.
>> >>
>> >> Be it real or joking, let's hear your guidelines.
>> >>
>> >> Steve (Hi-Res Joystick Interface) Bjork
>> >>
>> >>
>> > --
>> > Ohioan by birth, Floridian by the grace of U-Haul and a bad economy...
>> >
>> > --
>> > 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
>
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco
>