Korg Forums

I can't seem to get both EXs running without mishaps in 1.3. If I leave just 1 EXs loaded all is very good and back to normal. Go figure...

Hi Eric,
There is also another possibility to factor. How long have you had the OASYS and how many hours do you use it on an average? With time and extended periods of use, a computer motherboard will eventually start acting up. Random occurrences are usually a sign of impending hardward failure.

Could you please tell me roughly the steps that I could try to do to attempt to simulate this error? I can keep trying some permutation/combinations for the next two days and see if I can replicate a freeze with OS1.3.0 with your current senario.

Elvis Dowson

Lou wrote:I can't seem to get both EXs running without mishaps in 1.3. If I leave just 1 EXs loaded all is very good and back to normal. Go figure...

Hi Lou:

Sorry to hear of the continued troubles.

It seems that you haven't tried removing the second memory stick and going back to the Factory configuration, right?

Your comment here seems to point to the possibility that your additional memory is related to the problems. It seems the best thing to try would be to go back to Factory configuration and try things for a while. Did you ever give us the brand/specs of the memory you bought? I haven't done a search to look for that info...

Going back to stock 1 GB memory and trying to work with just EXs-1 loaded, and then just EXs-2 would be the most logical test scenario I can think of.

Dan - agreed?

Jerry

Hi Jerry

No, I haven't removed the added on stick. But I have gone back to loading only 1 Ex and the Oasys is functioning as it's suppose to. Maybe as Eric said, the O would like to have a matched pair?
Both EXs loaded fine in 123. I guess 1.3 has a lot more added, so maybe now it's showing up in the added ram stick?
Thanks Jerry, I'll give your suggestion a try.

FWIW ... the motherboard used by the Oasys doesn't require matched memory as some others do. I've checked some of the problems described by people and my O behaves fine. However I don't have EXs1 or EXs2 loaded currently and also I sourced my RAM from crucial.com using their wizard that determines exactly the right memory required for a named system or motherboard.

Daz.

Daz wrote:FWIW ... the motherboard used by the Oasys doesn't require matched memory as some others do. I've checked some of the problems described by people and my O behaves fine. However I don't have EXs1 or EXs2 loaded currently and also I sourced my RAM from crucial.com using their wizard that determines exactly the right memory required for a named system or motherboard.

Daz.

Daz, what is the right memory required by asys's MOBO (what is the ref of the MOBO ?) ?

I also had the "Error Code 2" from 1.1 to 1.2 and 1.2 to 1.3 . Now it works after 15 tries but it seems I have the same problem with my OASYS and I'm very interested to know what is the real solution.

Hi Daz

FWIW This is the stick I purchased from NewEgg, I thought it was a Kingston but I was incorrect:

G.SKILL Value
1GB 184-Pin DDR SDRAM DDR 400 (PC 3200) Desktop Memory -

 Item#:N82E16820231036

All was fine with it under 123. Once I updated to 1.3 is when the problems began.

sebbytriton wrote: Daz, what is the right memory required by asys's MOBO (what is the ref of the MOBO ?) ?

The MOBO is an AOpen MX4GVR and this is the memory that Crucial recommends for that :

http://www.crucial.com/store/listparts. ... del=MX4GVR

... I've used Crucial for years, it's a little more expensive than some sources but their memory has always worked well for me in Macs and PCs alike.

I also had the "Error Code 2" from 1.1 to 1.2 and 1.2 to 1.3 . Now it works after 15 tries but it seems I have the same problem with my OASYS and I'm very interested to know what is the real solution.

That old chestnut ... sorry to hear you're still with that. Personally I think that error is more likely hard disk related. The error means that a file can't be copied and I personally suspect that the reason for that is one of the system files on your harddisk has somehow got the wrong permission/access flags set on it, and that is causing the file copy to fail. My recommendation would be for Korg to make a bootable Linux disk image that mounts the Oasys HD's various partitions (as per the OS updater script) and then run fsck on those partitions and report the results, either to the display or by mounting a USB storage device and piping the output of fsck to a file on the USB device. The existing OS updater CD image only needs a few tweaks to perform this function.

Daz.

Lou wrote:
G.SKILL Value
1GB 184-Pin DDR SDRAM DDR 400 (PC 3200) Desktop Memory -

 Item#:N82E16820231036

In the Parameter Guide Korg quote two options for memory :

184‐pin DIMM DDR SDRAM, unbuffered, non‐ECC
PC2700 (DDR333 CL2.5)
PC3200 (DDR400 CL3)

Crucial took me down the PC2700 route and the memory you have is PC3200. So yours is the right spec., but I wonder if the difference might account for our different experiences.

What memory spec are other folks who are having problems using ?

Maybe vEddy or one of the other more hardware knowledgeable guys has a thought on that ... I am a software guy, so not really fully qualified to comment on this stuff in detail.

Daz.

Daz wrote:

I also had the "Error Code 2" from 1.1 to 1.2 and 1.2 to 1.3 . Now it works after 15 tries but it seems I have the same problem with my OASYS and I'm very interested to know what is the real solution.

That old chestnut ... sorry to hear you're still with that. Personally I think that error is more likely hard disk related. The error means that a file can't be copied and I personally suspect that the reason for that is one of the system files on your harddisk has somehow got the wrong permission/access flags set on it, and that is causing the file copy to fail. My recommendation would be for Korg to make a bootable Linux disk image that mounts the Oasys HD's various partitions (as per the OS updater script) and then run fsck on those partitions and report the results, either to the display or by mounting a USB storage device and piping the output of fsck to a file on the USB device. The existing OS updater CD image only needs a few tweaks to perform this function.

Daz.

Daz,

When I tried many times OS Update 1.2 to 1.3, it failed ! (Error code 2)
After that, I try many restoration --> it also failed ! (FATAL Error cannot install files)

With more patience, the restoration works !
After, then I try update from 1.1 to 1.3 and it failed 2/3 times.
I restart later and it works !! Now I'm in 1.3 (with some freeze using help).

I speak you about that because the situation seems to be very random !!
And I d'ont understand why you think it is a problem of Hard disk.
If a file cannot be copied, we can retry 1000 times and the file will never be copied, isn't it ?

PC2700 route and the memory you have is PC3200

AH HA!!! Could this be the problem? When I check tomorrow (maybe Tuesday....My wife wants to go to Niagara Falls... ) I might be able to see whether my factory ram is 2700. I believe my Kingston is 3200.

Jerry, Dan, anyone else, is the factory ram PC2700 or 3200? Daz, could this be part of the mismatch? Just trying to help search for answers.

All you guys who haven't done the ram test (pulling one of them out) but are still having issues, why aren't you trying to do this? So far, my system is 100 % stable now. So, just do it....LOL so we can confirm that this ram issue is possibly one of the culprits.

Cheers everyone,
Eric

Hi Eric

As of yet I haven't pulled the extra stick out. I can tell you though that just loading 1 of the EXs has remove ALL issues. (ALL)

I guess next is to confirm If and what kind of ram should be added.

sebbytriton wrote: When I tried many times OS Update 1.2 to 1.3, it failed ! (Error code 2)

I'm sorry that you encountered difficulties.
This error message indicates either a bad CD burn, or a connected USB device.

sebbytriton wrote:After that, I try many restoration --> it also failed ! (FATAL Error cannot install files)

This will occur if you downgrade without formatting. (Downgrading requires formatting, which is why it's not recommended!)

Best regards,

- Dan

danatkorg wrote:

sebbytriton wrote: When I tried many times OS Update 1.2 to 1.3, it failed ! (Error code 2)

I'm sorry that you encountered difficulties.
This error message indicates either a bad CD burn, or a connected USB device.

Dan, No USB device connected !
The CD was a verbatim burnt at the lowest speed.
Daz, suppose it is a problem accessing the hard disk with file/folder protected.

sebbytriton wrote:After that, I try many restoration --> it also failed ! (FATAL Error cannot install files)

This will occur if you downgrade without formatting. (Downgrading requires formatting, which is why it's not recommended!)

- Dan

Dan, First I try the restoration without formatting (1.1), it failed !!!
After that In tried the restoration with formatting (1.1) and it fail many times !!!
I tried the restoration with formatting with 1.0 (Factory CD) and if failed
(Always the same message "FATAL..........").
After many tries, it finally works with formatting in 1.0, I don't know why.
Then after I do 1.1 restoration (without formatting ), it didn't work the first times but after 1/2 tries.

Even with original master CD, there is random phenomenous, isn't ?

You know the suite, I'm in 1.3 but had much pain.
I scared for the futur minor update (1.3.1 I suppose).

Best regards
sebby

Is it just possible that OS 1.3 is fussy about the memory due to the fact that you have changed the compression type in order to give you better use of the RAM.
This was introduced with version 1.3, so all could be well with an expanded 2gb on 1.2.3, but maybe a problem with 1.3.

Could be Lou's problem?