I've had a microStation for several months & every so often when editing in the sequencer, the screen freezes with an error message,
after which all buttons & keys give no response.
The screen errors include code line numbers & phrases like:-
e/mmu/malloc.cpp,
dapi/cosglue.cpp
which are clearly technical messages indicating memory corruption, etc.
I tried re-setting factory defaults & it happened again. 5 times in all.
I contacted the supplier & returned the Keyboard.
After 4 weeks it was returned to me, saying that Korg had tested it & everything seems ok. They also reset factory defaults.
This was a week ago & the freeze has happened since.
I've asked for a replacement but they said no, because it might not rectify the problem.
The error occurs during editing, after pressing certain buttons. Sometimes it can be the 'Play' button which causes the error.
I've provided Korg with photos of the screen errors.
Am currently trying to produce more evidence.
Surely if a product is faulty, the buyer has the right to have it fixed or have a replacement?
Regards Mark
microStation Screen Freezes
Moderators: Sharp, X-Trade, Pepperpotty, karmathanever
Sounds normal to me, nothing can be 100% perfect! Just like with a PC it will crash sometimes doing stuff on it.
It happened me few times too, when editing and saving into mS memory and it crashed/freezed with an mem error, even after power off/on, mS stay hanging with mem error and no functioning at all!
I fixed it by Initalization.
OG manual:
Initialization
If operation becomes unstable, you can initialize the
microSTATION as follows.
1. Turn off the microSTATION’s power.
2. While holding down the PLAY/MUTE button and
the function 08 button, turn on the
microSTATION’s power.
The microSTATION will be initialized, and data will
be written to internal memory. While data is being
written, the display will indicate “Initializing...”
When initialization has been completed, you’ll need
to load the preload data from an SD card containing
the data, or dump it from a USB‐connected
computer using microSTATION Editor/Plug‐In
Editor. (“Loading the preloaded data”)
1) These crashes/glitches is caused by memory(buffer) overload/flow/shortage by giving too fast/many/combination etc. commands to mS!
Learn what sequence of commands cause the crashes and don't do/use it the same next time!
3)That's why you'll need always to backup the (all) data regulary to the SD card before editing important stuff!
4)Updating your mS Operating System (O.S.) to V1.0.1.
You gotto learn the way of the machine!
It happened me few times too, when editing and saving into mS memory and it crashed/freezed with an mem error, even after power off/on, mS stay hanging with mem error and no functioning at all!
I fixed it by Initalization.
OG manual:
Initialization
If operation becomes unstable, you can initialize the
microSTATION as follows.
1. Turn off the microSTATION’s power.
2. While holding down the PLAY/MUTE button and
the function 08 button, turn on the
microSTATION’s power.
The microSTATION will be initialized, and data will
be written to internal memory. While data is being
written, the display will indicate “Initializing...”
When initialization has been completed, you’ll need
to load the preload data from an SD card containing
the data, or dump it from a USB‐connected
computer using microSTATION Editor/Plug‐In
Editor. (“Loading the preloaded data”)
1) These crashes/glitches is caused by memory(buffer) overload/flow/shortage by giving too fast/many/combination etc. commands to mS!
2)Give the mS some processing time to finish the job, before pushing another command to it!MarkWeston wrote: The error occurs during editing, after pressing certain buttons. Sometimes it can be the 'Play' button which causes the error.
Learn what sequence of commands cause the crashes and don't do/use it the same next time!
3)That's why you'll need always to backup the (all) data regulary to the SD card before editing important stuff!
4)Updating your mS Operating System (O.S.) to V1.0.1.
You gotto learn the way of the machine!
-
MarkWeston
- Posts: 3
- Joined: Wed Aug 01, 2012 7:45 pm
Thanks for your reply.
Initialization is what I meany by 'Setting Factory defaults'.
Your situation was worse than mine if you had to Initialize to actually get it working again.
It's difficult to find an exact sequence of events.
I'm surrently videoing the screen continually.
I do tend to go through the menus quickly.
But the crash has definitely happened during a slow stage, ie after several seconds since I pressed any previous button.
But perhaps I've asked it to do multiple tasks earlier, so the problem has already potentially occurred, & the next button pushes it over.
I often use 'compare', which gives a 'busy' message for a second.
I had assumed that the buttons wouldn't be available while it's busy, but now I'm wondering: what if they were? This could lead to problems.
It should have been programmed to know that it is busy though, & not start another job.
3. Yes, I quickly power through the incremental backup names, saving after every 10 minutes.
4. At power up, mine has always said Version 1.0.1.
However, I have looked at the notes for the code update, & there are some changes in there that mine doesn't have.
I chose not to update, in case that caused problems in itself.
Do you think I should update the code anyway?
I'm concerned that it might omit some functionality that I currently rely upon.
Would the 'Initialize' procedure undo the code update, so that I could revert if necessary?
Initialization is what I meany by 'Setting Factory defaults'.
Your situation was worse than mine if you had to Initialize to actually get it working again.
It's difficult to find an exact sequence of events.
I'm surrently videoing the screen continually.
I do tend to go through the menus quickly.
But the crash has definitely happened during a slow stage, ie after several seconds since I pressed any previous button.
But perhaps I've asked it to do multiple tasks earlier, so the problem has already potentially occurred, & the next button pushes it over.
I often use 'compare', which gives a 'busy' message for a second.
I had assumed that the buttons wouldn't be available while it's busy, but now I'm wondering: what if they were? This could lead to problems.
It should have been programmed to know that it is busy though, & not start another job.
3. Yes, I quickly power through the incremental backup names, saving after every 10 minutes.
4. At power up, mine has always said Version 1.0.1.
However, I have looked at the notes for the code update, & there are some changes in there that mine doesn't have.
I chose not to update, in case that caused problems in itself.
Do you think I should update the code anyway?
I'm concerned that it might omit some functionality that I currently rely upon.
Would the 'Initialize' procedure undo the code update, so that I could revert if necessary?