You may know that I usually stick to the "preinstalled" version, but for one of the 1.1b6 beta I got excited and used the installer. Now I can't find an uninstaller anywhere. I downloaded an installer from the Uhbik site, however, it is completely unaware of any previous install.
So, all I'd like to do is clean up the old installation, which was a beta anyway, and update to the full release of 1.1.
Mostly I wanted to check out the G presets, I've played around with it a bit, but I'd really like to see what its capable of. There were a few minor visual glitches in the beta, but they did not affect usability in any way (I'm sure you've fixed them all by now). All the plugins have been rock solid, even though they were technically betas.
Er, so I guess all I need is what files are installed other than in the Program Files x86/u-he and VirtualStore so I can remove them.
Question about installer
- KVRAF
- 1736 posts since 19 May, 2006 from Nomadic (Chicago and San Francisco mostly)
noise and beats: Negutyv Xeiro do people actually click these?
gearlust: Roland JP-8000, too much/not enough eurorack
machinecode by: u-he, Bitwig, Fabfilter, NI, et al
gearlust: Roland JP-8000, too much/not enough eurorack
machinecode by: u-he, Bitwig, Fabfilter, NI, et al
- KVRAF
- 4141 posts since 11 Aug, 2006 from Texas
There really are only 2 directories where files are placed.
1. c:\program files\u-he\plugin_name -> This is the data file directory which has now been replaced by the newer plugin.data/ directory format. This is where your presets are stored.
2. c:\program files\vstplugins -> This is the directory where the actual plugin.dll program is placed. You may have changed this when installing your plugins. Keep in mind VST2 doesn't have the ability to group several plugins into one file like Audio Units do. This means you'll have separate .dll files for every UHBIK installed with names like Uhbik-A.dll, Uhbik-G.dll, Runciter.dll, etc.
1. c:\program files\u-he\plugin_name -> This is the data file directory which has now been replaced by the newer plugin.data/ directory format. This is where your presets are stored.
2. c:\program files\vstplugins -> This is the directory where the actual plugin.dll program is placed. You may have changed this when installing your plugins. Keep in mind VST2 doesn't have the ability to group several plugins into one file like Audio Units do. This means you'll have separate .dll files for every UHBIK installed with names like Uhbik-A.dll, Uhbik-G.dll, Runciter.dll, etc.
- KVRAF
- Topic Starter
- 1736 posts since 19 May, 2006 from Nomadic (Chicago and San Francisco mostly)
Alright cool. Just wanted to make sure I didn't miss something or break anything.bmrzycki wrote:There really are only 2 directories where files are placed.
Removed the Program Files/u-he folder and dropped the pre-installed uhbik archive into my vst folder, overwriting the betas I had. Tested ACE and Runciter right off. Everything looks and sounds great and I can also see G's new presets. Yay!
noise and beats: Negutyv Xeiro do people actually click these?
gearlust: Roland JP-8000, too much/not enough eurorack
machinecode by: u-he, Bitwig, Fabfilter, NI, et al
gearlust: Roland JP-8000, too much/not enough eurorack
machinecode by: u-he, Bitwig, Fabfilter, NI, et al
- u-he
- 30216 posts since 8 Aug, 2002 from Berlin
Un-Installers are typically used to clean the Registry from application-specific entires. My stuff doesn't use the Registry, so all you need to do is delete the files.
Btw. once you have the pre-installed version working you can always use the installer for updates. That way you can be sure that no files are accidentally deleted.
I would only post the pre-installed version with the new scheme, but I'm afraid that people lose their presets and stuff when they update. Hence I trust the installer more.
Urs
Btw. once you have the pre-installed version working you can always use the installer for updates. That way you can be sure that no files are accidentally deleted.
I would only post the pre-installed version with the new scheme, but I'm afraid that people lose their presets and stuff when they update. Hence I trust the installer more.
- KVRAF
- Topic Starter
- 1736 posts since 19 May, 2006 from Nomadic (Chicago and San Francisco mostly)
Good to hear.Urs wrote:Un-Installers are typically used to clean the Registry from application-specific entires. My stuff doesn't use the Registry, so all you need to do is delete the files.
Damn Urs I'm always posting about silly installers and stuff. I've probably even asked this same question before. Blarg. I need to be a more useful member of the community. I do think there are some ACE patches of mine floating out there somewhere though
Oh its smart enough to do that? Cool.Urs wrote:Btw. once you have the pre-installed version working you can always use the installer for updates. That way you can be sure that no files are accidentally deleted.
I tracked down my presets and manually copied them over, no biggie. I did notice that the data directory extracted as an encrypted folder for some reason though. I'm pretty sure it was specific to my system though, as I can't imagine how else it would have happened.Urs wrote:I would only post the pre-installed version with the new scheme, but I'm afraid that people lose their presets and stuff when they update. Hence I trust the installer more.
noise and beats: Negutyv Xeiro do people actually click these?
gearlust: Roland JP-8000, too much/not enough eurorack
machinecode by: u-he, Bitwig, Fabfilter, NI, et al
gearlust: Roland JP-8000, too much/not enough eurorack
machinecode by: u-he, Bitwig, Fabfilter, NI, et al
