☰ Table of Contents
- Complete Guide
- Table of Contents
- Welcome to iScreensaver
- Downloading and Installing
- Designing and Preparing
- Managing Projects
- Importing Media
- Editing a Screensaver
- Branding Control Panels
- Customizing Installers
- Building Installers
- Distributing Installers
- QuickStart and Sample Projects
- Installing a Screensaver
To get a cross-platform-created screensaver on to an end-user's system requires hundreds of files, libraries to be copied, and many OS-level settings to be changed. It's not something the average user can do by hand. For this reason, an "Installer" is used. An Installer is software that automates this process. Fortunately, iScreensaver Designer creates Installers for you. More importantly, iScreensaver Designer is the only tool which does this cross-platform work for you. You can edit your screensaver on Mac and create a Screensaver Installer for Windows. And vice-versa. Cool. Here we describe how to do this.
For help installing a screensaver, see Installing a Screensaver.
For help with distributing screensavers, see Distributing Screensaver Installers.
The Share tab is where you actually build the screensaver installers. First, of course, you might want to name the files, provide customized icons, or take advantage of the option of adding a custom Wallpaper desktop background for your users' machines. Also if not yet completed, links for easy registration of your copy of iScreensaver are available.
Using the Share tab
On the Builds tab you can set general information (such as your Author's name), select which platform(s) to build, and start a build for all selected platforms.
Using the Builds subtab
The screensaver software will only function in Demo Mode until a valid registration code has been entered. The current registration status and registration name are shown.
Setting an Author Name
Most operating systems will mention an author or publisher of the application when getting information on the file properties, and this text field can be customized for an author's clients, if any. This is an editable field with the Ultimate License.
Please note that this is not the same as a Software Publisher Certificate, as seen with Windows' User Access Control warnings upon software install. Purchasing a software certificate requires involvement with Microsoft-authorized third party software security companies.
See more information about this topic at Microsoft:
Exporting to all platforms
It is easy to quickly build installers for all checkboxed platforms using the 'Build All' button on the master Builds tab.
Exporting to single platforms
Each platform can be individually built from their individual platform tabs.
Using the Mac subtab
Using the Win subtab
Customizing the Install
- Naming Windows files : names are limited to 40 characters. The screensaver will automatically have ".SCR" appended, and the installer will have ".EXE" appended. You may or may not see these suffixes, depending on your OS settings.
- Naming Short Windows files : short names are limited to 8 characters. Having a unique Short Name allows a graceful playback and uninstallation experience for Windows users. They may or may not see these short names, depending on their OS settings. All Windows screensavers should be given a short name.
- Naming Macintosh files names are limited to 100 characters. The screensaver will automatically have ".saver" appended, and the installer will have ".app" appended. You may or may not see these suffixes, depending on your OS settings.
- Naming Installers : This is the filename that the end user will see on their desktop when downloading and installing. However, the installer's menubar title will be the same as listed in the Preview on the Installer panel.
- Naming Screensavers : This is the filename of the actual screensaver file on the end user's computer and is what will show up in the OS's Screensaver Control Panel.
Zip after Build
An option to automatically compress the installers into simple cross-platform-transportable formats for use on a website, sending through email, or moving across platforms. For Macintosh, it is checked on by default. For Windows, we recommend leaving this option off, as, in most cases, the Single-File EXE is an easier solution for user installation. Enable this either if you have file sizes, or if the installer itself is, larger than 2GB in size.
These icons are used when the user downloads the screensaver installer. To create an icon, make a 512x512 pixel file with the desired icon art and transparency masks, and save it in PNG-24 format. Click 'Edit' on the icon you desire to change, and then select the file with your new icon art.
Please note that Windows systems are limited in size to 256x256 pixel icons. If the icon must include a large Mac icon, we recommend moving and rebuilding the project on a Mac machine, or use a more complex technical procedure for inserting a larger icon into the Macintosh installer. You can still use original artwork sized at 512x512 pixels in Designer on either platform, and it will be sized as best it can.
Macintosh allows customized icons in the System Preferences' Display &: Screensaver pane. The exact size is 180x116 pixels, but any image can be scaled to fit.
You can choose an image to be included as a desktop background. Click on 'Edit' to select or delete a chosen image. Click on 'Test' to install or uninstall the image on your machine. The user will have the option whether to install the Wallpaper or not during installation.
Finding the Installers
The fastest way to find the newly created installers is by the Reveal buttons on either the master Builds or individual platform tabs.
Testing the Installer
It's possible to immediately test the installer, after building, from the Install buttons on the individual platform tabs. Of course, you can only test a screensaver on the same platform that you are building on... (the multi-platform build features of iScreensaver are cool, but they aren't magic!)
Code-signing, Gatekeeper, and AuthenticodeThe latest Macintosh and Windows operating systems have strengthened their developer security systems. This has changed how third party developers, such as iScreensaver, approach creating applications, and how our professional screensaver authors must adapt to their new security systems. Need help with distributing your screensaver?
Please see Distributing Screensaver Installers
Screensavers, identity, and software security in the modern era
Modern operating systems (beginning with Windows 10 and Mac OS X 10.10 Yosemite) are very careful to only run software that is ''trusted.'' This trust is established by the author of the software signing the code with a digital signature, based on a certificate that was issued to the author's company after a thorough background check to establish a valid identity. Our editing software, iScreensaver Designer, is signed with such a certificate (issued to our parent company Xochi Media Inc).
iScreensaver lets you, the author, create a fully customized screensaver and screensaver installer program, complete with your own icons, text descriptions, images, and copyright information.
These custom modifications change data within the software application executables, so that every screensaver you build is unique. This is a generally a good thing, as the end user of the screensaver software will see your name, your icons - your information.
Unfortunately, these modifications also prevent the screensaver installer software from being digitally signed with our corporate certificate. (If we were to sign it with our identity beforehand, when you built your screensaver, then the signature would be broken and the software application would not run at all).
So, when you build a screensaver installer using iScreensaver Designer, the final built software will be created without a digital signature.
This leaves you, the author, with two choices:
Option 1: No signature. | Option 2: Create your own digital signature.
Option 1: Deliver the software as-is, without a digital signature.
Mac OS X unsigned warning:
Windows' unsigned warning:
Windows' security warning:
Solution: Bypass these warnings.It is relatively easy to bypass these warnings - let your end users know ahead of time to expect the warning, and instruct them on the way to bypass the warning. These warnings are common to many software packages, and most customers already are familiar with the steps.
Important: when you bypass the warnings, you are allowing un-signed code to run on your computer, which in general is a bad idea. Users should only do this when they know and trust the software's source.
To bypass unsigned warnings on Mac OS X:
To bypass GateKeeper checks, one can simply right-click on the installer icon and choose "open", or hold down the control key while clicking the icon and choose "open".
There will then be a new window with the "open" button enabled:
To bypass unsigned warnings on Windows:
To bypass Authenticode checks, one can choose the "Actions" options and then click on 'More Options' and choose "Run anyway" from the second dialog.
With these two simple techniques, most of the problems of code-signing can be avoided. However, there are certainly situations where it's not feasible to take this approach. A better solution (but one that is much more expensive and technically demanding) is Option 2.
Option 2: Sign the screensaver installers with your own Digital Signature
Please note that this process is technical, time-consuming, and costs money. Furthermore, it uses third party companies, services, products and tools for which we can not provide technical support. We will provide an outline of the steps and some suggested vendors, but many of the details will be up to you.
Code-signing 101: Step-by-Step Instructions
Code-Signing and Notarization on macOS
- Get a Mac running OS X 10.14 or later. You can not code-sign Mac software on a Windows PC.
- Get an Apple Developer Account.
This currently costs $99 per year.
Enroll in the Apple Developer Program.
- Verify your identity with the Certificate issuer.
Typically this will require you to have a legal organization (such as LLC, Corporation, Non-Profit, or sole proprietorship).
This step can take several days to have your identify confirmed. You may need to make sure your company is listed properly in DNB (Dunn & Bradstreet) and that you know your DUNS number. You may also need copies of corporate documents such as the Articles of Incorporation.
- Create and download your code-signing certificate from Apple, which is called a "Developer ID Certificate"
- Create an app-specific password for your AppleID at appleid.apple.com
- Download a copy of our code-signing and notarization script:
(Right click and choose 'Download' file): sign_and_notarize_iscreensaver.sh
- Edit the file as per the instructions included within. You will need to provide your AppleID, app-specific password, and the file path and name of your screensaver, and a unique ID for the file
- Once you have your Developer ID Certificate, you can sign and notarize your finished screensaver installers with a single command line script
Code-Signing on Windows OS
- Get a Windows PC running Windows 10 or later. You can not code-sign Windows software on a Mac.
- Get a code-signing certificate. Numerous companies offer them, and current discount prices run about $100/year. We can recommend using certificates from these organizations:
- Verify your identity with the Certificate issuer. Typically this will require you to have a legal organization (such as LLC, Corporation, Non-Profit, etc.) and can not be done by an individual or sole proprietorship. This step can take several days to have your identify confirmed. You will want to make sure your company is listed properly in DNB (Dunn & Bradstreet) and that you know your DUNS number. You may also need copies of corporate documents such as the Articles of Incorporation.
- Retrieve your code-signing certificate from your vendor once it is ready. Important: use IE11 for this step and download your certificate on the same computer you will use for code-signing.
- Save the certificate and private key as a PFX format by following these steps in IE11:
- Open IE11 on the same computer where you downloaded your certificate.
- From the Tools menu, choose Internet Options.
- On the Content tab, click the Certificates button.
- Select the code-signing certificate you just purchased and downloaded (note: there may be several certificates in the list, be sure to choose the correct one).
- Click the Export button.
- Choose "Yes, export the private key".
- Choose "PKCS#12.PFX" as the kind.
- Check the box for "Include all certificates in the certification path if possible".
- Create a certificate password (and remember it for later).
- Export the file to your hard drive.
- Get the windows SDK which includes the 'signtool' command-line tool. The easiest way is to download the Windows 8.1 SDK, which can be used on Windows 10, directly from Microsoft: Download Windows 8.1 SDK.
Those are the hard steps. The next step is fairly easy:
- Once you have your Certificate and SignTool app installed, you can sign your finished screensaver installers with a single command line:
"C:\Program Files\Microsoft SDKs\Windows\v8.1\Bin\signtool.exe" sign /v /f MyCertificateAndPrivateKey.pfx /tr hhttp://timestamp.comodoca.com/ /p myPassword /fd sha256 /d "My Screensaver Description" /du "http://mywebsite.com" MyScreensaverInstaller.exe
...replacing 'MyCertificateAndPrivateKey' with the name of your certificate file, changing 'myPassword' to the password you created above, setting the description and URL to your company, and supplying the actual path and filename for your built screensaver installer for MyScreensaverSingleFileInstaller.exe.
- Important note: currently, iScreensaver Designer 5 only supports signing the Single-File-Installer format. This provides a digitally-signed installer; however the actual screensaver installed will not be digitally signed. Generally this does not cause problems and the installation will be straightforward. However, if the user chooses the option to install the screensaver "For All Users" on their computer, they will see one additional UAC prompt: which they must click "Yes" on.