[Coco] Re: Re: CoCo related question? (Better edit for coco3.rom)

[jdaggett at gate.net]

Albert

by compressing the basic interpreter you will slow down an already 
slow process. Not a wise decisison. 

I would run a program like TSEDIT for RSDOS and use that as an 
editor to write basic programs. If you are familiar with Unix VI editor 
then TSEDIT is nearly identical. 

james

On 23 Mar 2005 at 19:58, Albert Stinger wrote:

To:             	coco at maltedmedia.com
From:           	"Albert Stinger" 
<albertstinger24 at canada.com>
Date sent:      	Wed, 23 Mar 2005 19:58:23 -0500
Subject:        	[Coco] Re: Re: CoCo related question? 
(Better edit for coco3.rom)
Send reply to:  	CoCoList for Color Computer Enthusiasts 
<coco at maltedmedia.com>
	<mailto:coco-
request at maltedmedia.com?subject=unsubscribe>
	<mailto:coco-
request at maltedmedia.com?subject=subscribe>

> That would make a nice addition to the rom being you only get 32K on
> board rom and either a 16K or 32K cartridge rom. The rom image could
> be compressed and in the normal startup code you could include the
> decompression of rom into ram, but how much extra space would you get
> by compressing the rom image?
> 
> Albert Stinger
> 
> "John R. Hogerhuis" <jhoger at pobox.com> wrote 
> in message news:1111608552.15697.388.camel at aragorn...
> > On Wed, 2005-03-23 at 13:07 -0500, Albert Stinger wrote:
> >> More questions,
> >>
> >> Exactly how much rom space is available in the coco3 rom and
> >> could be used to make a better edit command?  Where is this
> >> rom space located in the rom image?  What would be the best
> >> way to interface to the edit command so you could have full
> >> screen editing with the cursor keys?
> >>
> >
> > Well I think coco3 copies ROM to RAM and runs from there.
> >
> > Maybe you could compress the ROM image and get some space that way?
> > Then your extensions would reside in the ROM, but you would run them
> > from RAM. Lots of RAM in the coco3.
> >
> > You would lose a bit of space to the decompression routine though.
> > But typically decompression routines are fairly small compared to
> > compression routines. On balance, I'm sure you would gain some
> > space.
> >
> > The compression routine would just be run on the desktop.
> >
> > -- John.
> >
> >
> >
> > -- 
> > 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