MediaWiki:Sitenotice:
2025-12-29: I have restored the wiki to a backup from the end of November. Starting in September 2025, accesses went form the 800MB-1.2GB range per month to 26GB in September, 42GB in October, and 70GB in November with most accesses originating from China. As soon as I realized what was causing all the access problems in November, I shut it down (it had reached 36GB by then) behind a password/login screen. The database had gotten corrupted, and I tried a restore from just before the spike in access but that didn't work. Thus, end of November. I still have the other daily backups so if there were any important additions in December, let me know and maybe they can be recovered. - Allen H.

Other I/O

From CoCopedia - The Tandy/Radio Shack Color Computer Wiki
Revision as of 21:17, 2 February 2007 by JOELAV (talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

Built-in I/O

1/25/2007 2:09 PM

From:  Mike Pepe

Joel Ewy wrote:

> > What about including a controller that would look to the CoCo like a WD
> > FDC, but which actually works with CoCo disk images on removable flash
> > media, such as MMC or CF?  The hardware could include a way to select
> > from multiple disk images via an external 3.5" form factor control
> > panel, perhaps with a 3-digit 7-segment display, and also an extra
> > internal register that new software could use to do the same
> > programmatically.  This would work with existing DECB and all other
> > current software, but could provide a much more reliable, convenient,
> > and compact removable mass-storage system.  Also, if the embedded
> > microcontroller can manage its CoCo image files on a FAT filesystem on
> > the flash drive, it also becomes a very convenient way to transfer files
> > between the PC and CoCo.  If the microcontroller core was sufficiently
> > similar to a real controller, these things could also be made as
> > stand-alone units for older CoCos, and they'd remain compatible.

That's a really great idea, but I'm thinking all the external hardware 
to control that pseudo-floppy is expensive. Wouldn't it be cool if the 
CPU core had an alternate register set and memory space? Like a 
user/supervisor mode- you hit a hotkey and the normal processing is 
suspended, you get an on-screen menu to mount/unmount floppy images with 
names and descriptions (instead of a number on an LED display) then you 
can just resume normal operation. Kind of like how MESS works. It would 
probably be less costly from a hardware perspective I would assume.