Re: ProDOS...

[Phoenyx <quazar@dcnet2000.com>]

> To be honest, I wrote the original code on paper and hand translated it
> to machine code and typed it in from the monitor. Later, after
> accidentally tripping over the mini-assembler, I began to use it to key
> in the still paper-written code. When a piece of code finally worked
> right, I'd use Appleworks to create a text document with the source code
> in it. By the time I finally got Merlin, my computer only had 2 or 3
> months to live. 

I used to program that way and it's certainly more difficult than assembly
but it has some drawbacks.
 
> As I stated before, the machine & drive that I kept that on had long
> since died. I'm currently re-writing the project based on the notes that
> I can still find. This time I'm writing the code in Merlin and backing
> it up on my PC.

A really great idea too. I think that periodic duplication to floppy disk
would also help, just in case something happens. 

> I wouldn't know how to gadge that, but the only non-relocatable portions
> were the storage locations in the 1st 4K of memory in Main and Aux0
> memory.

To efficiently use the system, modules are the key. This allows routines
to be loaded and/or unloaded as needed. Such functionality increases the
free ram available. Besides the system level modules, user modules could
be used as add on functions. These functions could also be unloaded or
reloaded as necessary. Similar to the GS's functionality.

There should be a memory manager to allocate and release ram from a
heap area. Granted, this may be difficult to implement unless the system
were to run from the aux ram. At least a large portion should run in the
aux $d000. This may require using the aux zero page and stack for the
system code. While difficult to implement, it certainly would allow for
more possibilities. This would be great for developing useful programs
which need memory but don't want to deal with the absolute addresses.

Another possibility would allow for global objects which other programs
could use. I could also envision the capability of Desk Accessories. A
feature which would be very useful.

There are so many possibilities.

> Between my job, my daughter, my parents, and my other projects, time is
> going to be a little tight between now & Jan. If I'm lucky, I'll be done
> re-constructing as much as I have notes for by mid Nov. All coding
> beyond that will be completely new.

I can understand the time issues, I'm more interested in the base source
code so others will be able to assist in the project. My reasons are
twofold.

First, you shouldn't have to do all the coding yourself. There are folks
who will help. This will require some rules to keep the code on track.

Second, users have the ability to make adaptations for specific systems.
Highly useful for oddball peripherals. This code could be incorporated
in the OS hopefully as a module.

-- 

Thank you for your time and interest. I hope it was helpful
or at least interesting.

Phoenyx,

Apple2 user since March 1984

Links to Phoenyx's pages:
preferred..... http://zip.to/Phoenyx_A2
alternate..... http://www.tinyangeldesigns.com/Apple2