Symlink installer walkthrough

Discussion in 'Software' started by big man, Nov 29, 2020.

  1. Xupito

    Xupito Audiosexual

    Joined:
    Jan 21, 2012
    Messages:
    6,956
    Likes Received:
    3,830
    Location:
    Europe
    Ok, I get what you said now.
    This release is actually based on a Team-VR's: v9.91 in 2017. So even the original is pre-patched. Couple months later the no install gets released.

    The author adds all the cr*cks it can in that "for information only" folder. Just in case I guess, to give credits... who knows, what a mess it is. Includes R2R's 2017.05 and 2017.08 keygens. Don't remember by heart the months but something like that.
     
    Last edited: Dec 2, 2020
    • Interesting Interesting x 2
    • List
  2. chumbo

    chumbo Ultrasonic

    Joined:
    Mar 2, 2017
    Messages:
    124
    Likes Received:
    30
    Hi Xupito,
    Hope you can help me out here...
    I edited the installer.cmd file to have it correspond to my VST folders and boldly removed everything I felt was irrelevant and didn't want to have installed, so all references to AAX and x32 plugins.

    It's seems to have created the app folder correctly but the not the plugins folder!

    here's what it looks like (I didn't copy the UAC code part because I didn't touch that):

    Code:
    GOTO START_POINT
    :: Source Directories Structure BEGIN
    
    Note: Characters "- ", before these lines, mean - "not for x86 Windows".
    
    
    C\Program Files\Peavey
    
    - C:\Program Files (x86)\VSTPlugins (x64)\Peavey
    
    :: Source Directories Structure END
    :START_POINT
    
    :x64Windows
    :: x64 Windows BEGIN
    
    
    cmd /c mklink /j "%PROGRAMFILES%\Peavey" "%~dp0C\Program Files\Peavey"
    cmd /c mkdir "%PROGRAMFILES(86)%\VSTPlugins (x64)\Peavey"
    cmd /c mklink /j "%PROGRAMFILES(86)%\VSTPlugins (x64)\Peavey" "%~dp0C\Program Files\VstPlugins\Peavey"
    REM cmd /c mkdir "%COMMONPROGRAMFILES(x86)%\Digidesign\DAE\Plug-Ins"
    REM cmd /c mklink /j "%COMMONPROGRAMFILES(x86)%\Digidesign\DAE\Plug-Ins\Peavey" "%~dp0C\Program Files (x86)\Common Files\Digidesign\DAE\Plug-Ins\Peavey"
    REM cmd /c mkdir "%COMMONPROGRAMFILES%\Avid\Audio\Plug-Ins"
    REM cmd /c mklink /j "%COMMONPROGRAMFILES%\Avid\Audio\Plug-Ins\ReValver4.aaxplugin" "%~dp0C\Program Files\Common Files\Avid\Audio\Plug-Ins\ReValver4.aaxplugin"
    
    
    CD /d "%~dp0"
    :: [[[OPTIONAL: IT IS A PLACE FOR ADDITIONAL x64 Windows COMMANDS]]]
    regedit.exe -s "%~dp064bit Windows ReValver.reg"
    :: x64 Windows END
    goto OUT
    
    :OUT
    PAUSE
    EXIT
    Any ideas what I did wrong?
    Thanks!
     
  3. Sylenth.Will.Fall

    Sylenth.Will.Fall Audiosexual

    Joined:
    Aug 21, 2015
    Messages:
    2,422
    Likes Received:
    1,640
    He says whilst holding a bottle of Vodka behind his back! :D
     
  4. clone

    clone Audiosexual

    Joined:
    Feb 5, 2021
    Messages:
    5,955
    Likes Received:
    2,528
    cmd /c mkdir "%PROGRAMFILES(86)%\VSTPlugins (x64)\Peavey"
    cmd /c mklink /j "%PROGRAMFILES(86)%\VSTPlugins (x64)\Peavey" "%~dp0C\Program Files\VstPlugins\Peavey"

    Should these lines both just be %PROGRAMFILES(x86)?
     
    • Interesting Interesting x 1
    • List
  5. Xupito

    Xupito Audiosexual

    Joined:
    Jan 21, 2012
    Messages:
    6,956
    Likes Received:
    3,830
    Location:
    Europe
    Vodka is one of Mankind's Patrimonies. Knows no borders.
     
  6. nyaa13

    nyaa13 Producer

    Joined:
    Jul 21, 2019
    Messages:
    102
    Likes Received:
    75
    You don't have to make your lives unnecessarily hard by running commands etc. You can just install this program then create the symlinks yourself manually.
    Every single plugin I run on my DAW is running with symlinks from an external SSD and everything works perfectly without problems, exactly as if it would do if you made your DAW to scan the folder where you have your VSTS inside...
    (Bonus: That way you can do anything run portable and update itself if a newer version of it comes out as well, by just creating a junction.)

    Link: https://schinagl.priv.at/nt/hardlinkshellext/hardlinkshellext.html
     
  7. Stuck In The 80s

    Stuck In The 80s Rock Star

    Joined:
    Jul 29, 2019
    Messages:
    526
    Likes Received:
    310
    People want simple to follow instructions. That link of yours with it's 50 different scenarios is anything but that.
     
  8. Sylenth.Will.Fall

    Sylenth.Will.Fall Audiosexual

    Joined:
    Aug 21, 2015
    Messages:
    2,422
    Likes Received:
    1,640
    Oh yes I definitely concur my friend. Last time I drank a bottle of Vodka, I knew no boundaries or borders either. :D
     
  9. nyaa13

    nyaa13 Producer

    Joined:
    Jul 21, 2019
    Messages:
    102
    Likes Received:
    75
    Sorry, but that's not my fault. Daddy please, don't spank me. I only tried to help here.
    Well let's just say that the creator of this website doesn't know how to organize stuff very well.
    But still let's not forget that you can still use Control + F to find stuff much easier in sites. You can use keywords like "64bit" for example to save time.
    Personally, I didn't bother reading that much there cause I found about this program from a different source and I also test programs in virtual operating systems first... (In case if someone is concerned about safety or whatever...)
    I am also here to help if anyone wants more information. I don't bite, I promise...

    But anyways it's pretty straightforward. For anyone that's interested:

    You just download the program and install it and it creates an option when you right click any folder that you want to symlink. It's very simple... You can also link vsts directly using the Hard Link option, but that's only if they don't use additional files. In that case you can create a Junction.

    And here is the direct link for X64 Windows OS: https://schinagl.priv.at/nt/hardlinkshellext/HardLinkShellExt_X64.exe
    But it's not available for MAC...
    Sorry, MAC users... :(
     
  10. Xupito

    Xupito Audiosexual

    Joined:
    Jan 21, 2012
    Messages:
    6,956
    Likes Received:
    3,830
    Location:
    Europe
    @clone is right. %PROGRAMFILES(86)% is not a valid path variable. %PROGRAMFILES(x86)% is the one. The destination folder is created, so you don't need to create one and then symlink.
    Also @chumbo, don't use x86 paths if you're using x64 plugins. Oh, it's a fact.
    Change these lines to this
    Code:
    REM DON'T, THE SYMLINK CREATION INCLUDES THE FOLDER cmd /c mkdir "%PROGRAMFILES%\VSTPlugins (x64)\Peavey"
    cmd /c mklink /j "%PROGRAMFILES%\VSTPlugins (x64)\Peavey" "%~dp0C\Program Files\VstPlugins\Peavey"
    
    Rem makes the line a comment so renders it un-executable
     
    Last edited: Dec 19, 2021
  11. chumbo

    chumbo Ultrasonic

    Joined:
    Mar 2, 2017
    Messages:
    124
    Likes Received:
    30
    Hi again Xupito!
    I got a new PC so I'm starting from scratch and I tried again to edit the CMD file to point to where I keep my plugin folders but failed miserably!

    Would you be so gracious as to do the edit the CMD file for me rather than I trial & error until it's a complete mess and beyond repair! :disco:
    My folders are:
    (you can remove all the AVID references)

    VST x32: VSTPlugins (x32)
    VST x64: VSTPlugins (x64)
    VST3: C:\Program Files (x86)\VSTPlugins (VST3)

    (I know you told me previously that I shouldn't keep my VST x86 or even VST3 plugins in the \Program Files (x86) folder but it's the way I've done it for years and has never been a problem and prefer to have all my plugins under one parent folder. Unless you are aware of some very good reason why I shouldn't, I would really prefer to keep it that way, thanks!)

    I think it's the best way to learn, to have the original unedited version + the corrected/edited one and be able to compare to try and understand the mechanisms. That and all the explanations you already provided on this page of course!
    And I'm sure this will be useful to many other users as well!
    All anybody would have to do then is compare both files and replaces my paths with their own and...voilĂ ! :wink:
    Cheers,
    Chumbo

    (I skipped all the beginning part with regard to UAC and getadmin as I imagine that stays unedited anyway so...)

    Code:
    :: x86? BEGIN
    Set xOS=x64& If "%PROCESSOR_ARCHITECTURE%"=="x86" (
    If Not Defined PROCESSOR_ARCHITEW6432 Set xOS=x86
    )
    Echo OS - %xOS%
    If "%xOS%"=="x86" (
      goto x86Windows
    ) Else (
      goto x64Windows
    )
    :: x86? END
    
    GOTO START_POINT
    :: Source Directories Structure BEGIN
    
    Note: Characters "- ", before these lines, mean - "not for x86 Windows".
    
    
    - C\Program Files\Common Files\Avid\Audio\Plug-Ins\Neural DSP
    - C\Program Files\Common Files\VST3\Neural DSP
    - C\Program Files\VSTPlugins\Neural DSP
    C\ProgramData\Neural DSP
    
    
    
    :: Source Directories Structure END
    :START_POINT
    
    :x64Windows
    :: x64 Windows BEGIN
    
    
    cmd /c mkdir "%COMMONPROGRAMFILES%\Avid\Audio\Plug-Ins"
    cmd /c mklink /j "%COMMONPROGRAMFILES%\Avid\Audio\Plug-Ins\Neural DSP" "%~dp0C\Program Files\Common Files\Avid\Audio\Plug-Ins\Neural DSP"
    cmd /c mkdir "%COMMONPROGRAMFILES%\VST3"
    cmd /c mklink /j "%COMMONPROGRAMFILES%\VST3\Neural DSP" "%~dp0C\Program Files\Common Files\VST3\Neural DSP"
    cmd /c mkdir "%PROGRAMFILES%\VSTPlugins"
    cmd /c mklink /j "%PROGRAMFILES%\VSTPlugins\Neural DSP" "%~dp0C\Program Files\VSTPlugins\Neural DSP"
    cmd /c mklink /j "%PROGRAMDATA%\Neural DSP" "%~dp0C\ProgramData\Neural DSP"
    cmd /c mklink /j "%PROGRAMFILES%\Neural DSP" "%~dp0C\Program Files\Neural DSP"
    
    
    CD /d "%~dp0"
    :: [[[OPTIONAL: IT IS A PLACE FOR ADDITIONAL x64 Windows COMMANDS]]]
    
    :: x64 Windows END
    goto OUT
    
    :x86Windows
    :: x86 Windows BEGIN
    
    
    cmd /c mklink /j "%PROGRAMDATA%\Neural DSP" "%~dp0C\ProgramData\Neural DSP"
    
    
    CD /d "%~dp0"
    :: [[[OPTIONAL: IT IS A PLACE FOR ADDITIONAL x86 Windows COMMANDS]]]
    
    :: x86 Windows END
    goto OUT
    
    :OUT
    PAUSE
    EXIT
     
  12. Xupito

    Xupito Audiosexual

    Joined:
    Jan 21, 2012
    Messages:
    6,956
    Likes Received:
    3,830
    Location:
    Europe
    Ok. So the thing is there's both 32 and 64 bit versions of both vst and vst3. At least, there can be. I understand your Windows is 64 bit. So a couple of things that can be the problem:

    1. Your
    "C:\Program Files (x86)\VSTPlugins" folder in your disk is "%PROGRAMFILES(X86)%\VstPlugins"
    And similarly:
    "C:\Program Files (x86)\Common Files\VST3" is "%COMMONPROGRAMFILES(X86)%\VstPlugins"

    I know. This can be mind-fucking. Those %PROGRAMFILES% are variables that avoid problems when you don't use an English language Windows (the keyboard is independent).

    Since you're doing this only for you, you can use the normal paths.


    2. Because your Windows is 64 bit, the Windows 32 bit section ( :x86Windows ) doesn't execute, which is this line
    Code:
    cmd /c mklink /j "%PROGRAMDATA%\Neural DSP" "%~dp0C\ProgramData\Neural DSP"
    The programdata folder doesn't care about 32 or 64 bits so this is the first candidate of a problem. Because it should be created no matter what version of plugin you're installing.
    Cheers ;)
     
    Last edited: May 24, 2022
  13. chumbo

    chumbo Ultrasonic

    Joined:
    Mar 2, 2017
    Messages:
    124
    Likes Received:
    30
    Yes! I finally managed to do it, thx Xupito :like:

    My recommendation to beginners like me is make use of the Windows Sandbox to fool around and test to see if the outcome is how you want. This way, no risk of messing up. And another beginner tip with I'm sure many might forget, after you have a working cmd file with your own plugin paths, remember to make the same edits in the Deinstaller.cm file as well! (just in case you want to remove the plugins at a later date).

    On a different topic...anybody know why I'm not getting email notifications for new messages or posts in followed threads? I have the notifications settings on so...:dunno:
     
  14. chumbo

    chumbo Ultrasonic

    Joined:
    Mar 2, 2017
    Messages:
    124
    Likes Received:
    30
    Strange...I got excited too soon. It worked in the Sandbox but doesn't work in Windows. Or more precisely, it did create some links - the vst x64, not the vst3 - but the vst x64 are not visible to Reaper? Or to be more precise, in the Sandbox, it scans them but then I can't load them as they don't appear in the list of plugins and in Windows, they are not even scanned, as if they didn't exist!

    This Symlink/No Install is not for me I'm afraid. Seems very iffy & problematic.
    Too bad, I liked the idea....
     
  15. Xupito

    Xupito Audiosexual

    Joined:
    Jan 21, 2012
    Messages:
    6,956
    Likes Received:
    3,830
    Location:
    Europe
    Never tried it some Sandbox environment.

    And yes, they're not for everyone. I started using versions made by others and eventually made my own. But they're tricky and because of work/geekiness I'm very experienced both in Windows shit and symlinks.
     
  16. stopped

    stopped Producer

    Joined:
    Mar 22, 2016
    Messages:
    339
    Likes Received:
    104
    I installed a bunch of symlink stuff a few years ago thinking I'd save some time installing and ended up regretting it. It was 50x more of a pain in the ass to update everything on new versions than it would've been otherwise. I can understand if people have strange setups they want to support (like xupito) but would recommend most people not bother with these releases
     
  17. Xupito

    Xupito Audiosexual

    Joined:
    Jan 21, 2012
    Messages:
    6,956
    Likes Received:
    3,830
    Location:
    Europe
    Well, it's not like a have a complex setup. It's more that you need some Windows experience and with symlinks in particular. So again, steep initial learning curve not for everyone, specially if you only want to install a couple. And I'd say several of the ones released in warez sites are half-wrong and can need fixes in several situations (typical one: non English Windows)

    If you get used to them the advantages are huge. I mean, all my DAW/VST stuff I can install or uninstall in a matter of 2 seconds. From a different partition even, so no matter if I backup/reinstall Windows. You can also redirect any kind of personal preset/project to the folder you want.

    There's also even advantages in many updates when you know how to create your own. Like all the new Toontrack stuff. But that's another beast.
     
    Last edited: May 27, 2022
Loading...
Similar Threads - Symlink installer walkthrough Forum Date
r2r waves symlinkinstaller not working in studio one Software Jul 22, 2023
Any step by step guide for making Symlink installer? (Personal use!) Software Jan 30, 2020
How to use - NO INSTALL, SymLink Installer Software Dec 14, 2019
Native Instruments - Reaktor 6.1.1 (SymLink Installer) Software Mar 12, 2018
What is up with these new symlink installers? Software Feb 3, 2018
Loading...