BigEd wrote:
Relatively often we see a 65xx system with more than 64k of RAM - sometimes an '816 system, sometimes an '02 system with memory banking or paging.
But here's a discussion question: what to do with a large memory model? What's the killer app, or the driver, or the useful-thing-to-do, with lots of memory?
Interesting to hear both about actual things-that-have-been-done, and things-that-might-be-done.
The Gamecube used a spinning disc because it was always accessing the disc.
At work we are using a humidity data logger that uses an SD card.
Bluetooth uses a stack so you would need lots of memory to use Bluetooth if that were a possibility.
Flight Simulator by Microsoft used a disk drive so a ram or rom based system like a GPS could reside in RAM.
Interesting that Simon's basic actually took away from memory so that the extra commands could reside in memory.
I wrote programs that ran out of string memory from regular CBM basic. It is frustrating to write a program only to run out of memory. One of the popular apps on my cell phone is 50 megabytes in size so in terms of computing power, more is better.
I have an updated cell phone that can handle a lot more texts from the previous model. The old cell phone use to stall when we had around 7 to 8 thousand text messages and the newer model seems to flow seamlessly between messages.
The reality is that people need terabyte hard drives because of video now a days and they keep getting larger and larger.
If you were to compete by building a 65XX system compared to the PC or cell phone, you would need a lot more in terms of resources. The real question is, "What are you going to put on the bus of that CPU to use it?"