Hello Bogi,

I have 192 Meg of RAM which is greater than even 128 Meg of RAM you
mentioned. And I have Libranet 3.0 running on my hard drive.

So I think it is very unlikely that my system is crashing due to having
too little RAM.

However, I will check out your link anyway.

It was my brother Mel who helped me upgrade my RAM to 192 Meg.

Thanks and Cheers,

Michael

_____________________________________________
_____________________________________________


bogi wrote:

>Hi Michael.
>
>Check this link out.
>http://www.openoffice.org/issues/show_bug.cgi?id=968
>
>Now these guys are talking 60-120 megs for a 10 meg documents, you have 96 
>megs on your system, i am sure you would have exhausted them running kde or 
>gnome plus a few services, so when you run oOo it just crashes on very low 
>memory. Now i have seen this behaviour on a knoppix run on a 128 Meg machine, 
>oOo would just crash at startup. try to stop some services, run blackbox 
>instead of kde or gnome and have a go at it, alternatively you may want to 
>add some ram to your system, 96 megs is really too small even for a kde or a 
>gnome.
>
>Cheers
>Szemir
>
>On July 12, 2005 13:54, Michael Walters wrote:
>  
>
>>Hello Mel,
>>
>>So it seems that my problem involves the failure of Open Office to
>>remove the lockfile when it shuts down, leaving a stale lockfile.
>>
>>I have a little further information on what happened to me today.
>>
>>I tried to open a file using open office gui and failed.
>>
>>I then tried several times to open an open office file using firefox. It
>>then prompted me to click on yes to open the file in open office and
>>then promptly hung.
>>
>>This happened several times, so I tried opening the file in Konqueror.
>>The first time it hung, but the second time I successfully opened the
>>file and printed it out.
>>
>>Does this give you a clue as to why my system frequently leaves stale
>>lockfiles?
>>
>>Blessings,
>>
>>Michael
>>
>>Mel Walters wrote:
>>    
>>
>>>On Monday 11 July 2005 12:28 pm, Michael Walters wrote:
>>>      
>>>
>>>>Although I at first thought that perhaps the lock file was created when
>>>>I perhaps right clicked when I should have left clicked, when I was
>>>>careful to only click the right way, I still got lock files.
>>>>
>>>>About every other time I create a new open office spread sheet I get a
>>>>lock file.
>>>>
>>>>I just remove the lockfile and open office works again, but does anyone
>>>>know of possible reasons lockfiles might be created when I work with
>>>>open office documents? If someone could tell me what to look for in
>>>>causes of lockfiles, I might be able to fix the problem by prevention
>>>>rather than by corrections.
>>>>
>>>>Regards,
>>>>
>>>>Michael
>>>>
>>>>Michael Walters wrote:
>>>>        
>>>>
>>>>>Hello All,
>>>>>
>>>>>When I open new documents in open office I sometimes get another
>>>>>lockfile. But removing the lockfile seems to free up open office again.
>>>>>
>>>>>It is a bit anoying to remove lockfiles, but at least I can edit new
>>>>>open office documents.
>>>>>          
>>>>>
>>>[SNIP]
>>>
>>>      
>>>
>>>>>>The reason that is partial success is we do not know what created the
>>>>>>lockfile in the first place.
>>>>>>            
>>>>>>
>>>Did I answer this already? I do not see my answer?
>>>Again:
>>>
>>>The royal WE here? I can see by your letter you do not understand what a
>>>lock file is or how it is suppose to work.
>>>Programs create lock files to keep track of things. That is normal. when a
>>>program closes down, it would normally delete the lock file (and all is
>>>well).
>>>If a program hangs up (freezes) or crashes, then the lock file (stale one)
>>>will still be there and we do not want it. This can prevent you from
>>>starting the program, as the OS thinks you are already running it.
>>>
>>>What has to be determined is, what is failing here?
>>>1/ Open Office could be going bye bye (hence a stale lock file to trip you
>>>up) or,
>>>2/ You could be trying to run ooffice twice, and the OS is complaining
>>>( this could easily go on by focus not being on ooffice but other things
>>>on your desktop covering it up)
>>>
>>>I am not saying I know what happened to you. But you may be a little lost
>>>as to the details too, since your first assumption you make could be
>>>false or true?
>>>
>>>You can figure out what is going on. Only then do you have a hope of
>>>solving your problem here.
>>>
>>>Hope this helps you Michael
>>>
>>>Mel Walters
>>>
>>>
>>>
>>>---------------------------------------------
>>>

_______________________________________________
clug-talk mailing list
[email protected]
http://clug.ca/mailman/listinfo/clug-talk_clug.ca
Mailing List Guidelines (http://clug.ca/ml_guidelines.php)
**Please remove these lines when replying

Reply via email to