It is not as simple as copying some files. The user can choose where to install the screen saver, so most files have a corresponding registry entry. Furthermore, some files have a 64bit and a 32 bit version for compatibility. I don’t recommend messing with the windows registry yourself, accidently changing an important component, could destroy your computer. However, if your clients want complete control of the installation, possibly they are tech savvy enough to safely delve into the registry.
Complete instructions for raw installation below.
Disclaimer: The instructions involve creating/modifying values of the windows registry. If you don’t know what you are doing, messing with the registry can permanently damage your computer. Late for Dinner Studios, LLC is not liable for any damage caused by following, or attempting to follow these directions. As a matter of fact, Late for Dinner Studios, LLC strongly recommends that you do not follow these directions and instead use the exported .msi file to install your screen saver.
I reserve the right to change these directions at any time, so this info is valid only for versions 1.0-1.4 of the plugin
The screen saver uses a combination of files and windows registry entries, if any part is missing or spelled wrong then screen saver will fail to work.
Everything in brackets will have to be replaced with a value specific to your screen saver
[ProductName] is the name of the screensaver exactly as it appears in the .sCr file.
Example. For HKLM\Software\Late For Dinner Studios, LLC\Video Screensaver Middleware\[ProductName] with a .scr called funScreenSaver.sCr, replace [ProductName] with funScreenSaver so the end value would be HKLM\Software\Late For Dinner Studios, LLC\Video Screensaver Middleware\funScreenSaver
[WOW6432Node] is a value that depends on whether or not the computer is 64 bit or 32 bit, if the computer is 64 bit replace [WOW6432Node] with WOW6432Node
If it is 32 bit, replace [WOW6432Node] with WOW6432Node with nothing
Example 1. On a 64 bit computer, HKLM\Software\[WOW6432Node]\Late For Dinner Studios, LLC\Video Screensaver should be HKLM\Software\WOW6432Node\Late For Dinner Studios, LLC\Video Screensaver
Example 2. On a 32 bit computer HKLM\Software\[WOW6432Node]\Late For Dinner Studios, LLC\Video Screensaver should be, HKLM\Software\Late For Dinner Studios, LLC\Video Screensaver
[#anyName] means replace the value in brackets with the full file path of anyName
Example1. Say the file videoFile is located at K:\CrazyFolder\Structure\videoFile
Then [#videoFile] would be replaced with K:\CrazyFolder\Structure\videoFile
Example2. Say the file audioFile is located at C:\Program Files\Monkeys\audioFile
Then [#audioFile] should be replaced with C:\Program Files\Monkeys\audioFile
[Manufacturer] means replace the value in brackets with the manufacturer name, this name is set in the export settings, when exporting the screen saver. The default value is You
Registry Entries:
Key: HKLM\Software\[WOW6432Node]\Late For Dinner Studios, LLC\Video Screensaver Middleware\[ProductName]
Name: videoFilePath
Value: [#videoFile]
Type: String
Key: HKLM\Software\[WOW6432Node]\Late For Dinner Studios, LLC\Video Screensaver Middleware\[ProductName]
Name: audioFilePath
Value: [#audioFile]
Type: String
Key: HKLM\Software\[WOW6432Node]\Late For Dinner Studios, LLC\Video Screensaver Middleware\[ProductName]
Name: settingsFilePath
Value: [#settingsFile]
Type: String
Key: HKLM\Software\[WOW6432Node]\Late For Dinner Studios, LLC\Video Screensaver Middleware\[ProductName]
Name: aboutFilePath
Value: [#aboutFile]
Type: String
Files:
videoFile
videoFile could be located any folder that has given read permissions to Everyone on the user’s computer
the typical location is C:\Program Files (x86)\[Manufacturer]\[ProductName]\videoFile
audioFile
videoFile could be located any folder that has read permissions to Everyone on the user’s computer
the typical location is C:\Program Files (x86)\[Manufacturer]\[ProductName]\audioFile
aboutFilePath
videoFile could be located any folder that has read permissions to Everyone on the user’s computer
the typical location is C:\Program Files (x86)\[Manufacturer]\[ProductName]\licenses.html
settingsFile
unlike the other files, this file must be in a directory that has read and write permissions to Everyone, not just read
the typical location is C:\ProgramData\Late for Dinner Studios, LLC\Video Screensaver Middleware\[ProductName]\settings.json
[ProductName].sCr
I recommend using .sCr instead of .scr, because there are some laptops that for reasons unknown, block all screensavers with the .scr extension. The work around is to use .sCr instead
Please note that Screen Saver Exporter actually creates two .sCr, a 32 bit version and a 64 bit version.
It will only install the 64 bit .sCr on a 64 bit computer and only the 32 bit .sCr on a 32 bit computer. If you want to get both .sCr files on one computer, you need to use a msi extractor tool, such as http://lessmsi.activescott.com/ or http://superuser.com/questions/307678/how-to-extract-files-from-msi-package to extract the file. Also note that you should never change the name of the file, if you rename, the screen saver will no longer play.
Where this file must be depends if the computer is 64bit or 32
This file must be located in C:\Windows\SysWOW64 on 64 bit computers, the 64 bit .sCr
Or C:\Windows\System32 on 32 bit computers, the .sCr
Technical note: Anyone windows savvy will tell you C:\Windows\SysWOW64 is a place to put 32-bit binaries, not 64 bit binaries, like I did above. Just know, that I know what I’m doing, put the 64 bit .sCr files in C:\Windows\SysWOW64, they will not work in C:\Windows\System32.
Likewise there is also SDL2.dll that also comes in 32bit and 64 bit versions.
Each dll file must be in the same folder as the .sCr file.
So C:\Windows\ SysWOW64\SDL2.dll on 64 bit windows
And C:\ Windows\ System32\SDL2.dll on 32 bit windows
The other version will have to be extracted.
Instead of hunting around your computer for the files, I would use msi file extractor such as http://lessmsi.activescott.com/ or http://superuser.com/questions/307678/how-to-extract-files-from-msi-package to extract the files.