Korg Forums

I have Korg PA4x Oriental.

I had installed the 2.0 OS Oriental a couple of months ago and everything was working fine. Today I installed the updated OS 2.01 Oriental - After the keyboard was updated and the OS install was complete, I turned the keyboard off. When I turned the keyboard on, the initial Korg Logo come on, but the keyboard got stuck on Korg Logo - Turned the keyboard off and turned it on again and this time the initial Korg Logo screen came one and then disappeared (blank screen).

I installed the OS a second time and third time - same problem.

Should I revert back to 2.00 and reinstall the 2.01? Why am I having this problem???

Start up time is increased quite significantly following the upgrade, are you sure you are waiting long enough to give the system time to start?

I seem to remember that the first boot after updating was particularly long on my keyboard.

[Start up time is increased quite significantly following the upgrade, are you sure you are waiting long enough to give the system time to start?
]

Several hours and nothing. I have been working on this issue all day - nothing.

Sad that you want to make music, but you have to through these types of glitches over and over again. Last I checked it was 2017 and not 2004 - Come one Korg get it right or some other company will.

I have been using Korg product for many years - started from Korg i30, PA1X, PA800, PA3x and PA4X. I am not new to this product. Ever since the KORGPA website has been changed, support for this product has gone down the drain.[/quote]

armaan , this is a hardware issue (corrupted sys files) and if still under guarantee , visit official cervice center ASAP !

All of Pa4X (or any Pa) users seriously consider , that you must always update your keyboard OS while connected with a UPS.
The most vulnerable point on any computing system is the power instability while writing system files !!!

I had upgraded to 2.01 OS (Oriental). The keyboard froze. Today I reinstalled the 2.0 OS (going backwards) and the problem is now solved.

Wonder what caused the problem in the first place.