org.openoffice.Office.Common/Misc/UseLocking = false
<item oor:path="/org.openoffice.Office.Common/Misc"><prop oor:name="FirstRun" oor:op="fuse"><value>false</value></prop></item>
<item oor:path="/org.openoffice.Office.Common/Misc"><prop oor:name="UseLocking" oor:op="fuse"><value>false</value></prop></item>
Ok, I will give you one of the reasons. I don't want any extra Writes happening on my SSD. Hope we will not get into the "Why" of that.
Villeroy wrote:If you can edit large XML files:
Make a backup copy of %APPDATA%\OpenOffice\4\user\registrymodifications.xcu
Find the following similar node:
- Code: Select all Expand viewCollapse view
<item oor:path="/org.openoffice.Office.Common/Misc"><prop oor:name="FirstRun" oor:op="fuse"><value>false</value></prop></item>
and add this node nearby:
- Code: Select all Expand viewCollapse view
<item oor:path="/org.openoffice.Office.Common/Misc"><prop oor:name="UseLocking" oor:op="fuse"><value>false</value></prop></item>
amsharma wrote:Is it possible to disable lock file creation.
amsharma wrote:Ok, I will give you one of the reasons. I don't want any extra Writes happening on my SSD. Hope we will not get into the "Why" of that.
My thought was that the lock file generation is not controlled by registrymodifications,xcu as there is no apparently relevant line in it.
Lupp wrote:@RoryOF: The registry node Villeroy described was most likely taken from his LibO registrymodifications.xcu. LibO definitely introduced the Boolean property under discussion. AOO didn't, and therefore may remove an inserted xml section containing it when tidying up.
On my 4GB PC (with an SSD) hiberfil.sys is 3.1 GB and pagefile.sys is 4.2 GB.
Booting the PC once therefore writes 7.3 GB which is equivalent to writing 73,000,000 lock files.
Do we have any OO Developers or Engineering team etc on this forum to confirm what @Villeroy wrote.
~.lock
amsharma wrote:Ok, I will give you one of the reasons. I don't want any extra Writes happening on my SSD. Hope we will not get into the "Why" of that.
amsharma wrote:So we aren't sure of the functionality in OO. Do we have any OO Developers or Engineering team etc on this forum to confirm what @Villeroy wrote.
The number of writes to the SSD would increase because LO requires more disk space than AOO and is updated more frequently.
Bill wrote:While there are reasons to use LO, switching to LO to save a few bytes by disabling lock file creation isn't one of them. The number of writes to the SSD would increase because LO requires more disk space than AOO and is updated more frequently.
John H,Bilbo-Baggins/John,Bilbo-Baggins,18.06.2019 12:44,file:///C:/Users/John/AppData/Roaming/OpenOffice/4;
AOOisdead wrote:Just a friendly reminder that AOO is a zombie project and it's unlikely to have any major changes pushed to AOO (If you look at their dev mailing list or their bugzilla, they aren't able to push major changes because of bitrot and lack of volunteers). I would pursue your uselock issue with LibreOffice developers.
That's not bad. As time goes by, however, you may also need to tell them they might better shift to LibreOffice one day to avoid a too big gap to step over concerning changes in the look-an-feel. It's mainly the user interface that may one day make it more difficult to move. That doesn't mean LibO is generally better insofar.amsharma wrote:I tell people at all forums to use OO.
AOOisdead wrote:There have been attempts at giving AOO a graceful retirement, but they are rebuffed by ego's. Currently there are only 4 or 5 people that occasionally file commits to the project, and mostly to language compatability improvements. There is only one existing active contributor that has any programming knowledge of the AOO code base. This is easy to see on the Dev mailing list archive if you look at the past few years. It's a fascinating case study of volunteer organization decline. However it's outrageous that the Apache Foundation would let a project that millions rely on to seem operational when there are unpatched security issues and ever increasing compatability problems.
Edit: actually there have also been attempts to pare down AOO to allow for rejuvenation of the code (they wanted it to be a skeleton other projects could build on and go different directions in by leveraging the freedom of the Apache license), but even those were rebuffed by some individuals that want the project to stay as is. The problem is, anyone new looks at the code base, sees how old it is (plus all the German language commits that LO took 3 years to fully convert to English), see's that LO has already refactored, and then moves on to a newer project, or to LO.
That's not bad. As time goes by, however, you may also need to tell them they might better shift to LibreOffice one day to avoid a too big gap to step over concerning changes in the look-an-feel. It's mainly the user interface that may one day make it more difficult to move. That doesn't mean LibO is generally better insofar.
Users browsing this forum: No registered users and 12 guests