Replies

If the “Install” in the title means to install a clean copy of Windows 11 on a computer that has been running activated Windows 10, what is the issue? Last night I used the MS Media Creation tool to create a USB installation drive. I used an old Dell E6440 i7 laptop as my test-bed to see if I even wanted Win 11. I booted on the USB drive and performed a normal offline installation of Pro without any warnings. I chose a clean install and deleted the existing partitions. After the install for a local account completed, I connected to my wifi and downloaded some Intel driver files from Microsoft.

Windows 11 is activated and seems to be working as expected with NO tinkering or disclaimer acceptance required. The Dell Secure Boot and TPM 1.2 BIOS options were enabled prior to installation.

True to MS form, the UI is a sad case of moving stuff around and declaring is better. The only positive thing I can say about the new “Menu” is that it is even worse than Win 8/10’s and Classic Shell still works.  It is also easy to relocate the Apple wannabe taskbar icons back to the left side.

I guess that’s a valid opinion if LO never expects to be taken seriously as a business or enterprise tool. In today’s world, people must take security seriously. Any modern software package that allows a user to unknowingly strip security protection from a file is an incredible risk to the organization.

If I were a business operating in that type of situation, I would never allow LO to be used in any of my business processes. For what it’s worth I actually like LO 7x as a very cost-effective substitute for many Office users.

I agree if I were saving an unprotected spreadsheet in either Excel or Calc. However as a user, I should be able to assume that if I have assigned a spreadsheet file the security-related attribute of “password protected”, then my action of later editing and saving the changed original with a different name would mean that the new file inherits the original file’s security attribute and will remain encrypted until I make an overt act to remove that attribute. My Excel operates in this manner.

My question is why can LO Calc, apparently by default, remove this attribute and allow an otherwise previously encrypted file to be saved as an un-encrypted file without my overtly removing that attribute?

The other side of my question is that in the overall hierarchy of file attributes, why does the Excel spreadsheet file structure allow this security attribute to be changed without similar user action in another vendor’s spreadsheet program? For many users, the integrity of the file security setting is kind of a biggie.