Please help testing upcoming openMSX release!

페이지 59/61
52 | 53 | 54 | 55 | 56 | 57 | 58 | | 60 | 61

By ren

Paragon (1888)

ren의 아바타

25-08-2021, 11:27

wouter_ wrote:

[...]
Thanks a lot for reporting! This should be fixed in the latest build.
Apparently this was a windows-only crash (I suspect caused by a bug(?) in the MSVC compiler). I also took some steps to ensure that similar future problems will cause compile errors rather than runtime crashes.

Cheers, I can confirm it's working. Aside of this issue, I see you had to revert quite some recent changes because of MSVC incompatibility apparently. Wouldn't it be an option to (just(?)) use GCC for Windows as well?

By Dolphin101546015

Champion (335)

Dolphin101546015의 아바타

25-08-2021, 21:46

Manuel wrote:

https://github.com/openMSX/openMSX/issues/1238 is the corresponding issue.
As Wouter wrote there: perhaps your editor is (temporarily) putting (backup?) files in the folder, causing it to be larger than 712kB, so that the disk becomes full? This will cause corruption.

oO No comments

Manuel wrote:

Please tell me how exactly you are modifying the content of the folder that is used as disk in openMSX.

From OpenMSX, by using save"name.bas"

By ren

Paragon (1888)

ren의 아바타

25-08-2021, 22:53

Some random thoughts/ideas:
* try another file system for the ram disk, or perhaps another RAM disk host application;
* exclude the directory in your AV config;
* would it be an option to use an MSX HDD?
* try a short dir without spaces;
* perhaps you can use Sysinternals Process Monitor as a diagnostic tool;
* perhaps some power saving stuff may interfere?
* ...

By Manuel

Ascended (18254)

Manuel의 아바타

25-08-2021, 22:53

I was under the impression you were using die as disk to also edit the files from outside the MSX. But is that correct?
If not, why are you using dir as disk in the first place?

By ren

Paragon (1888)

ren의 아바타

25-08-2021, 22:56

From the issue:

Quote:

About text editor: you mean I doing some file modifications outside emulator when it working?
No, I do not disturb FS. But I have antivirus, may be it doing some checks, idk.

By Manuel

Ascended (18254)

Manuel의 아바타

25-08-2021, 23:35

Yes, so why not use a disk image instead? At least as a workaround it may be very useful.

By Grauw

Ascended (10174)

Grauw의 아바타

26-08-2021, 00:46

Quote:

But I have antivirus, may be it doing some checks, idk.

Ooh, antivirus software on Windows is a definite possible culprit. Many of them acquire locks on the file when they detect it is accessed, which could cause openMSX to fail subsequent write accesses in the writing process. I’ve seen mysterious file corruptions in other software and I know for certain that e.g. version control software takes complicated special measures in their repository file management to work around that, it’s quite an ugly situation.

Try adding your dir-as-disk folder to the exclusion list of your antivirus software and I bet your issues will be gone.

By Dolphin101546015

Champion (335)

Dolphin101546015의 아바타

26-08-2021, 05:36

I trying work without antivirus too, it was disable for week or even more. Windows Defender was disabled too.
Problem the same.
Using any disk images is not possible for me.

By Manuel

Ascended (18254)

Manuel의 아바타

26-08-2021, 08:22

Why is it impossible?

By Dolphin101546015

Champion (335)

Dolphin101546015의 아바타

26-08-2021, 18:17

Manuel wrote:

Why is it impossible?

Coz I need reconfigure resources, data & code everytime from machine, and outside.
Everytime it needing recreate or update disk image without OpenMSX.

페이지 59/61
52 | 53 | 54 | 55 | 56 | 57 | 58 | | 60 | 61