- David Artis
David Artis
Well, if you're a registered owner of 2.2, you should have locked master
copies of it. :)
Anxiously waiting for my upgrade...
--
___________________________________________________________________
|Joe Finete jfi...@cats.ucsc.edu|
|'Happy, Happy...Joy, Joy!'_______________________________________|
I deleted my *registered* copy of 2.2 from my hard disk and I'm not worried.
By the way, 3.0 uses a new format, so if your sending a doc to a WN2.2 users
or a WriteNow for NeXT user remember to save in the old format!
Also, WordPerfect 2.1 for Mac _will_not_ convert the 3.0 format. I was hoping
it would, but alas it doesn't.
Actually that reminds me...there was a paculiar thing that happened...I saved
a doc from 3.0 in 2.2 format and then imported it to WordPerfect 2.1 at work
so that I could then convert it to PC WP for the secretary. The strange thing
is that it showed up in Mac WP2.1 in all bold letters. In WriteNow only the
title was bold. I suppose WP2.1 is probably the culprit.
I'll try to pin down this one soon.
Eric
Microsoft free of course.
Nice job T/Maker
stuff deleted
> Actually that reminds me...there was a paculiar thing that happened...I saved
> a doc from 3.0 in 2.2 format and then imported it to WordPerfect 2.1 at work
> so that I could then convert it to PC WP for the secretary. The strange thing
> is that it showed up in Mac WP2.1 in all bold letters. In WriteNow only the
> title was bold. I suppose WP2.1 is probably the culprit.
>
> I'll try to pin down this one soon.
>
> Eric
>
> Microsoft free of course.
> Nice job T/Maker
>
Eric ,
Maybe I missed something but I can use Save As... and indicate that I want
WN3.0 to save a file in *PC* WordPerfect format directly. If you don't have
a Super drive this might be a problem I guess :-).
As for WN 3.0 being stable: I switched to 32 bit clean mode for the first
time (WN was the last hold out) and life is great ( I deleted my *registered*
copy of 2.2 also :-). Now I am waiting for Apple to get time to make the
MacOS do protected memory...
EVerette
> Maybe I missed something but I can use Save As... and indicate that I want
> WN3.0 to save a file in *PC* WordPerfect format directly. If you don't have
> a Super drive this might be a problem I guess :-).
No, I have a SuperDrive, but, like I said, I don't read manuals! 8-)
Actually T/Maker told me that 3.0 did NOT support Save As WP 5.1, but
could only read WP 5.1 files. I'm very surprised since I went and told my
Dad to get WP 2.1 because of what T/Maker told me (he needs very good WP
5.1 compatibility)!
Oh well, at least he didn't buy WORD 5.0!!!!!!!!!!!!!
--
Eric S. Boltz
Materials Science and Engineering
The Johns Hopkins University
PLEASE RESPOND TO : ebo...@cndenext.mrs.jhu.edu (NeXTMail Welcome)
(ebo...@jhunix.hcf.jhu.edu), (ebo...@jhuvms.hcf.jhu.edu), (ebo...@jhuvms.BITNET)
,__o
_-\_<,
(*)/'(*) Keep on cycling!
I got my 3.0 upgrade last week and this is what I did.
First, I duplicated several files of various length and content. Then I tried
opening them from within WriteNow 3.0 (WN3). I then made a couple of changes
using old standard features, and some new ones. I then saved and quit. I then
tried opening the files by double-clicking and all ran well. After this, I
just made a leap of faith and placed all my WN2.2 files into the new WN3 folder
and I trashed my WN2.2 folder. So far, all has gone well.
BTW, if you have an ImageWriter II printer and a four color ribbon, try making
a file that uses colored text. It CAN be useful. In my case, I updated a
phone list that I keep on the refrigerator by changing all the emergency
numbers to red. This makes them standout quite nicely.
Good luck.
Jim Collymore
P.S. sorry about the lousy formatting! I hate these vi editors!
It sure seems to run just fine to me. It appears to import MS Word
files (various TechNotes from ftp.apple.com) just fine now, whereas I
had a few problems with 2.2 not being able to handle them. (Perhaps it
was just a newer format MS Word file that 2.2 couldn't read.)
WN 3.0 seems to work just fine in Sys7 32-bit mode. I also ran it under
A/UX 2.0.1 in 32-bit mode and it ran just fine. This was the last
32-bit clean upgrade that I was waiting for, so now I can finally make
the switch to 32-bit mode under A/UX.
-- Parag
By yanking INITs one by one, I discovered that Now's WYSIWYGMenus was
the culprit. (I had suspected that immediately, and had disabled
WriteNow's WYSIWYGness, and had added WriteNow to WYSIWYGMenu's
excluded applications list, but they still managed to interfere with
each other.)
After disabling WYSIWYGMenus and successfully running WriteNow, I
found I could then use WYSIWYGMenus, which I prefer, since you can
change the order of fonts, and make dingbats and symbols print in
Chicago.
So, if you use both WriteNow and WYSIWYGMenus, disable WYSIMYGMenus
after adding fonts.
--
::::: Jan Steinman stei...@is.morgan.com Bytesmiths :::::
::::: 2002 Parkside Court West Linn, OR 97068-2767 :::::
::::: 503/657-7703 212/956-8722 :::::
CWP
-=- D. J.
-=- dhag...@moose.uvm.edu
>> publish & subscribe. This is a major dissappointment to me.
>>
>I talked to them exactly about that. They didn't have time to put
>it in this release, but it's due for the next one (3.1). COnsidering
>their usual release rate, that may be a while :-(. Back to WordPerfect...
>
> -=- D. J.
> -=- dhag...@moose.uvm.edu
>
It will probably 'be a while', but that's the price of FAST code.
Try comparing WP2.1's actual fonts in menu to WN3.0's!
And WN3.0's new spelling checker is great.
I can live without P&S for a while if it means not having to wait!
(for my app that it!)
I do like WordPerfect 2.1 though...I'll buy it for my 'serious'
word processor as soon as they add a GOOD equation editor. Till
then it's WriteNow for most things and FrameMaker on my NeXT at
work for the 'serious' stuff (now there's a GOOD equation editor!).
Eric
Scott
--
Scott Ellsworth
sell...@jarthur.claremont.edu
OR consultant at large. For sale by owner. Reasonable Rates. Apply within