[Coco] My first CoCo device (virtual)

[Stephen Fischer]

I used a program to split one of the standard libraries into separate files.

Then I was able to change the first address the "core" file was missing 
to enable the loader maps to match the "core" dumps.

I used the file list driven merge program to put it all back together.

OS9Gen is that merge program. It does do one other task, write the file 
the DECB "DOS" command reads to start the boot process. I make sure that 
part was done before doing the library put together task. Using floppies 
of course.

I am unsure if the library split program which came from Delphi is 
available now.

http://cococoding.com/sfischer/SHF%20OS-9%20Disks/Z/SHF79.DSK

May have that program, I do not remember the name after so many decades.

Anybody besides me ever look at the loader maps?

SHF


On 5/28/2019 10:26 PM, Walter Zambotti wrote:
> I have been playing around with writing a virtual device module for OVCC.
> 
>   
> 
> It provides a FPU and a GPU.
> 
>   
> 
> The fpu has all the usual functions and is performing well. The FPU uses DMA
> to fetch values and write results directly into CoCo memory.
> 
>   
> 
> The GPU is still in its infancy but it can draw pixels and lines and it also
> uses DMA to draw directly into CoCo memory.
> 
>   
> 
> I now need to replace cfloats.a in clib.l with a version that can take
> advantage of the FPU.
> 
>   
> 
> I suppose I would need to change the graphics driver and libraries to take
> advantage of the GPU.
> 
>   
> 
> Walter
> 
>   
> 
> Ps OVCC on github is now public so everyone can see the code.
> WallyZambotti/OVCC
> 
>