Customizing the Omnigo

Wayne Venables (
Sat, 18 Jan 1997 21:06:56 -0800

Hello all,

I have a question (sort of) for all you Omnigo/Geos experts. I've been
reading up on what one can do to the the GEOS.INI, and I saw a few
interesting options. I added the following to my GEOS.INI:

launchModel = 1 ;Enable single instance of applications
exitOnClose = true ;Disable state file creation.

This effectly turns off the creation of State files on the Omnigo. This
may or may not be as advantageous as it might seem.

For those who want to try it:

When an application is opened, it now exists in memory until it is closed.
This means that only a small number of applications can be opened at once
and you might run out of memory. Closing an application involves pressing
FN-F3, clicking the exit button or pressing exit on the keyboard will not
close the applications. This mode of operation might be good for those who
use only a small few Omnigo applications.

The Omnigo might behave a bit strangely in this mode too... Date and Time
don't show up on the Home Screen for example.

I have a few questions for you GEOS gurus:

How does "transparent" mode work (ie launchModel = 0), does GEOS always
close the application when you leave it or only when it needs the memory?

Clicking on the "exit" button or pressing exit on the keyboard does not
close the applications it only "minimizes" them - if I add a control menu it
has a "close" option, does this actually close the application?

Would selecting launchModel = 1 increase the speed of app switching since
the apps never get removed from main memory?

What would GEOS do if I ran out of memory typing something into notepad or
the spreadsheet?

Can I enable disk swapping on the Omnigo? Would this be worse or better
than just having GEOS create the state files and run in transparent mode?
(Assuming that I'll be "closing" most of the apps that I'm not using)


Wayne Venables Simon Fraser University Burnaby, BC, Canada