Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!wuarchive!uunet!comp.vuw.ac.nz!actrix!Andrew.Merton
From: Andrew.Merton@actrix.gen.nz (Andrew Merton)
Newsgroups: comp.sys.ibm.pc.misc
Subject: Re: Geoworks
Message-ID: <1991Jun12.205801.754@actrix.gen.nz>
Date: 12 Jun 91 20:58:01 GMT
References: <1991Jun11.122522.26314@magnus.acs.ohio-state.edu> <1991Jun11.210447.18721@actrix.gen.nz> <15187@ucrmath.ucr.edu>
Organization: Actrix Information Exchange
Lines: 26
Comment-To: rhyde@hubbell.ucr.edu

> willing to live with such inefficiencies, why not stick with Windows
> 3.0?

That's easy.  I've been running W3 on my 12Mhz 286 with 1 Mbyte of RAM
for a while now.  I can't run W3 in standard mode because HIMEM.SYS seems
to do horrible things to my mother board or something; it causes Parity
errors and all sorts of stuff.  Even in real mode, W3 locks up at least
once every four hours; it simply runs out of memory or grunt or somethings
and gives up.

I ran Geoworks (the working model) for a couple of days playing with it.
It Never locked up.  It Never complained about not having any memory.
 It Never gave me the dreaded UAE.  It seems that after one version, Geoworks
 already have a more solid, robust product.  Besides, I like to think
 of myself as a s/w engineer.  Geoworks is Object Oriented.  At the coding
 level; the Assembler is an Object Assembler.  This means that when I
 get the SDK (may it happen soon) I can write programs the way I want
 to, eventually using C++.
 
 (I must stop preaching)
 
-- 
andrew.merton@bbs.actrix.gen.nz
"The relevant equation is Knowledge = Power = Energy = Mass.  A good bookshop
is a genteel Black Hole that can read."
                      Terry Pratchett, "Guards, Guards!"