Re: External RAMdisk
- From: Jack Crenshaw <jcrens@xxxxxxxxxxxxx>
- Date: Thu, 15 Jan 2009 21:11:16 -0500
rzh_nocal@xxxxxxxxx wrote:
On Jan 12, 9:34 pm, Herb Johnson <herbrjohn...@xxxxxxxxx>
Interesting thread!!
Maybe folks will be interested in this? I designed a Z80 SBC (which
ended up on 2 PCBs -- long story!). It runs at 10MHz, and has a 1 MB
battery backed RAM disk (SRAM based). The battery backup is via a
Dallas chip (DS-1202?? -- not sure if that's correct), and two D cell
flashlight batteries. I mounted the whole thing in the floppy bay
(floppies long gone) of a KayPro II that I got in a silicon valley
surplus place for $20. I goosed the KayPro II up to 5 MHz, and just
use the keyboard and screen as a "terminal" for my computer. The only
hitch is that I have to use a stall routine on my computer after it
sends out a linefeed, because the 5 MHz KayPro II can't scroll and
update its screen fast enough to keep up! The "R-Pro" (as I call it)
boots CP/M from EPROM (32K). Pictures on my Web site
(www.hanscom.us), but you'll have to drill down to find them! Oh, and
it also has an IDE interface (thanks to Phil Ruston -- www.retroleum.co.uk),
and runs on a 1 GB hard drive from Weird Stuff Warehouse, that cost me
all of $9.95. I use Xmodem to transfer files to/from the "R-Pro", and
am working on getting Zmodem up and running.
This is a *VERY* responsive system when running from the RAM disk, and
only a little slower running from the IDE drive.
Roger
FWIW< I used to have what I thought was a neat "first test" for a compiler: Compile and link the null program, then call the debugger and load the file. People used to tell me that this wasn't much of a test, because all I was measuring was the overhead time of the compiler and other tools. But to me, that's the point. I try never to write large programs that have to be compiled in one huge glop. So to me, the overhead is pretty much the entire task.
To put things in perspective, running this on a VAX 11/780, with BSD Unix, took 20 seconds, and generated a 20k object file. That doesn't include invoking the debugger. This was also at night, when I was the only user.
The same program, compiled on VAX/VMS, took a full 60 seconds and generated a 50k object file.
On my Kaypro (4 MHz) with an HD, I had a script file that did the whole thing. Compiling under BDS C, it took 0.6 sec, and generated a 2k object file.
Doing the same thing on the 2MHz Kaypro with RAMdisk took 0.2 sec. That's basically one tick of my stopwatch.
I told this story once, to New Zealander John Spray, who wrote a neat little Pascal-like compiler for the 68000, called Whimsical. I was bragging on the small size of the BDS C object file. He said, "Try it on Whimsical." I did. The file was under 256 bytes. This blew me away. But John said, "There's more to it than that. If you use the right compiler flags, you can get it down to two bytes, one 68000 instruction." The instruction? RETS.
I also like one of John's dictums a lot: "The best way to optimize the object code from a compiler is to not let it generate bad code in the first place" <g>.
Jack
On my 2MHz
.
- References:
- External RAMdisk
- From: Jack Crenshaw
- Re: External RAMdisk
- From: no . spam
- Re: External RAMdisk
- From: Jack Crenshaw
- Re: External RAMdisk
- From: Herb Johnson
- Re: External RAMdisk
- From: rzh_nocal
- External RAMdisk
- Prev by Date: Re: External RAMdisk
- Next by Date: Scelbi Basic
- Previous by thread: Re: External RAMdisk
- Next by thread: Re: External RAMdisk
- Index(es):
Relevant Pages
|
Loading