[Coco] Terminal program for 16K non-ECB coco?

Mon Sep 10 02:13:44 EDT 2012

I'm pretty sure Mike never had a 1200 bps rate though the bitbanger,
though I think later versions did support higher rates through the
RS232 Pak.

Art

On Mon, Sep 10, 2012 at 2:09 AM, Bill Pierce <ooogalapasooo at aol.com> wrote:
>
> I think MikeyTerm did go to higher baud rates later as Mike Ward found better ways of accessing the bitbanger. I only used 300 baud myself the whole time I had my Cocos going. That DCM-3 was a tough little critter. It lasted through 4 Cocos. I always wanted an auto-dial modem but could never afford one.
>
> Music from the Tandy/Radio Shack Color Computer 2 & 3
> https://sites.google.com/site/dabarnstudio/
> Bill Pierce
> ooogalapasooo at aol.com
>
>
>
>
> -----Original Message-----
> From: Arthur Flexser <flexser at fiu.edu>
> To: CoCoList for Color Computer Enthusiasts <coco at maltedmedia.com>
> Sent: Mon, Sep 10, 2012 1:54 am
> Subject: Re: [Coco] Terminal program for 16K non-ECB coco?
>
>
> One thing I recall about Mikeyterm (all versions) is that it was
> 300-baud only (unless later versions supported the RS232 Pak).  I was
> in touch with Mike Ward as he was developing the program, and I recall
> that he wanted 100% bulletproof full-duplex communications, and that
> precluded 1200 baud through the bitbanger, according to him.  So I
> greatly preferred Colorcom/E at the time because it supported 1200
> baud, though I don't recall if it could be used in 16K if you didn't
> have the Rompack version.  There was no cassette version of
> Colorcom/E, at least initially, and I recall saving and modifying
> (relocating) the Rompack version to turn it into one.  Colorcom/E
> could output text to a PMODE screen, but that slowed things down too
> much for my taste and I preferred the standard text screen output.
>
> Art
>
> On Mon, Sep 10, 2012 at 1:41 AM, Bill Pierce <ooogalapasooo at aol.com> wrote:
>>
>> Chris, I can't find one old enough. The smallest one I can find is 20k. I know
> there was one fo 16k because I used it for about a year till I upgraded to a 64k
> machine. It always pissed me off when my buffer would get full and I'd realise
> that the file I was downloading was larger than my memory. I have few cassettes
> that survived Hurrican Floyd so I may ty looking through them. It will be
> sometime next week though due to the fact I am not at home and my Coco is. I
> return home Friday and I'll search those tapes.
>>
>> Music from the Tandy/Radio Shack Color Computer 2 & 3
>> https://sites.google.com/site/dabarnstudio/
>> Bill Pierce
>> ooogalapasooo at aol.com
>>
>>
>>
>>
>> -----Original Message-----
>> From: chris <cralt at comcast.net>
>> To: CoCoList for Color Computer Enthusiasts <coco at maltedmedia.com>
>> Sent: Mon, Sep 10, 2012 12:57 am
>> Subject: Re: [Coco] Terminal program for 16K non-ECB coco?
>>
>>
>> Bill,
>>
>> So is Mikey happy to live in 16K?
>>
>>
>> CAPS ONLY is kinda a pain on a unix machine.. lol
>>
>>
>> thanks
>> -chris
>>
>> On Sep 8, 2012, at 12:26 PM, Bill Pierce wrote:
>>
>>>
>>> No need for further discussion. That did what I wanted. It seems for
>>> some reason, the Coco emulater is not indented in the list as the
>>> others. I had assumed it was a catagory listing and not an emulator
>>> as all the other Cocos are indented under it. Too many years in
>>> Windows Explorer I guess :-)
>>>
>>> Thanks again Mr Gault. The whole reason for this was to test some
>>> versions of MikeyTerm I've found for Chris and I wanted to emulate
>>> his machine.
>>>
>>> Music from the Tandy/Radio Shack Color Computer 2 & 3
>>> https://sites.google.com/site/dabarnstudio/
>>> Bill Pierce
>>> ooogalapasooo at aol.com
>>>
>>>
>>>
>>>
>>> -----Original Message-----
>>> From: Robert Gault <robert.gault at att.net>
>>> To: CoCoList for Color Computer Enthusiasts <coco at maltedmedia.com>
>>> Sent: Sat, Sep 8, 2012 11:09 am
>>> Subject: Re: [Coco] MESS at 16k non-ext was Terminal program for 16K
>>> non-ECB coco?
>>>
>>>
>>> Bill Pierce wrote:
>>>>
>>>> Mr Gault... I should have known better <laughing>
>>>>
>>>>  I'm not trying to change ANY hardware into any others. I mearly
>>>> want to set
>>> a Coco 2 or Coco 1 to 16k, Color Basic. (no ext basic), as was a
>>> standard retail
>>> configuration (I own one). I tried 2 versions of MESS, "Mess0125b" &
>>> "mess0143b_x64" (I have a 64 bit machine), both in Windows Home
>>> Premium 64 bit.
>>>>
>>>>  When the "Ext Basic" roms are removed from the rom zips, NO
>>>> version of Coco
>>> 1 or 2 will run at all. MESS reports missing Roms and exits the
>>> emulation. The
>>> Coco 1 will actually set to 4k, 16k, 32k, & 64k.... BUT....
>>>> Did anyone ever successfully run Ext Basic in 4K?
>>>>
>>>> I do not know how to set the "ini" file in ANY version of MESS, and
>>>> maybe this
>>> is what I should have asked in the beginning. Can you turn off the
>>> "Ext Basic"
>>> rom check? If so, How? And what version would do this best? I can
>>> and will run
>>> any Windows or Dos version to achieve this.
>>>>
>>>
>>> OK, I've tested with MESS .143 .
>>>
>>> With MESS, if you don't want Extended Basic present, you should use
>>> coco
>>> emulation not cocoe, coco2, coco2b or anything else. I've tried
>>> coco2 emulation
>>> and while you can remove the disk11.rom you can't get rid of the
>>> extbas11.rom
>>> and get emulation to start.
>>>
>>> This version still supports messui.exe and with my Windows system, I
>>> find it
>>> easier to set parameters using messui.exe than mess.exe. Even with
>>> coco2, I can
>>> set and get PCLREAR1 PRINTMEM 13095.
>>>
>>> Now, I find MESS .143 slightly buggy. That's because setting
>>> parameters for
>>> specific emulations does not always take. It helps when using
>>> messui.exe to set
>>> the paramters for say coco and then kill messui.exe. The next time
>>> it starts the
>>>
>>> parameters usually take.
>>> MESS uses the sub-directories cfg and ini to store parameters. If
>>> you set
>>> parameters or even used coco emulation, you should find a coco.ini
>>> file. Right
>>> clicking on an emulation in messui.exe permits selection of
>>> properties and there
>>>
>>> is a configuration panel for selecting memory size.
>>> ROMs are stored in the sub-directory roms which either holds zip
>>> files or more
>>> sub-directories for each emulation with .rom files.
>>>
>>> When coco is set for 16K and started, you should see
>>> COLOR BASIC 1.0
>>> Enter the following
>>> PRINT MEM
>>> and see
>>>  14631
>>>
>>> I think that further discussion would be better off this list by
>>> direct e-mail.
>>>
>>> --
>>> Coco mailing list
>>> Coco at maltedmedia.com
>>> http://five.pairlist.net/mailman/listinfo/coco
>>>
>>>
>>>
>>> --
>>> Coco mailing list
>>> Coco at maltedmedia.com
>>> http://five.pairlist.net/mailman/listinfo/coco
>>
>>
>> --
>> Coco mailing list
>> Coco at maltedmedia.com
>> http://five.pairlist.net/mailman/listinfo/coco
>>
>>
>>
>> --
>> Coco mailing list
>> Coco at maltedmedia.com
>> http://five.pairlist.net/mailman/listinfo/coco
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco
>
>
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco