> 2) All this information about DOS mode is very interesting. How does
> one write directly to the Omnigo screen in DOS? Does the keyboard
> require special drivers to work as well? How about pen input,
> anybody find out how to directly reference the pen?
The OmniGo DOS screen is just a "window" to a screen with CGA memory layout, so
once you have set the hardware into the proper mode (using one of the text mode
drivers), you can use all the ways of screen access open to a DOS application.
The keyboard doesn't require any drivers, but it can use some remapping. :-)
Afaik, pen input from DOS level has not yet been documented.
> 3) About book reader, is the format of book reader content files
> available anywhere? I'd like to create an offline webbrowser for
> the Omnigo. (Use the PC to download the HTML and convert it to book reader
> files).
Book reader content files are very closely related to the storage format used by
Geos text objects, and their format is not even documented from the perspective
of a Geos program, let alone as an independant file format. Your best bet would
be to write a Geos application that reads and formats an HTML file and displays
it in a text object - this is not too difficult, and it avoids any troubles with
the book reader.
> 4) Disk compression: Does GEOS access DOS or the BIOS to do file reads
> and writes? I have enough code lying around to write a good disk
> compression program provided that GEOS uses DOS for file access.
I know of at least one DOS-level decompression TSR that works well with Geos on
the OmniGo (dLite 1.12 by Rainer Schuetze from Germany), and I have heard of
success stories using Stacker on the Zoomer. DIET doesn't seem to work too well
with Geos, and its need for temporary files may become a problem in low-memory
situations.
> 5) How many other people are developing applications for the Omnigo?
> (Please drop me a line)
Count me for one. :-)
ciao marcus