# When ACTIVATE is set to YES, the software chooses a random value between 1 and the specified value to wait before the activation Volume attempt and between attempts. # Accepted Values: A valid 31-digit license number. # License Number of the TI software to be activated on the client computer. # Accepted values: A valid Unix, UNC, or Windows path. # Example, if TI-SmartView CE for the TI-84 Plus Family Software were installed successfully on the ClassDesktop01 computer on August 15, 2011, at 2:30 p.m., this entry would appear: TISmartViewCE84-Success- ClassDesktop01-20110815-1430.log The file name indicates success or failure using the following format: -.log # Creates an empty file immediately after activation. # deployment.properties for TI-SmartView CE for the TI-84 Plus Family 5.1 and TI-SmartView pour la famille TI-83 5.1 Writelog 'ERROR: TI-SmartView installer and/or deployment.properties file not detected.' exit 1 fi exit deployment.propertiesīelow is the standard deployment.properties file. Writelog 'TI-SmartView installation failed.' exit 1 fi else Writelog 'TI-SmartView installation successful!' Sudo installer - pkg '$INSTALLER' - target / if then Writelog 'CHECK: TI-SmartView installer and deployment.properties detected. # Checks for both the PKG & License, and installs if both exist I created a postinstall script to log the install and remove both files afterward. The SolutionĬreate a PKG installer and put both the standard TI-SmartView CE install PKG and the deployment.properties file in the same directory – I use /private/tmp/. However, in the most recent version of the software while the deployment.properties file still gets created through the installer in the directory specified above, the PKG installer as part of its install process now actively looks for a deployment.properties file in the same directory as the PKG installer. As a result, you could run the TI-SmartView PKG installer and then install a separately packaged deployment.properties file to this directory so that when a user launched the application for the first time it became activated.

This file is essentially a template in order to automatically activate a perpetual serial number when the software was launched for the first time.

When TI-SmartView CE is installed via its install PKG, a deployment.properties file gets created in /Library/Application Support/TI-SmartView CE 84/res/. I recently started testing some of our existing software on the latest version of macOS Sierra (10.12.5) and ran into an issue with the TI-SmartView CE emulator software for Mac when trying to activate with our institution’s license that was a result of a change Texas Instruments had made to the software installer that wasn’t communicated and is somewhat buried line in their software installation and activation knowledge base article. This is based on a post I made on Jamfnation back in March.

Ti 83 emulator mac