Re: Slightly OT: bad rap for Fedora, and realistic effects

Ric Moore wrote:

It was a bit of a clunker, but it worked just fine. All the CP/M
machines I had had 64k of memory, and I had darn near one of each. Ric

I had an 8085 based one that could only use 60k because of where 2K
of ROM was mapped in. It was not designed to let you map out the ROM
after booting. I still have a Z-80 system with 64k of dynamic RAM,
and 256K of static RAM - the static RAM has battery backup. The
system uses extended addressing, and the disk controller uses the
static RAM as a RAM disk. (DMA support as well.) You would be
surprised st how much faster the system boots/runs when you use the
RAM disk as the system drive. It also help to have the WS overlay
files on it.

Mikkel
--

Do not meddle in the affairs of dragons,
for thou art crunchy and taste good with Ketchup!

--
fedora-list mailing list
fedora-list@xxxxxxxxxx
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list

Relevant Pages

  • Re: Slightly OT: bad rap for Fedora, and realistic effects
    ... It was not designed to let you map out the ROM ... I still have a Z-80 system with 64k of dynamic RAM, ... and 256K of static RAM - the static RAM has battery backup. ... RAM disk as the system drive. ...
    (Fedora)
  • Re: I have a IIgs. So now what?
    ... But the Classic had the whole shebang in ROM. ... It would have been implemented with a ROM disk that contained the system ... implemented a ROM disk in static RAM with backup battery. ... later system software, which would have run newer system software (and ...
    (comp.sys.apple2)
  • Re: ON TOPIC: 1541 damageable by software?
    ... Thus, the ROM and the 6502 could drive the data bus simultaneously, which could damage something, theoretically. ... The schematic clearly shows that the the roms will dump data on the data bus if any address is selected over $8000. ... However an incrementation of the PC counter and a read of the data bus may cause conflict with the rom and the static ram. ... I don't foresee that this would be a problem with normal rom routines, however a ram based routine may cause a problem. ...
    (comp.sys.cbm)