headers
Arthur Flexser | 1 Dec 2009 01:14
Favicon

Re: drivewire serial port progress

You might check if pin 37 of the edge connector of the Super Controller
shows proper continuity to pin 26 of the EPROM socket, which is the line
that controls access to the upper 8K.

Art

On 11/30/09, Roger Taylor <operator@...> wrote:
>
> At 10:49 AM 11/30/2009, you wrote:
>
>>  I
> Now you ask, why do I use DriveWire when I have my own bitbanger drive
> system?  Because I can't get my 16K ROM to work in the Super Controller!  It
> just won't work.  It's like only the lower 8K is seen.  There's a jumper on
> the board that I have no clue about and it didn't seem to help any.  As soon
> as CoCoNet boots up and is scanning the ports for available devices (you can
> see this on the text screen), the first call to the upper bank causes a
> crash.  Yes, I'm doing it the right way.  The ROM works in any socket-based
> pak I've got but the Super Controller.
>
> --
> ~ Roger Taylor
>
>
>
>
> --
> Coco mailing list
> Coco@...
> http://five.pairlist.net/mailman/listinfo/coco
(Continue reading)

Permalink | Reply | 3 comments |
headers
Mike Pepe | 1 Dec 2009 01:38
Favicon

Re: drivewire serial port progress

I think the CoCo3 only enables the CART line for the first 8K of the external ROM by default, but I'd have to
recheck the service manual to be sure about that.

> -----Original Message-----
> From: coco-bounces@... [mailto:coco-
> bounces@...] On Behalf Of Arthur Flexser
> Sent: Monday, November 30, 2009 4:15 PM
> To: CoCoList for Color Computer Enthusiasts
> Subject: Re: [Coco] drivewire serial port progress
> 
> You might check if pin 37 of the edge connector of the Super Controller
> shows proper continuity to pin 26 of the EPROM socket, which is the
> line
> that controls access to the upper 8K.
> 
> Art
> 
> On 11/30/09, Roger Taylor <operator@...> wrote:
> >
> > At 10:49 AM 11/30/2009, you wrote:
> >
> >>  I
> > Now you ask, why do I use DriveWire when I have my own bitbanger
> drive
> > system?  Because I can't get my 16K ROM to work in the Super
> Controller!  It
> > just won't work.  It's like only the lower 8K is seen.  There's a
> jumper on
> > the board that I have no clue about and it didn't seem to help any.
> As soon
(Continue reading)

Permalink | Reply | 2 comments |
headers
Arthur Flexser | 1 Dec 2009 01:46
Favicon

Re: drivewire serial port progress

The upper 8K is definitely accessible on a CoCo 3 IF you have a controller
that has that upper address line properly connected.  Most Radio Shack
controllers do not, but all third-party controllers that I know of,
including the Disto Super Controller, do, though Roger's may be defective in
that respect.

Art

On 11/30/09, Mike Pepe <lamune@...> wrote:
>
> I think the CoCo3 only enables the CART line for the first 8K of the
> external ROM by default, but I'd have to recheck the service manual to be
> sure about that.
>
>
> > -----Original Message-----
> > From: coco-bounces@... [mailto:coco-
> > bounces@...] On Behalf Of Arthur Flexser
> > Sent: Monday, November 30, 2009 4:15 PM
> > To: CoCoList for Color Computer Enthusiasts
> > Subject: Re: [Coco] drivewire serial port progress
> >
> > You might check if pin 37 of the edge connector of the Super Controller
> > shows proper continuity to pin 26 of the EPROM socket, which is the
> > line
> > that controls access to the upper 8K.
> >
> > Art
> >
> > On 11/30/09, Roger Taylor <operator@...> wrote:
(Continue reading)

Permalink | Reply | 1 comment |
headers
Aaron Wolfe | 1 Dec 2009 01:52
Picon

Re: drivewire serial port progress

On Mon, Nov 30, 2009 at 2:18 PM, Roger Taylor <operator@...> wrote:
> At 10:49 AM 11/30/2009, you wrote:
>>
>> I agree it's ambiguous, but I think he was trying to say you can do
>> whatever you want on your own machine ("you own programs") but you
>> can't use his code in something that you distribute to others ("for
>> public release").
>>
>> Legally, I don't know if his license would hold any water anyway, but
>> I like to follow the spirit of these things rather than the letter.
>>
>> The code is not very complex, and Mr. Olsen's implementation is very
>> basic.  The virtual modem I'm just now finishing up for DriveWire is
>> much nicer (supports more commands, more efficient, etc).  Porting
>> this to the Windows version will be easier than adapting Internet
>> Modem anyway :)
>
> I don't know... the program is already there to build on or restructure
> without rewriting it from scratch.  And I've looked at the code and have
> decided that it is not "very basic".  The code that processes the commands
> is rather simple but the networking stuff took skill and knowledge and I
> doubt anybody can just whip that up overnight.  If you can do that and make

It took more than one night, but both a virtual modem and some nice
multithreaded networking code is complete in my modified drivewire
server.  There isn't much that translates cleanly between C and .Net,
but if my code is of any use to you, you're welcome to it.

I'm going to do.. something.. on the Windows side of DriveWire.  The
current server is written in Delphi, something I don't have access to
(Continue reading)

Permalink | Reply | 2 comments |
headers
Gene Heskett | 1 Dec 2009 04:07
Picon

Re: drivewire serial port progress

On Monday 30 November 2009, Arthur Flexser wrote:
>The upper 8K is definitely accessible on a CoCo 3 IF you have a controller
>that has that upper address line properly connected.  Most Radio Shack
>controllers do not, but all third-party controllers that I know of,
>including the Disto Super Controller, do, though Roger's may be defective
> in that respect.
>
>Art

Something is tickling the back of what little memory I have left.  I _think_ 
there is a jumper in the SC-II that controls whether the eprom is an 8k or a 
16k.  Check your docs on it Roger, just to satisfy an aging mind, if for no 
other reason.

--

-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
The NRA is offering FREE Associate memberships to anyone who wants them.
<https://www.nrahq.org/nrabonus/accept-membership.asp>

I'm not even going to *______bother* comparing C to BASIC or FORTRAN.
		-- L. Zolman, creator of BDS C

--
Coco mailing list
Coco@...
http://five.pairlist.net/mailman/listinfo/coco
(Continue reading)

Permalink | Reply | 0 comments |
headers
jdaggett | 1 Dec 2009 04:24
Favicon

Re: TRS-80 Color Computer: Wikipedia Article

On 30 Nov 2009 at 15:39, Lothan wrote:

> Don't forget that Tandy did not want the Color Computer to compete with
> the 
> Model III and IV because Radio Shack considered those "business class" 
> computers even though they were inferior in many ways. The real 
> differentiator in those early days was that Radio Shack had sunk a ton of
> money into business applications for the Model III and IV and was heavily
> promoting those to small businesses and promoted the Color Computer 
> exclusively to the education/home hobbyist/gaming market.

Also consider this that Motorola by the mid 80's considered the MC6809 a dead end 
processor. By then, the MC68K series were the main processor Motorola was selling for 
MACs and other industrial computers. For embedded processors the MC6805 and the 
HC11's were better suited for that process. The MC6809 died for lack of use. Outside the 
Coco and its derivatives the MC6809 was being pushed to the back burner. 

I once told a manager that did support for the HC11 line and told him that the biggest falilure 
of the HC11 was not including the U register. He agreed with me that it would have made the 
HC11 a bit more powerful. The HC12 finally incorparated most if not all the addressing 
modes of the MC6809 but still lacks the U register. 

If only the HC12 had a fourth pointer register! That would be a fantastic processor to migrate 
MC6809 code to. 

james
james 

--
Coco mailing list
(Continue reading)

Permalink | Reply | 0 comments |
headers
Aaron Wolfe | 1 Dec 2009 05:54
Picon

rs232/bitbanger in MESS?

Hi,

Looking through the MESS source, I find some interesting files in the
src/mess/devices directory:  coco_232.c and bitbngr.c.   The head of
the coco_232 file says "Code for emulating the CoCo RS-232 PAK".
bitbngr.c says "TRS style "bitbanger" serial port".  There is also a
file called orch90.c with description "Code for emulating the CoCo
Orch-90 (Orchestra 90) sound cartridge".

I am having no luck figuring out how I would use these, or finding any
reference to them.  Anybody have any info?

-Aaron

--
Coco mailing list
Coco@...
http://five.pairlist.net/mailman/listinfo/coco
Permalink | Reply | 6 comments |
headers
Wayne Campbell | 1 Dec 2009 10:58
Picon
Favicon

error trapping

I need to know how to trap an error generated by the makdir command when it's being executed with a SHELL
statement in a Basic09 subroutine. If I try to use it, and the directory already exists, the error is
displayed on the screen, despite the fact that I am using a ON ERROR GOTO statement to trap it. Execution
resumes in the correct location in the code, but I can't find anything in the OS-9 manual about suppressing
error messages.

Can anyone help?

Wayne

--
Coco mailing list
Coco@...
http://five.pairlist.net/mailman/listinfo/coco
Permalink | Reply | 16 comments |
headers
Mark Marlette | 1 Dec 2009 14:13

Re: drivewire serial port progress

Aaron,

I have not seen the blue screen in the DW server either. 

We run this 24/7 for testing on every CoCo product we ship out.

Regards,

Mark
Cloud-9

----- Original Message -----
From: "Aaron Wolfe" <aawolfe@...>
To: "CoCoList for Color Computer Enthusiasts" <coco@...>
Sent: Monday, November 30, 2009 6:52:53 PM GMT -06:00 US/Canada Central
Subject: Re: [Coco] drivewire serial port progress

On Mon, Nov 30, 2009 at 2:18 PM, Roger Taylor <operator@...> wrote:
> At 10:49 AM 11/30/2009, you wrote:
>>
>> I agree it's ambiguous, but I think he was trying to say you can do
>> whatever you want on your own machine ("you own programs") but you
>> can't use his code in something that you distribute to others ("for
>> public release").
>>
>> Legally, I don't know if his license would hold any water anyway, but
>> I like to follow the spirit of these things rather than the letter.
>>
>> The code is not very complex, and Mr. Olsen's implementation is very
>> basic.  The virtual modem I'm just now finishing up for DriveWire is
(Continue reading)

Permalink | Reply | 1 comment |
headers
Robert Gault | 1 Dec 2009 14:35
Picon

Re: error trapping

Wayne Campbell wrote:
> I need to know how to trap an error generated by the makdir command when it's being executed with a SHELL
statement in a Basic09 subroutine. If I try to use it, and the directory already exists, the error is
displayed on the screen, despite the fact that I am using a ON ERROR GOTO statement to trap it. Execution
resumes in the correct location in the code, but I can't find anything in the OS-9 manual about suppressing
error messages.
>
> Can anyone help?
>
> Wayne
>
>

Looks like the error is going to the Shell rather than back to Basic09. 
You may be able to get the Shell command to ignore the error by using 
the following syntax:
SHELL " -x makdir"+dirname
I've not tested this but if it works, the Shell will not make the 
directory because it exists but will return to Basic09 rather than 
halting on the error. Then it's a question of what you want your Basic09 
program to do as it won't know an error occurred.

--
Coco mailing list
Coco@...
http://five.pairlist.net/mailman/listinfo/coco
Permalink | Reply | 1 comment |

Gmane