But I hesitate to upload the scripts because of some questions of legality and I don't wanna run into problems with MS.
1. The scripts do not contain any MS files.
2. The scripts copy an existing viewer installation on host as well as the found language settings to the WB Build.
3. The scripts read and write the most relevant registry settings to the build.
As far as I can see in Jaclaz' thread this way should be the only way to avoid having problems with MS.
But what's about the MS EULA? (I'm totally unexperienced to interpret and to understand these EULAs)
PowerPointViewer shouldn't be any problem as the user has to accept the licence at the very first run and so the licence file is included in the script using the 'Ask_Licence' command.
I have doubts about the EULA for Word/Excelviewer that has to be accepted during installation on host and the following EULA snippet:
2. USE RIGHTS. If you comply with this agreement, for each licence you acquire you have the following rights: Installation and Use. a. General. You may install and use an unlimited number of copies of the software to view and screen print documents created with Microsoft Office software. You may not use the software for any other purpose. b. Distribution. You may copy and distribute the software, provided that: ... ... 3. BACKUP COPY. You may make one backup copy of the software. You may use it only to reinstall the software.
Is WinBuilder "any other purpose", is it in end user's responsibility to use the scripts or would it be better to forget an upload?
Thank you for your answers