Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!tut.cis.ohio-state.edu!unmvax!pprg.unm.edu!topgun!mustang!nntp-server.caltech.edu!rknop
From: rknop@nntp-server.caltech.edu (Robert Andrew Knop)
Newsgroups: comp.sys.cbm
Subject: Re: geoWizard
Message-ID: <1991Jan13.064030.3529@nntp-server.caltech.edu>
Date: 13 Jan 91 06:40:30 GMT
Organization: California Institute of Technology, Pasadena
Lines: 27

cs4344af@evax.arl.utexas.edu (Fuzzy Fox) writes:
>Wouldn't it be nice to know the incompatibilities BEFORE you buy?
>Otherwise it'd be a waste of money for some people.

The incompatibilities listed in the doc files that come with geoWizard are:

1) Don't use geoWizard with the SuperDebugger.  I (Rob) take this to mean,
don't activated geoWizard from within the SuperDebugger, and vice versa.  I
have geoWizard installed while I ran the SuperDebugger, and geoWizard still
worked afterward.

2) Don't use SuperBox 128 with geoWizard

3) If starting geoWizard from within geoWrite, don't modify the Text
Scrapt.

There are other incompatibilities listed in the docs, but those have been
fixed.  Jim now includes a second program with geoWizard that moves
geoWizard's handle into the GEOS kernal to a different (user specifiable)
place in memory, which makes geoWizard compatible with most things.  There
may also be other programs which show up in the future which, for whatever
reason, are incompatible with geoWizard.  And you can always confuse it by
doing things like deleting from disk the application from which you activated
geoWizard.  (The Text Scrap business is an example along these lines.)

-Rob Knop
rknop@tybalt.caltech.edu