🚀 go-pugleaf

In article <1991Apr19.170835.3504@waikato.ac.nz> phil@waikato.ac.nz writes:

>As far as I can determine, WriteNow 2.2 does not work on a Classic.  Does
>anyone know what, if anything, T/Maker plan to do about it, or if there is
>already a free upgrade to a bug fix version?  It would seem to be a sensible
>thing to provide, since an entry level WP isn't much good if it won't run on an
>entry-level computer...

I tried WriteNow 2.2 on a Classic in our lab.  GateKeeper immediately
began reporting that it was vetoing attempts by WriteNow to change some
of the resource attributes of one of the system's DRVR resources.  I
checked the application for virus infection using Disinfectant 2.4; it's
clean.

I gave WriteNow permission to do "res/system" operations in Gatekeeper's
Settings dialog.  This seems to have resolved the problem... I entered a
short Jabberwocky quotation, changed the fonts and point-sizes of the
text, and printed it (via our CAP spooler).  It worked just fine.

I'm not sure what Gatekeeper is doing to the DRVR resource in the
System... perhaps it's setting the "lock" bit to avoid memory clobbering
under obscure conditions?  Nor do I know why this affects only the
Classic (the same copy of WriteNow runs without complaint on my IIci).

To answer your question directly... I can't speak for T/Maker, but I do
have reason to believe that they're working on a new release which will
fix certain problems in version 2.2 (for one:  WriteNow 2.2 is not
32-bit clean, and will crash under System 7's 32-bit addressing mode).



-- 
Dave Platt                                                VOICE: (415) 813-8917
                    UUCP: ...apple!ntg!dplatt
 USNAIL: New Technologies Group Inc. 2468 Embarcardero Way, Palo Alto CA 94303