[Coco] Banked switched roms
John Collyer
johncollyer at zoominternet.net
Fri Jan 30 08:57:04 EST 2004
You can plainly see the beauty of having a virtual $FFxx address space
and having the emulator link in any hardware found. I can have the PC's
Clock interface linked in/out to it's default location. I could link in/out
the
virtual hard drives (*.vhd) to their default locations. If and when virtual
hardware devices became available I could link them in/out. I can even
make the NoCan 64MB interface to be one of the virtual hardware
devices and link it in/out to it's default address locations. Your
responsibility as a user would be to make sure there are no
virtual hardware address conflicts.
John Collyer
----- Original Message -----
From: "John Collyer"
> Both of these solutions sound like good ways to get the banked switched
rom
> data,
> but I have no access to the data that these solutions produced. However
the
> bank
> switching is in place, and I suspect that if the banked switch data was
> placed in a
> binary file that it would work with my bank switching method. I have some
> idea
> as to how you would create one of these banked switched roms, and if you
> wanted
> to create one then the means of testing it is there. This lends itself
> towards a developer
> view of the emulator and that is exactly why I wanted to make the
emulator.
> To let you
> have a way of creating products being either rom/ram or whatever type of
> software you
> select that will run on a real coco. I myself will try my hand at
creating
> the 512K/256K
> Banker board. This will be what I call a virtual device driver. This
will
> be one of the
> cartridges you'll be able to plug into the MPI interface I'm creating.
Let
> me add this
> statement, "Wow this stuff is exciting, it's like a big construction
> project, except your
> building your project with binary 0's and 1's." Don't laugh!
John Collyer
More information about the Coco
mailing list