Dada Life – Endless Smile 1.0.0, Sausage Fattener 1.0, VST, x86 x64 (NO INSTALL, SymLink Installer) [2018]

Audio DSP package, consisting of:
Dada Life Endless Smile 1.0.0
Dada Life Sausage Fattener 1.0
Dada Life Sausage Fattener by COLOVE Skins


Sources:

Hidden text
Dada.Life.Endless.Smile.v1.0.0-AudioZ
Dada.Life.Sausage.Fattener.VST.v1.0.x86.x64-ASSiGN
Dada Life Sausage Fattener by COLOVE Skins

Screenshots
Screenshots of the About window

{HOW TO INSTALL?}

Hidden text
The software package is intended for trial testing. Liked? Earn? – Support the manufacturer with a purchase.
{HOW TO “INSTALL” THIS PACKAGE USING SymLink Installer .CMD FILES?}
Brief description:
A) AFTER SAVE THE WORK, delete the folders left over from previous installations;
B) run the batch file for creating symlinks (Windows Junction Points) – SymLink Installer.cmd;
C) start the DAW by setting the VST2 plugins scan path*, scan for new plugins by running them and (if required) register.
* For x86 VST2 – C:\Program Files (x86)\VstPlugins. For x64 VST2 – C:\Program Files\VstPlugins.
The installation details are described below. The “installation” steps are indicated in curly braces.
Details (read if necessary) are enclosed in “spoilers” in triple square brackets.
Hidden text
[WHAT IS SYMLINK (SYMBOL LINK, SymLink)?]
Hidden text
A symlink (a symbolic link, in the case of a folder, the required type of symlink is Windows Junction Points) is a special type of link to a folder or file, which is taken by programs that read it as a regular folder or file, although the actual data source may be on another disk.
Link Shell Extension
schinagl.priv.at/nt/hardlinkshellext/linkshellextension.html
en.wikipedia.org/wiki/Symbol_link
ATTENTION! Deleting a symlink does not delete the folder referenced by that symlink.
ATTENTION! Deleting something when you enter inside the symlink folder, leads to the actual deletion of what is being deleted.
 
[IS IT POSSIBLE TO DO WITHOUT USING THE .CMD FILES OF THE SymLink Installer?]
Hidden text
Yes. SymLink Installer CMD files are optional,
you can just copy the files according to the folder names inside the ..\C\ folder,
and also pay attention to the presence or absence of *.reg registry files, keygen … etc. inside the package.
 
{0} {Pre-install required system software}
Install
[addon] Microsoft Visual C++ 2005-2008-2010-2012-2013-2017 Redistributable Package x86 & x64
forum.oszone.net/thread-145766.html
{1} {Proper unzipping of the package}
Open the .exe file of the package with the 7-zip.org archiver (without using drag and drop),
extract its contents to any disk for permanent storage*,
not deep by folder nesting, briefly by name, from letters, numbers , spaces, underscores, dots,
without other non-alphabetic characters, without Cyrillic and other national alphabets, for example:
D:\Dada Life
* For proper operation of symlinks, MOVE, DELETE, RENAME ANYTHING IN THE PACKAGE IS UNACCEPTABLE.
{2} {Remove traces of other package versions}
{2.1} ATTENTION! Save the developments (presets, etc.) of the one being deleted.
{2.2} Uninstall (or remove if there is no uninstaller) previous versions of the installable.
{2.3} Check for the absence of folders in the places where symlinks are created (IF FOLDERS ARE LEAVE, THEN SYMLINKS WILL NOT BE CREATED),
and delete the folders remaining after uninstallation, according to the list {FOLDERS OF THE PACKAGE CONTENTS FINAL LOCATION} .
NOTE. For a quick answer to the question “Should I delete any folders before running SymLink Installer?”
you can run Existing Folders.cmd – if any folders are not opened during its operation, then they do not exist and you do not need to delete them.
After working out the SymLink Installer, the batch file Existing Folders.cmd allows you to quickly show all the folders of the installed package.
{FOLDERS OF PACKAGE CONTENT DESTINATION}
Hidden text
The “-” characters (before the paths below) indicate which folders are not needed for the 32-bit version of Windows.
“C\” corresponds to the system drive – “C:\”.
– C\Program Files\VstPlugins\Dada Life
C\Program Files (x86)\VstPlugins\Dada Life
C\Program Files\Dada Life
ATTENTION! In many cases, the use of Cyrillic during registration and in the name of the user folder (Current User Name) may not be supported by the software.
ATTENTION! If the name of the system drive differs from “C:\”, you should check the attached .reg registry files (if any in the package) and correct the name of the system drive in them.
How to deal with non-standard placement of the Documents folder?
Hidden text
If there is content that should be placed in the %USERPROFILE%\Documents
folder, and if this folder has been moved (for example, to another disk), the CMD files should be corrected.
Let’s say the path to the Documents folder on your system
is D:\Documents
, then in Notepad++* you should find and replace all occurrences of the
%USERPROFILE%\Documents
line with the
D:\Documents line
* There is syntax highlighting of the CMD format.
{3} {Actually “installation”}
For instant installation based on symlinks, run as administrator (via the context menu of Windows Explorer) the batch file ** SymLink Installer.cmd,
and if necessary, change*** the path to VST2 in . cmd files.
** [WHAT IS THE PURPOSE OF .CMD FILES?]
Hidden text
CMD files serve to automate operations with files, folders, Windows administration. REFERENCE. ab57.ru/cmd.html
SymLink Installer.cmd – creates symbolic links to folders and files from the ..\C\ folder.
Hidden text
SymLink Installer.cmd consists of the following blocks:
– getting administrative permissions (for creating symlinks in system folders);
– determining the bitness of Windows OS (x86 or x64);
– creating symlinks for x64 Windows;
– creating symlinks for x86 Windows.
 
SymLink DeInstaller.cmd – Removes symbolic links to folders from ..\C\.
Hidden text
SymLink DeInstaller.cmd consists of the following blocks:
– getting administrative permissions (to delete symlinks or folders in system folders);
– determining the bitness of Windows OS (x86 or x64);
– removal of symlinks or real empty folders for x64 Windows;
– removal of symlinks or real empty ones for x86 Windows.
 
ATTENTION! If you have trouble starting SymLink*.cmd (“infinite run”), open the batch files and remove the snippet starting from the line:
:: BatchGotAdmin BEGIN sites.google.com/site/eneerge/home/BatchGotAdmin | ss64.com/nt/rem.html | ss64.com/nt/cacls.html
and line by line:
:: BatchGotAdmin END
inclusive. This snippet is responsible for “Run as administrator”.
When removing it, you should run batch files through the context menu item (right-click) above the file, selecting “Run as administrator”.
Utilities:
Existing Folders.cmd – checks for the existence of folders according to the list from the item {FOLDERS OF END PACKAGE CONTENT DISTRIBUTION} and shows them as separate windows if they exist.
FoldersList.cmd – creates a list of folders inside the ..\C\ folder.
 
*** [HOW TO CHANGE VST2 PATHS IN SymLink Installer .CMD FILES?]
Hidden text
The change of paths in .CMD files for the VST2 plugin format described below can be omitted
if you specify an additional scanning path for VST2 plugins in the DAW settings: C:\Program Files*\VstPlugins,
or place a symlink to the C:\Program Files*\VstPlugins folder inside folders where you usually have the rest of the VST2.
For example, if you have all VST2 plugins located in the C:\Program Files*\Steinberg\VstPlugins folder,
then inside this folder a symbolic link is made to the C:\Program Files*\VstPlugins folder.
If the specified location is not suitable, then you can edit the paths for creating symlinks in CMD files.
For example, in the SymLink Installer.cmd file, you can replace the lines (using any text editor):
cmd /c mkdir “%PROGRAMFILES%\VstPlugins”
cmd /c mklink /j “%PROGRAMFILES%\VstPlugins\Dada Life” “%~dp0C\Program Files\VstPlugins\Dada Life”
cmd /c mkdir “%PROGRAMFILES(x86) %\VstPlugins”
cmd /c mklink /j “%PROGRAMFILES(x86)%\VstPlugins\Dada Life” “%~dp0C\Program Files (x86)\VstPlugins\Dada Life”
for example, on the lines:
cmd /c mkdir “%PROGRAMFILES%\Steinberg\VstPlugins”
cmd /c MKLINK /j “%PROGRAMFILES%\Steinberg\VstPlugins\Dada Life” “%~dp0C\Program Files\VstPlugins\Dada Life”
cmd /c mkdir “% PROGRAMFILES(x86)%\Steinberg\VstPlugins”
cmd /c MKLINK /j “%PROGRAMFILES(x86)%\Steinberg\VstPlugins\Dada Life” “%~dp0C\Program Files (x86)\VstPlugins\Dada Life”
or for example, to strings (using absolute paths instead of relative ones (%PROGRAMFILES(x86)% or “%PROGRAMFILES%)):
cmd /c mkdir “C:\Program Files\Steinberg\VstPlugins”
cmd /c MKLINK /j “C:\Program Files\Steinberg\VstPlugins\Dada Life” “%~dp0C\Program Files\VstPlugins\Dada Life”
cmd / c mkdir “C:\Program Files (x86)\Steinberg\VstPlugins”
cmd /c MKLINK /j “C:\Program Files (x86)\Steinberg\VstPlugins\Dada Life” “%~dp0C\Program Files (x86)\ VstPlugins\Dada Life”
Or others required in specific circumstances.
Similar path changes (if necessary) should be made in other .CMD files.
[How does the MKLINK command that creates a symlink work?]
Hidden text
Help on MKLINK: ab57.ru/cmdlist/mklink.html
To create a symlink, the folder in which it is created must be created in advance.
Example:
cmd /c mkdir “C:\Program Files\Steinberg\VstPlugins”
This command creates a real folder “C:\Program Files\Steinberg\VstPlugins”, making it possible to create a symlink inside it.
Example command for creating a symlink:
cmd /c MKLINK /j “C:\Program Files\Steinberg\VstPlugins\MyFolder” “%~dp0C\Program Files (x86)\VstPlugins\MyFolder”
The command creates a symlink named MyFolder inside the folder “C: \Program Files\Steinberg\VstPlugins”,
while a link to the source folder is stored inside the symlink – “%~dp0C\Program Files (x86)\VstPlugins\MyFolder”.
%~dp0 – instead of this code, when executing a .cmd file, the full path to the folder from which the .cmd file is launched will be substituted.
cmd /c – code for calling the command processor for executing batch files.
/j is the key for creating a symlink to a folder, not to a file.
ATTENTION! Deleting a symlink does not delete the folder referenced by that symlink.
ATTENTION! Deleting something when you enter inside the symlink folder, leads to the actual deletion of what is being deleted.
 
{4} {Final step}
Installation completed.
Open the DAW, specify an additional VST plugin scanning path in the DAW settings
(for x86 VST2 – C:\Program Files (x86)\VstPlugins, for x64 VST2 – C:\Program Files\VstPlugins)
and perform an update plugin scan.
See above for more: {HOW TO CHANGE VST2 PATHS IN SymLink Installer .CMD FILES?}
[WHY DO THE NO INSTALL VERSIONS NEED?]