Possible FW bug in v5.1.2.1a update on Korg DSS-1

Post Reply
agent29
Posts: 67
Joined: Sun May 08, 2016 10:42 am

Possible FW bug in v5.1.2.1a update on Korg DSS-1

Post by agent29 »

Hi,

After recently updating from v3.3.1.1a to v5.1.2.1a the DSS-1 cannot write files to the HFE image, nor can it format and exising image.

The DSS-1 displays its writing or formatting but nothing happens?. The gotek displays read and write access also. If i regress the firmware back to v3.3.1.1a it works.

I dont know at what version update this bug introduced itself?

agent29
Posts: 67
Joined: Sun May 08, 2016 10:42 am

Re: Possible FW bug in v5.1.2.1a update on Korg DSS-1

Post by agent29 »

An small update, I was mistaken, it does write to the image but i cannot delete files or re format the image fromthe DSS1. I updated to v5.0.0.7a and the bug is still there. I regressed to v3.8.3.1a and the drive returns to normal operation.

Jeff
Site Admin
Posts: 8092
Joined: Fri Oct 20, 2006 12:12 am
Location: Paris
Contact:

Re: Possible FW bug in v5.1.2.1a update on Korg DSS-1

Post by Jeff »

agent29 wrote:
Mon Apr 24, 2023 2:24 pm
An small update, I was mistaken, it does write to the image but i cannot delete files or re format the image fromthe DSS1. I updated to v5.0.0.7a and the bug is still there. I regressed to v3.8.3.1a and the drive returns to normal operation.
What do you mean by "cannot delete files or re format the image fromthe DSS1. " ? Do you get any error from the korg dss1 ?

agent29
Posts: 67
Joined: Sun May 08, 2016 10:42 am

Re: Possible FW bug in v5.1.2.1a update on Korg DSS-1

Post by agent29 »

Hi Jeff,

I updated the fw back to the latest, and its now working? please consider this issue closed.

Jeff
Site Admin
Posts: 8092
Joined: Fri Oct 20, 2006 12:12 am
Location: Paris
Contact:

Re: Possible FW bug in v5.1.2.1a update on Korg DSS-1

Post by Jeff »

agent29 wrote:
Tue Apr 25, 2023 4:04 pm
Hi Jeff,

I updated the fw back to the latest, and its now working? please consider this issue closed.
Ok fine .
This was maybe an internal setting issue ? Maybe you have cleared the settings to the default state.

Post Reply