Wise Installation System is a script-based, easy-to-use installation utility that will help developers create reliable, professional installations to meet a wide range of requirements.
Whether you need to quickly create a simple, reliable install, or you have advanced requirements such as Internet/intranet distribution, Windows CE installs, or application self-healing, Wise Installation System is the script-based solution for you.
Wise Installation Studio contains the following applications:
· Windows Installer Editor
· WiseScript Package Editor
· Wise Virtual Package Editor
· Wise Mobile Device Package Editor
Here are some key features of "Wise Installation System":
· Create installations that support Microsoft* Windows Installer (MSI) standard.
· Create .EXE installations that use WiseScript technology.
· Virtualize applications to dramatically minimize application and OS conflicts.
· Integration with Altiris Software Virtualization Solution (SVS), lets you create, edit, and manage virtual software installations.
· Add VBScripts to a WiseScript. Use all VBScript capabilities including arrays and subfunctions.WiseScripts and VBscripts interact so variables can be passed between either type of script.
· WiseScripts can be moved to another machine by packaging all files, including source files, as a self-extracting .EXE.
· Enhancements for Vista include checking for the presence of Windows Vista on target machines, compatibility with Internet Explorer 7.0, minimizing reboots using the Restart Manager Infrastructure in Vista, access control for general user and administrator privileges, enhancements for digital signature support, validation for Vista logo standards, and setting logging options for the installation.
· Manage the 64-bit portion of the registry and file system, author a single .WSI project file that can create separate .MSIs for both the 32-bit and 64-bit versions of an application, and use the Release Settings page to specify which components to not install in the 32-bit or 64-bit version of the installation.
· Support for Nalpeiron's PRO-Tector* product, which allows developers to electronically generate, track and enforce software licenses and protect against unauthorized use by implementing a range of product activation and enablement software copy protection options. See www.nalpeiron.com/altiris/. The Wise Installation Studio installation includes a link to download a free copy of Nalpeiron PRO-Tector Standard ($799 value), which will trialware-enable a single product.
· Use the Windows Installer Editor to create an installation that will install a mobile device package to a desktop computer. The mobile device package can then be copied to the mobile device using HotSync (Palm) or ActiveSync (Windows).
· Easily create a project file in .INF format and compile it to one or more .CAB files that installs a mobile device application. Supports Windows Mobile 5.0 platform, Windows CE, Pocket PC* 2003 (and older versions), Palm* OS, .NET
· Compact Framework*.
· Allows you to view your .MSI installation as a logical, sequential script. Edit the script by adding script actions, and each modification automatically updates corresponding entries in the Windows Installer database tables. Includes ability to search for specific text, support for nested IF statements, ability to select multiple lines for moving or deleting an entire IF statement, and provides visual feedback on where to place custom actions within restricted locations.
· All the advanced tools you need to fully customize an installation. Provides an alternate view of your installation, giving you more control over organizing features and components, designing dialogs, editing database tables, creating and editing properties, and developing a wide range of custom actions.
· Merge modules, commonly used for third-party runtimes, can now be included in your installation.You can author your own modules, including support for creating static or configurable modules.
· Built-in scripting actions Our industry-leading scripting engine can be used to create special routines in your installation or add security to your installation when installing license files.
Limitations:
· 30-day trial period
· The Code Signing page has been renamed the Digital Signature page.
· Previously, when your installation created a shortcut in a new program group in the Start menu, the uninstall removed the shortcut but left the program group. This has been corrected.
· There was a problem when you used a variable to name a new shortcut. Another blank shortcut would appear, which in turn resulted in two Create Shortcut actions in the script. This has been corrected.
· Previously, a problem existed with reading text files into variables from a custom dialog script. This problem could cause a hang when reading text files into variables through a dialog script. Variables processed in a dialog script had a lower size limit than variables that were processed from the main script. Variables in dialog scripts now have the same size capabilities as variables in the main script.
· Sometimes users were not prompted to reboot at the end of uninstalls when a reboot was necessary in order to delete some files. These files were marked by the operating system to be deleted at next reboot. If the user then immediately reinstalled the software and THEN rebooted, the files got deleted, resulting in missing files. This has been corrected--now users get prompted to reboot when a reboot is necessary to remove files after an uninstall.
· In the Copy Local Files Settings dialog, the values you chose in the File Version and File Date/Time fields were not retained after the dialog was closed. This has been corrected.
· Previously, if your installation searched for a previous version, it would search the Recycle Bin. It would also offer the Recycle Bin as the destination location during installations when users browsed for a Destination Directory. This has been corrected. Now, hidden/system folders are not searched.
· If you enter a name in the Installation .EXE Name field on the Build Settings page without the extension (.EXE), the extension is now added to whatever name you enter. This prevents a problem where the last four letters of the installation .EXE name were cut off if it was specified with a compiler variable.
· Previously, if you set %VARIABLE1% to the value of %VARIABLE2% using the Convert to Long Filename option, but VARIABLE2 was blank, VARIABLE1 would get set to the value of the current working directory. This has been corrected.
· Previously, when you selected multiple files on the Files page and clicked the Details button, you saw a dialog that did not have the File Version or File Date/Time fields. These fields are now available.
· In a particular sequence of adding files, If Statements, and WiseUpdate to an installation, it was possible for the Install WiseUpdate Client script action to accidentally be placed inside an IF Statement. This has been corrected.
· If you added the Add Text to INSTALL.LOG script action, and entered a variable in the Log Text field, you did not get a warning if the variable was undefined. This has been corrected--now if you reference a variable in the Log Text field that is undefined, you get a compile error.
· There was a problem where the language specific changes you made on the Select Components dialog would disappear after editing components on the Components page. This has been corrected.
· Changing the vertical position of a dialog in the dialog box properties had no effect. This has been corrected.
· Previously, if you entered a name in the Installation .EXE Name field on the Build Settings page that did not have backslashes (i.e., was not a full pathname), WiseUpdate did not work properly. The installation name was not correctly inserted in the WiseUpdate .INI file, resulting in failed downloads. This has been corrected.
· The Check In-Use File script action previously reported an "In Use" result for files that are Read Only. This has been corrected. Now, the result of "Read Only" is returned for Read Only files.
· Previously, when WebDeploy evaluated proxy information, it first checked Netscape proxy settings. Because of the proprietary format of Netscape's proxy settings, this check would sometimes fail. To prevent this, WebDeploy now checks Internet Explorer proxy settings first, which results in more successful evaluation of proxy information because of the use of a standard format.
· Previously, the taskbar icon for the installation (the icon along the Windows taskbar) disappeared if certain conditions were true. If the background gradient was set to "No Gradient Window" AND if a dialog was not contained in a wizard loop, the taskbar icon did not appear. Now the taskbar icon appears during all custom dialogs, regardless of gradient and where dialogs are located.
· Previously, if you used the Read/Update Text File script action to read a text file and the file contained a NULL character, the installation would hang. Now, NULL characters are converted to spaces as they are read in.
