FullWrite Prof. problems under A/UX, slow, bombs, and lost margins

[John R. Galloway Jr.]

I recently consolidated all my work onto A/UX having previously been doing
part under MacOS.  When I opened a 40 page FullWrite document under A/UX I
was VERY annoyed to find that the page setup information (at least the
margin settings) had been lost.  I tried a simple test (make a doc under
MacOS with MacOS resident FWP, boot A/UX, move the file, run the A/UX resident
copy of FWP and open the unix file) and all was ok.  Any idea of what may have
happened?

And also let me say that while I generally like FWP, large docs seem to be too
much for it.  I have driven it crazy (uninterruptable loops of manic screen
updates culminating in deletion of a chapter) under MacOS, but Under A/UX
it bombs doing trivial things on a large complex document (40 pages, 8 chapters,
pictures, sidebars, footnotes, contents, etc.).  It also seems much slower
than under MacOS.  While I notice some slowness in most programs under A/UX it
isn't enough to be bothersome, but FWP seems 2 or 3 times as slow, at least on
large docs.  I have had to move my FWP work back to MacOS (what a hassle).

I REALLY like A/UX but FWP and A/UX don't seem quite read for each other (and
given FWP's troubles even under MacOS, its hard to guess where the problems
are).

Anyone out there doing large complex document processing under A/UX?  If so
what are you using?
	-jrg
-- 
internet   jrg at galloway.sj.ca.us  John R. Galloway, Jr.
applelink  d3413                  CEO..receptionist         795 Beaver Creek Way
human     (408) 259-2490          Galloway Research         San Jose, CA  95133
-- 
internet   jrg at galloway.sj.ca.us  John R. Galloway, Jr.
applelink  d3413                  CEO..receptionist         795 Beaver Creek Way
human     (408) 259-2490          Galloway Research         San Jose, CA  95133