[COLOR="Red"]DISCLAIMER: I am not a lawyer, so do not quote me on below arguments in the court. [/COLOR]
But I will try my best to give information as accurate as possible.
Eugenijus-Jonas said: Hello, I am living in Lithuania. I am a catholic.
Here exist some questions about e-sword. This program requires some dll from Microsoft and these dll's requires licence. In other words, if I want to play with Ubuntu CE I must purchase Microsoft Windows.
Thank you for your concern. But I don't think we need to have windows license to run e-Sword as we do not need to use all dll's that Microsoft has. We just need to use some of them, 4 to be exact. Why we must purchase windows license? Which dll force us to use windows license? As far as I know, below are the dlls that require windows license:
dcom98 MS DCOM (ole32, oleaut32); requires Win98 license! dotnet11 MS .NET 1.1 (requires Windows license) dotnet20 MS .NET 2.0 (requires Windows license) wininet MS wininet.dll (requires Windows license) wme9 MS Windows Media Encoder 9 (requires Windows license) wmp9 MS Windows Media Player 9 (requires Windows license) wmp10 MS Windows Media Player 10 (requires Windows license)
But as of today, we download none of them to run e-Sword.
Eugenijus-Jonas said:
It is good, that your distribution has such the capability, but the situation must be clean. Just be right, just be the Christians.
With love, Eugenijus-Jonas.
Sure, I also want to be clean. Below is my analysis:
- First of all, ubuntu ce is not shipped with any Microsoft dll, nor e-Sword. It is even illegal to host e-Sword in the internet, hence, we don't even host any of e-Sword program, nor its components. So, I am sure ubuntu ce is clean.
- Not All Microsoft dlls require license, many of those dlls are "redistributable", meaning you could shipped it with your software. e-Sword itself comes with those "redistributable" dll for example the riched20 and mfc42u
- There are many dlls you could obtain from Microsoft freely and legally, for example all those dll included in the Microsoft viewer.
- As far as e-Sword installer concern, it is actually intended to help you with technical problem, not law. Many people purchased computer with windows license, but want to install ubuntu/linux for some reason and do not want to keep rebooting just to open e-Sword. So, for those people, license is not really a problem I guess.
a. mfc42.dll b. msls31.dll c. mfc42u.dll d. riched20.dll
- As far as latest e-Sword concern, we only need:
So, now come to my analysis about the legal aspect of these 4 dlls, but again, please don't quote me in court room as I am not a lawyer:
http://www.winehq.org/pipermail/wine-bugs/2003-January/003807.html
- We use riched20.dll which is available in the e-Sword itself, as such, we do not even download it.
- Using the installer, you will download those dll legally i.e microsoft provide free download for those dll.
- mfc42u is shipped with e-Sword as well, but somehow it did not work in wine. From below mail, we understand that we could legaly repair it:
The Wine project cannot redistribute MFC42.dll. However, application developpers who use that library (and thus have a Microsoft Visual Studio license) are allowed by that license to redistribute it _with_ their application, and should do so if they want it to work on all Windows platforms (e.g. Win95). Anyway, if an application developper forgot to ship this library with his application, a simple 'google mfc42.dll' should allow you to repair his mistake.
- msls31.dll is extracted from InstMsiA.exe. While installing it, it would prompt you with below license:
http://www.microsoft.com/DownLoads/details.aspx?FamilyID=cebbacd8-c094-4255-b702-de3bb768148f&displaylang=en
You may install and use the SOFTWARE PRODUCT on a single computer solely for the purpose of developing applications for use with Microsoft(R) Windows(R) or Windows NT(R) ("Application"). You may not use the SOFTWARE PRODUCT to create files which are not compatible with the Microsoft Windows Installer file format.
Again, it never mention about windows license at all. The only restriction I could find is: [COLOR="Red"] You may not use the SOFTWARE PRODUCT to create files which are not compatible with the Microsoft Windows Installer file format.[/COLOR]
I think it refer to developer, which create files/software for competitors. But e-Sword user DO NOT CREATE FILE with InstMsiA.exe or msls31.dll. But even if it creates temporary file ( I doubt it, and it also out of context of developing software actually), it would still compatible with Microsoft Windows Installer file format.
I hope my explanation above clear your conscience. And please let me know if there are some mistakes in my explanation above. And again:
Do not quote me on court room, I just want to help people to run e-Sword on linux easily.
DK