How to avoid users having to unpack an hr1 file on first run of an instrument
-
@pcs800 said in How to avoid users having to unpack an hr1 file on first run of an instrument:
I do not know how to create a script that allows the user to set the samples location.
This is what the hr installer does already.
@pcs800 said in How to avoid users having to unpack an hr1 file on first run of an instrument:
Couldn't I just include this linkwindows file with that path already defined?
I didn't even think of that but yeah, actually I think that would work since it's the same location on both systems. The only issue I see is how do you get it in the app data folder on the user's system because they will have a different username to you. It's possible Innosetup provides a wildcard for the username though, I can't remember, so check the documentation.
-
@d-healey inno actually does provide a wildcard for that. I think it's something like {userprof}\etc\etc
So, where exactly do I put this linkwindows file? -
@pcs800 said in How to avoid users having to unpack an hr1 file on first run of an instrument:
where exactly do I put this linkwindows file?
-
@d-healey So I have inno put it in {userProf}\AppData\Roaming\company name\Product name\LinkWindows ?
-
@pcs800 said in How to avoid users having to unpack an hr1 file on first run of an instrument:
Couldn't I just include this linkwindows file with that path already defined?
I made a post about that a long time ago:
https://forum.hise.audio/topic/7832/automatic-installer-for-windows-inno-setup-script
-
@pcs800 I think so, try it and report back
-
@d-healey I just did it manually (not in inno) and it worked.
I put the LinkWindows file at C:\Users\pcs80\AppData\Roaming\company name\product name\LinkWindows
Which would be {userProf}\AppData\company name\product name\LinkWindowsInside the file I specified the location of the samples, and it worked.