Disk write protected

By Dolphin101546015

Master (254)

Dolphin101546015's picture

05-04-2020, 21:09

When I use Basic in OpenMSX, I everytime get this error after some random time amount, with any code.
When I go to catapult and reinsert disk (dir), error disapear for until next random time.
This bug anoying already.

machine "Yamaha YIS-805_128R MSX2+ XBasic-2.1"
ext msxdos2 
diska "Z:/MSX Fractal/"
set auto_enable_reverse off
set maxframeskip 10
set resampler fast
set horizontal_stretch 320
set disablesprites on
set deflicker off
set deinterlace on
set scale_algorithm SaI
Login or register to post comments

By Meits

Scribe (5825)

Meits's picture

05-04-2020, 23:21

There are actions that have this as a result. Reinjecting the disk image will make it work again.

By Dolphin101546015

Master (254)

Dolphin101546015's picture

06-04-2020, 03:39

Meits wrote:

There are actions that have this as a result. Reinjecting the disk image will make it work again.

Yes, I wrote it.
But (for example) I lost changes in my util already when it happen.

By sdsnatcher73

Paladin (891)

sdsnatcher73's picture

06-04-2020, 04:50

It’s best to report bugs on openMSX in their github, then the developers can pick it up. Anyway do you guys have any ideas of what actions could be the trigger, say a steps to reproduce kind of thing?

By Dolphin101546015

Master (254)

Dolphin101546015's picture

06-04-2020, 05:58

sdsnatcher73 wrote:

It’s best to report bugs on openMSX in their github, then the developers can pick it up.

Tnx, will do it.

sdsnatcher73 wrote:

Anyway do you guys have any ideas of what actions could be the trigger, say a steps to reproduce kind of thing?

No good ideas, I guess a bit, rewind function have some reason, may be, coz I using it often. But actualy not sure.
Also I often use speed boost with frame skip (up to 100).
I ready give full discribe of process and link to my font editor for X-Basic, where it hapen after 2-3 font saving.
Also I forever using RAM Drive for OpenMSX, where I keep my DriveA data.
My system is Windows 10.
Also I have Debian with OpenMSX, and don't remember such problem inside it.

By Dolphin101546015

Master (254)

Dolphin101546015's picture

06-04-2020, 06:24

By Dolphin101546015

Master (254)

Dolphin101546015's picture

06-04-2020, 10:11

Meits wrote:

There are actions that have this as a result. Reinjecting the disk image will make it work again.

Will be good, if you present some description too on GIT.

By NYYRIKKI

Enlighted (5508)

NYYRIKKI's picture

06-04-2020, 15:09

When there is data written to disk and then rewind is used, openMSX will protect the disk instead of deleting the already saved work from it... Especially as it is generally very easy to accidentally destroy progress with reverse bar, I think it is more safe that it works this way. How ever openMSX should notify user that it has taken this step. Have you seen such notification? IIRC the notification appears momentarily under reverse bar and is sent to STDERR as well.

By sdsnatcher73

Paladin (891)

sdsnatcher73's picture

06-04-2020, 15:28

NYYRIKKI wrote:

When there is data written to disk and then rewind is used, openMSX will protect the disk instead of deleting the already saved work from it... Especially as it is generally very easy to accidentally destroy progress with reverse bar, I think it is more safe that it works this way. How ever openMSX should notify user that it has taken this step. Have you seen such notification? IIRC the notification appears momentarily under reverse bar and is sent to STDERR as well.

But Dolphin has auto_enable_reverse set to off, so what you have described should not be happening (unless I am missing something, not entirely impossible/just very doubtful Hannibal )

By Dolphin101546015

Master (254)

Dolphin101546015's picture

06-04-2020, 19:06

NYYRIKKI wrote:

When there is data written to disk and then rewind is used, openMSX will protect the disk instead of deleting the already saved work from it... Especially as it is generally very easy to accidentally destroy progress with reverse bar, I think it is more safe that it works this way. How ever openMSX should notify user that it has taken this step. Have you seen such notification? IIRC the notification appears momentarily under reverse bar and is sent to STDERR as well.

Time to time I get this message, but this error appear without it, and even without using reverse too, just look config above.
I might doing some test, where I will not using speed boost, and reverse keys.
May be it give something new about problem, idk.