Questions
1. How to force an application to exit in standard (non-expert) mode?
2. Any way to save preferred configurations for standard apps?
3. Faxing?
4. Geos 3.0 compatible at what level? SDK?
5. Multiple windows/files possible with new Zoomer Text Editor?
6. Optimal memory setting in .ini file?
7. Quick cut/paste a la Geos desktop apps?
8. GeoCalc (in)compatibility (I think its a library!)?
9. Anyone hack the spell.lib down to reasonable size?
10. Ports for modem card, IR interface, serial interface?
11. Read the pen position (from DOS programs)?
12. Generate control characters for terminal comm with Graffiti?
13. What is loader.exe and how does it relate to the Geos kernel?
14. How much speedup does the newer motif.geo really give?
15. Anyone ever try diet, a PD real-time file compression utility?
Answers and Observations
1. Print to file can be set up -- can this help on faxing?
2. Graffiti sometimes gets locked into a mode where pen taps even
outside its window are interpreted as punctuation escapes.
3. A crash in "File Transfer" mode which had to be handled with a
reset brought me back to the apps running before I entered that mode.
4. Running the standard Geos or Zoomer text editors on ROM files can
crash the system (or make you have to reset).
5. The [paths] trick makes Geos tweaks much easier.
More verbose . . .
I'm running in semi-Expert mode, but with the standard (=0) launch
model, because I like to come back to exactly what I was doing.
Normally the system swaps apps out well, but I do find I have to
reboot fairly frequently. I have
maxTotalHeapSpace=45000
Is there a better number?
This model offers no "Exit" on "File" menus and closing a window
really just pushes it to the back. Can exiting be forced or a change
made to a .ini to allow it? This is irritating when, for example, a
task owns a file I want to look at.
I don't know if the Geos PrefMgr runs on the Zoomer, but if you want
multiple printers or the ability to print to file you can make the
entries directly into geos.ini and they will show up in your print
dialogs. This can also get you print to file (for which you also need
the c streams driver, cstream.geo). I thought this might help on the
eternal faxing question, since now I can produce a PCL file, but no
program that I run seems to be able to recognize the modem card
(standard AMT Starcard). I remember reading that there is no real
com: driver -- is that true? Is there a special combination of
interrupts/ports that might work?
I finally recovered my GeoCalc 2.0 -- and it still gives me the
incompatible operating systems message!! Does this suggest that this
problem is due to a library conflict? (I kept all of the 2.1
libraries). Is a different motif.geo or loader.exe in order?
The immediate re-entry to my apps after crashing in File Transfer mode
suggested to me that there might be a way to store my preferred
options in the state files and trick the zoomer into thinking it was
coming back from a call to DOS whenever it reboots? How does it know
this? Absence of geos_act.ive? How does it know which apps were
active and which swapped out?
Sorry if any of this is covered by the FAQs -- I can't get through to
check them out right now, but I don't remember these items being addressed.
Bill
smith@io.dsd.litton.com