So this is trivial to change how we install the course files.
There's a unique file in this root and a unique folder under DATA that signifies the installed pack.
2. After Teacherworks determines that a particular pack is installed it actually iterates through the root of all drives on the system in alphabetical order looking for:
And then links against other subfolders under Media when 'Betainst' is found. Evidently the presence of this folder is adequate to determine that a 'CD' is 'Inserted' where the Betainst folder is found. Even though 'Title.txt' appears to indicate which disk is inserted, this information apparently is not used.
3. Using this information, you can in theory package up the uniquely named files from both the Media and COURSES folders from. As well as making an MSI installer for the Teacherworks runtime itself. The end experience will be:
--Deploy the Teacherworks Runtime MSI package
--Determine the Teacherworks Package to be deployed
--Load up the TeacherworksRepackagingTemplate.ism in InstallShield
--Change the Product Name, Product Code of the template, and ensure that the Dynamic File Links point to your CD drive.
--Build the project
--Deploy the resultant MSi to install the course files pack to the machine with the already installed Teacherworks Runtime package.
--Run Teacherworks, and select the appropriate course package.
4. Finally, to avoid removing Title.txt file during uninstall, all files installed to 'betainst' folder have been marked as 'Permanent' and 'Never Overwrite'.
If it is a requirement to remove these when the runtime and all course packages are removed, then this would be fairly simple to accomplish via further script code. Otherwise, this needs to remain present as an index of what course packs are installed on the system.