--- Begin Message ---



 Hi Roger...

I´ve had same problems..... but I had downloaded the 90-days evalution of StarOffice 8, Product Update Five, and used it... And suddenly I´ve got a CPU running madly at least 90 % usage... sometimes higher....  the tree finger salute.. (CTRL+ALT+Delete) was the only solution... killing the process soffice.bin was my way out of this problem. In my world I thought this was a problem related to SO 8.

 I uninstalled SO8 and then I found OOo 2.2 sr3 on the net.. downloaded it and up till today, there is no such usage of the CPU....

I have 512 Mb RAM, 2.0 Ghz CPU, running WIN XP Home SR2.

I also have MS Office 2002 on my machine... never such a problem...... runs like a clock.... it´s true... :-)



as one other guy suggested....

.......................
Do you have sufficient memory on the machine?  I found that going from 512M RAM to 1G made a huge difference in getting rid of swapping problems.
.......................



I don´t think it´s the problem....  :-\ silly that 512 isn´t enough... it´s just a officesuite, and you don´t run the whole package... just Writer....



let´s see what solutions they found on this problem....


Best Regards

// Per


Roger Pye skrev:
I have used Open Office on my home system for a number of years and about 2 months ago downloaded V 2.1 to upgrade V 2.0. I realised about 3 weeks after the download it was not an upgrade as such but a whole new program. As soon as I began using OO Writer (effectively the same day as the download) it would run OK for about 30 mins and then my CPU would go to 100% usage and the whole system would lock up (forcing a crash). Usually I was running a number of other software programs as well as Windows XP Home Edition at the same time - these included Mozilla Firefox, Thunderbird, Paint Shop Pro. I had never had any trouble with Writer before.

I tried a number of solutions none of which worked. They included uninstalling 2.1 and reinstalling it. It was at that point I discovered that most of 2.0 was still in a folder in Program Files on C drive; I deleted it. I tracked the conflict to Firefox (and on occasion I think Thunderbird as well) by running Writer with individual programs and noting the result.

A typical sequence would be as follows:
Firefox would be running;
I would open Writer;
Within 30 minutes regardless of what I was doing (whether working in Writer or browsing), Writer would 'blow out' to near 100% CPU usage and stay there;
(If I was working with more than one document in Writer it wouldn't take 30 minutes!).
The system would lock up. If I was lucky I would be able to close Writer, the CPU usage would drop to 4%. For 90% of the time I wasn't lucky.

The first time it happened the system crashed so severely it took me three days and professional help to get the system working properly again.

By this morning I had had enough. I uninstalled Open Office 2.1, deleted the folder in Program Files, and reinstalled OO 2.0. I have had no trouble since nor do I expect any.

In terms of computer experience I am not a newbie. I have about 20 years usage under my belt - I was a system manager in the RAAF with the first NCR Towers in the late 1980s and have kept reasonably up-to-date ever since. However I don't know much about the back end of modern windows and other programs. Possibly the problem is with my system but I don't think so. System details are:

Intel (R) Celeron (R) CPU 2.00 GHz, 2.02 GHz, 768 Mb RAM
OS Windows XP Home Edition Version 2002 SP2

Currently I am also network administrator of a non-government not-for-profit organisation and we are considering installing Open Office on our 10 systems in place of (currently) MS Office. However we can't take this step if there is a chance of conflict.

Cheers

Roger Pye
Canberra Australia






---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]





--- End Message ---
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to