I'm still working on getting my Android devices to talk to my M100 via
the BlueM module.
They talk, but I'm working on creating a service and a broadcaster which
would allow one to use the M100 as a keyboard for the Android device.
I want to learn to implement the TPDD protocol, but it doesn't look
easy. Once I do that, my ambition is still to be able to connect to your
phone via the BlueM and use it for storage w/o even taking the phone out
of your pocket (a variation on "cloud" computing...)
I'm also hoping to allow Android devices to "share" their internet
connection with the M100 as a kind of filtering proxy.
I'd love to use my M100 for twitter messages (which are limited to 140
chars, anyway). An idea I thought would be cool would be if, when
viewing a tweet with an attached image, the text would appear on the
M100s screen, and the image on the Android device's screen. Or a link
would take you to a website on the Android device while still
reading/writing tweets on the M100.
I've also got SMAUG MUD sitting on my desktop. I've been toying with the
idea of running a SMAUG-based MUD, maybe writing a custom mud client for
the M100, and maybe a graphical mud client for DOS/Win/Android/etc
Dunno if possible, but it'd be nice to be able to flow seamlessly from
using one device to using another.
The M100 client could even be semi-graphical, I think.
I still wonder what could be done with the M100 via the expansion port.
I read somewhere recently that the expansion port allows for direct
access to memory. It made me wonder if someone clever could come up with
a memory management device (small, of course) plugged into the expansion
port, allowing it to semi-automatically bank-switch the memory in a
Quad, effectively expanding the "ram" of the M100 to 128k. Or,
theoretically, using a swap file system like DOS, have virtual ram as
large as your storage allows. I confess I've almost no technical
expertise, so this could be a laughable idea. To be backwards
compatible, it'd have to be able to, on the fly, change the absolute
addressing into some kind of relative addressing and back again. Of
course, then, with DMA, it could serve not just as a MMU, but
math-coprocessor, GPU, etc, since almost any such device would be
faster/more powerful than the M100's 8085...
It's interesting, I always thought the slow screen refresh would be the
most frustrating limitation on my M100, but I'm finding that it's the
limited RAM that's more frustrating.
