From: lachlan@dmp.csiro.au (Lachlan Cranswick)
Subject: Re: WFW Ver 2.0 2.0a 2.0b 2.0
Organization: CSIRO Division of Mineral Products, Melbourne, AUSTRALIA
Date: Wed, 6 Jan 1993 06:07:38 GMT

thomas@datamark.co.nz (Thomas Beagle) writes:

>In article <6350.1099.uupcb@satalink.com> vince.maiocco@satalink.com (Vince Maiocco) writes:
>>an entirely new program.  MS, or maybe someone else, one 
>>day came up with the idea to tack alpha characters onto 
>>version numbers when the only "enhancements" were, in 

>I quite like this system. It allows me to distinguish between bug
>fixes, minor enhahncements and major rewrites.

>>Apparently, we're just supposed to keep shelling out the 
>>money, to pay 2 and 3 times for what we should have 

>Well, Microsoft sent me the bug fixes for free. They will undoubtedly
>charge for new versions with improved functionality. This seems fair
>to me - TANSTAAFL.

>-- 
>    Thomas Beagle | thomas@datamark.co.nz           Work: 64 4 233 8186
>Datamark Intl Ltd | thomas@cavebbs.welly.gen.nz     Home: 64 4 499 3832
> Technical Writer | Yes, I do have long ears, a black nose, and a tail.

Mmmmmmm  -  Your address implies you live on the 
same planet as the rest of us - what did you have to do
to get this free upgrade sent to you? - nothing unsanitary
I hope?

We are still waiting for a copy of Windows 2.0c to
fix the not enough memory to save problem.
(It was promised almost 1 month ago)
Has anyone in Australia recieved a reply after
sending in the registration forms to MS - they
promise extra info etc.  The only way we can get semi decent
service from MS here is to be a member of their
MS Communique Club - which costs money)

Can anyone explain why this "not enough
memory to ave error" error is so erratic?

We have around 50 to 70 copies of Winword running
on our site and yet this error seems to strike
like random lightning.  It is also not consistent.

On most of the Winword machines, it hasn't occured (2.0,2.0a)

On some machines, its has struck either 1 or 2 times.

On 3 other PCs, it seems to cascade - the error progressively
occurs more often and then starts slowing down the machine
for a particular document (ususally the most important one)
till you can only press a few keys in the document you
are editing and the error comes up.  It also seems to embedd
the error is some large documents such that the error can now
be reproduced in any machine trying to load/edit and save the file.
The document ussually has to be retyped from scratch.
Its reeally wierd.
Staff here are roughly doing the same types of documents
and these are pretty vanilla installations of windows and DOS..


As the costs of changing to a new word processor package/
retraining etc, we are effectively stuck with Winword.


One bright spark on the horizon is that a high level
site manager has just encountered this bug in a big way.

As the only theraputic(sp?) reply was to tell him he
was using a crap program (He failed to get through to
MS support - which made him very happy),  the solution
was to advise him to load his old copy of MS Word 5.0
for DOS and keep editing his text and table document
in safety.  

Why is this a bright spark?  Because when peasants (i.e.
non high level managers) get these problems - we just
have to lump it.  But when one of the Gods gets stung,
heads start getting kicked - possibly 
a decision to go to a new
Windows based Word Processor.

A few other queries:-

Does 2.0c fix this bug?  What about 
if this bug seems to have
corrupted the document?

What is a good possible replacement program?
I like the sounds of Ami Pro as I have heard
good things about it and Lotus have a good 
reputation (well - with me) for userr support
and getting unsolicited bug fixes out quickly.


Lachlan.
-- 
  Lachlan Cranswick  -  CSIRO             _--_|\  lachlan@dmp.CSIRO.AU
  Division of Mineral Products           /      \ tel +61 3 647 0367
  PO Box 124, Port Melbourne 3207        \_.--._/ fax +61 3 646 3223
  AUSTRALIA                                    v