From rietveldh at hotmail.com Mon Aug 2 12:04:12 2021 From: rietveldh at hotmail.com (rietveld rietveld) Date: Mon, 2 Aug 2021 16:04:12 +0000 Subject: [Coco] Modded MPI help pls Message-ID: Has anyone seen this mod before? Does anyone know what it does? https://i.imgur.com/u3749ui.jpg 2 toggle switches marked 2 and 3 Sent from my BlackBerry ? the most secure mobile device From phxmark at yahoo.com Mon Aug 2 11:56:40 2021 From: phxmark at yahoo.com (Mark Schoenberger) Date: Mon, 2 Aug 2021 15:56:40 +0000 (UTC) Subject: [Coco] Coco Stuff Giveaway, Phoenix, AZ only In-Reply-To: <1b3a0c95-6207-a5dc-94fe-a6879bac42e6@markoverholser.com> References: <1788761421.546763.1627058011653.ref@mail.yahoo.com> <1788761421.546763.1627058011653@mail.yahoo.com> <1b3a0c95-6207-a5dc-94fe-a6879bac42e6@markoverholser.com> Message-ID: <2129677012.2341099.1627919800355@mail.yahoo.com> Someone already picked it all up. On Thursday, July 29, 2021, 8:19:49 PM MST, Mark D. Overholser wrote: On 7/23/21 9:33 AM, Mark Schoenberger via Coco wrote: > If there is anyone in the Phoenix Arizona area interested in some > FREE stuff, contact me. I have an MC-10 with service manual and three > 16k expansion cartridges, an XPad with service manual, a CGP-115 > printer, an Amiga 500 computer, and a Commodore 1084 RGB/Composite > monitor. Please message me here if interested. PICK UP ONLY. Stuff is > too much to ship. Regards,Mark Schonberger > Do you have anything left??? MarkO -- Coco mailing list Coco at maltedmedia.com https://pairlist5.pair.net/mailman/listinfo/coco From badfrog at gmail.com Thu Aug 5 15:13:59 2021 From: badfrog at gmail.com (Sean) Date: Thu, 5 Aug 2021 14:13:59 -0500 Subject: [Coco] Modded MPI help pls In-Reply-To: References: Message-ID: Might be a mod to switch between the Coco2 and Coco3 PAL chip? On Mon, Aug 2, 2021 at 11:04 AM rietveld rietveld wrote: > Has anyone seen this mod before? > Does anyone know what it does? > > https://i.imgur.com/u3749ui.jpg > > 2 toggle switches marked 2 and 3 > > Sent from my BlackBerry ? the most secure mobile device > > -- > Coco mailing list > Coco at maltedmedia.com > https://pairlist5.pair.net/mailman/listinfo/coco > From rietveldh at hotmail.com Fri Aug 6 05:56:42 2021 From: rietveldh at hotmail.com (rietveld rietveld) Date: Fri, 6 Aug 2021 05:56:42 -0400 Subject: [Coco] Modded MPI help pls In-Reply-To: References: Message-ID: That seems to be what the mod is. I took a closer look and the new PAL is piggy backing the original one. The setup does not seem to be working so i will remove it and replace the piggy back with a single new PAL I don t know why someone would need both PALs > > On Aug 5, 2021 at 3:14 PM, Sean wrote: > > > Might be a mod to switch between the Coco2 and Coco3 PAL chip? > > On Mon, Aug 2, 2021 at 11:04 AM rietveld rietveld > wrote: > > > Has anyone seen this mod before? > > Does anyone know what it does? > > > > https://i.imgur.com/u3749ui.jpg > > > > 2 toggle switches marked 2 and 3 > > > > Sent from my BlackBerry ? the most secure mobile device > > > > -- > > 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 > From chawks at dls.net Fri Aug 6 10:15:45 2021 From: chawks at dls.net (Christopher R. Hawks) Date: Fri, 6 Aug 2021 09:15:45 -0500 Subject: [Coco] Modded MPI help pls In-Reply-To: References: Message-ID: <20210806091545.30473752@Manfred.lan> On Fri, 6 Aug 2021 05:56:42 -0400 rietveld rietveld wrote: > > > > That seems to be what the mod is. I took a closer look and the new > PAL is piggy backing the original one. > > > The setup does not seem to be working so i will remove it and replace > the piggy back with a single new PAL > > > I don t know why someone would need both PALs > > Maybe they had both Coco 3 and Coco 1/2 computers, and some of their Coco 1/2 hardware used addresses that the new pal locked out. > > > > > > On Aug 5, 2021 at 3:14 PM, Sean wrote: > > > > > > Might be a mod to switch between the Coco2 and Coco3 PAL chip? > > > > On Mon, Aug 2, 2021 at 11:04 AM rietveld rietveld > > wrote: > > > > > Has anyone seen this mod before? > > > Does anyone know what it does? > > > > > > https://i.imgur.com/u3749ui.jpg > > > > > > 2 toggle switches marked 2 and 3 > > > > > > Sent from my BlackBerry ? the most secure mobile device > > > > > > -- > > > 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 > > > > Christopher R. Hawks HAWKSoft -- Think it over, think it under . ---Winnie Ther Pooh ---------------------------------------- \ ^__^ \ (oo)\_______ (__)\ )\/\ ||----w | || || From coco at jechar.ca Fri Aug 6 11:15:12 2021 From: coco at jechar.ca (coco at jechar.ca) Date: Fri, 06 Aug 2021 11:15:12 -0400 Subject: [Coco] Canadian CoCoFest? In-Reply-To: <5CF9C7D0-69A3-4D97-B6BB-31FA27EF3A1F@sasktel.net> References: <34AD028F-498E-4D4A-B3B4-24B7C075AE57@pobox.com> <5CF9C7D0-69A3-4D97-B6BB-31FA27EF3A1F@sasktel.net> Message-ID: When I first started with a Coco in 1990 there were about four coco clubs within an hour of Toronto a couple of years later only the Toronto club and that closed up in the late 90's. It got absorbed into a Retro Club which basically became a Commodore club, About 97 or 98 lasted a while but I don't know how long. In any case they soon went back to being Commodore only and they are still around https://www.tpug.ca/ ( I had no Idea they were still around until I goggled it as I had not heard anything about them since early 2000's ) Charlie On 2021-07-27 12:13, L. Curtis Boyle wrote: > Not that I am aware of. Local club meetings in the early-mid 1980?s, > but that?s it. > > L. Curtis Boyle > curtisboyle at sasktel.net > > > >> On Jul 27, 2021, at 8:59 AM, Allen Huffman wrote: >> >>> On Jul 27, 2021, at 9:47 AM, EDDY SZCZERBINSKI >>> wrote: >>> >>> Well, let's have CoCoFest in Canada then ! >> >> Has there ever been a Canadian CoCo show? I remember when we reached >> the Canadian tipping point and started playing the Canadian national >> anthem at Fests. >> >> -- >> Coco mailing list >> Coco at maltedmedia.com >> https://pairlist5.pair.net/mailman/listinfo/coco >> From ogsteviestrow at gmail.com Sat Aug 7 09:54:20 2021 From: ogsteviestrow at gmail.com (Steve Strowbridge) Date: Sat, 7 Aug 2021 09:54:20 -0400 Subject: [Coco] Live Dragon Special August 14th Message-ID: The Dragon community is taking over CoCoTALK! for the first ever live DragonTALK! August 14th, 2021 at 1 PM EDT 6PM UK time. Check out this YouTube promo: https://youtu.be/JmP8xIKQ05I This is probably the first time a completely Dragon centric gathering, recording or broadcast has taken place covering the past, present, and future of this CoCo cousin. Schedule to appear: - Chris Poacher Microdeal Collector and runs MicroDeal Facebook group - Ciaran Anscomb Author of Xroar, Dunjunz, Blockdown - Duncan Smeed Co-author of ?Inside the Dragon? with Ian Sommerville - Henry Reitveld Owner of NTSC North American TANO Dragon - John Vella - John Whitworth Added MSX2+ support to MAME for the Dragon - Nigel Barnes MAME developer for UK/EU 8-bit systems - Pere Serrat Ported AGD engine from Spectrum, converting 200+ games. Author of MSX2+ demo software, The Hobbit. Extra game mention for Dark Pit for younger kids - Richard Harding One of the Admins of the Facebook Dragon group; Also the one making the fancy USB keyboard - Roberto Fernandez Add PAL color blending to Dragon emulation in MAME - Simon Waterfield Twitch streamer of Dragon games - Steve Bamford Currently working on Circe?s Island game (which Includes sound chip support), Flagon Bird - Stewart Orchard Author of Balldozer, Revenge of the Alien Bongo Beast (ROTABB), Return of the The Beast - Tim Gilberts Adventure games, and background of why The Quill never got ported And possibly more! If you want to know more about the Dragon, the community, the new hardware and software, emulation, and more, this is the show to watch please join us. Steve ?Stevie Strow? Strowbridge Retro nerd, vintage computing enthusiasts, self proclaimed CoCo ?Nut? ogStevieStrow at gmail.com primary email address http://ogsteviestrow.com web site http://cocotalk.live CoCoTALK! the world's leading live CoCo talk show http://imacoconut.com for all things CoCo related From ogsteviestrow at gmail.com Sat Aug 7 09:56:55 2021 From: ogsteviestrow at gmail.com (Steve Strowbridge) Date: Sat, 7 Aug 2021 09:56:55 -0400 Subject: [Coco] Maybe we should RE-THINK CoCo Fest for this year??? In-Reply-To: References: <2089284188.1015040.1627298236600.ref@mail.yahoo.com> <2089284188.1015040.1627298236600@mail.yahoo.com> <006301d7825f$990effc0$cb2cff40$@bds-soft.com> Message-ID: Regards to a possible "virtual" CoCoFEST! We did a fairly decent one last year, and while I'd much prefer for an in-person event this year, if that's not an option, plan B will be to have another. For reference, last year's virtual FEST! on YouTube: https://youtu.be/t4qkRI1JyqU Steve ?Stevie Strow? Strowbridge Retro nerd, vintage computing enthusiasts, self proclaimed CoCo ?Nut? ogStevieStrow at gmail.com primary email address http://ogsteviestrow.com web site http://cocotalk.live CoCoTALK! the world's leading live CoCo talk show http://imacoconut.com for all things CoCo related On Mon, Jul 26, 2021 at 4:55 PM John Mautz wrote: > If you want to go virtual.... reach out to the Kanasfest team. They just > finished their second year of virtual Apple II conference. I?m sure they > would tell you the ins and outs of what they did to see if it would work > for you. > > John. > > On Mon, Jul 26, 2021 at 1:48 PM M. David Johnson wrote: > > > It would seem to me that whether or not someone is going to be able to > > attend CoCoFest (and the reasons why or why not) would indeed be on > topic. > > Am I missing something here? > > > > -- > > M. David Johnson > > mdj at bds-soft.com > > > > > > > > -----Original Message----- > > From: Coco [mailto:coco-bounces at maltedmedia.com] On Behalf Of Dennis > > Bathory-Kitsz > > Sent: Monday, July 26, 2021 3:45 PM > > To: CoCoList for Color Computer Enthusiasts > > Subject: Re: [Coco] Maybe we should RE-THINK CoCo Fest for this year??? > > > > Hi all, > > > > Please keep posts on topic. I know this one riled some of you (I've > > heard off-list) and I know there are a lot of folks whose politics don't > > align and find anything Covid-related to be political. > > > > This advice from your left-wing admin goes for everyone. Hey, even some > > of the sigs are political and off-topic. > > > > So let's all chill and keep the politics elsewhere. > > > > Thanks, > > Dennis > > > > > > > > On 2021-07-26 07:17, Joe Schutts via Coco wrote: > > > Hi Everyone, > > > I honestly wish I had better news about the border closure between > > > Canada and the US, but I don't. And I know everyone is sick to death > > > hearing about Covid, but this is something we'll all have to live with > > > for the foreseeable future... > > > > > > -- > > 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 > > > -- > Sent from Gmail Mobile > > -- > Coco mailing list > Coco at maltedmedia.com > https://pairlist5.pair.net/mailman/listinfo/coco > From alsplace at pobox.com Sat Aug 7 13:47:11 2021 From: alsplace at pobox.com (Allen Huffman) Date: Sat, 7 Aug 2021 12:47:11 -0500 Subject: [Coco] Maybe we should RE-THINK CoCo Fest for this year??? In-Reply-To: References: Message-ID: On Aug 7, 2021, at 8:57 AM, Steve Strowbridge wrote: > > Regards to a possible "virtual" CoCoFEST! We did a fairly decent one last > year I greatly enjoyed the schedule of presentations from this video stream. Predicting the future is never an easy task, so having a fallback plan in case Tandy Assembly or CoCoFEST cannot happen is a great thing. From rietveldh at hotmail.com Sun Aug 8 21:56:01 2021 From: rietveldh at hotmail.com (rietveld rietveld) Date: Mon, 9 Aug 2021 01:56:01 +0000 Subject: [Coco] Modded MPI update Message-ID: Earlier in the week I posted pics of a MPI I bought that had a new PAL piggybacked onto the original old one. The whole mess of wires looked cool but did not work anymore. I removed all of the jumper wires , pulled the doubled up chip, and replaced the PAL with a new CLOUD9 upgrade. The MPI works perfectly now Big thanks to Neil (from the CoCo crew podcast) for meeting up with me in Niagara Falls and giving me the upgraded PAL for free I love the support this community offers Sent from my BlackBerry ? the most secure mobile device From kevin.phillipson at gmail.com Mon Aug 9 16:15:32 2021 From: kevin.phillipson at gmail.com (Kevin Phillipson) Date: Mon, 9 Aug 2021 16:15:32 -0400 Subject: [Coco] Turbo9 - Pipelined 6809 update video Message-ID: Hi everyone. Just want to let you guys know we released an update video on the progress of our pipelined 6809 microprocessor core project - the Turbo9. It's now part of our master theses for graduate school. This video mostly covered the verification and toolkit that we have developed. Also we give the CoCo community a shoutout on the last slide! Thank you for your support! https://www.youtube.com/watch?v=eTlfH86KUog Looking forward to your feedback! Kevin & Michael From mheermance at gmail.com Mon Aug 9 19:28:22 2021 From: mheermance at gmail.com (Martin Heermance) Date: Mon, 9 Aug 2021 19:28:22 -0400 Subject: [Coco] Turbo9 - Pipelined 6809 update video In-Reply-To: References: Message-ID: I watched part of it and it was interesting. I plan to watch the rest later. On Mon, Aug 9, 2021, 4:15 PM Kevin Phillipson wrote: > Hi everyone. Just want to let you guys know we released an update video on > the progress of our pipelined 6809 microprocessor core project - the > Turbo9. It's now part of our master theses for graduate school. This video > mostly covered the verification and toolkit that we have developed. Also we > give the CoCo community a shoutout on the last slide! Thank you for your > support! > > https://www.youtube.com/watch?v=eTlfH86KUog > > Looking forward to your feedback! > Kevin & Michael > > -- > Coco mailing list > Coco at maltedmedia.com > https://pairlist5.pair.net/mailman/listinfo/coco > From mmarlette at frontiernet.net Mon Aug 9 20:22:02 2021 From: mmarlette at frontiernet.net (Mark Marlette) Date: Tue, 10 Aug 2021 00:22:02 +0000 (UTC) Subject: [Coco] Turbo9 - Pipelined 6809 update video In-Reply-To: References: Message-ID: <2102955782.449916.1628554922696@mail.yahoo.com> Kevin and Michael, Just finished watching the complete video. VERY COOL work!!! Congrats on your progress and look forward to future updates! Regards, Mark Marlette http://www.cloud9tech.com mark at cloud9tech.com mark at gamecamaddict.com On Monday, August 9, 2021, 03:15:49 PM CDT, Kevin Phillipson wrote: Hi everyone. Just want to let you guys know we released an update video on the progress of our pipelined 6809 microprocessor core project - the Turbo9. It's now part of our master theses for graduate school. This video mostly covered the verification and toolkit that we have developed. Also we give the CoCo community a shoutout on the last slide! Thank you for your support! https://www.youtube.com/watch?v=eTlfH86KUog Looking forward to your feedback! Kevin & Michael -- Coco mailing list Coco at maltedmedia.com https://pairlist5.pair.net/mailman/listinfo/coco From tonym at compusource.net Mon Aug 9 21:14:40 2021 From: tonym at compusource.net (Tony M) Date: Tue, 10 Aug 2021 01:14:40 +0000 Subject: [Coco] Turbo9 - Pipelined 6809 update video In-Reply-To: <2102955782.449916.1628554922696@mail.yahoo.com> References: , <2102955782.449916.1628554922696@mail.yahoo.com> Message-ID: Excellent work! And as an aside, same place my youngest got his Bachelor's in EE from in '17!! Tony ________________________________ From: Coco on behalf of Mark Marlette Sent: Monday, August 9, 2021 8:22 PM To: CoCoList for Color Computer Enthusiasts Subject: Re: [Coco] Turbo9 - Pipelined 6809 update video Kevin and Michael, Just finished watching the complete video. VERY COOL work!!! Congrats on your progress and look forward to future updates! Regards, Mark Marlette http://www.cloud9tech.com mark at cloud9tech.com mark at gamecamaddict.com On Monday, August 9, 2021, 03:15:49 PM CDT, Kevin Phillipson wrote: Hi everyone. Just want to let you guys know we released an update video on the progress of our pipelined 6809 microprocessor core project - the Turbo9. It's now part of our master theses for graduate school. This video mostly covered the verification and toolkit that we have developed. Also we give the CoCo community a shoutout on the last slide! Thank you for your support! https://www.youtube.com/watch?v=eTlfH86KUog Looking forward to your feedback! Kevin & Michael -- 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 From jrosslist at outlook.com Wed Aug 11 01:15:38 2021 From: jrosslist at outlook.com (James Ross) Date: Wed, 11 Aug 2021 05:15:38 +0000 Subject: [Coco] Turbo9 - Pipelined 6809 update video In-Reply-To: References: Message-ID: Wow, this is extremely cool! Definitely a worthy project for a master?s thesis! The fact that it is open-source is icing on the cake. Super advanced but educational for those who want to learn HDL/Verilog, pipeline, and microcode architectures. A 100mhz NitrOS9 version running this CPU would be wicked fast. Add to that an FPGA GPU that could do 1080p resolutions, that might rekindle my interest in OS-9! James ________________________________________ From: Coco on behalf of Kevin Phillipson Sent: Monday, August 9, 2021 8:15 PM To: CoCoList for Color Computer Enthusiasts Subject: [Coco] Turbo9 - Pipelined 6809 update video Hi everyone. Just want to let you guys know we released an update video on the progress of our pipelined 6809 microprocessor core project - the Turbo9. It's now part of our master theses for graduate school. This video mostly covered the verification and toolkit that we have developed. Also we give the CoCo community a shoutout on the last slide! Thank you for your support! https://www.youtube.com/watch?v=eTlfH86KUog Looking forward to your feedback! Kevin & Michael -- Coco mailing list Coco at maltedmedia.com https://pairlist5.pair.net/mailman/listinfo/coco From johnmarkmelanie at gmail.com Wed Aug 11 22:52:55 2021 From: johnmarkmelanie at gmail.com (Melanie and John Mark Mobley) Date: Wed, 11 Aug 2021 21:52:55 -0500 Subject: [Coco] Glenside Color Computer Club, Inc. Demo Meeting and Business Meeting Message-ID: <009b01d78f25$271a5cc0$754f1640$@gmail.com> On the 3rd Thursday of the Month (like August the 19th) at 6:30 PM Central Time we will have the Glenside Color Computer Club, Inc. Demo Meeting. The meeting last 1 hour. It will be a video conference call. I want you to volunteer to do a demo on a subject and let me know in advance what the demo subject is. That way I can advertise the demo and drum up more interest. At 7:30 PM Central Time starts the Business Meeting. The Business Meeting last about 2 hours. To join the Meeting: https://bluejeans.com/889394355 You can call in: Phone Dial-in +1.408.740.7256 (United States) +1.408.317.9253 (Alternate number) (Global Numbers) Meeting ID: 889 394 355 Room System: 199.48.152.152 or bjn.vc John Mark Mobley Vice-President of Glenside Color Computer Club, Inc. From mdj at bds-soft.com Thu Aug 12 09:24:07 2021 From: mdj at bds-soft.com (M. David Johnson) Date: Thu, 12 Aug 2021 08:24:07 -0500 Subject: [Coco] Glenside Color Computer Club, Inc. Demo Meeting and Business Meeting In-Reply-To: <009b01d78f25$271a5cc0$754f1640$@gmail.com> References: <009b01d78f25$271a5cc0$754f1640$@gmail.com> Message-ID: <008301d78f7d$54694cb0$fd3be610$@bds-soft.com> Neat concept! Unfortunately, since I'm a Trustee of the Glenview Public Library, and since the Board also meets on the third Thursdays, I pretty much always have to miss the Glenside meetings. Will the Demos be recorded and archived somewhere for future reference? -- M. David Johnson mdj at bds-soft.com -----Original Message----- From: Coco [mailto:coco-bounces at maltedmedia.com] On Behalf Of Melanie and John Mark Mobley Sent: Wednesday, August 11, 2021 9:53 PM To: coco at maltedmedia.com Subject: [Coco] Glenside Color Computer Club, Inc. Demo Meeting and Business Meeting On the 3rd Thursday of the Month (like August the 19th) at 6:30 PM Central Time we will have the Glenside Color Computer Club, Inc. Demo Meeting. The meeting last 1 hour. It will be a video conference call. I want you to volunteer to do a demo on a subject and let me know in advance what the demo subject is. That way I can advertise the demo and drum up more interest. At 7:30 PM Central Time starts the Business Meeting. The Business Meeting last about 2 hours. To join the Meeting: https://bluejeans.com/889394355 You can call in: Phone Dial-in +1.408.740.7256 (United States) +1.408.317.9253 (Alternate number) (Global Numbers) Meeting ID: 889 394 355 Room System: 199.48.152.152 or bjn.vc John Mark Mobley Vice-President of Glenside Color Computer Club, Inc. -- Coco mailing list Coco at maltedmedia.com https://pairlist5.pair.net/mailman/listinfo/coco From coco at jechar.ca Thu Aug 12 20:16:44 2021 From: coco at jechar.ca (coco at jechar.ca) Date: Thu, 12 Aug 2021 20:16:44 -0400 Subject: [Coco] CoCo Keys2USB - Problem Message-ID: <92b369240a6f0a81e888e044a17d9d5c@jechar.ca> Hi I have a CoCo Keys2USB which I have used in the past however the piece of plastic holds in the keyboard ribbon cable must have fallen out and when I moved the keyboard and realized that the connection had come loose and I am not sure which is the correct way to plug it in nor do I know if I plug it in the wrong way If I will destroy it can't find the documentation I had nor does there seem to be a PDF online can anyone help. Charlie From chawks at dls.net Thu Aug 12 20:29:23 2021 From: chawks at dls.net (Christopher R. Hawks) Date: Thu, 12 Aug 2021 19:29:23 -0500 Subject: [Coco] CoCo Keys2USB - Problem In-Reply-To: <92b369240a6f0a81e888e044a17d9d5c@jechar.ca> References: <92b369240a6f0a81e888e044a17d9d5c@jechar.ca> Message-ID: <20210812192923.23b95841@Manfred.lan> On Thu, 12 Aug 2021 20:16:44 -0400 coco at jechar.ca wrote: > > Hi I have a CoCo Keys2USB which I have used in the past however the > piece of plastic holds in the keyboard ribbon cable must have fallen > out and when I moved the keyboard and realized that the connection > had come loose and I am not sure which is the correct way to plug it > in nor do I know if I plug it in the wrong way If I will destroy it > can't find the documentation I had nor does there seem to be a PDF > online can anyone help. > > Charlie > A quick search with DuckDuckGo shows the kit web page is here: https://www.tindie.com/products/fiscap0768/coco-keys2usb-kit/ It includes links to the documentation and source code. Christopher R. Hawks HAWKSoft -- Piglet noticed that even though he had a very small heart, it could hold a rather large amount of gratitude. ---Winnie Ther Pooh ---------------------------------------- \ ^__^ \ (oo)\_______ (__)\ )\/\ ||----w | || || From coco at jechar.ca Thu Aug 12 21:52:54 2021 From: coco at jechar.ca (coco at jechar.ca) Date: Thu, 12 Aug 2021 21:52:54 -0400 Subject: [Coco] CoCo Keys2USB - Problem In-Reply-To: <20210812192923.23b95841@Manfred.lan> References: <92b369240a6f0a81e888e044a17d9d5c@jechar.ca> <20210812192923.23b95841@Manfred.lan> Message-ID: <615957394bdbf2a4d1f35ffe844c4d7c@jechar.ca> Ok I found some documentation at https://www.tindie.com/products/fiscap0768/coco-keys2usb-kit/ but it was .md format I do not have a program to read that why did they not stick to a standard like .docx or .pdf Do you know someone who can convert it to .pdf if I email it to them. Charlie. On 2021-08-12 20:29, Christopher R. Hawks wrote: > On Thu, 12 Aug 2021 20:16:44 -0400 > coco at jechar.ca wrote: > >> >> Hi I have a CoCo Keys2USB which I have used in the past however the >> piece of plastic holds in the keyboard ribbon cable must have fallen >> out and when I moved the keyboard and realized that the connection >> had come loose and I am not sure which is the correct way to plug it >> in nor do I know if I plug it in the wrong way If I will destroy it >> can't find the documentation I had nor does there seem to be a PDF >> online can anyone help. >> >> Charlie >> > > A quick search with DuckDuckGo shows the kit web page is here: > https://www.tindie.com/products/fiscap0768/coco-keys2usb-kit/ > > It includes links to the documentation and source code. > > > Christopher R. Hawks > HAWKSoft > -- > Piglet noticed that even though he had a very small heart, > it could hold a rather large amount of gratitude. > ---Winnie Ther Pooh > ---------------------------------------- > \ ^__^ > \ (oo)\_______ > (__)\ )\/\ > ||----w | > || || From fiscap0768 at gmail.com Thu Aug 12 22:49:44 2021 From: fiscap0768 at gmail.com (Paul F) Date: Thu, 12 Aug 2021 22:49:44 -0400 Subject: [Coco] CoCo Keys2USB - Problem In-Reply-To: <615957394bdbf2a4d1f35ffe844c4d7c@jechar.ca> References: <92b369240a6f0a81e888e044a17d9d5c@jechar.ca> <20210812192923.23b95841@Manfred.lan> <615957394bdbf2a4d1f35ffe844c4d7c@jechar.ca> Message-ID: Charlie - The CoCo Keys2USB is my project. There are two links on the Tindie site - one for the source code and one for the .pdf version of the documentation. It sounds like you clicked the first link which brings you to the GitHub repository, and the readme.md file that you mentioned in your post is an industry standard markdown document which accompanies most git repositories. It can be viewed with a standard text viewer or is rendered through any HTML viewer/browser. I believe the document you need though is the second link, which can be accessed here - https://github.com/wyndec/CoCoKeys2USB/blob/master/docs/CoCo%20Keys2USB%20v1.2%20Instruction%20Sheet.pdf The thin piece of plastic you referred to in your original post is just a clear piece of nylon cut from a milk jug. It's only purpose is to provide a non-conductive wedge between the flat-flex mylar keyboard cable and the 2x16 card edge connector on the Keys2USB kit. As the documentation mentions, you want to have that under (on the non-conductive) side of the mylar cable to ensure the conductive (upper) side of the cable makes a firm and solid contact with the card edge connector. Also, the kit is designed so that the card edge connector could be used in both orientations (with the micro USB connector either on the left or the right). The important thing is that in either orientation, the nylon wedge is on the underside of the flat-flex mylar cable. Paul On Thu, Aug 12, 2021 at 9:53 PM wrote: > Ok I found some documentation at > https://www.tindie.com/products/fiscap0768/coco-keys2usb-kit/ but it was > .md format I do not have a program to > read that why did they not stick to a standard like .docx or .pdf > > Do you know someone who can convert it to .pdf if I email it to them. > > Charlie. > > On 2021-08-12 20:29, Christopher R. Hawks wrote: > > On Thu, 12 Aug 2021 20:16:44 -0400 > > coco at jechar.ca wrote: > > > >> > >> Hi I have a CoCo Keys2USB which I have used in the past however the > >> piece of plastic holds in the keyboard ribbon cable must have fallen > >> out and when I moved the keyboard and realized that the connection > >> had come loose and I am not sure which is the correct way to plug it > >> in nor do I know if I plug it in the wrong way If I will destroy it > >> can't find the documentation I had nor does there seem to be a PDF > >> online can anyone help. > >> > >> Charlie > >> > > > > A quick search with DuckDuckGo shows the kit web page is here: > > https://www.tindie.com/products/fiscap0768/coco-keys2usb-kit/ > > > > It includes links to the documentation and source code. > > > > > > Christopher R. Hawks > > HAWKSoft > > -- > > Piglet noticed that even though he had a very small heart, > > it could hold a rather large amount of gratitude. > > ---Winnie Ther Pooh > > ---------------------------------------- > > \ ^__^ > > \ (oo)\_______ > > (__)\ )\/\ > > ||----w | > > || || > > -- > Coco mailing list > Coco at maltedmedia.com > https://pairlist5.pair.net/mailman/listinfo/coco > From coco at jechar.ca Fri Aug 13 16:47:11 2021 From: coco at jechar.ca (coco at jechar.ca) Date: Fri, 13 Aug 2021 16:47:11 -0400 Subject: [Coco] CoCo Keys2USB - Problem In-Reply-To: References: <92b369240a6f0a81e888e044a17d9d5c@jechar.ca> <20210812192923.23b95841@Manfred.lan> <615957394bdbf2a4d1f35ffe844c4d7c@jechar.ca> Message-ID: I found the documentation and with a by cutting a piece of a used google play card to size I replaced the lost nylon and I got the keyboard working. However there are issues. 1. The documentation says "You can tell which key map is selected as a ?V?, ?X?, or ?M? will display on the screen ? indicating ?VCC?, ?XRoar?, and ?MAME? respectively." however this does not happen. I am using Vcc and in OS9 CLEAR works fine and as do the arrow keys and the alphabet and numbers but much of the top row works incorrectly for example [SHIFT2] gets @ and should get a " by the way the notation here [SHIFT2] means hold down the shift key and the 2 key at the same time. [SHIFT6] gets ^ and should get & [SHIFT7] gets & and should get ' [SHIFT8] gets * and should get ( [SHIFT9] gets ( and should get ) [SHIFT0] gets ) and should not [:] by which I mean pressing the : key which is in the top row on a COCO. [:] gets a - but should get a : [SHIFT:] gets an underscore but should get a * [-] gets a = should get a - "minus" [SHIFT-] should get an = but gets a + [CTRL-] should get an underscore but gets an = And finally BREAK and ESCAPE do not seem to work. Is there a way to fix this. Will there be a software update to fix these and is there a way to update I did not notice if there is a PROGRAM button like on a pi pico and in the documentation included no Info about flashing in new keyboard maps. Charlie On 2021-08-12 22:49, Paul F wrote: > Charlie - > > The CoCo Keys2USB is my project. There are two links on the Tindie site > - > one for the source code and one for the .pdf version of the > documentation. > It sounds like you clicked the first link which brings you to the > GitHub > repository, and the readme.md file that you mentioned in your post is > an > industry standard markdown document which accompanies most git > repositories. It can be viewed with a standard text viewer or is > rendered > through any HTML viewer/browser. > > I believe the document you need though is the second link, which can be > accessed here - > https://github.com/wyndec/CoCoKeys2USB/blob/master/docs/CoCo%20Keys2USB%20v1.2%20Instruction%20Sheet.pdf > > The thin piece of plastic you referred to in your original post is just > a > clear piece of nylon cut from a milk jug. It's only purpose is to > provide a > non-conductive wedge between the flat-flex mylar keyboard cable and the > 2x16 card edge connector on the Keys2USB kit. As the documentation > mentions, you want to have that under (on the non-conductive) side of > the > mylar cable to ensure the conductive (upper) side of the cable makes a > firm > and solid contact with the card edge connector. > > Also, the kit is designed so that the card edge connector could be used > in > both orientations (with the micro USB connector either on the left or > the > right). The important thing is that in either orientation, the nylon > wedge > is on the underside of the flat-flex mylar cable. > > Paul > > On Thu, Aug 12, 2021 at 9:53 PM wrote: > >> Ok I found some documentation at >> https://www.tindie.com/products/fiscap0768/coco-keys2usb-kit/ but it >> was >> .md format I do not have a program to >> read that why did they not stick to a standard like .docx or .pdf >> >> Do you know someone who can convert it to .pdf if I email it to them. >> >> Charlie. >> >> On 2021-08-12 20:29, Christopher R. Hawks wrote: >> > On Thu, 12 Aug 2021 20:16:44 -0400 >> > coco at jechar.ca wrote: >> > >> >> >> >> Hi I have a CoCo Keys2USB which I have used in the past however the >> >> piece of plastic holds in the keyboard ribbon cable must have fallen >> >> out and when I moved the keyboard and realized that the connection >> >> had come loose and I am not sure which is the correct way to plug it >> >> in nor do I know if I plug it in the wrong way If I will destroy it >> >> can't find the documentation I had nor does there seem to be a PDF >> >> online can anyone help. >> >> >> >> Charlie >> >> >> > >> > A quick search with DuckDuckGo shows the kit web page is here: >> > https://www.tindie.com/products/fiscap0768/coco-keys2usb-kit/ >> > >> > It includes links to the documentation and source code. >> > >> > >> > Christopher R. Hawks >> > HAWKSoft >> > -- >> > Piglet noticed that even though he had a very small heart, >> > it could hold a rather large amount of gratitude. >> > ---Winnie Ther Pooh >> > ---------------------------------------- >> > \ ^__^ >> > \ (oo)\_______ >> > (__)\ )\/\ >> > ||----w | >> > || || >> >> -- >> Coco mailing list >> Coco at maltedmedia.com >> https://pairlist5.pair.net/mailman/listinfo/coco >> From rietveldh at hotmail.com Fri Aug 13 18:59:07 2021 From: rietveldh at hotmail.com (rietveld rietveld) Date: Fri, 13 Aug 2021 22:59:07 +0000 Subject: [Coco] Our answer to a Canadian cocofest? Sort of... Message-ID: Not Tandy only but Tandy will be represented at this southern Ontario retro computer show. This will help tide us over until we can cross the boarder https://www.kijiji.ca/v-events/kitchener-waterloo/world-of-retro-computing-expo/1580760299?undefined Sent from my BlackBerry ? the most secure mobile device From ejjaquay at gmail.com Fri Aug 13 19:51:09 2021 From: ejjaquay at gmail.com (edward jaquay) Date: Fri, 13 Aug 2021 19:51:09 -0400 Subject: [Coco] CoCo Keys2USB - Problem In-Reply-To: References: <92b369240a6f0a81e888e044a17d9d5c@jechar.ca> <20210812192923.23b95841@Manfred.lan> <615957394bdbf2a4d1f35ffe844c4d7c@jechar.ca> Message-ID: The latest version of Vcc has a keyboard map editor. You may be able to fix the mapping using the editor. On Fri, Aug 13, 2021, 4:47 PM wrote: > > I found the documentation and with a by cutting a piece of a used google > play card to size I replaced the lost nylon and I got the keyboard > working. > > However there are issues. > > 1. The documentation says "You can tell which key map is selected as a > ?V?, ?X?, or ?M? will display on the screen ? indicating ?VCC?, ?XRoar?, > and ?MAME? respectively." however this does not happen. > > I am using Vcc and in OS9 CLEAR works fine and as do the arrow keys and > the alphabet and numbers but much of the top row works incorrectly for > example > > [SHIFT2] gets @ and should get a " > by the way the notation here > [SHIFT2] means hold down the shift key and the 2 key at the same > time. > [SHIFT6] gets ^ and should get & > [SHIFT7] gets & and should get ' > [SHIFT8] gets * and should get ( > [SHIFT9] gets ( and should get ) > [SHIFT0] gets ) and should not > [:] by which I mean pressing the : key which is in the top row on a > COCO. > [:] gets a - but should get a : > [SHIFT:] gets an underscore but should get a * > [-] gets a = should get a - "minus" > [SHIFT-] should get an = but gets a + > [CTRL-] should get an underscore but gets an = > > And finally BREAK and ESCAPE do not seem to work. > > Is there a way to fix this. Will there be a software update to fix > these and is there a way to update I did not notice if there is a > PROGRAM button like on a pi pico and in the documentation included > no Info about flashing in new keyboard maps. > > Charlie > > > On 2021-08-12 22:49, Paul F wrote: > > Charlie - > > > > The CoCo Keys2USB is my project. There are two links on the Tindie site > > - > > one for the source code and one for the .pdf version of the > > documentation. > > It sounds like you clicked the first link which brings you to the > > GitHub > > repository, and the readme.md file that you mentioned in your post is > > an > > industry standard markdown document which accompanies most git > > repositories. It can be viewed with a standard text viewer or is > > rendered > > through any HTML viewer/browser. > > > > I believe the document you need though is the second link, which can be > > accessed here - > > > https://github.com/wyndec/CoCoKeys2USB/blob/master/docs/CoCo%20Keys2USB%20v1.2%20Instruction%20Sheet.pdf > > > > The thin piece of plastic you referred to in your original post is just > > a > > clear piece of nylon cut from a milk jug. It's only purpose is to > > provide a > > non-conductive wedge between the flat-flex mylar keyboard cable and the > > 2x16 card edge connector on the Keys2USB kit. As the documentation > > mentions, you want to have that under (on the non-conductive) side of > > the > > mylar cable to ensure the conductive (upper) side of the cable makes a > > firm > > and solid contact with the card edge connector. > > > > Also, the kit is designed so that the card edge connector could be used > > in > > both orientations (with the micro USB connector either on the left or > > the > > right). The important thing is that in either orientation, the nylon > > wedge > > is on the underside of the flat-flex mylar cable. > > > > Paul > > > > On Thu, Aug 12, 2021 at 9:53 PM wrote: > > > >> Ok I found some documentation at > >> https://www.tindie.com/products/fiscap0768/coco-keys2usb-kit/ but it > >> was > >> .md format I do not have a program to > >> read that why did they not stick to a standard like .docx or .pdf > >> > >> Do you know someone who can convert it to .pdf if I email it to them. > >> > >> Charlie. > >> > >> On 2021-08-12 20:29, Christopher R. Hawks wrote: > >> > On Thu, 12 Aug 2021 20:16:44 -0400 > >> > coco at jechar.ca wrote: > >> > > >> >> > >> >> Hi I have a CoCo Keys2USB which I have used in the past however the > >> >> piece of plastic holds in the keyboard ribbon cable must have fallen > >> >> out and when I moved the keyboard and realized that the connection > >> >> had come loose and I am not sure which is the correct way to plug it > >> >> in nor do I know if I plug it in the wrong way If I will destroy it > >> >> can't find the documentation I had nor does there seem to be a PDF > >> >> online can anyone help. > >> >> > >> >> Charlie > >> >> > >> > > >> > A quick search with DuckDuckGo shows the kit web page is here: > >> > https://www.tindie.com/products/fiscap0768/coco-keys2usb-kit/ > >> > > >> > It includes links to the documentation and source code. > >> > > >> > > >> > Christopher R. Hawks > >> > HAWKSoft > >> > -- > >> > Piglet noticed that even though he had a very small heart, > >> > it could hold a rather large amount of gratitude. > >> > ---Winnie Ther Pooh > >> > ---------------------------------------- > >> > \ ^__^ > >> > \ (oo)\_______ > >> > (__)\ )\/\ > >> > ||----w | > >> > || || > >> > >> -- > >> 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 > From ooogalapasooo at aol.com Sat Aug 14 07:12:31 2021 From: ooogalapasooo at aol.com (Bill Pierce) Date: Sat, 14 Aug 2021 11:12:31 +0000 (UTC) Subject: [Coco] CoCo Keys2USB - Problem In-Reply-To: References: <92b369240a6f0a81e888e044a17d9d5c@jechar.ca> <20210812192923.23b95841@Manfred.lan> <615957394bdbf2a4d1f35ffe844c4d7c@jechar.ca> Message-ID: <1138238394.405470.1628939551291@mail.yahoo.com> Charlie, the OS9 keymap in VCC is set to be a normal PC keyboard and not a Coco keyboard. If it matched the COco keys... it would be the same as the Coco keymap and not needed LOL. Also, in the latest VCC release, there is a custom keymap editor in which you can set the keys any way you want. -----Original Message----- From: coco at jechar.ca To: CoCoList for Color Computer Enthusiasts Sent: Fri, Aug 13, 2021 4:47 pm Subject: Re: [Coco] CoCo Keys2USB - Problem I found the documentation and with a by cutting a piece of a used google play card to size I replaced the lost nylon and I got the keyboard working. However there are issues. 1. The documentation says "You can tell which key map is selected as a ?V?, ?X?, or ?M? will display on the screen ? indicating ?VCC?, ?XRoar?, and ?MAME? respectively." however this does not happen. I am using Vcc and in OS9 CLEAR works fine and as do the arrow keys and the alphabet and numbers but much of the top row works incorrectly for example ? ? [SHIFT2] gets @ and should get a " ? ? by the way the notation here ? ? [SHIFT2] means hold down the shift key and the 2 key at the same time. ? ? [SHIFT6] gets ^ and should get? & ? ? [SHIFT7] gets & and should get ' ? ? [SHIFT8] gets * and should get ( ? ? [SHIFT9] gets ( and should get ) ? ? [SHIFT0] gets ) and should not ? ? [:] by which I mean pressing the : key which is in the top row on a COCO. ? ? [:] gets a - but should get a : ? ? [SHIFT:] gets an underscore but should get a * ? ? [-] gets a = should get a - "minus" ? ? [SHIFT-] should get an = but gets a + ? ? [CTRL-] should get an underscore but gets an = ? ? And finally BREAK and ESCAPE do not seem to work. ? ? Is there a way to fix this. Will there be a software update to fix ? ? these and is there a way to update I did not notice if there is a ? ? PROGRAM button like on a pi pico and in the documentation included ? ? no Info about flashing in new keyboard maps. ? ? Charlie On 2021-08-12 22:49, Paul F wrote: > Charlie - > > The CoCo Keys2USB is my project. There are two links on the Tindie site > - > one for the source code and one for the .pdf version of the > documentation. > It sounds like you clicked the first link which brings you to the > GitHub > repository, and the readme.md file that you mentioned in your post is > an > industry standard markdown document which accompanies most git > repositories. It can be viewed with a standard text viewer or is > rendered > through any HTML viewer/browser. > > I believe the document you need though is the second link, which can be > accessed here - > https://github.com/wyndec/CoCoKeys2USB/blob/master/docs/CoCo%20Keys2USB%20v1.2%20Instruction%20Sheet.pdf > > The thin piece of plastic you referred to in your original post is just > a > clear piece of nylon cut from a milk jug. It's only purpose is to > provide a > non-conductive wedge between the flat-flex mylar keyboard cable and the > 2x16 card edge connector on the Keys2USB kit. As the documentation > mentions, you want to have that under (on the non-conductive) side of > the > mylar cable to ensure the conductive (upper) side of the cable makes a > firm > and solid contact with the card edge connector. > > Also, the kit is designed so that the card edge connector could be used > in > both orientations (with the micro USB connector either on the left or > the > right). The important thing is that in either orientation, the nylon > wedge > is on the underside of the flat-flex mylar cable. > > Paul > > On Thu, Aug 12, 2021 at 9:53 PM wrote: > >> Ok I found some documentation at >> https://www.tindie.com/products/fiscap0768/coco-keys2usb-kit/ but it >> was >> .md format I do not have a program to >> read that why did they not stick to a standard like .docx or .pdf >> >> Do you know someone who can convert it to .pdf if I email it to them. >> >> Charlie. >> >> On 2021-08-12 20:29, Christopher R. Hawks wrote: >> > On Thu, 12 Aug 2021 20:16:44 -0400 >> > coco at jechar.ca wrote: >> > >> >> >> >> Hi I have a CoCo Keys2USB which I have used in the past however the >> >> piece of plastic holds in the keyboard ribbon cable must have fallen >> >> out and when I moved the keyboard and realized that the connection >> >> had come loose and I am not sure which is the correct way to plug it >> >> in nor do I know if I plug it in the wrong way If I will destroy it >> >> can't find the documentation I had nor does there seem to be a PDF >> >> online can anyone help. >> >> >> >> Charlie >> >> >> > >> >? ? A quick search with DuckDuckGo shows the kit web page is here: >> > https://www.tindie.com/products/fiscap0768/coco-keys2usb-kit/ >> > >> >? ? It includes links to the documentation and source code. >> > >> > >> > Christopher R. Hawks >> > HAWKSoft >> > -- >> > Piglet noticed that even though he had a very small heart, >> > it could hold a rather large amount of gratitude. >> >? ? ? ? ? ? ? ? ? ? ? ---Winnie Ther Pooh >> > ---------------------------------------- >> >? ? ? ? \? ^__^ >> >? ? ? ? \? (oo)\_______ >> >? ? ? ? ? ? (__)\? ? ? )\/\ >> >? ? ? ? ? ? ? ? ||----w | >> >? ? ? ? ? ? ? ? ||? ? || >> >> -- >> 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 From fiscap0768 at gmail.com Sat Aug 14 08:13:53 2021 From: fiscap0768 at gmail.com (Paul F) Date: Sat, 14 Aug 2021 08:13:53 -0400 Subject: [Coco] CoCo Keys2USB - Problem In-Reply-To: References: <92b369240a6f0a81e888e044a17d9d5c@jechar.ca> <20210812192923.23b95841@Manfred.lan> <615957394bdbf2a4d1f35ffe844c4d7c@jechar.ca> Message-ID: Charlie - I'm out of town for the weekend and won't be able to test your setup until Monday evening, but are you able to verify that this behavior is only present in OS-9 versus in VCC DECB by itself? It's the first I'm hearing of the potential issue and it's possible that OS-9 requires a separate key map. The software/repository is open source and is fairly well documented. I did this so that anyone who has a device and wants to create custom keymaps or add functionality, will have the ability to do so. The flashing procedure involves installing the freely available Arduino IDE, updating the code from GitHub, and uploading the modified code from the IDE to the Pro Micro over a standard USB cable. This process is fairly well documented and there are numerous videos out there that can get you started if you're a beginner. If OS-9 does require a separate key map, I should have some time next week to create one and upload the changes to the GitHub repo. Paul On Fri, Aug 13, 2021 at 4:47 PM wrote: > > I found the documentation and with a by cutting a piece of a used google > play card to size I replaced the lost nylon and I got the keyboard > working. > > However there are issues. > > 1. The documentation says "You can tell which key map is selected as a > ?V?, ?X?, or ?M? will display on the screen ? indicating ?VCC?, ?XRoar?, > and ?MAME? respectively." however this does not happen. > > I am using Vcc and in OS9 CLEAR works fine and as do the arrow keys and > the alphabet and numbers but much of the top row works incorrectly for > example > > [SHIFT2] gets @ and should get a " > by the way the notation here > [SHIFT2] means hold down the shift key and the 2 key at the same > time. > [SHIFT6] gets ^ and should get & > [SHIFT7] gets & and should get ' > [SHIFT8] gets * and should get ( > [SHIFT9] gets ( and should get ) > [SHIFT0] gets ) and should not > [:] by which I mean pressing the : key which is in the top row on a > COCO. > [:] gets a - but should get a : > [SHIFT:] gets an underscore but should get a * > [-] gets a = should get a - "minus" > [SHIFT-] should get an = but gets a + > [CTRL-] should get an underscore but gets an = > > And finally BREAK and ESCAPE do not seem to work. > > Is there a way to fix this. Will there be a software update to fix > these and is there a way to update I did not notice if there is a > PROGRAM button like on a pi pico and in the documentation included > no Info about flashing in new keyboard maps. > > Charlie > > > On 2021-08-12 22:49, Paul F wrote: > > Charlie - > > > > The CoCo Keys2USB is my project. There are two links on the Tindie site > > - > > one for the source code and one for the .pdf version of the > > documentation. > > It sounds like you clicked the first link which brings you to the > > GitHub > > repository, and the readme.md file that you mentioned in your post is > > an > > industry standard markdown document which accompanies most git > > repositories. It can be viewed with a standard text viewer or is > > rendered > > through any HTML viewer/browser. > > > > I believe the document you need though is the second link, which can be > > accessed here - > > > https://github.com/wyndec/CoCoKeys2USB/blob/master/docs/CoCo%20Keys2USB%20v1.2%20Instruction%20Sheet.pdf > > > > The thin piece of plastic you referred to in your original post is just > > a > > clear piece of nylon cut from a milk jug. It's only purpose is to > > provide a > > non-conductive wedge between the flat-flex mylar keyboard cable and the > > 2x16 card edge connector on the Keys2USB kit. As the documentation > > mentions, you want to have that under (on the non-conductive) side of > > the > > mylar cable to ensure the conductive (upper) side of the cable makes a > > firm > > and solid contact with the card edge connector. > > > > Also, the kit is designed so that the card edge connector could be used > > in > > both orientations (with the micro USB connector either on the left or > > the > > right). The important thing is that in either orientation, the nylon > > wedge > > is on the underside of the flat-flex mylar cable. > > > > Paul > > > > On Thu, Aug 12, 2021 at 9:53 PM wrote: > > > >> Ok I found some documentation at > >> https://www.tindie.com/products/fiscap0768/coco-keys2usb-kit/ but it > >> was > >> .md format I do not have a program to > >> read that why did they not stick to a standard like .docx or .pdf > >> > >> Do you know someone who can convert it to .pdf if I email it to them. > >> > >> Charlie. > >> > >> On 2021-08-12 20:29, Christopher R. Hawks wrote: > >> > On Thu, 12 Aug 2021 20:16:44 -0400 > >> > coco at jechar.ca wrote: > >> > > >> >> > >> >> Hi I have a CoCo Keys2USB which I have used in the past however the > >> >> piece of plastic holds in the keyboard ribbon cable must have fallen > >> >> out and when I moved the keyboard and realized that the connection > >> >> had come loose and I am not sure which is the correct way to plug it > >> >> in nor do I know if I plug it in the wrong way If I will destroy it > >> >> can't find the documentation I had nor does there seem to be a PDF > >> >> online can anyone help. > >> >> > >> >> Charlie > >> >> > >> > > >> > A quick search with DuckDuckGo shows the kit web page is here: > >> > https://www.tindie.com/products/fiscap0768/coco-keys2usb-kit/ > >> > > >> > It includes links to the documentation and source code. > >> > > >> > > >> > Christopher R. Hawks > >> > HAWKSoft > >> > -- > >> > Piglet noticed that even though he had a very small heart, > >> > it could hold a rather large amount of gratitude. > >> > ---Winnie Ther Pooh > >> > ---------------------------------------- > >> > \ ^__^ > >> > \ (oo)\_______ > >> > (__)\ )\/\ > >> > ||----w | > >> > || || > >> > >> -- > >> 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 > From coco at jechar.ca Sat Aug 14 13:38:16 2021 From: coco at jechar.ca (coco at jechar.ca) Date: Sat, 14 Aug 2021 13:38:16 -0400 Subject: [Coco] CoCo Keys2USB - Problem In-Reply-To: References: <92b369240a6f0a81e888e044a17d9d5c@jechar.ca> <20210812192923.23b95841@Manfred.lan> <615957394bdbf2a4d1f35ffe844c4d7c@jechar.ca> Message-ID: <8f4d0c1fe1feed9b61306336720dea80@jechar.ca> Similar issues in RS-DOS "Disk Extended Color Basic 2.1" except that [SHIFT6] produces the two characters =7 On 2021-08-14 08:13, Paul F wrote: > Charlie - > > I'm out of town for the weekend and won't be able to test your setup > until > Monday evening, but are you able to verify that this behavior is only > present in OS-9 versus in VCC DECB by itself? It's the first I'm > hearing of > the potential issue and it's possible that OS-9 requires a separate key > map. > > The software/repository is open source and is fairly well documented. I > did > this so that anyone who has a device and wants to create custom keymaps > or > add functionality, will have the ability to do so. The flashing > procedure > involves installing the freely available Arduino IDE, updating the code > from GitHub, and uploading the modified code from the IDE to the Pro > Micro > over a standard USB cable. This process is fairly well documented and > there > are numerous videos out there that can get you started if you're a > beginner. > > If OS-9 does require a separate key map, I should have some time next > week > to create one and upload the changes to the GitHub repo. > > Paul > > On Fri, Aug 13, 2021 at 4:47 PM wrote: > >> >> I found the documentation and with a by cutting a piece of a used >> google >> play card to size I replaced the lost nylon and I got the keyboard >> working. >> >> However there are issues. >> >> 1. The documentation says "You can tell which key map is selected as a >> ?V?, ?X?, or ?M? will display on the screen ? indicating ?VCC?, >> ?XRoar?, >> and ?MAME? respectively." however this does not happen. >> >> I am using Vcc and in OS9 CLEAR works fine and as do the arrow keys >> and >> the alphabet and numbers but much of the top row works incorrectly for >> example >> >> [SHIFT2] gets @ and should get a " >> by the way the notation here >> [SHIFT2] means hold down the shift key and the 2 key at the same >> time. >> [SHIFT6] gets ^ and should get & >> [SHIFT7] gets & and should get ' >> [SHIFT8] gets * and should get ( >> [SHIFT9] gets ( and should get ) >> [SHIFT0] gets ) and should not >> [:] by which I mean pressing the : key which is in the top row on >> a >> COCO. >> [:] gets a - but should get a : >> [SHIFT:] gets an underscore but should get a * >> [-] gets a = should get a - "minus" >> [SHIFT-] should get an = but gets a + >> [CTRL-] should get an underscore but gets an = >> >> And finally BREAK and ESCAPE do not seem to work. >> >> Is there a way to fix this. Will there be a software update to >> fix >> these and is there a way to update I did not notice if there is a >> PROGRAM button like on a pi pico and in the documentation >> included >> no Info about flashing in new keyboard maps. >> >> Charlie >> >> >> On 2021-08-12 22:49, Paul F wrote: >> > Charlie - >> > >> > The CoCo Keys2USB is my project. There are two links on the Tindie site >> > - >> > one for the source code and one for the .pdf version of the >> > documentation. >> > It sounds like you clicked the first link which brings you to the >> > GitHub >> > repository, and the readme.md file that you mentioned in your post is >> > an >> > industry standard markdown document which accompanies most git >> > repositories. It can be viewed with a standard text viewer or is >> > rendered >> > through any HTML viewer/browser. >> > >> > I believe the document you need though is the second link, which can be >> > accessed here - >> > >> https://github.com/wyndec/CoCoKeys2USB/blob/master/docs/CoCo%20Keys2USB%20v1.2%20Instruction%20Sheet.pdf >> > >> > The thin piece of plastic you referred to in your original post is just >> > a >> > clear piece of nylon cut from a milk jug. It's only purpose is to >> > provide a >> > non-conductive wedge between the flat-flex mylar keyboard cable and the >> > 2x16 card edge connector on the Keys2USB kit. As the documentation >> > mentions, you want to have that under (on the non-conductive) side of >> > the >> > mylar cable to ensure the conductive (upper) side of the cable makes a >> > firm >> > and solid contact with the card edge connector. >> > >> > Also, the kit is designed so that the card edge connector could be used >> > in >> > both orientations (with the micro USB connector either on the left or >> > the >> > right). The important thing is that in either orientation, the nylon >> > wedge >> > is on the underside of the flat-flex mylar cable. >> > >> > Paul >> > >> > On Thu, Aug 12, 2021 at 9:53 PM wrote: >> > >> >> Ok I found some documentation at >> >> https://www.tindie.com/products/fiscap0768/coco-keys2usb-kit/ but it >> >> was >> >> .md format I do not have a program to >> >> read that why did they not stick to a standard like .docx or .pdf >> >> >> >> Do you know someone who can convert it to .pdf if I email it to them. >> >> >> >> Charlie. >> >> >> >> On 2021-08-12 20:29, Christopher R. Hawks wrote: >> >> > On Thu, 12 Aug 2021 20:16:44 -0400 >> >> > coco at jechar.ca wrote: >> >> > >> >> >> >> >> >> Hi I have a CoCo Keys2USB which I have used in the past however the >> >> >> piece of plastic holds in the keyboard ribbon cable must have fallen >> >> >> out and when I moved the keyboard and realized that the connection >> >> >> had come loose and I am not sure which is the correct way to plug it >> >> >> in nor do I know if I plug it in the wrong way If I will destroy it >> >> >> can't find the documentation I had nor does there seem to be a PDF >> >> >> online can anyone help. >> >> >> >> >> >> Charlie >> >> >> >> >> > >> >> > A quick search with DuckDuckGo shows the kit web page is here: >> >> > https://www.tindie.com/products/fiscap0768/coco-keys2usb-kit/ >> >> > >> >> > It includes links to the documentation and source code. >> >> > >> >> > >> >> > Christopher R. Hawks >> >> > HAWKSoft >> >> > -- >> >> > Piglet noticed that even though he had a very small heart, >> >> > it could hold a rather large amount of gratitude. >> >> > ---Winnie Ther Pooh >> >> > ---------------------------------------- >> >> > \ ^__^ >> >> > \ (oo)\_______ >> >> > (__)\ )\/\ >> >> > ||----w | >> >> > || || >> >> >> >> -- >> >> 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 >> From ooogalapasooo at aol.com Sun Aug 15 07:43:14 2021 From: ooogalapasooo at aol.com (Bill Pierce) Date: Sun, 15 Aug 2021 11:43:14 +0000 (UTC) Subject: [Coco] CoCo Keys2USB - Problem In-Reply-To: References: <92b369240a6f0a81e888e044a17d9d5c@jechar.ca> <20210812192923.23b95841@Manfred.lan> <615957394bdbf2a4d1f35ffe844c4d7c@jechar.ca> Message-ID: <1945305346.561172.1629027794252@mail.yahoo.com> Paul, VCC uses a PC keyboard. You have the option of "emulating" the layout of an actual Coco keyboard or use it as a PC keyboard. The PC layout is labeled as OS9 (nothing to do with OS9 itself). If he is using a real Coco keyboard, then he needs to use the Coco keymap in VCC or keys will be missing. The layout of the keymaps are in the manual. There is also a custom keymap editor in which the keys can be remapped to any desired location. Bill P. (VCC Dev Team) BTW, I haven't been posting the updates here, but the latest release of VCC is here... https://github.com/VCCE/VCC/releases/tag/v2.1.0d -----Original Message----- From: Paul F To: CoCoList for Color Computer Enthusiasts Sent: Sat, Aug 14, 2021 8:13 am Subject: Re: [Coco] CoCo Keys2USB - Problem Charlie - I'm out of town for the weekend and won't be able to test your setup until Monday evening, but are you able to verify that this behavior is only present in OS-9 versus in VCC DECB by itself? It's the first I'm hearing of the potential issue and it's possible that OS-9 requires a separate key map. The software/repository is open source and is fairly well documented. I did this so that anyone who has a device and wants to create custom keymaps or add functionality, will have the ability to do so. The flashing procedure involves installing the freely available Arduino IDE, updating the code from GitHub, and uploading the modified code from the IDE to the Pro Micro over a standard USB cable. This process is fairly well documented and there are numerous videos out there that can get you started if you're a beginner. If OS-9 does require a separate key map, I should have some time next week to create one and upload the changes to the GitHub repo. Paul On Fri, Aug 13, 2021 at 4:47 PM wrote: > > I found the documentation and with a by cutting a piece of a used google > play card to size I replaced the lost nylon and I got the keyboard > working. > > However there are issues. > > 1. The documentation says "You can tell which key map is selected as a > ?V?, ?X?, or ?M? will display on the screen ? indicating ?VCC?, ?XRoar?, > and ?MAME? respectively." however this does not happen. > > I am using Vcc and in OS9 CLEAR works fine and as do the arrow keys and > the alphabet and numbers but much of the top row works incorrectly for > example > >? ? [SHIFT2] gets @ and should get a " >? ? by the way the notation here >? ? [SHIFT2] means hold down the shift key and the 2 key at the same > time. >? ? [SHIFT6] gets ^ and should get? & >? ? [SHIFT7] gets & and should get ' >? ? [SHIFT8] gets * and should get ( >? ? [SHIFT9] gets ( and should get ) >? ? [SHIFT0] gets ) and should not >? ? [:] by which I mean pressing the : key which is in the top row on a > COCO. >? ? [:] gets a - but should get a : >? ? [SHIFT:] gets an underscore but should get a * >? ? [-] gets a = should get a - "minus" >? ? [SHIFT-] should get an = but gets a + >? ? [CTRL-] should get an underscore but gets an = > >? ? ? And finally BREAK and ESCAPE do not seem to work. > >? ? ? Is there a way to fix this. Will there be a software update to fix >? ? ? these and is there a way to update I did not notice if there is a >? ? ? PROGRAM button like on a pi pico and in the documentation included >? ? ? no Info about flashing in new keyboard maps. > >? ? ? Charlie > > > On 2021-08-12 22:49, Paul F wrote: > > Charlie - > > > > The CoCo Keys2USB is my project. There are two links on the Tindie site > > - > > one for the source code and one for the .pdf version of the > > documentation. > > It sounds like you clicked the first link which brings you to the > > GitHub > > repository, and the readme.md file that you mentioned in your post is > > an > > industry standard markdown document which accompanies most git > > repositories. It can be viewed with a standard text viewer or is > > rendered > > through any HTML viewer/browser. > > > > I believe the document you need though is the second link, which can be > > accessed here - > > > https://github.com/wyndec/CoCoKeys2USB/blob/master/docs/CoCo%20Keys2USB%20v1.2%20Instruction%20Sheet.pdf > > > > The thin piece of plastic you referred to in your original post is just > > a > > clear piece of nylon cut from a milk jug. It's only purpose is to > > provide a > > non-conductive wedge between the flat-flex mylar keyboard cable and the > > 2x16 card edge connector on the Keys2USB kit. As the documentation > > mentions, you want to have that under (on the non-conductive) side of > > the > > mylar cable to ensure the conductive (upper) side of the cable makes a > > firm > > and solid contact with the card edge connector. > > > > Also, the kit is designed so that the card edge connector could be used > > in > > both orientations (with the micro USB connector either on the left or > > the > > right). The important thing is that in either orientation, the nylon > > wedge > > is on the underside of the flat-flex mylar cable. > > > > Paul > > > > On Thu, Aug 12, 2021 at 9:53 PM wrote: > > > >> Ok I found some documentation at > >> https://www.tindie.com/products/fiscap0768/coco-keys2usb-kit/ but it > >> was > >> .md format I do not have a program to > >> read that why did they not stick to a standard like .docx or .pdf > >> > >> Do you know someone who can convert it to .pdf if I email it to them. > >> > >> Charlie. > >> > >> On 2021-08-12 20:29, Christopher R. Hawks wrote: > >> > On Thu, 12 Aug 2021 20:16:44 -0400 > >> > coco at jechar.ca wrote: > >> > > >> >> > >> >> Hi I have a CoCo Keys2USB which I have used in the past however the > >> >> piece of plastic holds in the keyboard ribbon cable must have fallen > >> >> out and when I moved the keyboard and realized that the connection > >> >> had come loose and I am not sure which is the correct way to plug it > >> >> in nor do I know if I plug it in the wrong way If I will destroy it > >> >> can't find the documentation I had nor does there seem to be a PDF > >> >> online can anyone help. > >> >> > >> >> Charlie > >> >> > >> > > >> >? ? A quick search with DuckDuckGo shows the kit web page is here: > >> > https://www.tindie.com/products/fiscap0768/coco-keys2usb-kit/ > >> > > >> >? ? It includes links to the documentation and source code. > >> > > >> > > >> > Christopher R. Hawks > >> > HAWKSoft > >> > -- > >> > Piglet noticed that even though he had a very small heart, > >> > it could hold a rather large amount of gratitude. > >> >? ? ? ? ? ? ? ? ? ? ? ---Winnie Ther Pooh > >> > ---------------------------------------- > >> >? ? ? ? \? ^__^ > >> >? ? ? ? \? (oo)\_______ > >> >? ? ? ? ? ? (__)\? ? ? )\/\ > >> >? ? ? ? ? ? ? ? ||----w | > >> >? ? ? ? ? ? ? ? ||? ? || > >> > >> -- > >> 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 > -- Coco mailing list Coco at maltedmedia.com https://pairlist5.pair.net/mailman/listinfo/coco From ogsteviestrow at gmail.com Mon Aug 16 07:01:23 2021 From: ogsteviestrow at gmail.com (Steve Strowbridge) Date: Mon, 16 Aug 2021 07:01:23 -0400 Subject: [Coco] Live Dragon Special August 14th In-Reply-To: References: Message-ID: > If you missed the first ever DragonTALK! live you can catch any of the > following replays, the show was as grandiose and magnificent as our 2020 > Virtual CoCoFEST! > > YouTube: https://youtu.be/NNDDh1ZLkYg > Audio Podcast: https://www.podbean.com/ew/pb-6dnv2-10b60ca > Video Podcast: https://www.podbean.com/ew/pb-rxbjs-10b63c4 > > Speaker/Segment time stamps: > 00:00:00 - Opening > 00:02:55 - Panel Introductions > 00:08:27 - GameON! Intro - special presentation by Amigos Retro Gaming > 00:24:07 - GameON! Results - Reveals of next week's game > 00:48:23 - Chris Poacher > 01:08:29 - Ciaran Anscomb > 01:27:52 - Duncan Smeed > 01:57:52 - John Vella > 02:16:44 - John Witworth > 02:55:14 - Nigel Barnes > 03:11:09 - Pere Serrat > 03:28:25 - Richard Harding > 04:03:52 - Roberto Fernandez > 04:33:31 - Simon Waterfield > 04:46:03 - Steve Bamford > 05:11:47 - Stewart Orchard > 05:28:32 - Tim Gilberts > 05:50:18 - Outro > 05:51:49 - Parting thoughts > From coco at jechar.ca Mon Aug 16 17:45:47 2021 From: coco at jechar.ca (coco at jechar.ca) Date: Mon, 16 Aug 2021 17:45:47 -0400 Subject: [Coco] CoCo Keys2USB - Problem In-Reply-To: <1945305346.561172.1629027794252@mail.yahoo.com> References: <92b369240a6f0a81e888e044a17d9d5c@jechar.ca> <20210812192923.23b95841@Manfred.lan> <615957394bdbf2a4d1f35ffe844c4d7c@jechar.ca> <1945305346.561172.1629027794252@mail.yahoo.com> Message-ID: <5ea89f0e9f900e4911838cc2860eb922@jechar.ca> Yes I am using a Real Coco keyboard though a device that adapts it to USB. I will have to download this new Vcc and remap the keys. On 2021-08-15 07:43, Bill Pierce via Coco wrote: > Paul, VCC uses a PC keyboard. You have the option of "emulating" the > layout of an actual Coco keyboard or use it as a PC keyboard. The PC > layout is labeled as OS9 (nothing to do with OS9 itself). If he is > using a real Coco keyboard, then he needs to use the Coco keymap in > VCC or keys will be missing. The layout of the keymaps are in the > manual. There is also a custom keymap editor in which the keys can be > remapped to any desired location. > Bill P. (VCC Dev Team) > > BTW, I haven't been posting the updates here, but the latest release > of VCC is here... > > https://github.com/VCCE/VCC/releases/tag/v2.1.0d > > > -----Original Message----- > From: Paul F > To: CoCoList for Color Computer Enthusiasts > Sent: Sat, Aug 14, 2021 8:13 am > Subject: Re: [Coco] CoCo Keys2USB - Problem > > Charlie - > > I'm out of town for the weekend and won't be able to test your setup > until > Monday evening, but are you able to verify that this behavior is only > present in OS-9 versus in VCC DECB by itself? It's the first I'm > hearing of > the potential issue and it's possible that OS-9 requires a separate key > map. > > The software/repository is open source and is fairly well documented. I > did > this so that anyone who has a device and wants to create custom keymaps > or > add functionality, will have the ability to do so. The flashing > procedure > involves installing the freely available Arduino IDE, updating the code > from GitHub, and uploading the modified code from the IDE to the Pro > Micro > over a standard USB cable. This process is fairly well documented and > there > are numerous videos out there that can get you started if you're a > beginner. > > If OS-9 does require a separate key map, I should have some time next > week > to create one and upload the changes to the GitHub repo. > > Paul > > On Fri, Aug 13, 2021 at 4:47 PM wrote: > >> >> I found the documentation and with a by cutting a piece of a used >> google >> play card to size I replaced the lost nylon and I got the keyboard >> working. >> >> However there are issues. >> >> 1. The documentation says "You can tell which key map is selected as a >> ?V?, ?X?, or ?M? will display on the screen ? indicating ?VCC?, >> ?XRoar?, >> and ?MAME? respectively." however this does not happen. >> >> I am using Vcc and in OS9 CLEAR works fine and as do the arrow keys >> and >> the alphabet and numbers but much of the top row works incorrectly for >> example >> >> ? ? [SHIFT2] gets @ and should get a " >> ? ? by the way the notation here >> ? ? [SHIFT2] means hold down the shift key and the 2 key at the same >> time. >> ? ? [SHIFT6] gets ^ and should get? & >> ? ? [SHIFT7] gets & and should get ' >> ? ? [SHIFT8] gets * and should get ( >> ? ? [SHIFT9] gets ( and should get ) >> ? ? [SHIFT0] gets ) and should not >> ? ? [:] by which I mean pressing the : key which is in the top row on >> a >> COCO. >> ? ? [:] gets a - but should get a : >> ? ? [SHIFT:] gets an underscore but should get a * >> ? ? [-] gets a = should get a - "minus" >> ? ? [SHIFT-] should get an = but gets a + >> ? ? [CTRL-] should get an underscore but gets an = >> >> ? ? ? And finally BREAK and ESCAPE do not seem to work. >> >> ? ? ? Is there a way to fix this. Will there be a software update to >> fix >> ? ? ? these and is there a way to update I did not notice if there is >> a >> ? ? ? PROGRAM button like on a pi pico and in the documentation >> included >> ? ? ? no Info about flashing in new keyboard maps. >> >> ? ? ? Charlie >> >> >> On 2021-08-12 22:49, Paul F wrote: >> > Charlie - >> > >> > The CoCo Keys2USB is my project. There are two links on the Tindie site >> > - >> > one for the source code and one for the .pdf version of the >> > documentation. >> > It sounds like you clicked the first link which brings you to the >> > GitHub >> > repository, and the readme.md file that you mentioned in your post is >> > an >> > industry standard markdown document which accompanies most git >> > repositories. It can be viewed with a standard text viewer or is >> > rendered >> > through any HTML viewer/browser. >> > >> > I believe the document you need though is the second link, which can be >> > accessed here - >> > >> https://github.com/wyndec/CoCoKeys2USB/blob/master/docs/CoCo%20Keys2USB%20v1.2%20Instruction%20Sheet.pdf >> > >> > The thin piece of plastic you referred to in your original post is just >> > a >> > clear piece of nylon cut from a milk jug. It's only purpose is to >> > provide a >> > non-conductive wedge between the flat-flex mylar keyboard cable and the >> > 2x16 card edge connector on the Keys2USB kit. As the documentation >> > mentions, you want to have that under (on the non-conductive) side of >> > the >> > mylar cable to ensure the conductive (upper) side of the cable makes a >> > firm >> > and solid contact with the card edge connector. >> > >> > Also, the kit is designed so that the card edge connector could be used >> > in >> > both orientations (with the micro USB connector either on the left or >> > the >> > right). The important thing is that in either orientation, the nylon >> > wedge >> > is on the underside of the flat-flex mylar cable. >> > >> > Paul >> > >> > On Thu, Aug 12, 2021 at 9:53 PM wrote: >> > >> >> Ok I found some documentation at >> >> https://www.tindie.com/products/fiscap0768/coco-keys2usb-kit/ but it >> >> was >> >> .md format I do not have a program to >> >> read that why did they not stick to a standard like .docx or .pdf >> >> >> >> Do you know someone who can convert it to .pdf if I email it to them. >> >> >> >> Charlie. >> >> >> >> On 2021-08-12 20:29, Christopher R. Hawks wrote: >> >> > On Thu, 12 Aug 2021 20:16:44 -0400 >> >> > coco at jechar.ca wrote: >> >> > >> >> >> >> >> >> Hi I have a CoCo Keys2USB which I have used in the past however the >> >> >> piece of plastic holds in the keyboard ribbon cable must have fallen >> >> >> out and when I moved the keyboard and realized that the connection >> >> >> had come loose and I am not sure which is the correct way to plug it >> >> >> in nor do I know if I plug it in the wrong way If I will destroy it >> >> >> can't find the documentation I had nor does there seem to be a PDF >> >> >> online can anyone help. >> >> >> >> >> >> Charlie >> >> >> >> >> > >> >> >? ? A quick search with DuckDuckGo shows the kit web page is here: >> >> > https://www.tindie.com/products/fiscap0768/coco-keys2usb-kit/ >> >> > >> >> >? ? It includes links to the documentation and source code. >> >> > >> >> > >> >> > Christopher R. Hawks >> >> > HAWKSoft >> >> > -- >> >> > Piglet noticed that even though he had a very small heart, >> >> > it could hold a rather large amount of gratitude. >> >> >? ? ? ? ? ? ? ? ? ? ? ---Winnie Ther Pooh >> >> > ---------------------------------------- >> >> >? ? ? ? \? ^__^ >> >> >? ? ? ? \? (oo)\_______ >> >> >? ? ? ? ? ? (__)\? ? ? )\/\ >> >> >? ? ? ? ? ? ? ? ||----w | >> >> >? ? ? ? ? ? ? ? ||? ? || >> >> >> >> -- >> >> 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 >> > > -- > Coco mailing list > Coco at maltedmedia.com > https://pairlist5.pair.net/mailman/listinfo/coco From chawks at dls.net Mon Aug 16 20:41:04 2021 From: chawks at dls.net (Christopher R. Hawks) Date: Mon, 16 Aug 2021 19:41:04 -0500 Subject: [Coco] CoCo Keys2USB - Problem In-Reply-To: <5ea89f0e9f900e4911838cc2860eb922@jechar.ca> References: <92b369240a6f0a81e888e044a17d9d5c@jechar.ca> <20210812192923.23b95841@Manfred.lan> <615957394bdbf2a4d1f35ffe844c4d7c@jechar.ca> <1945305346.561172.1629027794252@mail.yahoo.com> <5ea89f0e9f900e4911838cc2860eb922@jechar.ca> Message-ID: <20210816194104.7c810438@Manfred.lan> On Mon, 16 Aug 2021 17:45:47 -0400 coco at jechar.ca wrote: > > Yes I am using a Real Coco keyboard though a device that adapts it to > USB. I will have to download this new Vcc and remap the keys. > I'd be curious to know what the Keys2USB is sending without VCC. Can you open a console and type to see what it is sending? It is a USB keyboard after all. Also can you tell us what 'map' the Keys2USB is in? Or does it not output a V, X, or M after you press SHIFT+F2? [Big Snip] Christopher R. Hawks HAWKSoft -- By the time you make ends meet, they move the ends. ---------------------------------------- \ ^__^ \ (oo)\_______ (__)\ )\/\ ||----w | || || From fiscap0768 at gmail.com Mon Aug 16 21:16:11 2021 From: fiscap0768 at gmail.com (Paul F) Date: Mon, 16 Aug 2021 21:16:11 -0400 Subject: [Coco] CoCo Keys2USB - Problem In-Reply-To: <1945305346.561172.1629027794252@mail.yahoo.com> References: <92b369240a6f0a81e888e044a17d9d5c@jechar.ca> <20210812192923.23b95841@Manfred.lan> <615957394bdbf2a4d1f35ffe844c4d7c@jechar.ca> <1945305346.561172.1629027794252@mail.yahoo.com> Message-ID: Thanks for the heads-up Bill - I thought this might be the case, but wanted to confirm with my setup to verify it. I just got home from a trip and tested the different custom Keyboard options in VCC. Charlie - please check the Configuration of your VCC setup - Configuration/Config and select Keyboard tab - you want to make sure that you have CoCo (DECB) selected from the drop-down menu when using the physical CoCo keyboard with the Keys2USB encoder. Paul On Sun, Aug 15, 2021 at 7:53 AM Bill Pierce via Coco wrote: > Paul, VCC uses a PC keyboard. You have the option of "emulating" the > layout of an actual Coco keyboard or use it as a PC keyboard. The PC layout > is labeled as OS9 (nothing to do with OS9 itself). If he is using a real > Coco keyboard, then he needs to use the Coco keymap in VCC or keys will be > missing. The layout of the keymaps are in the manual. There is also a > custom keymap editor in which the keys can be remapped to any desired > location. > Bill P. (VCC Dev Team) > > BTW, I haven't been posting the updates here, but the latest release of > VCC is here... > > https://github.com/VCCE/VCC/releases/tag/v2.1.0d > > > -----Original Message----- > From: Paul F > To: CoCoList for Color Computer Enthusiasts > Sent: Sat, Aug 14, 2021 8:13 am > Subject: Re: [Coco] CoCo Keys2USB - Problem > > Charlie - > > I'm out of town for the weekend and won't be able to test your setup until > Monday evening, but are you able to verify that this behavior is only > present in OS-9 versus in VCC DECB by itself? It's the first I'm hearing of > the potential issue and it's possible that OS-9 requires a separate key > map. > > The software/repository is open source and is fairly well documented. I did > this so that anyone who has a device and wants to create custom keymaps or > add functionality, will have the ability to do so. The flashing procedure > involves installing the freely available Arduino IDE, updating the code > from GitHub, and uploading the modified code from the IDE to the Pro Micro > over a standard USB cable. This process is fairly well documented and there > are numerous videos out there that can get you started if you're a > beginner. > > If OS-9 does require a separate key map, I should have some time next week > to create one and upload the changes to the GitHub repo. > > Paul > > On Fri, Aug 13, 2021 at 4:47 PM wrote: > > > > > I found the documentation and with a by cutting a piece of a used google > > play card to size I replaced the lost nylon and I got the keyboard > > working. > > > > However there are issues. > > > > 1. The documentation says "You can tell which key map is selected as a > > ?V?, ?X?, or ?M? will display on the screen ? indicating ?VCC?, ?XRoar?, > > and ?MAME? respectively." however this does not happen. > > > > I am using Vcc and in OS9 CLEAR works fine and as do the arrow keys and > > the alphabet and numbers but much of the top row works incorrectly for > > example > > > > [SHIFT2] gets @ and should get a " > > by the way the notation here > > [SHIFT2] means hold down the shift key and the 2 key at the same > > time. > > [SHIFT6] gets ^ and should get & > > [SHIFT7] gets & and should get ' > > [SHIFT8] gets * and should get ( > > [SHIFT9] gets ( and should get ) > > [SHIFT0] gets ) and should not > > [:] by which I mean pressing the : key which is in the top row on a > > COCO. > > [:] gets a - but should get a : > > [SHIFT:] gets an underscore but should get a * > > [-] gets a = should get a - "minus" > > [SHIFT-] should get an = but gets a + > > [CTRL-] should get an underscore but gets an = > > > > And finally BREAK and ESCAPE do not seem to work. > > > > Is there a way to fix this. Will there be a software update to fix > > these and is there a way to update I did not notice if there is a > > PROGRAM button like on a pi pico and in the documentation included > > no Info about flashing in new keyboard maps. > > > > Charlie > > > > > > On 2021-08-12 22:49, Paul F wrote: > > > Charlie - > > > > > > The CoCo Keys2USB is my project. There are two links on the Tindie site > > > - > > > one for the source code and one for the .pdf version of the > > > documentation. > > > It sounds like you clicked the first link which brings you to the > > > GitHub > > > repository, and the readme.md file that you mentioned in your post is > > > an > > > industry standard markdown document which accompanies most git > > > repositories. It can be viewed with a standard text viewer or is > > > rendered > > > through any HTML viewer/browser. > > > > > > I believe the document you need though is the second link, which can be > > > accessed here - > > > > > > https://github.com/wyndec/CoCoKeys2USB/blob/master/docs/CoCo%20Keys2USB%20v1.2%20Instruction%20Sheet.pdf > > > > > > The thin piece of plastic you referred to in your original post is just > > > a > > > clear piece of nylon cut from a milk jug. It's only purpose is to > > > provide a > > > non-conductive wedge between the flat-flex mylar keyboard cable and the > > > 2x16 card edge connector on the Keys2USB kit. As the documentation > > > mentions, you want to have that under (on the non-conductive) side of > > > the > > > mylar cable to ensure the conductive (upper) side of the cable makes a > > > firm > > > and solid contact with the card edge connector. > > > > > > Also, the kit is designed so that the card edge connector could be used > > > in > > > both orientations (with the micro USB connector either on the left or > > > the > > > right). The important thing is that in either orientation, the nylon > > > wedge > > > is on the underside of the flat-flex mylar cable. > > > > > > Paul > > > > > > On Thu, Aug 12, 2021 at 9:53 PM wrote: > > > > > >> Ok I found some documentation at > > >> https://www.tindie.com/products/fiscap0768/coco-keys2usb-kit/ but it > > >> was > > >> .md format I do not have a program to > > >> read that why did they not stick to a standard like .docx or .pdf > > >> > > >> Do you know someone who can convert it to .pdf if I email it to them. > > >> > > >> Charlie. > > >> > > >> On 2021-08-12 20:29, Christopher R. Hawks wrote: > > >> > On Thu, 12 Aug 2021 20:16:44 -0400 > > >> > coco at jechar.ca wrote: > > >> > > > >> >> > > >> >> Hi I have a CoCo Keys2USB which I have used in the past however the > > >> >> piece of plastic holds in the keyboard ribbon cable must have > fallen > > >> >> out and when I moved the keyboard and realized that the connection > > >> >> had come loose and I am not sure which is the correct way to plug > it > > >> >> in nor do I know if I plug it in the wrong way If I will destroy it > > >> >> can't find the documentation I had nor does there seem to be a PDF > > >> >> online can anyone help. > > >> >> > > >> >> Charlie > > >> >> > > >> > > > >> > A quick search with DuckDuckGo shows the kit web page is here: > > >> > https://www.tindie.com/products/fiscap0768/coco-keys2usb-kit/ > > >> > > > >> > It includes links to the documentation and source code. > > >> > > > >> > > > >> > Christopher R. Hawks > > >> > HAWKSoft > > >> > -- > > >> > Piglet noticed that even though he had a very small heart, > > >> > it could hold a rather large amount of gratitude. > > >> > ---Winnie Ther Pooh > > >> > ---------------------------------------- > > >> > \ ^__^ > > >> > \ (oo)\_______ > > >> > (__)\ )\/\ > > >> > ||----w | > > >> > || || > > >> > > >> -- > > >> 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 > > > > -- > 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 > From johnmarkmelanie at gmail.com Mon Aug 16 22:25:37 2021 From: johnmarkmelanie at gmail.com (Melanie and John Mark Mobley) Date: Mon, 16 Aug 2021 21:25:37 -0500 Subject: [Coco] Glenside Color Computer Club, Inc. Demo Meeting and Business Meeting In-Reply-To: <008301d78f7d$54694cb0$fd3be610$@bds-soft.com> References: <009b01d78f25$271a5cc0$754f1640$@gmail.com> <008301d78f7d$54694cb0$fd3be610$@bds-soft.com> Message-ID: <023101d7930f$2ae17490$80a45db0$@gmail.com> M. David Johnson, Currently the Demo is not recorded but the Business Meeting is recorded. Jim Brain starts the recording. I don't know where the recordings are kept. There are some podcast on the CoCo. The podcast are available in "audio only" and "audio and video". Links: http://cococrew.org/ https://www.youtube.com/playlist?list=PLlHPSI-9Teu7WDQDrXQSEZecKYn41IvuN http://cocotalk.live/video-episodes/ -John Mark Mobley -----Original Message----- From: Coco [mailto:coco-bounces at maltedmedia.com] On Behalf Of M. David Johnson Sent: Thursday, August 12, 2021 8:24 AM To: 'CoCoList for Color Computer Enthusiasts' Subject: Re: [Coco] Glenside Color Computer Club, Inc. Demo Meeting and Business Meeting Neat concept! Unfortunately, since I'm a Trustee of the Glenview Public Library, and since the Board also meets on the third Thursdays, I pretty much always have to miss the Glenside meetings. Will the Demos be recorded and archived somewhere for future reference? -- M. David Johnson mdj at bds-soft.com From president at glensideccc.com Mon Aug 16 22:38:53 2021 From: president at glensideccc.com (Glenside President (Jim Brain)) Date: Mon, 16 Aug 2021 21:38:53 -0500 Subject: [Coco] Glenside Color Computer Club, Inc. Demo Meeting and Business Meeting In-Reply-To: <023101d7930f$2ae17490$80a45db0$@gmail.com> References: <009b01d78f25$271a5cc0$754f1640$@gmail.com> <008301d78f7d$54694cb0$fd3be610$@bds-soft.com> <023101d7930f$2ae17490$80a45db0$@gmail.com> Message-ID: On 8/16/2021 9:25 PM, Melanie and John Mark Mobley wrote: > M. David Johnson, > > Currently the Demo is not recorded but the Business Meeting is recorded. Jim > Brain starts the recording. I don't know where the recordings are kept. I stream the meeting to Facebook, so there's a record there. Jim -- Jim Brain, 2020-21 President Glenside Color Computer Club (GCCC) president at glensideccc.com www.glensideccc.com From mdj at bds-soft.com Tue Aug 17 09:24:01 2021 From: mdj at bds-soft.com (M. David Johnson) Date: Tue, 17 Aug 2021 08:24:01 -0500 Subject: [Coco] Glenside Color Computer Club, Inc. Demo Meeting and Business Meeting In-Reply-To: <023101d7930f$2ae17490$80a45db0$@gmail.com> References: <009b01d78f25$271a5cc0$754f1640$@gmail.com> <008301d78f7d$54694cb0$fd3be610$@bds-soft.com> <023101d7930f$2ae17490$80a45db0$@gmail.com> Message-ID: <00cf01d7936b$24ea0820$6ebe1860$@bds-soft.com> Thanks - I'll hunt around and see what I can find. -- M. David Johnson mdj at bds-soft.com -----Original Message----- From: Coco [mailto:coco-bounces at maltedmedia.com] On Behalf Of Melanie and John Mark Mobley Sent: Monday, August 16, 2021 9:26 PM To: 'CoCoList for Color Computer Enthusiasts' Subject: Re: [Coco] Glenside Color Computer Club, Inc. Demo Meeting and Business Meeting M. David Johnson, Currently the Demo is not recorded but the Business Meeting is recorded. Jim Brain starts the recording. I don't know where the recordings are kept. There are some podcast on the CoCo. The podcast are available in "audio only" and "audio and video". Links: http://cococrew.org/ https://www.youtube.com/playlist?list=PLlHPSI-9Teu7WDQDrXQSEZecKYn41IvuN http://cocotalk.live/video-episodes/ -John Mark Mobley -----Original Message----- From: Coco [mailto:coco-bounces at maltedmedia.com] On Behalf Of M. David Johnson Sent: Thursday, August 12, 2021 8:24 AM To: 'CoCoList for Color Computer Enthusiasts' Subject: Re: [Coco] Glenside Color Computer Club, Inc. Demo Meeting and Business Meeting Neat concept! Unfortunately, since I'm a Trustee of the Glenview Public Library, and since the Board also meets on the third Thursdays, I pretty much always have to miss the Glenside meetings. Will the Demos be recorded and archived somewhere for future reference? -- M. David Johnson mdj at bds-soft.com -- Coco mailing list Coco at maltedmedia.com https://pairlist5.pair.net/mailman/listinfo/coco From mdj at bds-soft.com Tue Aug 17 09:24:44 2021 From: mdj at bds-soft.com (M. David Johnson) Date: Tue, 17 Aug 2021 08:24:44 -0500 Subject: [Coco] Glenside Color Computer Club, Inc. Demo Meeting and Business Meeting In-Reply-To: References: <009b01d78f25$271a5cc0$754f1640$@gmail.com> <008301d78f7d$54694cb0$fd3be610$@bds-soft.com> <023101d7930f$2ae17490$80a45db0$@gmail.com> Message-ID: <00d101d7936b$3e51f020$baf5d060$@bds-soft.com> Thanks. I'm not on facebook though. -- M. David Johnson mdj at bds-soft.com -----Original Message----- From: Coco [mailto:coco-bounces at maltedmedia.com] On Behalf Of Glenside President (Jim Brain) via Coco Sent: Monday, August 16, 2021 9:39 PM To: coco at maltedmedia.com Cc: Glenside President (Jim Brain) Subject: Re: [Coco] Glenside Color Computer Club, Inc. Demo Meeting and Business Meeting On 8/16/2021 9:25 PM, Melanie and John Mark Mobley wrote: > M. David Johnson, > > Currently the Demo is not recorded but the Business Meeting is recorded. Jim > Brain starts the recording. I don't know where the recordings are kept. I stream the meeting to Facebook, so there's a record there. Jim -- Jim Brain, 2020-21 President Glenside Color Computer Club (GCCC) president at glensideccc.com www.glensideccc.com -- Coco mailing list Coco at maltedmedia.com https://pairlist5.pair.net/mailman/listinfo/coco From go4retro at go4retro.com Tue Aug 17 10:15:52 2021 From: go4retro at go4retro.com (RETRO Innovations) Date: Tue, 17 Aug 2021 09:15:52 -0500 Subject: [Coco] Glenside Color Computer Club, Inc. Demo Meeting and Business Meeting In-Reply-To: <00d101d7936b$3e51f020$baf5d060$@bds-soft.com> References: <009b01d78f25$271a5cc0$754f1640$@gmail.com> <008301d78f7d$54694cb0$fd3be610$@bds-soft.com> <023101d7930f$2ae17490$80a45db0$@gmail.com> <00d101d7936b$3e51f020$baf5d060$@bds-soft.com> Message-ID: <394773cc-049d-8734-75aa-63c1af7257c3@go4retro.com> On 8/17/2021 8:24 AM, M. David Johnson wrote: > Thanks. I'm not on facebook though. I understand. I've been trying to stream to Youtube as well, but I can't seem to get the account to allow it (my normal account does, it's just the glenside google (youtube) account). I didn't work on it very much, since the streaming is not a requirement, just a value add, but I can take another look. Jim From coco at jechar.ca Tue Aug 17 22:41:57 2021 From: coco at jechar.ca (coco at jechar.ca) Date: Tue, 17 Aug 2021 22:41:57 -0400 Subject: [Coco] CoCo Keys2USB - Problem In-Reply-To: <20210816194104.7c810438@Manfred.lan> References: <92b369240a6f0a81e888e044a17d9d5c@jechar.ca> <20210812192923.23b95841@Manfred.lan> <615957394bdbf2a4d1f35ffe844c4d7c@jechar.ca> <1945305346.561172.1629027794252@mail.yahoo.com> <5ea89f0e9f900e4911838cc2860eb922@jechar.ca> <20210816194104.7c810438@Manfred.lan> Message-ID: <779b0fdf369787e8539d7859498690d8@jechar.ca> On 2021-08-16 20:41, Christopher R. Hawks wrote: > On Mon, 16 Aug 2021 17:45:47 -0400 > coco at jechar.ca wrote: > >> >> Yes I am using a Real Coco keyboard though a device that adapts it to >> USB. I will have to download this new Vcc and remap the keys. >> > > I'd be curious to know what the Keys2USB is sending without VCC. > Can you open a console and type to see what it is sending? It is a USB > keyboard after all. > > Also can you tell us what 'map' the Keys2USB is in? Or does it not > output a V, X, or M after you press SHIFT+F2? > > [Big Snip] > > > Christopher R. Hawks > HAWKSoft > -- > By the time you make ends meet, they move the ends. > ---------------------------------------- > \ ^__^ > \ (oo)\_______ > (__)\ )\/\ > ||----w | > || || I will send you the results of typing into a terminal tomarrow. But right now I can tell you that SHIFT+F2 is problematic because the desktop wants to do other things with that keystroke combo. In XFCE you are supposed to be able to disable it but I got no indication that it was working even after disabeling it in XFCE in Cinnamon my usual desktop I cannot even figure out how to disable the Desktop stealing those keys. Charlie From president at glensideccc.com Wed Aug 18 00:51:43 2021 From: president at glensideccc.com (Glenside President (Jim Brain)) Date: Tue, 17 Aug 2021 23:51:43 -0500 Subject: [Coco] Glenside Club Meeting: Thursday August 19, 2021 @ 7:30PM Message-ID: <43933e7c-fa26-98f0-cf54-cd00e978ad9f@glensideccc.com> I hope everyone stepped away from your Color Computer 1 chicklet keyboard long enough to enjoy the Summer weather, especially as some of us now hunker down for the Fall, especially as school discussions now fill the air. We'll all have to adapt to younger children returning to school, young adults navigating college, and many of us needing to adjust to that part of the year when Summer help leaves and businesses start closing earlier. While I am rather glad my principal educational career has long ago completed, I do try to stay engaged on new developments all over the spectrum. And, with the continued challenges in the world encouraging hobbies and projects that focus on individual contributions, I?m eager to see all of the developments the CoCo community has kept under wraps for the past year or so. Some have been unveiled, but I think others will make their appearance at shows like the 2021 CoCoFEST! Speaking of the show, we?re less than 3 months away from congregating in the Chicago area for some community and collaboration. It?ll be the first year in our new venue, and I do hope you?ll consider joining us, if you can. I know politics intrude in the hobby at times, but I hope a majority of our membership (and visitors) can join us to belatedly celebrate the Color Computer?s 40th anniversary. Even as we focus on the 2021 show, we?re making plans for our 2022 show in mid-May next year. I?m sure that will present its own specific challenges, but we?ll rise to them as well! We?re fast approaching the general vintage computing festival period, with shows like the Vintage Computer Festival Southeast occurring this weekend, VCF Midwest kicking off in September, followed by Tandy Assembly and VCF East in October, and CoCoFEST! in November. For those of us attending multiple shows, it?ll be a wild few months of activity. Please join us this Thursday, August 19th, to get updates on the club and activities. And, if you?re interested in more social perspectives, please consider joining the call at 6:30PM Central (1 hour prior). It?s a great opportunity to visit with far flung members, watch some demonstrations, hear about projects, and just enjoy some humor. To join the Meeting: https://bluejeans.com/889394355 You can call in: Phone Dial-in +1.408.740.7256 (United States) +1.408.317.9253 (Alternate number) (Global Numbers) Meeting ID: 889 394 355 Room System: 199.48.152.152 or bjn.vc Want to test your video connection? https://bluejeans.com/111 For those unable to join us for the meeting, we hope to have a replay available on our Facebook page (https://www.facebook.com/groups/290791956162) to help you catch up. Prior to the formal business meeting at 7:30PM Central, we?ll be enjoying a time of demonstrations and discussion. If you?d like to show a project you?re working on, please consider joining us starting at 6:30PM. -- Jim Brain, 2020-21 President Glenside Color Computer Club (GCCC) president at glensideccc.com www.glensideccc.com From allencoco at yahoo.com Wed Aug 18 03:49:25 2021 From: allencoco at yahoo.com (Joshua Harper) Date: Wed, 18 Aug 2021 02:49:25 -0500 Subject: [Coco] (no subject) References: <5C5D1766-73EA-4513-B00F-D472A93D0422.ref@yahoo.com> Message-ID: <5C5D1766-73EA-4513-B00F-D472A93D0422@yahoo.com> Hi guys I?m looking for somebody that is good with soldering I have a video plus board that goes into a Coco one it is the little board that has the video out cable and the audio out cable then and from the little board you have several very tiny wires that go to a socket for the 1372 chip wires have broken off between the board and the socket and I Cannot see well enough to fix it the video cable looks like it?s been displaced and fixed at one point and there is some sort of circuit running across the chip into a couple of the pins on the socket now my original one did not have that Looking for someone that would be willing to fix this I am wanting to put it into one of my white Coco ones any help would be appreciated thanks Also if anybody has any of these boards I might be willing to purchase them for my other Coco ones thanks again From wieselerb at gmail.com Wed Aug 18 07:12:44 2021 From: wieselerb at gmail.com (Brian Wieseler) Date: Wed, 18 Aug 2021 06:12:44 -0500 Subject: [Coco] (no subject) In-Reply-To: <5C5D1766-73EA-4513-B00F-D472A93D0422@yahoo.com> References: <5C5D1766-73EA-4513-B00F-D472A93D0422@yahoo.com> Message-ID: <6E0369AF-C2B7-4183-9B85-449DA53A6D02@gmail.com> Joshua, I can solder it for you. I think I have one of those boards I can compare it to as well. If you want to put it in the box with the one items I would be happy to take a look at it. Brian Wieseler Sent from my iPhone > On Aug 18, 2021, at 2:50 AM, Joshua Harper via Coco wrote: > > ?Hi guys I?m looking for somebody that is good with soldering I have a video plus board that goes into a Coco one it is the little board that has the video out cable and the audio out cable then and from the little board you have several very tiny wires that go to a socket for the 1372 chip wires have broken off between the board and the socket and I Cannot see well enough to fix it the video cable looks like it?s been displaced and fixed at one point and there is some sort of circuit running across the chip into a couple of the pins on the socket now my original one did not have that > > Looking for someone that would be willing to fix this I am wanting to put it into one of my white Coco ones any help would be appreciated thanks > Also if anybody has any of these boards I might be willing to purchase them for my other Coco ones thanks again > > -- > Coco mailing list > Coco at maltedmedia.com > https://pairlist5.pair.net/mailman/listinfo/coco From idevgames at gmail.com Thu Aug 19 09:31:22 2021 From: idevgames at gmail.com (Carlos Camacho) Date: Thu, 19 Aug 2021 09:31:22 -0400 Subject: [Coco] video plus board In-Reply-To: References: Message-ID: Joshua, Where do you live? A potential 'quick fix' if you can't solder is to use a small little push clip on both ends of a wire. You push the button on the back of the clip and a small little metal hook comes out. You can then hook the little metal hook around an IC pin. Under the button is where the wire would wrap to. So... IC -- CLIP --- WIRE --- CLIP -- IC An example: https://www.digikey.com/en/products/detail/e-z-hook/X100WRED/528235 There are many other styles and they are very cheap. While not as ideal as soldering, it would do the job for something like the composite video. Cheers Carlos Camacho Color Computer Store From coco at jechar.ca Thu Aug 19 10:23:37 2021 From: coco at jechar.ca (coco at jechar.ca) Date: Thu, 19 Aug 2021 10:23:37 -0400 Subject: [Coco] CoCo Keys2USB - Problem Message-ID: <6b3d2d9cb723b4dbac59e1f6949f2aeb@jechar.ca> The problems I am still having with Coco Keys2USB with the RSDOS keymap chosen in Vcc are 1. The [Ctrl -] combo is not making an underscore and and the Arrow keys do not work in OS9 also since keymaps cannot be changed on the fly I can't just switch back and forth between OS9 and RS-DOS keymaps depending on what I need at the time, even If I could It would be a hassel. Charlie On 2021-08-17 22:41, coco at jechar.ca wrote: > On 2021-08-16 20:41, Christopher R. Hawks wrote: >> On Mon, 16 Aug 2021 17:45:47 -0400 >> coco at jechar.ca wrote: >> >>> >>> Yes I am using a Real Coco keyboard though a device that adapts it to >>> USB. I will have to download this new Vcc and remap the keys. >>> >> >> I'd be curious to know what the Keys2USB is sending without VCC. >> Can you open a console and type to see what it is sending? It is a USB >> keyboard after all. >> >> Also can you tell us what 'map' the Keys2USB is in? Or does it not >> output a V, X, or M after you press SHIFT+F2? >> >> [Big Snip] >> >> >> Christopher R. Hawks >> HAWKSoft >> -- >> By the time you make ends meet, they move the ends. >> ---------------------------------------- >> \ ^__^ >> \ (oo)\_______ >> (__)\ )\/\ >> ||----w | >> || || > > > I will send you the results of typing into a terminal tomarrow. > But right now I can tell you that SHIFT+F2 is problematic because > the desktop wants to do other things with that keystroke combo. > > In XFCE you are supposed to be able to disable it but I got no > indication > that it was working even after disabeling it in XFCE in Cinnamon my > usual > desktop I cannot even figure out how to disable the Desktop stealing > those keys. > > Charlie From coco at jechar.ca Thu Aug 19 10:29:33 2021 From: coco at jechar.ca (coco at jechar.ca) Date: Thu, 19 Aug 2021 10:29:33 -0400 Subject: [Coco] Looking for Most Recent Vcc. Executable for Windows. Message-ID: I have found reference to a Vcc version dated 2015-08-26 On Source Forge Is there something more recent particularly a version that includes a keymap editor. I can choose between three keymaps but none of them are suitable. Charlie From mdj at bds-soft.com Thu Aug 19 10:35:17 2021 From: mdj at bds-soft.com (M. David Johnson) Date: Thu, 19 Aug 2021 09:35:17 -0500 Subject: [Coco] Looking for Most Recent Vcc. Executable for Windows. In-Reply-To: References: Message-ID: <001801d79507$6ea49af0$4bedd0d0$@bds-soft.com> https://github.com/VCCE/VCC/releases is Bill Pierce's page on this. Ignore the top (2.1.0c) entry (I think they may have accidentally got out of order) and go to the second (2.1.0d) entry - it was released 2021/07/03. -- M. David Johnson mdj at bds-soft.com -----Original Message----- From: Coco [mailto:coco-bounces at maltedmedia.com] On Behalf Of coco at jechar.ca Sent: Thursday, August 19, 2021 9:30 AM To: Coco List Subject: [Coco] Looking for Most Recent Vcc. Executable for Windows. I have found reference to a Vcc version dated 2015-08-26 On Source Forge Is there something more recent particularly a version that includes a keymap editor. I can choose between three keymaps but none of them are suitable. Charlie -- Coco mailing list Coco at maltedmedia.com https://pairlist5.pair.net/mailman/listinfo/coco From ejjaquay at gmail.com Thu Aug 19 16:42:23 2021 From: ejjaquay at gmail.com (edward jaquay) Date: Thu, 19 Aug 2021 16:42:23 -0400 Subject: [Coco] Looking for Most Recent Vcc. Executable for Windows. In-Reply-To: References: Message-ID: Once you get the Vcv 2.1.0d version installed and try out the custom key map editor let us know how it works for you. If you have trouble please ask for help. The editor should be able to deal with a non standard keyboard as long as you don't have to remap the shift, ctrl, or alt keys. Also I wrote the editor and am looking for feedback on how it can be improved. On Thu, Aug 19, 2021, 10:29 AM wrote: > > I have found reference to a Vcc version dated 2015-08-26 > On Source Forge Is there something more recent particularly > a version that includes a keymap editor. > > I can choose between three keymaps but none of them are suitable. > > Charlie > > -- > Coco mailing list > Coco at maltedmedia.com > https://pairlist5.pair.net/mailman/listinfo/coco > From go4retro at go4retro.com Thu Aug 19 22:44:15 2021 From: go4retro at go4retro.com (RETRO Innovations) Date: Thu, 19 Aug 2021 21:44:15 -0500 Subject: [Coco] Glenside Color Computer Club, Inc. Demo Meeting and Business Meeting In-Reply-To: <00d101d7936b$3e51f020$baf5d060$@bds-soft.com> References: <009b01d78f25$271a5cc0$754f1640$@gmail.com> <008301d78f7d$54694cb0$fd3be610$@bds-soft.com> <023101d7930f$2ae17490$80a45db0$@gmail.com> <00d101d7936b$3e51f020$baf5d060$@bds-soft.com> Message-ID: <9f0e3c82-1590-c801-edca-cc2492235d1d@go4retro.com> On 8/17/2021 8:24 AM, M. David Johnson wrote: > Thanks. I'm not on facebook though. Miraculously, I was able to get streaming to work on Youtube, so here's the August meeting: https://www.youtube.com/watch?v=fvH7VEojrHQ From go4retro at go4retro.com Thu Aug 19 23:12:58 2021 From: go4retro at go4retro.com (RETRO Innovations) Date: Thu, 19 Aug 2021 22:12:58 -0500 Subject: [Coco] Glenside Color Computer Club, Inc. Demo Meeting and Business Meeting In-Reply-To: <9f0e3c82-1590-c801-edca-cc2492235d1d@go4retro.com> References: <009b01d78f25$271a5cc0$754f1640$@gmail.com> <008301d78f7d$54694cb0$fd3be610$@bds-soft.com> <023101d7930f$2ae17490$80a45db0$@gmail.com> <00d101d7936b$3e51f020$baf5d060$@bds-soft.com> <9f0e3c82-1590-c801-edca-cc2492235d1d@go4retro.com> Message-ID: <17038974-82a8-836b-fc47-26c12f9e7c1b@go4retro.com> On 8/19/2021 9:44 PM, RETRO Innovations wrote: > On 8/17/2021 8:24 AM, M. David Johnson wrote: >> Thanks. I'm not on facebook though. > > Miraculously, I was able to get streaming to work on Youtube, so > here's the August meeting: > > > https://www.youtube.com/watch?v=fvH7VEojrHQ > Perhaps Eric Canales will dload the Facebook meetings from June and July and post on YT. Jim -- RETRO Innovations, Contemporary Gear for Classic Systems www.go4retro.com store.go4retro.com From ooogalapasooo at aol.com Fri Aug 20 07:37:43 2021 From: ooogalapasooo at aol.com (Bill Pierce) Date: Fri, 20 Aug 2021 11:37:43 +0000 (UTC) Subject: [Coco] Looking for Most Recent Vcc. Executable for Windows. In-Reply-To: References: Message-ID: <1332121195.397442.1629459463579@mail.yahoo.com> The most recent version of VCC is here: https://github.com/VCCE/VCC/releases/tag/v2.1.0d -----Original Message----- From: coco at jechar.ca To: Coco List Sent: Thu, Aug 19, 2021 10:29 am Subject: [Coco] Looking for Most Recent Vcc. Executable for Windows. I have found reference to a Vcc version dated 2015-08-26 On Source Forge Is there something more recent particularly a version that includes a keymap editor. I can choose between three keymaps but none of them are suitable. Charlie -- Coco mailing list Coco at maltedmedia.com https://pairlist5.pair.net/mailman/listinfo/coco From ooogalapasooo at aol.com Fri Aug 20 07:39:26 2021 From: ooogalapasooo at aol.com (Bill Pierce) Date: Fri, 20 Aug 2021 11:39:26 +0000 (UTC) Subject: [Coco] Looking for Most Recent Vcc. Executable for Windows. In-Reply-To: <001801d79507$6ea49af0$4bedd0d0$@bds-soft.com> References: <001801d79507$6ea49af0$4bedd0d0$@bds-soft.com> Message-ID: <1461441542.409144.1629459566738@mail.yahoo.com> Yeah, the 210c version got bumped up to "Most Recent" somehow by GitHub and it won't let me bump 210d up -----Original Message----- From: M. David Johnson To: 'CoCoList for Color Computer Enthusiasts' Sent: Thu, Aug 19, 2021 10:35 am Subject: Re: [Coco] Looking for Most Recent Vcc. Executable for Windows. https://github.com/VCCE/VCC/releases is Bill Pierce's page on this. Ignore the top (2.1.0c) entry (I think they may have accidentally got out of order) and go to the second (2.1.0d) entry - it was released 2021/07/03. -- M. David Johnson mdj at bds-soft.com -----Original Message----- From: Coco [mailto:coco-bounces at maltedmedia.com] On Behalf Of coco at jechar.ca Sent: Thursday, August 19, 2021 9:30 AM To: Coco List Subject: [Coco] Looking for Most Recent Vcc. Executable for Windows. I have found reference to a Vcc version dated 2015-08-26 On Source Forge Is there something more recent particularly a version that includes a keymap editor. I can choose between three keymaps but none of them are suitable. Charlie -- 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 From coco at jechar.ca Fri Aug 20 10:26:54 2021 From: coco at jechar.ca (coco at jechar.ca) Date: Fri, 20 Aug 2021 10:26:54 -0400 Subject: [Coco] Looking for Most Recent Vcc. Executable for Windows. & Coco Key2USB In-Reply-To: References: Message-ID: <50e3b6f04ee66575dc0e9e00a0026394@jechar.ca> Ok thanks Vcc 2.1.0d does have a editor for custom keys. But I was wondering if I have to program every single key or if there is a way to start with an existing keymap and just change the ones that are a problem. If there was some "OS9keymap.ini" that I could just copy to "Custom.ini" in Windows explorer first and just change the problem keys in the editor that would be great but I do not see even a keyboard.ini in the C:\PROGRAMS\Vcc 2.1.0d directory but maybe I am looking in the wrong place ? Charlie. On 2021-08-19 16:42, edward jaquay wrote: > Once you get the Vcv 2.1.0d version installed and try out the custom > key > map editor let us know how it works for you. If you have trouble > please > ask for help. The editor should be able to deal with a non standard > keyboard as long as you don't have to remap the shift, ctrl, or alt > keys. > Also I wrote the editor and am looking for feedback on how it can be > improved. > > On Thu, Aug 19, 2021, 10:29 AM wrote: > >> >> I have found reference to a Vcc version dated 2015-08-26 >> On Source Forge Is there something more recent particularly >> a version that includes a keymap editor. >> >> I can choose between three keymaps but none of them are suitable. >> >> Charlie >> >> -- >> Coco mailing list >> Coco at maltedmedia.com >> https://pairlist5.pair.net/mailman/listinfo/coco >> Thanks From robert.gault at att.net Fri Aug 20 10:50:33 2021 From: robert.gault at att.net (Robert Gault) Date: Fri, 20 Aug 2021 14:50:33 +0000 (UTC) Subject: [Coco] Looking for Most Recent Vcc. Executable for Windows. & Coco Key2USB In-Reply-To: <50e3b6f04ee66575dc0e9e00a0026394@jechar.ca> References: <50e3b6f04ee66575dc0e9e00a0026394@jechar.ca> Message-ID: <367628554.447964.1629471033332@mail.yahoo.com> You just need to change the keys you don't like. I think your changes will be retained regardless of which keyboard type you select. Sent from AT&T Yahoo Mail on Android From ejjaquay at gmail.com Fri Aug 20 15:01:59 2021 From: ejjaquay at gmail.com (edward jaquay) Date: Fri, 20 Aug 2021 15:01:59 -0400 Subject: [Coco] Looking for Most Recent Vcc. Executable for Windows. & Coco Key2USB In-Reply-To: <367628554.447964.1629471033332@mail.yahoo.com> References: <50e3b6f04ee66575dc0e9e00a0026394@jechar.ca> <367628554.447964.1629471033332@mail.yahoo.com> Message-ID: Robert you have a non official copy I gave you a link to for testing.that allows modification of any keymap. The official version only allows modification of the custom keymap. I expect the version you have will make it into the next release one testing is complete and Bill blesses it. On Fri, Aug 20, 2021, 10:50 AM Robert Gault wrote: > You just need to change the keys you don't like. I think your changes will > be retained regardless of which keyboard type you select. > > Sent from AT&T Yahoo Mail on Android > > > > From jrosslist at outlook.com Fri Aug 20 17:21:07 2021 From: jrosslist at outlook.com (James Ross) Date: Fri, 20 Aug 2021 21:21:07 +0000 Subject: [Coco] Looking for Most Recent Vcc. Executable for Windows. In-Reply-To: <1332121195.397442.1629459463579@mail.yahoo.com> References: <1332121195.397442.1629459463579@mail.yahoo.com> Message-ID: You have been doing a good job w/ the releases! I just have two suggestions: 1) drop the letters instead of v2.1.0d why not 2.1.4 .... what is the purpose of the letters if you have a 3rd numerical digit already. 2) on GitHub can we rename (or save off) the current "master" to something else, for example master_old and rename the VCC_2.0.1c to master? Have the "master" be the current version? James ________________________________________ From: Coco on behalf of Bill Pierce via Coco Sent: Friday, August 20, 2021 11:37 AM To: coco at maltedmedia.com Cc: Bill Pierce Subject: Re: [Coco] Looking for Most Recent Vcc. Executable for Windows. The most recent version of VCC is here: https://github.com/VCCE/VCC/releases/tag/v2.1.0d -----Original Message----- From: coco at jechar.ca To: Coco List Sent: Thu, Aug 19, 2021 10:29 am Subject: [Coco] Looking for Most Recent Vcc. Executable for Windows. I have found reference to a Vcc version dated 2015-08-26 On Source Forge Is there something more recent particularly a version that includes a keymap editor. I can choose between three keymaps but none of them are suitable. Charlie -- 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 From robert.gault at att.net Fri Aug 20 17:58:19 2021 From: robert.gault at att.net (Robert Gault) Date: Fri, 20 Aug 2021 21:58:19 +0000 (UTC) Subject: [Coco] Looking for Most Recent Vcc. Executable for Windows. & Coco Key2USB In-Reply-To: References: <50e3b6f04ee66575dc0e9e00a0026394@jechar.ca> <367628554.447964.1629471033332@mail.yahoo.com> Message-ID: <495127680.587190.1629496699227@mail.yahoo.com> Ah, I did not realize that. Sent from AT&T Yahoo Mail on Android On Fri, Aug 20, 2021 at 3:02 PM, edward jaquay wrote: Robert you have a non official copy I gave you a link to for testing.that allows modification of any keymap.The official version only allows modification of the custom keymap.? I expect the version you have will make it into the next release one testing is complete and Bill blesses it. On Fri, Aug 20, 2021, 10:50 AM Robert Gault wrote: You just need to change the keys you don't like. I think your changes will be retained regardless of which keyboard type you select. Sent from AT&T Yahoo Mail on Android From deek at d2dc.net Fri Aug 20 21:07:23 2021 From: deek at d2dc.net (Jeff Teunissen) Date: Fri, 20 Aug 2021 21:07:23 -0400 Subject: [Coco] Looking for Most Recent Vcc. Executable for Windows. In-Reply-To: References: <1332121195.397442.1629459463579@mail.yahoo.com> Message-ID: 1. is a good idea. There's very little reason to extend the patch level to a fourth level like that. 2. would probably not go well; "master" is the current code, not necessarily the current release. If you had, e.g. a "2.1" branch for all 2.1 releases, then you could tag each bug fix release as 2.1.1...2.1.999 on the 2.1 branch, while you do development on the master, "next", etc. branch. Then when you release 2.2.0, make a 2.2 branch for the bug fix releases of that. On Fri, Aug 20, 2021 at 5:21 PM James Ross wrote: > > You have been doing a good job w/ the releases! > > I just have two suggestions: > > 1) drop the letters instead of v2.1.0d why not 2.1.4 .... what is the purpose of the letters if you have a 3rd numerical digit already. > > 2) on GitHub can we rename (or save off) the current "master" to something else, for example master_old and rename the VCC_2.0.1c to master? Have the "master" be the current version? > > James > > ________________________________________ > From: Coco on behalf of Bill Pierce via Coco > Sent: Friday, August 20, 2021 11:37 AM > To: coco at maltedmedia.com > Cc: Bill Pierce > Subject: Re: [Coco] Looking for Most Recent Vcc. Executable for Windows. > > The most recent version of VCC is here: > > https://github.com/VCCE/VCC/releases/tag/v2.1.0d > > > -----Original Message----- > From: coco at jechar.ca > To: Coco List > Sent: Thu, Aug 19, 2021 10:29 am > Subject: [Coco] Looking for Most Recent Vcc. Executable for Windows. > > > I have found reference to a Vcc version dated 2015-08-26 > On Source Forge Is there something more recent particularly > a version that includes a keymap editor. > > I can choose between three keymaps but none of them are suitable. > > Charlie > > -- > 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 > > -- > Coco mailing list > Coco at maltedmedia.com > https://pairlist5.pair.net/mailman/listinfo/coco From coco at jechar.ca Fri Aug 20 21:28:28 2021 From: coco at jechar.ca (coco at jechar.ca) Date: Fri, 20 Aug 2021 21:28:28 -0400 Subject: [Coco] Looking for Most Recent Vcc. Executable for Windows. In-Reply-To: References: <1332121195.397442.1629459463579@mail.yahoo.com> Message-ID: I believe in this latest version of Vcc the keyboard ini files have been moved to a different directory. I see there is a keyboard editor but it does not seem to work. Is there documentation as to what each byte in the keyboard map files do I could probably create a custom keyboard with a disk editor and sufficient documentation. Charlie. On 2021-08-20 21:07, Jeff Teunissen wrote: > 1. is a good idea. There's very little reason to extend the patch > level to a fourth level like that. > > 2. would probably not go well; "master" is the current code, not > necessarily the current release. If you had, e.g. a "2.1" branch for > all 2.1 releases, then you could tag each bug fix release as > 2.1.1...2.1.999 on the 2.1 branch, while you do development on the > master, "next", etc. branch. Then when you release 2.2.0, make a 2.2 > branch for the bug fix releases of that. > > > On Fri, Aug 20, 2021 at 5:21 PM James Ross > wrote: >> >> You have been doing a good job w/ the releases! >> >> I just have two suggestions: >> >> 1) drop the letters instead of v2.1.0d why not 2.1.4 .... what is the >> purpose of the letters if you have a 3rd numerical digit already. >> >> 2) on GitHub can we rename (or save off) the current "master" to >> something else, for example master_old and rename the VCC_2.0.1c to >> master? Have the "master" be the current version? >> >> James >> >> ________________________________________ >> From: Coco on behalf of Bill Pierce via >> Coco >> Sent: Friday, August 20, 2021 11:37 AM >> To: coco at maltedmedia.com >> Cc: Bill Pierce >> Subject: Re: [Coco] Looking for Most Recent Vcc. Executable for >> Windows. >> >> The most recent version of VCC is here: >> >> https://github.com/VCCE/VCC/releases/tag/v2.1.0d >> >> >> -----Original Message----- >> From: coco at jechar.ca >> To: Coco List >> Sent: Thu, Aug 19, 2021 10:29 am >> Subject: [Coco] Looking for Most Recent Vcc. Executable for Windows. >> >> >> I have found reference to a Vcc version dated 2015-08-26 >> On Source Forge Is there something more recent particularly >> a version that includes a keymap editor. >> >> I can choose between three keymaps but none of them are suitable. >> >> Charlie >> >> -- >> 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 >> >> -- >> Coco mailing list >> Coco at maltedmedia.com >> https://pairlist5.pair.net/mailman/listinfo/coco From ooogalapasooo at aol.com Fri Aug 20 21:53:48 2021 From: ooogalapasooo at aol.com (Bill Pierce) Date: Sat, 21 Aug 2021 01:53:48 +0000 (UTC) Subject: [Coco] Looking for Most Recent Vcc. Executable for Windows. In-Reply-To: References: <1332121195.397442.1629459463579@mail.yahoo.com> Message-ID: <606804296.625401.1629510828820@mail.yahoo.com> To fix a permission problem with win7-10, all ini type files were moved to "user\%home%\appdata\VCC" (%home% is generic for the? current username and windows recognizes it as such). Pre win7 systems (Vista & XP) will default to "user\%home%\Documents\VCC" (I think). The keymap editor does indeed work and the operating info is in the manual. If you installed using the installer, the manual will be under "My Documents\Coco Manuals" and if you used the zip file it will be in your VCC installation folder. It should also show under the VCC group in your Start menu. -----Original Message----- From: coco at jechar.ca To: CoCoList for Color Computer Enthusiasts Cc: Jeff Teunissen Sent: Fri, Aug 20, 2021 9:28 pm Subject: Re: [Coco] Looking for Most Recent Vcc. Executable for Windows. I believe in this latest version of Vcc the keyboard ini files have been moved to? a different directory. I see there is a keyboard editor but it does not seem to work. Is there documentation as to what each byte in the keyboard map files do I could probably create a custom keyboard with a disk editor and sufficient documentation. Charlie. On 2021-08-20 21:07, Jeff Teunissen wrote: > 1. is a good idea. There's very little reason to extend the patch > level to a fourth level like that. > > 2. would probably not go well; "master" is the current code, not > necessarily the current release. If you had, e.g. a "2.1" branch for > all 2.1 releases, then you could tag each bug fix release as > 2.1.1...2.1.999 on the 2.1 branch, while you do development on the > master, "next", etc. branch. Then when you release 2.2.0, make a 2.2 > branch for the bug fix releases of that. > > > On Fri, Aug 20, 2021 at 5:21 PM James Ross > wrote: >> >> You have been doing a good job w/ the releases! >> >> I just have two suggestions: >> >> 1) drop the letters instead of v2.1.0d why not 2.1.4 .... what is the >> purpose of the letters if you have a 3rd numerical digit already. >> >> 2) on GitHub can we rename (or save off) the current "master" to >> something else, for example master_old? and rename the VCC_2.0.1c to >> master?? Have the "master" be the current version? >> >> James >> >> ________________________________________ >> From: Coco on behalf of Bill Pierce via >> Coco >> Sent: Friday, August 20, 2021 11:37 AM >> To: coco at maltedmedia.com >> Cc: Bill Pierce >> Subject: Re: [Coco] Looking for Most Recent Vcc. Executable for >> Windows. >> >> The most recent version of VCC is here: >> >> https://github.com/VCCE/VCC/releases/tag/v2.1.0d >> >> >> -----Original Message----- >> From: coco at jechar.ca >> To: Coco List >> Sent: Thu, Aug 19, 2021 10:29 am >> Subject: [Coco] Looking for Most Recent Vcc. Executable for Windows. >> >> >> I have found reference to a Vcc version dated 2015-08-26 >> On Source Forge Is there something more recent particularly >> a version that includes a keymap editor. >> >> I can choose between three keymaps but none of them are suitable. >> >> Charlie >> >> -- >> 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 >> >> -- >> 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 From ooogalapasooo at aol.com Fri Aug 20 22:05:45 2021 From: ooogalapasooo at aol.com (Bill Pierce) Date: Sat, 21 Aug 2021 02:05:45 +0000 (UTC) Subject: [Coco] Looking for Most Recent Vcc. Executable for Windows. In-Reply-To: References: <1332121195.397442.1629459463579@mail.yahoo.com> Message-ID: <401034783.609606.1629511545514@mail.yahoo.com> Personally, I don't see a problem with using letters in the version number. A lot of various software does this. Originally the idea was the letters were incremental updates and bug fixes and number (i.e. 2.1.0 to 2.1.1) would be major changes. Trying to manage it alone with (currently) one programmer (our other 2 had life issues and hope to be back soon) gets hectic sometimes and we're lucky to get new releases out LOL The "Master" fork was originally the current release until a former team member uploaded a completely unusable version that could not be stepped back to the current build, so the "201" fork was made to be current (it was originally our work area). I have been musing over rearranging everything to bring things back they way they should be, but time and patience are not on my side lately. Maybe soon. Again, I am but one man. LOL Bill P. -----Original Message----- From: James Ross To: CoCoList for Color Computer Enthusiasts Sent: Fri, Aug 20, 2021 5:21 pm Subject: Re: [Coco] Looking for Most Recent Vcc. Executable for Windows. You have been doing a good job w/ the releases! I just have two suggestions: 1) drop the letters instead of v2.1.0d why not 2.1.4 .... what is the purpose of the letters if you have a 3rd numerical digit already. 2) on GitHub can we rename (or save off) the current "master" to something else, for example master_old? and rename the VCC_2.0.1c to master?? Have the "master" be the current version? James ________________________________________ From: Coco on behalf of Bill Pierce via Coco Sent: Friday, August 20, 2021 11:37 AM To: coco at maltedmedia.com Cc: Bill Pierce Subject: Re: [Coco] Looking for Most Recent Vcc. Executable for Windows. The most recent version of VCC is here: https://github.com/VCCE/VCC/releases/tag/v2.1.0d -----Original Message----- From: coco at jechar.ca To: Coco List Sent: Thu, Aug 19, 2021 10:29 am Subject: [Coco] Looking for Most Recent Vcc. Executable for Windows. I have found reference to a Vcc version dated 2015-08-26 On Source Forge Is there something more recent particularly a version that includes a keymap editor. I can choose between three keymaps but none of them are suitable. Charlie -- 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 -- Coco mailing list Coco at maltedmedia.com https://pairlist5.pair.net/mailman/listinfo/coco From deek at d2dc.net Fri Aug 20 21:12:14 2021 From: deek at d2dc.net (Jeff Teunissen) Date: Fri, 20 Aug 2021 21:12:14 -0400 Subject: [Coco] Looking for Most Recent Vcc. Executable for Windows. & Coco Key2USB In-Reply-To: References: <50e3b6f04ee66575dc0e9e00a0026394@jechar.ca> <367628554.447964.1629471033332@mail.yahoo.com> Message-ID: I would suggest if you were going to enable editing of any keymap, that it would be useful to force copying to a new one -- e.g. if you want to "edit" the "OS-9" keymap, instead of editing it would create a new "OS-9 (Custom)" and modify _that_ one, so that the original remains available for use. On Fri, Aug 20, 2021 at 3:02 PM edward jaquay wrote: > > Robert you have a non official copy I gave you a link to for testing.that > allows modification of any keymap. > The official version only allows modification of the custom keymap. I > expect the version you have will make it into the next release one testing > is complete and Bill blesses it. > > On Fri, Aug 20, 2021, 10:50 AM Robert Gault wrote: > > > You just need to change the keys you don't like. I think your changes will > > be retained regardless of which keyboard type you select. > > > > Sent from AT&T Yahoo Mail on Android > > > > > > > > > > -- > Coco mailing list > Coco at maltedmedia.com > https://pairlist5.pair.net/mailman/listinfo/coco From jrosslist at outlook.com Sat Aug 21 01:28:14 2021 From: jrosslist at outlook.com (James Ross) Date: Sat, 21 Aug 2021 05:28:14 +0000 Subject: [Coco] Looking for Most Recent Vcc. Executable for Windows. In-Reply-To: References: <1332121195.397442.1629459463579@mail.yahoo.com> Message-ID: Jeff Teunissen wrote: > "master" is the current code, not > necessarily the current release. Which would be fine as well ... not trying to be picky, it would be better than having VCC_2.0.1c where the code in there is actually from 8 releases back. In practicality the majority of GitHub sites are probably doing it how you propose. You have master and that's it ... all code development and releases come from it. And if you tag your releases properly, there is not a whole lot of difference (of how I propose it), since with Git you can download the current submit back to any other submit (again if they are tagged properly, that is...) However, a simple traditional version control practice is to separate current tested and released code known to work from development code that is still in the process of being tested and worked on. Call the branches whatever -- i.e. current stable release in "master" and development release in "development" or "next". However, the maintainers and developers need to be meticulous with the process. Of course we are lucky to have any work whatever being done to VCC so we'll take whatever we can get ... I'm just throwing out suggestions (and opinions) in an attempt to lessen any confusion ... James From ooogalapasooo at aol.com Sat Aug 21 06:29:51 2021 From: ooogalapasooo at aol.com (Bill Pierce) Date: Sat, 21 Aug 2021 10:29:51 +0000 (UTC) Subject: [Coco] Looking for Most Recent Vcc. Executable for Windows. & Coco Key2USB In-Reply-To: References: <50e3b6f04ee66575dc0e9e00a0026394@jechar.ca> <367628554.447964.1629471033332@mail.yahoo.com> Message-ID: <1327934063.645870.1629541791023@mail.yahoo.com> Jeff, the original keymaps are hard coded and always available. We are still experimenting with how this works and looking for the best way. -----Original Message----- From: Jeff Teunissen To: CoCoList for Color Computer Enthusiasts Sent: Fri, Aug 20, 2021 9:12 pm Subject: Re: [Coco] Looking for Most Recent Vcc. Executable for Windows. & Coco Key2USB I would suggest if you were going to enable editing of any keymap, that it would be useful to force copying to a new one -- e.g. if you want to "edit" the "OS-9" keymap, instead of editing it would create a new "OS-9 (Custom)" and modify _that_ one, so that the original remains available for use. On Fri, Aug 20, 2021 at 3:02 PM edward jaquay wrote: > > Robert you have a non official copy I gave you a link to for testing.that > allows modification of any keymap. > The official version only allows modification of the custom keymap.? I > expect the version you have will make it into the next release one testing > is complete and Bill blesses it. > > On Fri, Aug 20, 2021, 10:50 AM Robert Gault wrote: > > > You just need to change the keys you don't like. I think your changes will > > be retained regardless of which keyboard type you select. > > > > Sent from AT&T Yahoo Mail on Android > > > > > > > > > > -- > 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 From ejjaquay at gmail.com Sat Aug 21 09:39:17 2021 From: ejjaquay at gmail.com (edward jaquay) Date: Sat, 21 Aug 2021 09:39:17 -0400 Subject: [Coco] Looking for Most Recent Vcc. Executable for Windows. & Coco Key2USB In-Reply-To: References: <50e3b6f04ee66575dc0e9e00a0026394@jechar.ca> <367628554.447964.1629471033332@mail.yahoo.com> Message-ID: Thank everyone for the comments. I do need feedback. The custom keymap file created by the installer has comments detailing it's format and use in the header. The initial key mapping is hard-coded in the exe and is used are if the map file is not found. To revert simply rename or delete the file and restart. Clicking the save button after making modifications creates a new file if one does not exist. An experimental version I am testing allows you edit any of the key maps and adds a button to delete the file for you. It also eliminates the save button and auto saves any changes. On Fri, Aug 20, 2021, 10:23 PM Jeff Teunissen wrote: > I would suggest if you were going to enable editing of any keymap, > that it would be useful to force copying to a new one -- e.g. if you > want to "edit" the "OS-9" keymap, instead of editing it would create a > new "OS-9 (Custom)" and modify _that_ one, so that the original > remains available for use. > > On Fri, Aug 20, 2021 at 3:02 PM edward jaquay wrote: > > > > Robert you have a non official copy I gave you a link to for testing.that > > allows modification of any keymap. > > The official version only allows modification of the custom keymap. I > > expect the version you have will make it into the next release one > testing > > is complete and Bill blesses it. > > > > On Fri, Aug 20, 2021, 10:50 AM Robert Gault > wrote: > > > > > You just need to change the keys you don't like. I think your changes > will > > > be retained regardless of which keyboard type you select. > > > > > > Sent from AT&T Yahoo Mail on Android > > > < > https://go.onelink.me/107872968?pid=InProduct&c=Global_Internal_YGrowth_AndroidEmailSig__AndroidUsers&af_wl=ym&af_sub1=Internal&af_sub2=Global_YGrowth&af_sub3=EmailSignature&af_web_dp=https://more.att.com/currently/imap > > > > > > > > > > > > > > > -- > > 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 > From ejjaquay at gmail.com Sat Aug 21 16:11:37 2021 From: ejjaquay at gmail.com (edward jaquay) Date: Sat, 21 Aug 2021 16:11:37 -0400 Subject: [Coco] Looking for Most Recent Vcc. Executable for Windows. In-Reply-To: <1461441542.409144.1629459566738@mail.yahoo.com> References: <001801d79507$6ea49af0$4bedd0d0$@bds-soft.com> <1461441542.409144.1629459566738@mail.yahoo.com> Message-ID: I was able to get GitHub to list 2.1.0d as the latest release by changing a tag. Hope this eliminates the confusion on that point. On Fri, Aug 20, 2021 at 7:50 AM Bill Pierce via Coco wrote: > Yeah, the 210c version got bumped up to "Most Recent" somehow by GitHub > and it won't let me bump 210d up > > > -----Original Message----- > From: M. David Johnson > To: 'CoCoList for Color Computer Enthusiasts' > Sent: Thu, Aug 19, 2021 10:35 am > Subject: Re: [Coco] Looking for Most Recent Vcc. Executable for Windows. > > https://github.com/VCCE/VCC/releases is Bill Pierce's page on this. > > Ignore the top (2.1.0c) entry (I think they may have accidentally got out > of > order) and go to the second (2.1.0d) entry - it was released 2021/07/03. > > -- > M. David Johnson > mdj at bds-soft.com > > > -----Original Message----- > From: Coco [mailto:coco-bounces at maltedmedia.com] On Behalf Of > coco at jechar.ca > Sent: Thursday, August 19, 2021 9:30 AM > To: Coco List > Subject: [Coco] Looking for Most Recent Vcc. Executable for Windows. > > > I have found reference to a Vcc version dated 2015-08-26 > On Source Forge Is there something more recent particularly > a version that includes a keymap editor. > > I can choose between three keymaps but none of them are suitable. > > Charlie > > -- > 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 > > -- > Coco mailing list > Coco at maltedmedia.com > https://pairlist5.pair.net/mailman/listinfo/coco > From ejjaquay at gmail.com Sat Aug 21 16:41:03 2021 From: ejjaquay at gmail.com (edward jaquay) Date: Sat, 21 Aug 2021 16:41:03 -0400 Subject: [Coco] Looking for Most Recent Vcc. Executable for Windows. In-Reply-To: References: <1332121195.397442.1629459463579@mail.yahoo.com> Message-ID: Regarding creating a branch for each release. That would be less confusing than having the working branch named after an older release. But since we are not currently patching old releases we really don't need to keep old branches. Github keeps track of the release tags and the old source is always still there. .I am more in favor of naming the working branch something that does not change with the releases and perhaps having a beta branch that is a few commits ahead of what we are sure of for the next release. From ooogalapasooo at aol.com Sat Aug 21 18:12:57 2021 From: ooogalapasooo at aol.com (Bill Pierce) Date: Sat, 21 Aug 2021 22:12:57 +0000 (UTC) Subject: [Coco] Looking for Most Recent Vcc. Executable for Windows. In-Reply-To: References: <1332121195.397442.1629459463579@mail.yahoo.com> Message-ID: <1183642073.758067.1629583977435@mail.yahoo.com> That was similar to what I've was thinking. We definitely need a "temp" branch for pushing our new changes, but also a stable "release" branch that reflects the current release. -----Original Message----- From: edward jaquay To: CoCoList for Color Computer Enthusiasts Sent: Sat, Aug 21, 2021 4:41 pm Subject: Re: [Coco] Looking for Most Recent Vcc. Executable for Windows. Regarding creating a branch for each release.? That would be less confusing than having the working branch named after an older release.? But since we are not currently patching old releases we really don't need to keep old branches.? Github keeps track of the release tags and the old source is always still there.? .I am more in favor of naming the working branch something that does not change with the releases and perhaps having a beta branch that is a few commits ahead of what we are sure of for the next release. -- Coco mailing list Coco at maltedmedia.com https://pairlist5.pair.net/mailman/listinfo/coco From coco at jechar.ca Sat Aug 21 19:44:06 2021 From: coco at jechar.ca (coco at jechar.ca) Date: Sat, 21 Aug 2021 19:44:06 -0400 Subject: [Coco] Looking for Most Recent Vcc. Executable for Windows. & Coco Key2USB In-Reply-To: References: <50e3b6f04ee66575dc0e9e00a0026394@jechar.ca> <367628554.447964.1629471033332@mail.yahoo.com> Message-ID: <24d5d9a7366138fbd3c30b6133a2c421@jechar.ca> Excelent Idea. On 2021-08-20 21:12, Jeff Teunissen wrote: > I would suggest if you were going to enable editing of any keymap, > that it would be useful to force copying to a new one -- e.g. if you > want to "edit" the "OS-9" keymap, instead of editing it would create a > new "OS-9 (Custom)" and modify _that_ one, so that the original > remains available for use. > > On Fri, Aug 20, 2021 at 3:02 PM edward jaquay > wrote: >> >> Robert you have a non official copy I gave you a link to for >> testing.that >> allows modification of any keymap. >> The official version only allows modification of the custom keymap. I >> expect the version you have will make it into the next release one >> testing >> is complete and Bill blesses it. >> >> On Fri, Aug 20, 2021, 10:50 AM Robert Gault >> wrote: >> >> > You just need to change the keys you don't like. I think your changes will >> > be retained regardless of which keyboard type you select. >> > >> > Sent from AT&T Yahoo Mail on Android >> > >> > >> > >> > >> >> -- >> Coco mailing list >> Coco at maltedmedia.com >> https://pairlist5.pair.net/mailman/listinfo/coco From coco at jechar.ca Sat Aug 21 20:20:20 2021 From: coco at jechar.ca (coco at jechar.ca) Date: Sat, 21 Aug 2021 20:20:20 -0400 Subject: [Coco] Custom Keyboards for Vcc Message-ID: Found the manual in my Windows7 under C:\USERS\COCO\Documents\Coco Manuals\ directory all it says about custom keyboards is "Custom key mapping coming soon !" Not much help there also there is no blank custom keyboard.ini file included with Vcc so it has nowhere to save. Charlie From chawks at dls.net Sat Aug 21 20:52:04 2021 From: chawks at dls.net (Christopher R. Hawks) Date: Sat, 21 Aug 2021 19:52:04 -0500 Subject: [Coco] Custom Keyboards for Vcc In-Reply-To: References: Message-ID: <20210821195204.5715fdd8@Manfred.lan> On Sat, 21 Aug 2021 20:20:20 -0400 coco at jechar.ca wrote: > > Found the manual in my Windows7 under C:\USERS\COCO\Documents\Coco > Manuals\ directory all it says about custom keyboards is > > "Custom key mapping coming soon !" > > Not much help there also there is no blank custom keyboard.ini file > included with Vcc so it has nowhere to save. > > Charlie > The one I downloaded at 10:46 on Aug 19 has about 6 pages of explanation and info. I didn't realize there was a section in the manual and found the brief explanation on the page itself was sufficient. Manfred(chrish)$ ls -l VCC.2.1.0d.Coco.3.Emulator.zip chrish users 4789168 Aug 19 10:46 VCC.2.1.0d.Coco.3.Emulator.zip Christopher R. Hawks HAWKSoft -- "Friendship is born at that moment when one person says to another, 'What! You too? I thought I was the only one!'" -- C.S. Lewis ---------------------------------------- \ ^__^ \ (oo)\_______ (__)\ )\/\ ||----w | || || From coco at jechar.ca Sat Aug 21 21:27:17 2021 From: coco at jechar.ca (coco at jechar.ca) Date: Sat, 21 Aug 2021 21:27:17 -0400 Subject: [Coco] Custom Keyboards for Vcc In-Reply-To: <20210821195204.5715fdd8@Manfred.lan> References: <20210821195204.5715fdd8@Manfred.lan> Message-ID: <94265cbfd00233f808ef84b05192a919@jechar.ca> Ok I will download again I may have a manual a day or two older After finding out that I needed to go into control panel in windows to change folder settings to let me see AppData to begin with I found a \AppData\Roaming\VCC folder but It had no keymaps in it so I cannot press the Select File button in Vcc > Vcc Options > Keyboard > Edit Custom Key Map to get a keymap to work on and my "Save Keymap" button is greyed out so not getting anyware yet. Charlie On 2021-08-21 20:52, Christopher R. Hawks wrote: > On Sat, 21 Aug 2021 20:20:20 -0400 > coco at jechar.ca wrote: > >> >> Found the manual in my Windows7 under C:\USERS\COCO\Documents\Coco >> Manuals\ directory all it says about custom keyboards is >> >> "Custom key mapping coming soon !" >> >> Not much help there also there is no blank custom keyboard.ini file >> included with Vcc so it has nowhere to save. >> >> Charlie >> > > The one I downloaded at 10:46 on Aug 19 has about 6 pages of > explanation and info. I didn't realize there was a section in the > manual and found the brief explanation on the page itself was > sufficient. > > Manfred(chrish)$ ls -l VCC.2.1.0d.Coco.3.Emulator.zip > chrish users 4789168 Aug 19 10:46 VCC.2.1.0d.Coco.3.Emulator.zip > > > Christopher R. Hawks > HAWKSoft > -- > "Friendship is born at that moment when one person says to another, > 'What! You too? I thought I was the only one!'" > -- C.S. Lewis > ---------------------------------------- > \ ^__^ > \ (oo)\_______ > (__)\ )\/\ > ||----w | > || || From ejjaquay at gmail.com Sat Aug 21 21:58:10 2021 From: ejjaquay at gmail.com (edward jaquay) Date: Sat, 21 Aug 2021 21:58:10 -0400 Subject: [Coco] Custom Keyboards for Vcc In-Reply-To: <94265cbfd00233f808ef84b05192a919@jechar.ca> References: <20210821195204.5715fdd8@Manfred.lan> <94265cbfd00233f808ef84b05192a919@jechar.ca> Message-ID: The save keymap will activate after a key mapping is changed. On Sat, Aug 21, 2021, 9:30 PM wrote: > > Ok I will download again I may have a manual a day or two older > After finding out that I needed to go into control panel in windows to > change folder settings to let me see AppData to begin with I found a > \AppData\Roaming\VCC folder but It had no keymaps in it so I cannot > press the Select File button in Vcc > Vcc Options > Keyboard > Edit > Custom Key Map to get a keymap to work on and my "Save Keymap" button is > greyed > out so not getting anyware yet. > > Charlie > > On 2021-08-21 20:52, Christopher R. Hawks wrote: > > On Sat, 21 Aug 2021 20:20:20 -0400 > > coco at jechar.ca wrote: > > > >> > >> Found the manual in my Windows7 under C:\USERS\COCO\Documents\Coco > >> Manuals\ directory all it says about custom keyboards is > >> > >> "Custom key mapping coming soon !" > >> > >> Not much help there also there is no blank custom keyboard.ini file > >> included with Vcc so it has nowhere to save. > >> > >> Charlie > >> > > > > The one I downloaded at 10:46 on Aug 19 has about 6 pages of > > explanation and info. I didn't realize there was a section in the > > manual and found the brief explanation on the page itself was > > sufficient. > > > > Manfred(chrish)$ ls -l VCC.2.1.0d.Coco.3.Emulator.zip > > chrish users 4789168 Aug 19 10:46 VCC.2.1.0d.Coco.3.Emulator.zip > > > > > > Christopher R. Hawks > > HAWKSoft > > -- > > "Friendship is born at that moment when one person says to another, > > 'What! You too? I thought I was the only one!'" > > -- C.S. Lewis > > ---------------------------------------- > > \ ^__^ > > \ (oo)\_______ > > (__)\ )\/\ > > ||----w | > > || || > > -- > Coco mailing list > Coco at maltedmedia.com > https://pairlist5.pair.net/mailman/listinfo/coco > From allencoco at yahoo.com Sun Aug 22 02:34:25 2021 From: allencoco at yahoo.com (Joshua Harper) Date: Sun, 22 Aug 2021 01:34:25 -0500 Subject: [Coco] (no subject) References: Message-ID: Hi guys was wondering if somebody can help does anybody know what model number of Coco to have the motherboard that had two rows of pins on the motherboard that you plugged in a little board on top of that that upgraded the memory are used to have one of these but I cannot remember what the actual model number was to it I am looking for that particular model thanks for any help From robert.gault at att.net Sun Aug 22 04:02:08 2021 From: robert.gault at att.net (Robert Gault) Date: Sun, 22 Aug 2021 08:02:08 +0000 (UTC) Subject: [Coco] (no subject) In-Reply-To: References: Message-ID: <817011292.791512.1629619328399@mail.yahoo.com> The CoCo3 has two sockets on the motherboard into which you can plug a small board to increase memory. So the pins are on the memory upgrade not the motherboard. Sent from AT&T Yahoo Mail on Android On Sun, Aug 22, 2021 at 2:45 AM, Joshua Harper via Coco wrote: Hi guys was wondering if somebody can help does anybody know what model number of Coco to have the motherboard that had two rows of pins on the motherboard that you plugged in a little board on top of that that upgraded the memory are used to have one of these but I cannot remember what the actual model number was to it I am looking for that particular model thanks for any help -- Coco mailing list Coco at maltedmedia.com https://pairlist5.pair.net/mailman/listinfo/coco From brucewcalkins at charter.net Sun Aug 22 08:27:18 2021 From: brucewcalkins at charter.net (Bruce W. Calkins) Date: Sun, 22 Aug 2021 08:27:18 -0400 Subject: [Coco] (no subject) In-Reply-To: References: Message-ID: <5927288d-5cc6-12bb-a049-ee4a06fe56eb@charter.net> The last two versions of the CoCo two had the A and B suffix on the model number. FWIW: I have two 64k upgrade boards in my midden heap from then. Bruce W. On 8/22/21 2:34 AM, Joshua Harper via Coco wrote: > Hi guys was wondering if somebody can help does anybody know what model number of Coco to have the motherboard that had two rows of pins on the motherboard that you plugged in a little board on top of that that upgraded the memory are used to have one of these but I cannot remember what the actual model number was to it I am looking for that particular model thanks for any help > From ooogalapasooo at aol.com Sun Aug 22 09:16:31 2021 From: ooogalapasooo at aol.com (Bill Pierce) Date: Sun, 22 Aug 2021 13:16:31 +0000 (UTC) Subject: [Coco] Custom Keyboards for Vcc In-Reply-To: References: Message-ID: <1529898237.824709.1629638191985@mail.yahoo.com> Charlie, you have an old copy of the manual. Which brings to mind that I've never checked to see if the installer overwrites an old copy of the manual. Hmmm. Download the zip version and get the manual from that. I may make the manual a separate download as well. -----Original Message----- From: coco at jechar.ca To: Coco List Sent: Sat, Aug 21, 2021 8:20 pm Subject: [Coco] Custom Keyboards for Vcc Found the manual in my Windows7 under C:\USERS\COCO\Documents\Coco Manuals\ directory all it says about custom keyboards is "Custom key mapping coming soon !" Not much help there also there is no blank custom keyboard.ini file included with Vcc so it has nowhere to save. Charlie -- Coco mailing list Coco at maltedmedia.com https://pairlist5.pair.net/mailman/listinfo/coco From zathrasldf at outlook.com Sun Aug 22 10:11:30 2021 From: zathrasldf at outlook.com (Doug Fraser) Date: Sun, 22 Aug 2021 14:11:30 +0000 Subject: [Coco] (no subject) In-Reply-To: References: Message-ID: I think the model number of the CoCo 2 is the 26-3134A/B. Get Outlook for Android ________________________________ From: Coco on behalf of Joshua Harper via Coco Sent: Saturday, August 21, 2021 11:34:25 PM To: coco at maltedmedia.com Cc: Joshua Harper Subject: [Coco] (no subject) Hi guys was wondering if somebody can help does anybody know what model number of Coco to have the motherboard that had two rows of pins on the motherboard that you plugged in a little board on top of that that upgraded the memory are used to have one of these but I cannot remember what the actual model number was to it I am looking for that particular model thanks for any help -- Coco mailing list Coco at maltedmedia.com https://pairlist5.pair.net/mailman/listinfo/coco From mdj at bds-soft.com Sun Aug 22 23:38:39 2021 From: mdj at bds-soft.com (M. David Johnson) Date: Sun, 22 Aug 2021 22:38:39 -0500 Subject: [Coco] CoCo 3's CoCo 1/2 mode Message-ID: <010c01d797d0$5d4195d0$17c4c170$@bds-soft.com> I read that when Bit 7 of &HFF90 (cf. http://www.cococommunity.net/socks-gime-register-reference/ ) is set, the CoCo 3 is then in CoCo 1/2 mode. I don't have a physical CoCo 3 to check that on (I only have a CoCo 2). But in VCC 2.1.0d I notice that, immediately on startup, &HFF90 contains &HCC (1100 1100 binary). So it's already in CoCo 1/2 mode? Am I missing something? -- M. David Johnson mdj at bds-soft.com From allencoco at yahoo.com Mon Aug 23 00:19:34 2021 From: allencoco at yahoo.com (Joshua Harper) Date: Sun, 22 Aug 2021 23:19:34 -0500 Subject: [Coco] Source for CoCo 3 Rubber Feet In-Reply-To: <1422090773.3031849.1438010234501.JavaMail.yahoo@mail.yahoo.com> References: <1422090773.3031849.1438010234501.JavaMail.yahoo@mail.yahoo.com> Message-ID: Hi there I was just checking do you still by chance have any of the Coco 3 feet for the bottom case if you do anyway of buying them direct as it?s hard for me to navigate webpages very well thanks please let me know > On Jul 27, 2015, at 10:17 AM, Raymond Jett via Coco wrote: > > ?I have a small number (about a dozen) of the round plastic feet that have the push pin in the middle to hold them in place. > > They were a perfect fit on my CoCo 3 which had the little holes in the bottom for the pin to fit in. > > Raymond > > Date: Sun, 26 Jul 2015 20:53:57 -0700 > From: Steve Batson > To: CoCoList for Color Computer Enthusiasts > Subject: Re: [Coco] Source for CoCo 3 Rubber Feet > Message-ID: <64D6CC9A-0824-4001-8F3A-24EAAA0A0C86 at yahoo.com> > Content-Type: text/plain; charset=us-ascii > > > I found some very much like what is on the CoCo at a Local Ace Hardware Store. They were white instead of Black, but very close in size and shape. They work great. It was a pack of at least 8, I don't recall. > > > >> On Jul 26, 2015, at 7:10 PM, Richard Goedeken wrote: >> >> I was recently looking for the same thing, and I ended up buying these: >> >> http://www.ebay.com/itm/281033730630 >> >> They aren't exactly the same. They are not as 'slippery' as the original Coco >> feet (the flat ones, not the rubber hemisphere ones) and they are not quite as >> tall either, but they at least keep the bottom of the case off of the table. >> >> Ricahrd >> >>> On 07/25/2015 12:25 AM, K. Pruitt wrote: >>> Has anybody found a source for a good match for the rubber feet on a CoCo 3? >>> >>> I'd like to use it with an MPI, so a good match is important. >>> >>> So many CoCo's seem to be footless that I figure someone here probably went >>> down this road already. >>> >>> I was thinking that those long rubber feet they sell for laptops might work as >>> they come in a variety of thicknesses. But something that actually replaces >>> the stock feet on a CoCo 3 would certainly be better. That is if they >>> available anywhere other than on the bottom of another CoCo. >>> >>> Thanks >>> >>> >>> >> >> -- >> 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 From flexser at fiu.edu Mon Aug 23 00:14:44 2021 From: flexser at fiu.edu (Arthur Flexser) Date: Mon, 23 Aug 2021 00:14:44 -0400 Subject: [Coco] CoCo 3's CoCo 1/2 mode In-Reply-To: <010c01d797d0$5d4195d0$17c4c170$@bds-soft.com> References: <010c01d797d0$5d4195d0$17c4c170$@bds-soft.com> Message-ID: I found this at http://www.roust-it.dk/coco/Lomont_CoCoHardware_2.pdf ----------- To use CoCo 3 graphics, the COCO bit must be set to zero. When using CoCo 1/2 resolutions, the bit is set to 1. RSDOS typically sets the INIT0 register [$FF90] to 196 in CoCo 2 resolutions and 68 when using CoCo 3 graphics modes. ----------- So, it would seem that Bit 7 of $FF90 (the "COCO bit") is just something that has to be set appropriately by the user, or by the Basic ROM graphics routines, depending on whether the CoCo 3 or the CoCo 1/2 graphics modes are being employed. It's not a general compatibility switch. At startup, the CoCo 3 defaults to CoCo 1/2 graphics resolution, so $FF90 bit 7 starts out set to 1. Art On Sun, Aug 22, 2021 at 11:38 PM M. David Johnson wrote: > I read that when Bit 7 of &HFF90 (cf. > http://www.cococommunity.net/socks-gime-register-reference/ ) is set, the > CoCo 3 is then in CoCo 1/2 mode. > > > > I don't have a physical CoCo 3 to check that on (I only have a CoCo 2). > > > > But in VCC 2.1.0d I notice that, immediately on startup, &HFF90 contains > &HCC (1100 1100 binary). > > > > So it's already in CoCo 1/2 mode? Am I missing something? > > > > -- > > M. David Johnson > > mdj at bds-soft.com > > > > > > > -- > Coco mailing list > Coco at maltedmedia.com > https://pairlist5.pair.net/mailman/listinfo/coco > From mdj at bds-soft.com Mon Aug 23 11:30:34 2021 From: mdj at bds-soft.com (M. David Johnson) Date: Mon, 23 Aug 2021 10:30:34 -0500 Subject: [Coco] CoCo 3's CoCo 1/2 mode In-Reply-To: References: <010c01d797d0$5d4195d0$17c4c170$@bds-soft.com> Message-ID: <013d01d79833$d1434600$73c9d200$@bds-soft.com> I see. So then the bit only affects the graphics, not the memory management, i.e. setting it doesn't limit the bank switching capability? -- M. David Johnson mdj at bds-soft.com -----Original Message----- From: Coco [mailto:coco-bounces at maltedmedia.com] On Behalf Of Arthur Flexser Sent: Sunday, August 22, 2021 11:15 PM To: CoCoList for Color Computer Enthusiasts Subject: Re: [Coco] CoCo 3's CoCo 1/2 mode I found this at http://www.roust-it.dk/coco/Lomont_CoCoHardware_2.pdf ----------- To use CoCo 3 graphics, the COCO bit must be set to zero. When using CoCo 1/2 resolutions, the bit is set to 1. RSDOS typically sets the INIT0 register [$FF90] to 196 in CoCo 2 resolutions and 68 when using CoCo 3 graphics modes. ----------- So, it would seem that Bit 7 of $FF90 (the "COCO bit") is just something that has to be set appropriately by the user, or by the Basic ROM graphics routines, depending on whether the CoCo 3 or the CoCo 1/2 graphics modes are being employed. It's not a general compatibility switch. At startup, the CoCo 3 defaults to CoCo 1/2 graphics resolution, so $FF90 bit 7 starts out set to 1. Art On Sun, Aug 22, 2021 at 11:38 PM M. David Johnson wrote: > I read that when Bit 7 of &HFF90 (cf. > http://www.cococommunity.net/socks-gime-register-reference/ ) is set, the > CoCo 3 is then in CoCo 1/2 mode. > > > > I don't have a physical CoCo 3 to check that on (I only have a CoCo 2). > > > > But in VCC 2.1.0d I notice that, immediately on startup, &HFF90 contains > &HCC (1100 1100 binary). > > > > So it's already in CoCo 1/2 mode? Am I missing something? > > > > -- > > M. David Johnson > > mdj at bds-soft.com > > > > > > > -- > 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 From flexser at fiu.edu Mon Aug 23 12:15:14 2021 From: flexser at fiu.edu (Arthur Flexser) Date: Mon, 23 Aug 2021 12:15:14 -0400 Subject: [Coco] CoCo 3's CoCo 1/2 mode In-Reply-To: <013d01d79833$d1434600$73c9d200$@bds-soft.com> References: <010c01d797d0$5d4195d0$17c4c170$@bds-soft.com> <013d01d79833$d1434600$73c9d200$@bds-soft.com> Message-ID: Yes, shouldn't affect bank switching. Art On Mon, Aug 23, 2021 at 11:30 AM M. David Johnson wrote: > I see. So then the bit only affects the graphics, not the memory > management, > i.e. setting it doesn't limit the bank switching capability? > > -- > M. David Johnson > mdj at bds-soft.com > > > > -----Original Message----- > From: Coco [mailto:coco-bounces at maltedmedia.com] On Behalf Of Arthur > Flexser > Sent: Sunday, August 22, 2021 11:15 PM > To: CoCoList for Color Computer Enthusiasts > Subject: Re: [Coco] CoCo 3's CoCo 1/2 mode > > I found this at http://www.roust-it.dk/coco/Lomont_CoCoHardware_2.pdf > ----------- > To use CoCo 3 graphics, the COCO bit must be set to zero. When using CoCo > 1/2 resolutions, the bit is set to 1. RSDOS typically sets the INIT0 > register [$FF90] to 196 in CoCo 2 resolutions and 68 when using CoCo 3 > graphics modes. > ----------- > > So, it would seem that Bit 7 of $FF90 (the "COCO bit") is just something > that has to be set appropriately by the user, or by the Basic ROM graphics > routines, depending on whether the CoCo 3 or the CoCo 1/2 graphics modes > are being employed. It's not a general compatibility switch. At startup, > the CoCo 3 defaults to CoCo 1/2 graphics resolution, so $FF90 bit 7 starts > out set to 1. > > Art > > On Sun, Aug 22, 2021 at 11:38 PM M. David Johnson > wrote: > > > I read that when Bit 7 of &HFF90 (cf. > > http://www.cococommunity.net/socks-gime-register-reference/ ) is set, > the > > CoCo 3 is then in CoCo 1/2 mode. > > > > > > > > I don't have a physical CoCo 3 to check that on (I only have a CoCo 2). > > > > > > > > But in VCC 2.1.0d I notice that, immediately on startup, &HFF90 contains > > &HCC (1100 1100 binary). > > > > > > > > So it's already in CoCo 1/2 mode? Am I missing something? > > > > > > > > -- > > > > M. David Johnson > > > > mdj at bds-soft.com > > > > > > > > > > > > > > -- > > 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 > > > -- > Coco mailing list > Coco at maltedmedia.com > https://pairlist5.pair.net/mailman/listinfo/coco > From robert.gault at att.net Mon Aug 23 17:07:50 2021 From: robert.gault at att.net (Robert Gault) Date: Mon, 23 Aug 2021 21:07:50 +0000 (UTC) Subject: [Coco] CoCo 3's CoCo 1/2 mode In-Reply-To: References: <010c01d797d0$5d4195d0$17c4c170$@bds-soft.com> <013d01d79833$d1434600$73c9d200$@bds-soft.com> Message-ID: <599763190.1204090.1629752870481@mail.yahoo.com> Of course one could always assume that VCC is working correctly regards the content of $FF90 and read the contents when in different screen modes, text and graphics. You should be able to find the CoCo3 service manual in the colorcomputerarchive.com under documents which will list what the bits do. However, the fun of having the hardware or emulator is writing programs to see what you can do with the unit. ? Sent from AT&T Yahoo Mail on Android On Mon, Aug 23, 2021 at 12:15 PM, Arthur Flexser wrote: Yes, shouldn't affect bank switching. Art On Mon, Aug 23, 2021 at 11:30 AM M. David Johnson wrote: > I see. So then the bit only affects the graphics, not the memory > management, > i.e. setting it doesn't limit the bank switching capability? > > -- > M. David Johnson > mdj at bds-soft.com > > > > -----Original Message----- > From: Coco [mailto:coco-bounces at maltedmedia.com] On Behalf Of Arthur > Flexser > Sent: Sunday, August 22, 2021 11:15 PM > To: CoCoList for Color Computer Enthusiasts > Subject: Re: [Coco] CoCo 3's CoCo 1/2 mode > > I found this at http://www.roust-it.dk/coco/Lomont_CoCoHardware_2.pdf > ----------- > To use CoCo 3 graphics, the COCO bit must be set to zero. When using CoCo > 1/2 resolutions, the bit is set to 1. RSDOS typically sets the INIT0 > register [$FF90] to 196 in CoCo 2 resolutions and 68 when using CoCo 3 > graphics modes. > ----------- > > So, it would seem that Bit 7 of $FF90 (the "COCO bit") is just something > that has to be set appropriately by the user, or by the Basic ROM graphics > routines, depending on whether the CoCo 3 or the CoCo 1/2 graphics modes > are being employed.? It's not a general compatibility switch.? At startup, > the CoCo 3 defaults to CoCo 1/2 graphics resolution, so $FF90 bit 7 starts > out set to 1. > > Art > > On Sun, Aug 22, 2021 at 11:38 PM M. David Johnson > wrote: > > > I read that when Bit 7 of &HFF90 (cf. > > http://www.cococommunity.net/socks-gime-register-reference/ ) is set, > the > > CoCo 3 is then in CoCo 1/2 mode. > > > > > > > > I don't have a physical CoCo 3 to check that on (I only have a CoCo 2). > > > > > > > > But in VCC 2.1.0d I notice that, immediately on startup, &HFF90 contains > > &HCC (1100 1100 binary). > > > > > > > > So it's already in CoCo 1/2 mode? Am I missing something? > > > > > > > > -- > > > > M. David Johnson > > > > mdj at bds-soft.com > > > > > > > > > > > > > > -- > > 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 > > > -- > 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 From joel.rees at gmail.com Mon Aug 23 17:47:39 2021 From: joel.rees at gmail.com (Joel Rees) Date: Tue, 24 Aug 2021 06:47:39 +0900 Subject: [Coco] CoCo 3's CoCo 1/2 mode In-Reply-To: <010c01d797d0$5d4195d0$17c4c170$@bds-soft.com> References: <010c01d797d0$5d4195d0$17c4c170$@bds-soft.com> Message-ID: What happens if you set it to zero, then read it? 2021?8?23?(?) 12:38 M. David Johnson : > I read that when Bit 7 of &HFF90 (cf. > http://www.cococommunity.net/socks-gime-register-reference/ ) is set, the > CoCo 3 is then in CoCo 1/2 mode. > > > > I don't have a physical CoCo 3 to check that on (I only have a CoCo 2). > > > > But in VCC 2.1.0d I notice that, immediately on startup, &HFF90 contains > &HCC (1100 1100 binary). > > > > So it's already in CoCo 1/2 mode? Am I missing something? > > > > -- > > M. David Johnson > > mdj at bds-soft.com > > > > > > > -- > Coco mailing list > Coco at maltedmedia.com > https://pairlist5.pair.net/mailman/listinfo/coco > From lost at l-w.ca Mon Aug 23 17:52:24 2021 From: lost at l-w.ca (William Astle) Date: Mon, 23 Aug 2021 15:52:24 -0600 Subject: [Coco] CoCo 3's CoCo 1/2 mode In-Reply-To: References: <010c01d797d0$5d4195d0$17c4c170$@bds-soft.com> Message-ID: <8d2a85ed-ae0a-6600-c9a5-0e3f00bffdf0@l-w.ca> If VCC is implemented correctly, most stuff in FF9x will return junk when read. Those registers are write-only on the real hardware. Regardless, setting FF90 to 0 will likely crash the system. That turns off the MMU and the "constant page" at FExx. On 2021-08-23 3:47 p.m., Joel Rees wrote: > What happens if you set it to zero, then read it? > > 2021?8?23?(?) 12:38 M. David Johnson : > >> I read that when Bit 7 of &HFF90 (cf. >> http://www.cococommunity.net/socks-gime-register-reference/ ) is set, the >> CoCo 3 is then in CoCo 1/2 mode. >> >> >> >> I don't have a physical CoCo 3 to check that on (I only have a CoCo 2). >> >> >> >> But in VCC 2.1.0d I notice that, immediately on startup, &HFF90 contains >> &HCC (1100 1100 binary). >> >> >> >> So it's already in CoCo 1/2 mode? Am I missing something? >> >> >> >> -- >> >> M. David Johnson >> >> mdj at bds-soft.com >> >> >> >> >> >> >> -- >> Coco mailing list >> Coco at maltedmedia.com >> https://pairlist5.pair.net/mailman/listinfo/coco >> > From mdj at bds-soft.com Mon Aug 23 18:30:30 2021 From: mdj at bds-soft.com (M. David Johnson) Date: Mon, 23 Aug 2021 17:30:30 -0500 Subject: [Coco] CoCo 3's CoCo 1/2 mode In-Reply-To: <599763190.1204090.1629752870481@mail.yahoo.com> References: <010c01d797d0$5d4195d0$17c4c170$@bds-soft.com> <013d01d79833$d1434600$73c9d200$@bds-soft.com> <599763190.1204090.1629752870481@mail.yahoo.com> Message-ID: <016101d7986e$7b1ea770$715bf650$@bds-soft.com> Yes, indeed! Much fun! Now if I could just find a CoCo 3 for a reasonable price without having to try to outbid someone on ebay.... -- M. David Johnson mdj at bds-soft.com -----Original Message----- From: Coco [mailto:coco-bounces at maltedmedia.com] On Behalf Of Robert Gault Sent: Monday, August 23, 2021 4:08 PM To: CoCoList for Color Computer Enthusiasts Subject: Re: [Coco] CoCo 3's CoCo 1/2 mode Of course one could always assume that VCC is working correctly regards the content of $FF90 and read the contents when in different screen modes, text and graphics. You should be able to find the CoCo3 service manual in the colorcomputerarchive.com under documents which will list what the bits do. However, the fun of having the hardware or emulator is writing programs to see what you can do with the unit. ? Sent from AT&T Yahoo Mail on Android On Mon, Aug 23, 2021 at 12:15 PM, Arthur Flexser wrote: Yes, shouldn't affect bank switching. Art On Mon, Aug 23, 2021 at 11:30 AM M. David Johnson wrote: > I see. So then the bit only affects the graphics, not the memory > management, > i.e. setting it doesn't limit the bank switching capability? > > -- > M. David Johnson > mdj at bds-soft.com > > > > -----Original Message----- > From: Coco [mailto:coco-bounces at maltedmedia.com] On Behalf Of Arthur > Flexser > Sent: Sunday, August 22, 2021 11:15 PM > To: CoCoList for Color Computer Enthusiasts > Subject: Re: [Coco] CoCo 3's CoCo 1/2 mode > > I found this at http://www.roust-it.dk/coco/Lomont_CoCoHardware_2.pdf > ----------- > To use CoCo 3 graphics, the COCO bit must be set to zero. When using CoCo > 1/2 resolutions, the bit is set to 1. RSDOS typically sets the INIT0 > register [$FF90] to 196 in CoCo 2 resolutions and 68 when using CoCo 3 > graphics modes. > ----------- > > So, it would seem that Bit 7 of $FF90 (the "COCO bit") is just something > that has to be set appropriately by the user, or by the Basic ROM graphics > routines, depending on whether the CoCo 3 or the CoCo 1/2 graphics modes > are being employed. It's not a general compatibility switch. At startup, > the CoCo 3 defaults to CoCo 1/2 graphics resolution, so $FF90 bit 7 starts > out set to 1. > > Art > > On Sun, Aug 22, 2021 at 11:38 PM M. David Johnson > wrote: > > > I read that when Bit 7 of &HFF90 (cf. > > http://www.cococommunity.net/socks-gime-register-reference/ ) is set, > the > > CoCo 3 is then in CoCo 1/2 mode. > > > > > > > > I don't have a physical CoCo 3 to check that on (I only have a CoCo 2). > > > > > > > > But in VCC 2.1.0d I notice that, immediately on startup, &HFF90 contains > > &HCC (1100 1100 binary). > > > > > > > > So it's already in CoCo 1/2 mode? Am I missing something? > > > > > > > > -- > > > > M. David Johnson > > > > mdj at bds-soft.com > > > > > > > > > > > > > > -- > > 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 > > > -- > 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 -- Coco mailing list Coco at maltedmedia.com https://pairlist5.pair.net/mailman/listinfo/coco From chawks at dls.net Fri Aug 27 12:36:04 2021 From: chawks at dls.net (Christopher R. Hawks) Date: Fri, 27 Aug 2021 11:36:04 -0500 Subject: [Coco] Ed Snider Message-ID: <20210827113604.56ce8b40@Manfred.lan> Anyone heard from the Zippster recently? I know he is pretty quiet on the list. I left a message on his website a couple of days ago and haven't heard back. Christopher R. Hawks HAWKSoft -- "I got some gas,... all I need is a house, a Porche, a highway, and a girlfriend." -- C. Dean Sparkman ---------------------------------------- \ ^__^ \ (oo)\_______ (__)\ )\/\ ||----w | || || From ejmautz2 at gmail.com Fri Aug 27 12:39:43 2021 From: ejmautz2 at gmail.com (John Mautz) Date: Fri, 27 Aug 2021 12:39:43 -0400 Subject: [Coco] Ed Snider In-Reply-To: <20210827113604.56ce8b40@Manfred.lan> References: <20210827113604.56ce8b40@Manfred.lan> Message-ID: I haven't heard specifically but I thought it was mentioned on the list that he was moving. Therefore I figured he was just off line getting the new place set up, but I really don't know. On Fri, Aug 27, 2021 at 12:36 PM Christopher R. Hawks wrote: > > Anyone heard from the Zippster recently? I know he is pretty quiet > on the list. I left a message on his website a couple of days ago and > haven't heard back. > > > Christopher R. Hawks > HAWKSoft > -- > "I got some gas,... all I need is a house, a Porche, a highway, and a > girlfriend." > -- C. Dean Sparkman > ---------------------------------------- > \ ^__^ > \ (oo)\_______ > (__)\ )\/\ > ||----w | > || || > > -- > Coco mailing list > Coco at maltedmedia.com > https://pairlist5.pair.net/mailman/listinfo/coco > From mdj at bds-soft.com Fri Aug 27 16:01:54 2021 From: mdj at bds-soft.com (M. David Johnson) Date: Fri, 27 Aug 2021 15:01:54 -0500 Subject: [Coco] Ed Snider In-Reply-To: <20210827113604.56ce8b40@Manfred.lan> References: <20210827113604.56ce8b40@Manfred.lan> Message-ID: <010701d79b7e$62af01e0$280d05a0$@bds-soft.com> Well, I just ordered another CoCo SDC from him this past Tuesday. I got an immediate email response, but that may have been automatically generated. That's all I know. -- M. David Johnson mdj at bds-soft.com -----Original Message----- From: Coco [mailto:coco-bounces at maltedmedia.com] On Behalf Of Christopher R. Hawks Sent: Friday, August 27, 2021 11:36 AM To: CoCo List Subject: [Coco] Ed Snider Anyone heard from the Zippster recently? I know he is pretty quiet on the list. I left a message on his website a couple of days ago and haven't heard back. Christopher R. Hawks HAWKSoft -- "I got some gas,... all I need is a house, a Porche, a highway, and a girlfriend." -- C. Dean Sparkman ---------------------------------------- \ ^__^ \ (oo)\_______ (__)\ )\/\ ||----w | || || -- Coco mailing list Coco at maltedmedia.com https://pairlist5.pair.net/mailman/listinfo/coco From zippster278 at gmail.com Fri Aug 27 16:15:59 2021 From: zippster278 at gmail.com (Ed Snider) Date: Fri, 27 Aug 2021 15:15:59 -0500 Subject: [Coco] Ed Snider In-Reply-To: <010701d79b7e$62af01e0$280d05a0$@bds-soft.com> References: <20210827113604.56ce8b40@Manfred.lan> <010701d79b7e$62af01e0$280d05a0$@bds-soft.com> Message-ID: I'm here guys. Sometimes I miss messages from the website. Probably better to send me a direct email in most cases. I replied off list to you as well Christopher. - Ed > On Aug 27, 2021, at 3:01 PM, M. David Johnson wrote: > > Well, I just ordered another CoCo SDC from him this past Tuesday. > > I got an immediate email response, but that may have been automatically > generated. > > That's all I know. > > -- > M. David Johnson > mdj at bds-soft.com > > > > -----Original Message----- > From: Coco [mailto:coco-bounces at maltedmedia.com] On Behalf Of Christopher R. > Hawks > Sent: Friday, August 27, 2021 11:36 AM > To: CoCo List > Subject: [Coco] Ed Snider > > > Anyone heard from the Zippster recently? I know he is pretty quiet > on the list. I left a message on his website a couple of days ago and > haven't heard back. > > > Christopher R. Hawks > HAWKSoft > -- > "I got some gas,... all I need is a house, a Porche, a highway, and a > girlfriend." > -- C. Dean Sparkman > ---------------------------------------- > \ ^__^ > \ (oo)\_______ > (__)\ )\/\ > ||----w | > || || > > -- > 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 From rod.barnhart at gmail.com Mon Aug 30 12:39:33 2021 From: rod.barnhart at gmail.com (Rod Barnhart) Date: Mon, 30 Aug 2021 12:39:33 -0400 Subject: [Coco] Ed Snider In-Reply-To: <20210827113604.56ce8b40@Manfred.lan> References: <20210827113604.56ce8b40@Manfred.lan> Message-ID: I ordered an item from him a few weeks back and received it in a timely manner. Didn't really communicate with him outside the ordering process, though. Rod -- "Knowledge is knowing Frankenstein wasn't the monster. Wisdom is knowing that he was." On Fri, Aug 27, 2021 at 12:36 PM Christopher R. Hawks wrote: > > Anyone heard from the Zippster recently? I know he is pretty quiet > on the list. I left a message on his website a couple of days ago and > haven't heard back. > > > Christopher R. Hawks > HAWKSoft > -- > "I got some gas,... all I need is a house, a Porche, a highway, and a > girlfriend." > -- C. Dean Sparkman > ---------------------------------------- > \ ^__^ > \ (oo)\_______ > (__)\ )\/\ > ||----w | > || || > > -- > Coco mailing list > Coco at maltedmedia.com > https://pairlist5.pair.net/mailman/listinfo/coco > From coco at jechar.ca Mon Aug 30 18:30:37 2021 From: coco at jechar.ca (coco at jechar.ca) Date: Mon, 30 Aug 2021 18:30:37 -0400 Subject: [Coco] Sugestion for Vcc Developers re: Custom KeyBoards Message-ID: <607bf3c7fe1b121fe5de062ace473028@jechar.ca> Please may I suggest that Vcc include with it three extra files VCC-Coco-DECB-Key.keymap VCC-Natural-OS-9-Key.keymap and VCC-Compact-OS-9-Key.keymap These being files that contain lines of text and can be edited using Notepad or Nano if that is desired and that describe the three standard keyboards. And in the documentation the Instructions to copy the file closest to the keymap you are looking for into "custom.keymap" and then use that VCC Custom Keyboard Map File as a starting point for creating your personal Custom Keyboard Map by customizing further without having to define every single key from scratch. Charles From ejjaquay at gmail.com Mon Aug 30 19:45:13 2021 From: ejjaquay at gmail.com (edward jaquay) Date: Mon, 30 Aug 2021 19:45:13 -0400 Subject: [Coco] Sugestion for Vcc Developers re: Custom KeyBoards In-Reply-To: <607bf3c7fe1b121fe5de062ace473028@jechar.ca> References: <607bf3c7fe1b121fe5de062ace473028@jechar.ca> Message-ID: I have a version that allows any of the four keyboard layouts to be edited. Edits are saved as text in .keymap files with simular or user defined names. I think it's operation may be more intuitive than the current version. I have been waiting on community comments to help choose the best direction for the next release. On Mon, Aug 30, 2021, 6:50 PM wrote: > > Please may I suggest that Vcc include with it three extra files > > VCC-Coco-DECB-Key.keymap > VCC-Natural-OS-9-Key.keymap > and > VCC-Compact-OS-9-Key.keymap > > These being files that contain lines of text and can be > edited using Notepad or Nano if that is desired and that describe > the three standard keyboards. > > And in the documentation the Instructions to copy the file closest > to the keymap you are looking for into "custom.keymap" > and then use that VCC Custom Keyboard Map File as a starting point > for creating your personal Custom Keyboard Map by customizing further > without having to define every single key from scratch. > > Charles > > -- > Coco mailing list > Coco at maltedmedia.com > https://pairlist5.pair.net/mailman/listinfo/coco > From linville at tuxdriver.com Tue Aug 31 15:46:12 2021 From: linville at tuxdriver.com (John W. Linville) Date: Tue, 31 Aug 2021 15:46:12 -0400 Subject: [Coco] The CoCo Crew Podcast -- Episode 75 is available! Message-ID: Episode 75 -- Community 'State of the Art' ; Issues re: CoCoSDC w/ FDC ; Review of Glen H's Joust Show notes: http://cococrew.org/cococrew-podcast-75.html The CoCo Crew Podcast homepage: http://cococrew.org/ Our usual collection of News and Announcements, plus the hosts discuss what is considered as 'advancing the state of the art in the community'. The tech segment tosses around issues related to using the CoCoSDC with a real FDC on the CoCo and Dragon, and Neil closes us out with a review of the new port of Joust to the CoCo3 by Glen Hewlett!! So...come and give us a listen? -- John W. Linville Someday the world will need a hero, and you linville at tuxdriver.com might be all we have. Be ready. From linville at tuxdriver.com Tue Aug 31 15:48:10 2021 From: linville at tuxdriver.com (John W. Linville) Date: Tue, 31 Aug 2021 15:48:10 -0400 Subject: [Coco] The CoCo Crew Podcast -- Episode 75 is available! In-Reply-To: References: Message-ID: On Tue, Aug 31, 2021 at 03:46:13PM -0400, John W. Linville wrote: > Episode 75 -- Community 'State of the Art' ; Issues re: CoCoSDC w/ FDC ; Review of Glen H's Joust > > Show notes: http://cococrew.org/cococrew-podcast-75.html > > The CoCo Crew Podcast homepage: http://cococrew.org/ > > Our usual collection of News and Announcements, plus the hosts > discuss what is considered as 'advancing the state of the art in the > community'. The tech segment tosses around issues related to using the > CoCoSDC with a real FDC on the CoCo and Dragon, and Neil closes us out > with a review of the new port of Joust to the CoCo3 by Glen Hewlett!! > > So...come and give us a listen? > > -- > John W. Linville Someday the world will need a hero, and you > linville at tuxdriver.com might be all we have. Be ready. P.S. Also available on YouTube -- https://www.youtube.com/watch?v=LG5HQ2rgUGQ -- John W. Linville Someday the world will need a hero, and you linville at tuxdriver.com might be all we have. Be ready.