Re: Appleworks 4.0 arrives - compatibility with 3.0

[dempson@swell.actrix.gen.nz (David Empson)]

In article <2bono3$9oo@hub.ucsb.edu> uerics@mcl.ucsb.edu (Eric D. Shepherd) writes:
> What problems are you referring to?  The only one I'm aware of is that
> it doesn't like having interrupts in the background (which does
> indicate that whoever wrote the interrupt-handling code for AW4 wasn't
> particularly clever about it).

Understatement of the century, there.  I haven't received my copy of
AppleWorks 4.0 yet (and it now sounds like it will be delayed a bit
longer), but I can't make head or tail out of these claims that it
doesn't like interrupts.

The only way this could be causing problems on the IIgs is if
AppleWorks has patched out the master interrupt vector, which is
severely frowned upon.

Is it just TIMER interrupts that it doesn't like, or interrupts in
general?  If it didn't like any interrupts, then you couldn't even get
into the IIgs Control Panel (pressing Ctrl-Apple-Esc generates an
interrupt).

If it is just the timer interrupts, then it sounds like they have a
badly written timer interrupt handler.

What are the symptoms of the problem?  Does AppleWorks crash?  Does its
screen blank at the wrong time?
-- 
David Empson                                                               
dempson@swell.actrix.gen.nz                                                
Snail mail: P.O. Box 27-103, Wellington, New Zealand