Me Too !!! and i`ve been in this game for 15 yrs or so ... i hang my head in shame !!

 

If you find out how to do it give us a shout will ya`s dude ??

 

looks like they have a purpose for some ppl, me i get only confused by those releases, so until i have the "need" i will not care about getting into the why of these new "fixes".. im not into testing no more, i make an install thats it, there is enough distraction

 

im def lost too! they need to include a text that can be fully read or post one somewhere that we can see

 

I always look at those SymLink no-installs and sometimes keep them, because they help me understand the structure of all these goodies. What annoys me is the weather.

 

This, as in many other things, is my advise. Keep the R2R working one unless you really need a later version.

In case you wanna try:
1. If you've a serious complex workflow back up everything, you can break things more likely.
2. You can install the no install/symlink releases without symlinks (manually). But chances are you'll break something even more likely.

 

I know exactly what you mean. I think this is one of the biggest problems with the Symlink No-Installs. People are really confused as to what this is all about. I've seen dozens of people asking for some direction and there seems to be very little information available.

I do wish that someone who really understood how this whole symlink thing works would write up a detailed explanation. I believe that then, most people would be more comfortable with this "new" idea.

I've gotten a couple of the symlink no-installs to work by using guess method. I, too, have been at this for over 15 years and have a pretty good understanding of the Windows OS so have been able to attempt to figure what goes where but I'm still confused as to how this whole thing works.

Someone please write up a detailed explanation of the install method and some details of the theory of how this works in place of a "normal" Windows install.

 

thanks to them i use NEMESIS on MAC :D thanks to their key and little snitch /

 

Voice my opinion I did.

 

These are the instructions for installing the latest SERUM Symlink, for example.

I google-tranlated this and cleaned it up a tiny bit. TBH, I have not seriously sat down and ingested the following - yet.

.....ok, here we go.......

{AS "SET" THIS PACKAGE WITH FILE .CMD SymLink Installer?}

################################################## ####
software is for trial testing.
Support manufacturer, if the software is pleasant
and it is planned to use for a living,
by the rules of the Manufacturer License.
################################################## #### {HOW "SET" THIS PACKAGE WITH FILE .CMD SymLink Installer} Although the following is a long description, the essence is simple:
A) Save HOURS, remove some folders, possibly left over from previous installations;
B) run the batch file create symlinks - SymLink Installer.cmd;
C) specified in the DAW scan path VST2 plugin (C: \ Program Files (x86 ) \ VstPlugins),
D) to start the DAW, scan for new plug-ins, running them, and (if required) to register.

Stage "setting" are specified in curly brackets.
Explanations (read only if necessary) highlighted in spoilers (or triple the square brackets in annexes to the distribution of txt file).

[WHAT symbolic links (symlinks, SymLink)?]

Symlink (symbolic link) - a special kind of links to a file or folder,
which is perceived to read them programs like the real folder or file,
although it is only a reference, the real source of which is located elsewhere on the disc. https://www.youtube.com/results?search_query=Link+Shell+Extension Link of Shell the Extension schinagl.priv.at/nt/hardlinkshellext/linkshellextension.html ru.wikipedia.org/wiki/Simvolnaya_ssylka WARNING! Deleting a symbolic link does not delete the folder that is referenced by the symbolic link. Removal of anything inside the entrance symlinking folder leads to the actual removal of exhaust.

[Can we do without installation using .CMD FILE SymLink Installer?]

Yes. CMD files SymLink Installer not required to use,
you can simply copy the files according to the folder names in the folder .. \ C \,
and also pay attention to the presence or absence of * .reg registry file, crack ... etc. inside the package.

{0} {Pre-installation of the system software required}
Install Microsoft packages Visual C ++ Redistributable,
required for many plug-ins (if not installed or partially installed)
[addon] Microsoft the Visual the C ++ Redistributable the Package 2005-2008-2010-2012-2013-2015 the x86 x64 &
forum.oszone.net/thread-145766.html
{1} {correct} unzipping the package Open the package .exe file using the shell 7zip archiver, and extract the contents to any disc for permanent storage - so, so you do not delete * for example, in the folder: D: \ Xfer - not deep on subfolders and without the Cyrillic alphabet. * To ensure the efficiency of SymLink Installer .CMD files


Move, delete, rename anything in CONTENT DISTRIBUTION unacceptable.

{2} {Pre-cleaning from possible "the remains" of early versions of the package}
{2.1} NOTE! Save operating time (presets etc.) removed.
{2.2} Uninstall (or delete if not uninstall) previous versions installed.
{2.3} Check for a folder in a location where they will set up symlinks (if the folder LEAVE THEN symlink will not be created), and remove the remaining (if left) after the uninstall folder according to the list {FOLDER END OF PLACING OF PACKAGE} . {FOLDER END OF PACKET ALLOCATION}

Package content is located in folders listed below ( "C \" is the system drive - "C: \").
To successfully create symbolic links before starting .CMD SymLink Installer files, you need to make in the absence of these folders.
NOTE. For a quick answer to the question "Do I have to delete some folders before starting SymLink Installer?"
You can run Existing Folders.cmd - if in the course of his work will not open any folder, so they do not exist, and remove them is not required.

After working SymLink Installer, batch file Existing Folders.cmd allows you to quickly open all folders specified content.
Next is a list of the folders needed for the package (some of them may not be required, and some - are critical to performance).
Symbols "-" (to the paths below) indicate which folders are not required for x86 systems.

- the C \ Program Files \ VSTplugins \ Xfer x64
the C \ Program Files (the x86) \ VSTplugins \ Xfer the x86
the C \ Users Offline \ (Current the User the Name) \ the AppData \ Roaming folder \ Xfer
the C \ Users Offline \ (Current the User the Name) \ the Documents \ Xfer
- the C \ Program Files \ the Common Files \ the Avid \ the Audio \ the Plug-Ins \ Xfer
the C \ Program Files (the x86) \ the Common Files \ the Avid \ the Audio \ the Plug-Ins \ Xfer

WARNING! As a rule, the use of the Cyrillic alphabet in the registration and user name folder (Current User Name) makes it impossible to register and normal operation of the software.

ATTENTION! If different from the name of the system drive "C: \", you need to pay attention to the attached registry files (if any in this package) and correct system drive letter in which the required.

{3} {Actually the "Installation"}
for instant installation on the basis of symbolic links,
run by an administrator (through the context menu) command file * SymLink Installer.cmd,
and if necessary, change the path to VST2 ** in .CMD files.

* [What is the purpose .CMD FILE?]

NOTE. CMD files - these are files automate operations with the file system and Windows administration.
REFERENCE. ab57.ru/cmd.html

In this particular case .CMD files provide creating symbolic links or the removal of symbolic links or real folders.
SymLink Installer.cmd - creates symbolic links to folders and files from the folder .. \ C \.

SymLink Installer.cmd consists of blocks:
- obtaining administrative authority (to create symbolic links to system folders);
- definition of bit OS Windows (x86 or x64);
- create symbolic links for x64 Windows;
- create symbolic links for x86 Windows.

SymLink DeInstaller.cmd - removes the symbolic links to folders in .. \ C \ or !!! ordinary folders !!!.

SymLink DeInstaller.cmd consists of blocks:
- obtaining administrative authority (to remove or folder symbolic links to system folders);
- definition of bit OS Windows (x86 or x64);
- removal of symlinks or real folders for x64 Windows;
- removal of symlinks or real folders for x86 Windows.

ATTENTION! If you have problems launching SymLink * .cmd ( "endless run"), open the batch files and remove the fragment beginning with the line:
:: BatchGotAdmin the BEGIN sites.google.com/site/eneerge/home/BatchGotAdmin | ss64.com/nt/rem.html | ss64.com/nt/cacls.html
and line:
:: BatchGotAdmin the END
, inclusive. This fragment is responsible for the "Run as administrator".
If it is removed you need to run batch files through the context menu (right-click) on the file, selecting "Run as administrator".
Utilities:
the Existing Folders.cmd - verifies the existence of the folder in the list of points {FOLDER END OF PLACING OF PACKAGE} and open them in separate windows, if they exist.
FoldersList.cmd - creates a list of folders within the folder .. \ C \.

** [HOW TO CHANGE THE WAY TO VST2 In .CMD FILE SymLink Installer?]

The following items change the ways in .CMD files for VST2 plugin format can not do,
if the settings DAW specify additional scan path VST2 plugins: C: \ Program Files (x86 ) \ VstPlugins,
or place a symlink to the folder C: \ Program Files (x86 ) \ VstPlugins inside the folder where you usually placed the rest VST2,
for example, all VST2 plug you placed in the folder C: \ Program Files \ Steinberg \ VstPlugins,
then inside that folder is a symbolic link to the folder C: \ Program Files (x86 ) \ VstPlugins.
If the specified location (for whatever reasons) is not suitable, you can edit the path of creating symbolic links to the CMD-files.

For example, in SymLink Installer.cmd file can replace the line (using any text editor):
cmd /c mkdir "%PROGRAMFILES%\VstPlugins"
cmd /c mklink /j "%PROGRAMFILES%\VstPlugins\Xfer x64" "%~dp0C\Program Files\VstPlugins\Xfer x64"
cmd /c mkdir "%PROGRAMFILES(x86)%\VstPlugins"
cmd /c mklink /j "%PROGRAMFILES(x86)%\VstPlugins\Xfer x86" "%~dp0C\Program Files (x86)\VstPlugins\Xfer x86"

for example, on lines:
cmd /c mkdir "%PROGRAMFILES%\Steinberg\VstPlugins"
cmd /c MKLINK /j "%PROGRAMFILES%\Steinberg\VstPlugins\Xfer" "%~dp0C\Program Files\VstPlugins\Xfer x64"
cmd /c mkdir "%PROGRAMFILES(x86)%\Steinberg\VstPlugins"
cmd /c MKLINK /j "%PROGRAMFILES(x86)%\Steinberg\VstPlugins\Xfer" "%~dp0C\Program Files (x86)\VstPlugins\Xfer x86"

or for example, on-line (using absolute path instead of relative (% PROGRAMFILES (x86)% or "% PROGRAMFILES%)):
cmd / c mkdir" C: \ Program Files \ Steinberg \ VstPlugins "
cmd / c MKLINK / j" C: \ Program Files \ Steinberg's \ VSTplugins \ Xfer ""% ~ dp0C \ Program Files \ VSTplugins \ Xfer x64 "
cmd / c the mkdir" the c: \ Program Files (the x86) \ Steinberg's \ VSTplugins "
cmd / c Mklink / j" the c: \ Program Files (x86) \ Steinberg \ VstPlugins \ Xfer ""% ~ dp0C \ Program Files (x86) \ VstPlugins \ Xfer x86 "
or other required in the particular circumstances.
Similar changes (if necessary) can be carried out in SymLink DeInstaller file .cmd,
which RMDIR team - deletes the folder at the specified path.
Similar changes (if necessary) can be done in other .CMD files.

[How does MKLINK command that creates a symlink?]

Help MKLINK: ab57.ru/cmdlist/mklink.html
To create a symbolic link, the folder in which it is created to be created in advance.

Example:
cmd / c the mkdir "the C: \ Program Files \ Steinberg's \ VSTplugins"
This command creates a real folder "C: \ Program Files \ Steinberg \ VstPlugins", preparing the possibility of creating a symbolic link inside it.

Example commands to create symbolic link:
cmd / c Mklink / j "C: \ Program Files \ Steinberg's \ VSTplugins \ MyFolder" "% ~ dp0C \ Program Files (the x86) \ VSTplugins \ MyFolder"
command creates a symbolic link named MyFolder inside the folder "C: \ Program Files \ Steinberg \ VstPlugins " ,
while inside the symbolic link stores a reference to the folder the source -"% ~ dp0C \ Program Files (x86) \ VstPlugins \ MyFolder ".
% ~ dp0 - instead of this code, when executed .cmd file will be replaced by the full path to the folder from which you run the .cmd file.
cmd / c - calling code execution shell command files.
/ j - key create symbolic link to the folder rather than the file.

ATTENTION!
Deleting a symbolic link does not delete the folder that is referenced by the symbolic link.
Removal of anything inside the entrance symlinking folder leads to the actual removal of exhaust.

[How to unlock CREATING symlinks for ProTools files?]

To unlock, create symbolic links for ProTools files, delete comment operator (characters "REM") at the beginning of the following SymLink Installer.cmd file lines:
REM cmd / c the mkdir "% COMMONPROGRAMFILES% \ the Avid \ the Audio \ the Plug-Ins"
REM cmd / c mklink / j "% COMMONPROGRAMFILES% \ the Avid \ the Audio \ the Plug-Ins \ Xfer" "% ~ dp0C \ Program Files \ the Common Files \ the Avid \ the Audio \ the Plug-Ins \ Xfer"
REM cmd / c the mkdir "% COMMONPROGRAMFILES (the x86)% \ the Avid \ the Audio \ the Plug-Ins "
REM cmd / c mklink / j"% COMMONPROGRAMFILES (the x86)% \ the Avid \ the Audio \ the Plug-Ins \ Xfer ""% ~ dp0C \ Program Files (the x86) \ the Common Files \ the Avid \ the Audio \ Plug-Ins \ Xfer "

{4} {} The final stage of installation is completed. Next, you need to open a DAW,
to specify in the settings DAW additional scan path VST plug-in: C: \ Program Files (x86 ) \ VstPlugins
and perform updates the scan plugins.
For more information see above:. {HOW TO CHANGE THE WAY TO VST2 In .CMD FILE Installer SymLink?}

For manual placement of content on the system drive, you need a startup command file
Create Serum.cfg.cmd - who writes the file
% USERPROFILE% \ AppData \ Roaming \ Xfer \ Serum \ Serum.cfg
indicating deployed towards user posting content folder - path to folder:
% USERPROFILE% \ the Documents \ Xfer \ Serum the Presets \ (in the last row Serum.cfg).
1
Enter key and use the key to FiXED NO KEYGEN version * are required.
* In the distribution there are two versions of plug-ins (in the initial state, in the folder .. \ C \ is FiXED NO KEYGEN version):
.. \ Xfer_Serum_121b4 Original \
- version without patching - works as a player, the presets in this version you can not save Serum - thus overwrites the file% AppData% \ Xfer \ Serum \ user.dat and loss of registration,
.. \ Xfer_Serum_121b4 Patced the SN of NO \
- version with patching - presets in this version you can save Serum - at the same time need the attribute "read only" file (in the properties) of the file% AppData% \ Xfer \ Serum \ user.dat
Patching prevents an error that would arise in the original version with the% AppData% overwriting \ xfer \ Serum \ user.dat having the attribute "read Only".
Quickly change to Original Patced version can use a batch file
Replace to Xfer_Serum_121b4 Patced NO SN.cmd
quickly change Patced on Original version is using a batch file
Replace to Xfer_Serum_121b4 Original.cmd
Thus there is a copy of the replacement tethers plugins
folder .. \ Xfer_Serum_121b4 Original \
or folder .. \ Xfer_Serum_121b4 Patced NO SN \
in .. \ C \ - in permanent storage folder assembly content for which are created symlinks.
These batch files are working strictly with the folder structure of the original distribution, for their proper functioning is not necessary to change this structure. {How is the registration version Original?}

1
To log in, run one of the key generators of the folder:
.. \ For information only \ the KeyGen \
and selecting the registration option "Serum", click next to the field "- TEAM R2R PRESENTS -"
copy key (selecting and pressing Ctrl + C ).
Several Kegen necessary in order that the key may come from one of them to the N-th input attempts,
do not select serial numbers starting with SJ.
2
Open the DAW, scan and upload new plugins Serum,
a key in the query window, insert the key (Ctrl + V),
click OK and restart the plugin. {Cyrillic script in the folder name USER IS NOT PERMITTED!} Www.youtube.com/results?search_query=izmenit+imya+papki+polzovatelya

 

Last edited: Nov 18, 2017

i am annoyed by annoying people that find NON annoying things Annoying, isn't that annoying?

 

Oh this man again
lets see how PERFECT you are?
I bet you never have drive faster than what the speed limit is?
You never had bring more alcohol when you cross the border to your homeland and if you have done so i bet you have reported ti to custom?
You have never ever ride for free on the bus or subway?
You have never shoplift?
Etc it must be so good that never have done anything criminal so lets hope you continue that life..

 

now THAT is a nightmare of a "fix"



.

 

Last edited: Nov 21, 2017

i dont like their method but i have no other choice lol

 

wow, i'm sorry you can't read simple instructions to install free software. maybe you should try something easier, like playing with legos. i'm sorry you are confused, but no most of us can figure it out.

 

Wow, that's very helpful. Thank you for all your time and effort.

 

Hey guys, does anyone now where I could learn about making my own NO INSTALL apps. I know how to do symlinks but not how to have all the files in one folder mainly reg files.

 

I wouldn't advise it. I know, it's a temptation... I've read the basics myself and it's way too complex.

Besides, it only works with certain apps like plugins. That's why you won't find no install versions of DAWs, Photoshop and so on.

If you still want to know, it's explained in the information files of the no install releases. In Russian... good luck and remain alive...

 

Since I'm locked in my place half sick this weekend I could make some video tutorial and upload a prepackaged kontakt 5.5.0/5.6.8/5.7.1 with the releases of AZ.

PM me if you're interested.

Admins, censor me if I crossed the line with the upload thing.