Page 2 of 2

Re: Response much appreciated!!!

Posted: Sat Feb 11, 2012 6:29 am
by SeedyLee
seapea wrote:
DrpC wrote: I believe someone on the forum came up with a way to reset everything to factory setting with a couple of extra steps
I think this is what you are after.
This will only reset the program banks and global settings back to factory defaults. It will not remove the EXs PCM data or extra SGX-1 piano types from the system.

Posted: Sun Feb 12, 2012 6:25 pm
by Scott
danatkorg wrote:Re uninstalling an EXs: currently, there is no way to do so. However, we are aware that this is a desirable feature. That's all that I can say for now.
Wow, I'm glad I found this out before installing the demo of the new piano! I'll wait.

If it's going to take some time to create a solution for this problem, I'd like to suggest that the installation instructions for new EXs inform people that, for now, installing them will permanently take up x amount of disk space, even if the user decides not to keep them. This could be a rather nasty surprise to learn about after-the-fact, especially if someone may be intending to create other large samples of their own.

Since the only "solution" is to reformat the drive and reinstall from DVD (correct?), I assume that you can at least back up your custom programs (and other custom samples) before formatting the drive, then load them back in after you put everything back to factory-fresh, and all of your custom stuff will work fine, even though you don't restore the (unused) EX data that was in the machine when you backed up, right?

As for the implementation of this "desirable feature," I would guess it might come along with the some-day editor...!

Posted: Sun Feb 12, 2012 7:00 pm
by mm-pro
I vote for both...the software fix until the update comes along.

Regards,

MM
burningbusch wrote:Seems Korg could approach this one of two ways. The easy way would be to create an uninstall script just like the install script that comes with the EXs. This could be a simple download. The slicker solution would be to have an uninstall button in GLOBAL-OPTIONS INFO. That would require an OS update.

Busch.

Posted: Wed Feb 15, 2012 1:55 pm
by devix
and if you simply delete the directory from HD?????

Posted: Wed Feb 15, 2012 4:43 pm
by Dniss
Scott wrote:Wow, I'm glad I found this out before installing the demo of the new piano! I'll wait.
So do I!

With the Karo lib around the corner, I don't want to run out of space or have to format the drive and re-install everything.

Posted: Wed Feb 15, 2012 4:52 pm
by GregC
thinking long term, the issue is what pro level 128 gig SSD is available for the Kronos, will Korg honor the warranty when SSD is replaced.

Posted: Wed Feb 15, 2012 5:22 pm
by LTEDT
Hi All,

I had installed the EXs12(demo) on my K. For some weird reason, IIRC Austrian Dark Grand 1 and 2 showed a black color piano instead of the blue one. I found out that the two austrian piano types showed a black piano. So i tried to re-install EXs12 on my K thinking it would make everything alright. When i tried to install it again, a box appeared telling me that EXs12 would be replaced (since it was already installed). i proceeded and half way through, the keyboard froze. So did my heart!!!

I turned it off and waited for 20secs. turned it back on without any problem. But the Austrian piano would play at only low velocity. I figured that it was due to the freeze. Anyway, i just tried loading my PCG to see if it would make any difference and then the keyboard froze (when it was writing to the bank). I switched it off and then back on. But it never booted fully again.

I successfully reformatted and restored the keyboard from the factory DVD. It was a bit long, but glad that it worked. I was planning to do this to get some space back anyways, but ended up doing it sooner than i had planned.

rgds,

Posted: Wed Feb 15, 2012 5:43 pm
by CaptLego
GregC wrote:thinking long term, the issue is what pro level 128 gig SSD is available for the Kronos, will Korg honor the warranty when SSD is replaced.
+1

As more and more sound libraries become available, this will become important.

I'm hoping that Korg will continue to take my $ for the next ten years as I purchase sound libraries, new synth engines, SSD upgrades, processor and memory upgrades, maybe a USB MIDI foot switch / pedal board, etc

Posted: Wed Feb 15, 2012 5:57 pm
by Oasyianv
burningbusch wrote: The slicker solution would be to have an uninstall button in GLOBAL-OPTIONS INFO.
This :)

Posted: Wed Feb 15, 2012 6:06 pm
by GregC
CaptLego wrote:
GregC wrote:thinking long term, the issue is what pro level 128 gig SSD is available for the Kronos, will Korg honor the warranty when SSD is replaced.
+1

As more and more sound libraries become available, this will become important.

I'm hoping that Korg will continue to take my $ for the next ten years as I purchase sound libraries, new synth engines, SSD upgrades, processor and memory upgrades, maybe a USB MIDI foot switch / pedal board, etc
Sure thing, I bet that many of the KARO EXs libs are a large size. Plus I would prefer all my sounds to always be on-board. I would prefer not to fuss with a load/unload process ( which does not exist for the new libs) to preserve storage.

Posted: Fri May 08, 2015 2:20 am
by Maralc
Hi All,

Is it still current that an EXs cannot be uninstalled?

Cheers

Posted: Fri May 08, 2015 4:09 am
by Rich Z
Maralc wrote:Hi All,

Is it still current that an EXs cannot be uninstalled?

Cheers
Yeah, I'm just catching up on this little tidbit myself, so I would like to know more about this as well. So what, three years later and this has still not been resolved?

Posted: Fri May 08, 2015 7:27 am
by SanderXpander
Before you get upset, go to Global/Options info, select an EXs and open the Utility menu to find the option "uninstall EXs" exactly where you'd expect it. This is the problem with resurrecting three year old threads.

Posted: Fri May 08, 2015 7:37 am
by Rich Z
SanderXpander wrote:Before you get upset, go to Global/Options info, select an EXs and open the Utility menu to find the option "uninstall EXs" exactly where you'd expect it. This is the problem with resurrecting three year old threads.
Thank you......