ARE MY 64MB RAM IS DESTROYED?

AVI6520 · Post by **AVI6520** » Sun Jan 06, 2008 6:44 pm

Rob Sherratt wrote:
AVI6520 wrote:My problem is with the RAM and not with the ROM [-SSD]. I do not know how to do the NAND Format, and if it is not for the RAM, and work only for the ROM [-SSD] it will not help.
Hi AVI,

With respect, you have not understood my earlier post where I explained how SSD User PCM memory (in FLASH EEPROM) and User PCM RAM memory are inter-related. Because data stored in RAM memory disappears when you turn power off, the way the Pa800 and Pa2x work is that User PCM samples are saved in the SSD FLASH EEPROM memory when you do a "Write Sample" from the page menu.

Then when you turn the power off and back on again, the contents of the SSD User PCM memory (in FLASH EEPROM) are loaded by the Pa800 operating system back into RAM again, and are played back from RAM.

The reason that User PCM samples can not be played back from FLASH EEPROM memory is that there is no FLASH EEPROM device that is fast enough for the required PCM playback sample rate, whereas RAM is sufficiently fast.

I took trouble to explain this because if SSD User PCM (FLASH EEPROM) memory is corrupted, then this corruption will also be copied into RAM.

I'm sure that your keyboard fault is because SSD FLASH EEPROM contents have become corrupted and then, when you turn the keyboard on, the corrupted portion of SSD memory is copied into USER PCM RAM which also prevents you from using the RAM memory because the OS mistakenly thinks it is full.

Best regards,
Rob

HI-

LET'S start from the beginning,

[Maybe I did not understand you well... [English...]]

THE 256 mb is OK [20 MB SSD of course, are ok to].It be seen in "MEDIA"-Device info.. I can save end erase to the SSD-U and can see the device info of the SSD-U and SSD-S, -can see how mach still free... [MB..]

BUT------- [FOR THE RAM NOT ROM...]

In -SOUND
-RECORD
-Sampling Info-
In the -"Available Memory" =
"RAM Bank-" The line is empty.
"Mono time-0 s."
"Bytes-0" -----That means- or that the RAM full- or damaged!

And that data always like that!
[os... res... 1.01 1.5 1.51... pcm autoloud off....].

I can record wav and save it [EXPORT to usb OR ssd-u], I can not WRITE it -the message say- that "there is not enough RAM for PCM".
[AND i see that there is in the ROM! [SSD]]

And if I open=SOUND-MENU-BASIC-OSC Basic-Rom\Ram there… there is no access to it. [there is no option to choose the RAM instead of the ROM].

What didn't I explain right?

No problem- just teach me,

Happy with your responses

AVI.

sandy39 · Post by **sandy39** » Mon Jan 07, 2008 5:07 pm

Hello everyone...

Same problem has popped up with me also... I tried to write one .wav file but it says "pcm memory full"

In -SOUND > RECORD > Sampling Info-
In the -"Available Memory" -there is nothing!
"RAM Bank-" is just empty!
"Mono time-0 s."
"Bytes-0"

I deleted about 10 mb of data but still when I try to write a sample of 150 Kb it says "pcm memory full". I deleted the data from sampling screen > touch 'empty' > select the sample > page menu > delete > select the first option > okay

Also, I can load the file but cannot hear it UNLESS I timeslice it... and the next step is to save it but it says "pcm memory full"

Please guide me what to do? Everything was so well suddenly my machine is going crazy.... please help !!

Thanks & Regards

SP

Rob Sherratt · Post by **Rob Sherratt** » Mon Jan 07, 2008 6:04 pm

Hi Sandy,

Is it possible you Loaded a .SET file recently? Was your GLOBAL memory locked or not? Could you Open any .SET files you loaded recently and tell me if there was a GLOBAL directory inside? If so, where did you get the .SET file from?

In my opinion, it's most likely that a software fault has caused or allowed the User SSD memory to become badly formatted (like a Hard Disk crash where you lose all available sectors because the sector directory has become corrupted). I think the failure is triggered when you load a .SET file from another source containing an incompatible GLOBAL folder. In this sense, I confirm that the GLOBAL folder in a .SET file can act like a virus that can incapacitate your keyboard. For example, I was able to brick my Pa1x by loading a .SET file from a Pa800 that contained a GLOBAL directory. However I was also able to unbrick my Pa1x by reloading the OS and Musical Resources. A similar approach does not fix the problem on the Pa800 or the Pa2x.

Anyway, your RAM is still working OK despite the message on the user interface. For example Avi can still record a new sample (into RAM) but can not save it. The OS may be saying no bytes are available because the User SSD contains badly formatted sectors, which leads the OS to believe there is no sample space available for saving the sample data.

I was informed in a PM that Korg are investigating this and will reply as soon as they can. I do not know how to advise you to "fix" the problem. I have been trying to help Avi offline to try to diagnose the problem and come up with a workaround. Would you be willing to chat via email and see if we have more success?

Meanwhile - please do not use Sample Edit mode on a Pa800 or Pa2x until Korg have advised us what to do about this problem

Also - please do not attempt to use the NAND format procedure that is described elsewhere in this forum because this may invalidate your warranty.

Best regards,
Rob

sandy39 · Post by **sandy39** » Tue Jan 08, 2008 5:26 am

Thanks for your concern Rob,

NO ! I have always avoided .set files. There is only one .set file that I had loaded on my pa800 some 3 months back and that was of Shahids desi kit - this desi kit I have checked fortunately contains - MULTISMP, PCM & SOUND Folders only & DOES NOT contain any Global or Song book folder secondly never used that kit or never attempted to load any files that use that kit. Yesterday I have deleted that set files one by one from sampling screen as mentioned above in order to create some available space.

I had been using my pa800 all along and never faced any problem. Earlier & recently, I have loaded .wav files - which are playing perfectly in variations [it means they are not corrupt] & I don't think .wav files can be of any problem to operating system [provided they are not corrupt].

Yes! Whatever .set files are freely distributed over forum - I do download but remain upto my PC only & never[except Shahid's desi kit] loaded on my pa800.

As far as my Global memory is concerned right now I am in office and cannot say exactly but shall confirm in the evening.

What about my data Rob ? Will I be able to save it and use it again ?

Yes, sure I would love to solve this problem... my email id is:
ssmickey@rediffmail.com

Some 4 or 5 days back, there was a significant automatic decrease in volume too...

Awaiting your response...

SP

BasariStudios · Post by **BasariStudios** » Tue Jan 08, 2008 9:09 am

The Desi or Bhangra kit you are using now is the one i created and its
free from any additional folders, all you have is PCG, PCM i think, unless
i forgot something.

sandy39 · Post by **sandy39** » Tue Jan 08, 2008 10:49 am

Yes... I know Nedim...

sandy39 · Post by **sandy39** » Tue Jan 08, 2008 12:03 pm

Hello Rob,

Under the circumstances, I was forced to reload the fresh operating system 1.51 and after loading... when I saw the sampling info... it said...

In the -"Available Memory" -there is nothing!
"RAM Bank-" is just empty!
"Mono time-0 s."
"Bytes-0"

I reloaded the resources 1.50 and again checked the sampling info... it said...

In the -"Available Memory" -there is nothing!
"RAM Bank-" is just empty!
"Mono time-0 s."
"Bytes-0"

At this stage I had FULL 64 MB space but it refused to write 150 KB of data & said as above... it means that something somewhere is wrong at KORG's end be it a software or hardware problem.

Thereafter I copied my FULL backup into PA800 which got loaded and played well. I played my styles that had user samples. I checked sampling info again. It said the same:

In the -"Available Memory" -there is nothing!
"RAM Bank-" is just empty!
"Mono time-0 s."
"Bytes-0"

Now last thing, when I tried to load back a sample of 150 kb it loads it but refuses to write the same saying "PCM memory full".

so the thing is that now I cannot create any fresh song from a 'Milti Thousand $ machine'.

Let's see... machine is under manufacturers warranty...

Regards

SP

Rob Sherratt · Post by **Rob Sherratt** » Tue Jan 08, 2008 12:14 pm

Hello Sandy,

To restore your Pa800 to full health you should do the same as Avi, and load the .PKG file from the CD that was supplied with your machine. This solves the problem.

It appears that to date you have only re-loaded the OS1.51 and Musical resources 1.5 that were posted by Korg on www.korgpa.com.

According to the testing that AVi has done, OS1.51 has a serious fault in it which corrupts the SSD memory and consequently the Sample RAM after you edit a sample and do a "Write Sample". Also, reloading OS1.51 does not clear the SSD memory corruption after it has happened.

I think it would be wise not to use OS1.51 until we hear more about this from Korg.

Best regards,
Rob

sandy39 · Post by **sandy39** » Tue Jan 08, 2008 2:04 pm

Hello Rob,

With my machine, the CD that I have received, contains the following files:

(1). Pa800_os_v102.pkg which is of 4.85 MB

(2). Pa800_os_res_v102.pkg WHICH IS OF 126 MB

Both are .pkg files and the resource one is of 126 MB... is it okay??? As resource file at present is a Pa800_res_v150.BKP and is of 7.48MB only.

Please clarify the following:

1. Should I load both the OS (1) and Resource (2) .PKG files???

2. What about my data backup which is on 1.51 version, will I be able to use it on version 1.02 ???

Kindly be patient Rob and give me the instructions clearly. I do not know what Avi has done...

Thanks & Regards

SP

Rob Sherratt · Post by **Rob Sherratt** » Tue Jan 08, 2008 2:15 pm

Hello Sandy,

If you back up only your User Sounds and Styles etc into a .SET file with OS1.51 then you will definitely be able to reload them once the OS problems are fixed. I do not know if the .SET file will work with OS1.02 - it will do no harm to try. The worst that can happen is that the Styles may not sound right because they might index to the wrong Sounds in OS1.02.

You should load Pa800_os_v102.pkg first. Use a clean USB memory stick, nothing else on it apart from this OS file. Then cycle power and load Pa800_os_res_v102.pkg. Again use a clean USB memory stick, nothing else on it apart from this resources file. Hold down the INTRO1 button while you turn power on in both cases.

Then before loading any .SET files, try to edit and save a .WAV file as a new sample, then check user PCM memory etc. I think your keyboard will work OK. At least Avi's did. I have a Pa1x pro so can't test this myself.

Avi says that if you reload OS1.51 and Musical resources 1.5, then the problem with corruption of the SSD User memory and user RAM memory immediately returns - even before loading .SET files or editing a .WAV file etc.

Best regards,
Rob

BasariStudios · Post by **BasariStudios** » Tue Jan 08, 2008 2:24 pm

That is true Rb but there is another problem, OS 1.50 is even worst
especially with single samples and DRUM KITS, thats why 1.51 came out.

Rob Sherratt · Post by **Rob Sherratt** » Tue Jan 08, 2008 2:29 pm

Nedim wrote:That is true Rb but there is another problem, OS 1.50 is even worst
especially with single samples and DRUM KITS, thats why 1.51 came out.

That's why I'm saying revert to OS1.02 ... it seems to be stable even if there is no Guitar Mode.

sandy39 · Post by **sandy39** » Tue Jan 08, 2008 2:34 pm

Thanks for your reply Rob... it is really showing some light in darkness...

Pa800_os_res_v102.pkg IS OF 126 MB... 126 MB ROb... is it okay??

As the resource file at present is a Pa800_res_v150.BKP and is of 7.48MB only.

If you say load 'Pa800_os_res_v102.pkg', i'll bloody load it

I want my .wav files to be there on pa800 otherwise what's the use of Pa800 !!!

Regards

SP

Rob Sherratt · Post by **Rob Sherratt** » Tue Jan 08, 2008 3:45 pm

Hi Sandy,

You can't use your .wav files under OS1.51, right? So, what do you have to lose by regressing to an earlier OS?

I can't promise that all the work you've done under OS1.51 will be compatible with OS1.02. There will be some things that sound OK and some things that won't. But hang onto the .SET file you created, store on a PC, and don't change it. When (hopefully) a new version of the OS is made available, you will be able to relad the .SET file and everything will work again.

Anyway assuming you are going ahead ...

Please save all your current work into a .SET file. (only save SAMPLE, SOUND, MULTISAMPLE and STYLE). Do not save Media/ GLOBAL. Then load both OS1.02 and then the resources 1.02 as already discussed. This will clear out the whole of SSD memory and reload it from scratch.

I think the reason that the res file for v1.50 is so much smaller than the res file for v1.02 is because the v1.50 is loaded incrementally on top of the v1.02 resources. Whereas the v.102 is a stand alone load from scratch which is what we need. I have no "insider" information from Korg about any of this, but the normal approach when any software system fails is to restore service by loading known previously working OS and data. You have to wipe the previous system image by loading a "stand alone" image and not just reload an incremental backup. I believe that the .PKG files supplied by Korg on the backup CD are a "stand alone" image that reload system and resource data from scratch. Whereas the RES1.50 file on Korg's web site is probably just an incremental load that will not clean out corrupted data.

So go ahead and get that bloody keyboard working for you again

Best regards,
Rob

sandy39 · Post by **sandy39** » Tue Jan 08, 2008 4:51 pm

Thanks for all the clarification, time and concern Rob...

I have written an email to Audioplus, mumbai. My instrument in under KORG's warranty... Warranty is of limited period... the question is "Why is my instrument not running well, as earlier, on latest operating system??" It is running well for many of you out there.... why NOT for me???

I'll wait for an official reply Rob... I have spent lot of money.. I want a proper machine... simple....

Regards

SP