1980 4K CoCo Programming Challenge - Revision history

AllenHuffman: Adding "Current Entries" link

2015-01-07T16:00:59Z

Adding "Current Entries" link

← Older revision		Revision as of 12:00, 7 January 2015
Line 42:		Line 42:
	* Simon Johansen has a cool [http://cocobotomy.roust-it.dk/sgedit/ VDG screen editor] that may be useful for designing CoCo 1 semi graphics screens.		* Simon Johansen has a cool [http://cocobotomy.roust-it.dk/sgedit/ VDG screen editor] that may be useful for designing CoCo 1 semi graphics screens.

			== Current Entries ==
			You can see the current entries here:

			http://subethasoftware.com/4k/
	== Admin ==		== Admin ==
	I (Allen Huffman, alsplace@pobox.com) am working on this idea. Feel free to organize and edit this page with more ideas.		I (Allen Huffman, alsplace@pobox.com) am working on this idea. Feel free to organize and edit this page with more ideas.

AllenHuffman: /* Using a Bigger CoCo */

2015-01-02T16:04:34Z

Using a Bigger CoCo

← Older revision		Revision as of 12:04, 2 January 2015
Line 34:		Line 34:
	== Using a Bigger CoCo ==		== Using a Bigger CoCo ==
	Art Flexser mentions that if you have a 16K or larger CoCo, you can simulate the limited 4K memory to BASIC using the CLEAR command:		Art Flexser mentions that if you have a 16K or larger CoCo, you can simulate the limited 4K memory to BASIC using the CLEAR command:
	CLEAR 200,~~4096~~		CLEAR 200,4095
			After doing this, "PRINT MEM" should show 2343 bytes available.

	We will have to see what tricks can be done on a 64K CoCo (copying ROM to RAM then doing some pokes) to disable Extended Color BASIC, and figure out how to do that on a CoCo 3.		We will have to see what tricks can be done on a 64K CoCo (copying ROM to RAM then doing some pokes) to disable Extended Color BASIC, and figure out how to do that on a CoCo 3.

AllenHuffman: /* Using an Emulator */

2015-01-02T15:12:37Z

Using an Emulator

← Older revision		Revision as of 11:12, 2 January 2015
Line 30:		Line 30:
	== Using an Emulator ==		== Using an Emulator ==

	You can find a quick-start guide to installing and [[Using XRoar]] to emulate an original 4K CoCo.		XRoar is a free emulator for Windows, Mac and Linux (and others). You can find a quick-start guide to installing and [[Using XRoar]] to emulate an original 4K CoCo.

	== Using a Bigger CoCo ==		== Using a Bigger CoCo ==

AllenHuffman at 01:50, 1 January 2015

2015-01-01T01:50:38Z

← Older revision		Revision as of 21:50, 31 December 2014
Line 36:		Line 36:
	CLEAR 200,4096		CLEAR 200,4096
	We will have to see what tricks can be done on a 64K CoCo (copying ROM to RAM then doing some pokes) to disable Extended Color BASIC, and figure out how to do that on a CoCo 3.		We will have to see what tricks can be done on a 64K CoCo (copying ROM to RAM then doing some pokes) to disable Extended Color BASIC, and figure out how to do that on a CoCo 3.

			== Helpful Resources ==
			* Simon Johansen has a cool [http://cocobotomy.roust-it.dk/sgedit/ VDG screen editor] that may be useful for designing CoCo 1 semi graphics screens.

	== Admin ==		== Admin ==
	I (Allen Huffman, alsplace@pobox.com) am working on this idea. Feel free to organize and edit this page with more ideas.		I (Allen Huffman, alsplace@pobox.com) am working on this idea. Feel free to organize and edit this page with more ideas.

AllenHuffman: real coco 4K notes

2015-01-01T01:21:40Z

real coco 4K notes

← Older revision		Revision as of 21:21, 31 December 2014
Line 31:		Line 31:

	You can find a quick-start guide to installing and [[Using XRoar]] to emulate an original 4K CoCo.		You can find a quick-start guide to installing and [[Using XRoar]] to emulate an original 4K CoCo.

			== Using a Bigger CoCo ==
			Art Flexser mentions that if you have a 16K or larger CoCo, you can simulate the limited 4K memory to BASIC using the CLEAR command:
			CLEAR 200,4096
			We will have to see what tricks can be done on a 64K CoCo (copying ROM to RAM then doing some pokes) to disable Extended Color BASIC, and figure out how to do that on a CoCo 3.

	== Admin ==		== Admin ==
	I (Allen Huffman, alsplace@pobox.com) am working on this idea. Feel free to organize and edit this page with more ideas.		I (Allen Huffman, alsplace@pobox.com) am working on this idea. Feel free to organize and edit this page with more ideas.

AllenHuffman: /* Using an Emulator */

2014-12-29T14:29:20Z

Using an Emulator

← Older revision		Revision as of 10:29, 29 December 2014
Line 29:		Line 29:

	== Using an Emulator ==		== Using an Emulator ==
	The Xroar emulator for PC, Mac, Linux (and more) can be configured to act as a 1980 4K CoCo. Make sure you have the "bas10.rom" ROM file (Color BASIC 1.0) and you can use the command line "-ram 4" option to limit memory to 4K. However, Xroar author Ciaran suggests creating a new entry in the GUI menu for a 4K CoCo. Edit (or create) the "xroar.conf" file (located where you have the .exe on PC, elsewhere on Mac/Linux) and create an entry like this:

	~~<pre>~~		You can find a quick-start guide to installing and [[Using XRoar]] to emulate an original 4K CoCo.
	~~default-machine coco4k~~
	~~machine coco4k~~
	~~machine-desc Tandy CoCo 4K~~
	~~machine-arch coco~~
	~~ram 4~~
	~~bas bas10~~
	~~noextbas~~
	~~nodos~~
	~~tv-type ntsc~~
	~~</pre>~~

	~~This will create~~ a ~~new entry in the Machine pull~~-~~down menu that says "Tandy CoCo 4K". The "default-machine" option will make it be the default, so just running xroar.exe will launch as a~~ 4K ~~1980~~ CoCo~~. I will add instructions for Mac (and links) when I get time~~.

	== Admin ==		== Admin ==
	I (Allen Huffman, alsplace@pobox.com) am working on this idea. Feel free to organize and edit this page with more ideas.		I (Allen Huffman, alsplace@pobox.com) am working on this idea. Feel free to organize and edit this page with more ideas.

AllenHuffman: AllenHuffman moved page CoCoCoding 1980 Contest to 1980 4K CoCo Programming Challenge: New name

2014-12-29T00:04:02Z

AllenHuffman moved page CoCoCoding 1980 Contest to 1980 4K CoCo Programming Challenge: New name

← Older revision	Revision as of 20:04, 28 December 2014
(No difference)

AllenHuffman: /* Contest Concept */ adding note about Program Pak entry

2014-12-20T22:41:25Z

Contest Concept: adding note about Program Pak entry

← Older revision		Revision as of 18:41, 20 December 2014
Line 11:		Line 11:

	== Contest Concept ==		== Contest Concept ==
	The goal here is to write something as if you were using the original 1980 CoCo. There was no Extended Color BASIC, and you couldn't afford to upgrade the memory past 4K. You only have a cassette recorder for storage... Were joysticks available when the machine was released? If so, you can use them.		The goal here is to write something as if you were using the original 1980 CoCo. There was no Extended Color BASIC, and you couldn't afford to upgrade the memory past 4K. You only have a cassette recorder for storage... Were joysticks available when the machine was released? If so, you can use them. (If someone really wants too, I suppose they would write a Program Pak entry, as a different category, allowing them to have 8K or 16K of code in ROM, using only 4K of RAM.)

	We should probably split the contest in to two categories: BASIC and MACHINE LANGUAGE.		We should probably split the contest in to two categories: BASIC and MACHINE LANGUAGE.

AllenHuffman: /* Contest Concept */

2014-12-20T22:39:27Z

Contest Concept

← Older revision		Revision as of 18:39, 20 December 2014
Line 26:		Line 26:
	* '''Emulated''' - done on a virtual CoCo		* '''Emulated''' - done on a virtual CoCo

	A '''Native/Real''' attempt would be much more "legit" in 1980 compared to an ''Cross Hosted/Emulated''' attempt, though the focus is the end result.		A '''Native/Real''' attempt would be much more "legit" in 1980 compared to an '''Cross Hosted/Emulated''' attempt, though the focus is the end result.

	== Using an Emulator ==		== Using an Emulator ==

AllenHuffman: /* Contest Concept */

2014-12-20T22:38:00Z

Contest Concept

← Older revision		Revision as of 18:38, 20 December 2014
Line 18:		Line 18:

	At the very least, we should note how the program was developed:		At the very least, we should note how the program was developed:
	* Native - programmed on a 4K CoCo		* '''Native''' - programmed on a 4K CoCo
	* Expanded - programmed on a larger CoCo		* '''Expanded''' - programmed on a larger CoCo
	* Cross Hosted - programmed on a non-CoCo		* '''Cross Hosted''' - programmed on a non-CoCo

	I suppose we can also note:		I suppose we can also note:
	* Real - done on a real, physical CoCo		* '''Real''' - done on a real, physical CoCo
	* Emulated - done on a virtual CoCo		* '''Emulated''' - done on a virtual CoCo

			A '''Native/Real''' attempt would be much more "legit" in 1980 compared to an ''Cross Hosted/Emulated''' attempt, though the focus is the end result.

	== Using an Emulator ==		== Using an Emulator ==