SOT: SAW|MWS Customizer v2.0
Good day,
For those that may not know, I am sort of a "stickler" when it comes to the installation of software. I do believe that this penchant of mine is due to EULA's - which I have always understood as meaning in effect, "Install this software at your risk!"
This is why I love RML Labs software - all of which simply takes up a bit of drive space! Thus, no EULA - at least, in the "installation sense" of the term.
According to Wikipedia:
"Many EULAs assert extensive liability limitations. Most commonly, a EULA will attempt to hold harmless the software licensor in the event that the software causes damage to the user's computer or data, but some software also proposes limitations on whether the licensor can be held liable for damage that arises through improper use of the software."
Thus, really-and-truly, installer beware!!
SAW|MWS Customizer V2.0 is an application for the removal of, and the restoration, of MIDI WorkShop. I simply required the means of being able to restore and remove MWS whenever required.
"The Investigation Process"
For those that might be at all interested, what is required during the investigative process is to determine what effect the installation of MWS had on the original installation of SAW. Seems simply enough? Thus, this investigative process is as follows:
1. Install SAW
2. Cleanup the installation materialize
3. Note the current folder/file structure
4. Backup the entire SAW installation
5. Install MWS
6. Cleanup the installation
7. Note the current folder/file structure
8. Backup the entire SAW|MWS installation
9. Compare the pre-installation and post-installation statuses
Observations
Following are the result of my investigation:
1. SAW root data was unaffected by the MWS installation
2. SAWStudioFX_Native is unaffected by the MWS installation
* Other than MWS consuming some drive space within the Native_PlugIns folder
3. After updating MWS preferences, SAW preferences remain unaffected
Summary
What can be deduced from the above is that SAW is unaffected by the installation of MWS - thus, making such an installation scenario perfect for scripting.
What this Script Does?
This script simply deletes or restores specific contents with the main application folder or the "Native_PlugIns" folder. "That is it!"
What this Script Offers?
Very simply...eighteen options under five categories, namely:
1. Copies a pre-made backup folder to a pre-designated location
2. Launch SAW: Launches SAW - for confirmation purposes only
3. Exit SAW: Exits SAW - for confirmation purposes only
4. Installs SAW: All automated
5. Configure SAW: This is manual procedure
6. Backup SAW: For later restoration purposes
7. Restore SAW Default: Deletes any updated data and confirms deletion
8. Restore SAW Update: Restores the updated data and confirms restoration
9. Install MWS: As #4
10. Update Shade: Copies the Contemporary MWS shade to match SAW
11. Confirm Install: Confirms the install of MWS
12. Backup MWS: As #6
13. Remove MWS: Remove the entire MWS installation
14. Restore MWS: As #8
15. Configure INT: As #5
16: Backup INT: As #6
17. Remove INT: As #13
18. Restore INT: As #8
19. About!: Displays a dialog
20. Exit: Exits the application
Observations
As can be seen, there are in effect, three types of installations involved here: 1) SAW alone, MWS alone, and SAW|MWS, referred to as "INT" for integrated.
The Requirements
All that is really required is a destination location to store the contents of the pre-made backup folder.
* In my particular situation, this destination location is: E:\Master_Backup\SAW_MWS
Other Info
The demo versions of both SAWStudio and MIDIWorkshop were employed/deployed throughout this entire procedure.
For an image of the completed application...please [Click_Me]
In closing...
If anyone is interested in this application, simply send me an email...
As always, I do sincerely hope that the above information may be of some practicable use to others.
Reply With Quote
Connect With Us