OpenMSX stands for: obliterate, perge, eliminate & nuke MSX!!!
Well... Succeeded!
To replicate (be careful what you wish for)..
Just run openmsx-catapult (Linux, ubuntu 22), with a folder as disk A, for example, Dynamic Publisher or DD-graph, wbass2,
Accidentally put a file in your home directory and think ah no problem.
Use the menu button (upper left corner) in the active openmsx window,
Click on Drive A, select home directory (~/), close menu, try to get your file from your application.
As general, even with new 'disk' inserted, it shows the files from previous directory.
So, select from application B: drive and depending on the application it will ask to put a disk in drive B ( I only have 1drive), and press enter.
Select drive A from application again, will ask to put and press.. Now the files appear!
Not sure if it as already truncated, but select your file, DD graph or so, you can view the tragedy..
Everything is kaput! Everything larger than 1kb is truncated. Parts of other files are added to others.. Recursively in every directory!
Incl. user files, config.. You can imagine what is stored in a user directory.
Afterwards it said it is full, wanted to return to basic and it went to reset.
At least I have not had to use Boabab to see where I could remove some data/folders to regain disk space.
Which MSX were you emulating?
The issue that the files are not appearing sounds like https://github.com/openMSX/openMSX/issues/1410 which got fixed a while ago. It's due to caching on the MSX side.
What openmsx version?
I will try to nuke a home directory with it. Reproducing this problem could be helpfull.
He uses OpenMSX 17.0 / Linux .. first post
ohw good. I have that version too. I will build a testsystem and see what happens.
Manual wrote:
Which MSX were you emulating?
Sony HB-F700D, no extensions.
Manual wrote:
Which MSX were you emulating?
Sony HB-F700D, no extensions.
OK, so that explains some things. https://github.com/openMSX/openMSX/issues/1410 applies for that machine. I guess there is something that went wrong with the caching, but let's try to reproduce it with this knowledge.
From the 18.0 release notes:
- Fixed bug in DirAsDSK which could lead to corruption
- Fixed DirAsDSK on MSX systems that require a disk-change signal to notice changes
OK, the 1410 issue seems different. It was about files not appearing in a dir-as-disk when you add them from the host side. So, when I change dir-as-disk, I see the effect immediately in MSX-BASIC, even on the Sony HB-F700P with openMSX 17.0.
I tried to reproduce the corrupted host files issues with openMSX 17.0, switching dir-as-disks, saving files there, removing files, but it works fine for me... that is, no single time the host files were corrupted or even touched (except the ones I KILLed in basic). I also COPY'd a file from dir-a to dir-b, swapping dirs as the machine only has one drive. Worked fine.
So if someone can post a confirmed detailed scenario, please let me know.
Accumulator: Just a quick question. Your home directory, on which filesystem was it residing? a regular ext4? or a shared setup with NTFS or some samba mount? Just so that we can correctly try to reproduce this...
rturbor wrote:
Accumulator: Just a quick question. Your home directory, on which filesystem was it residing? a regular ext4? or a shared setup with NTFS or some samba mount? Just so that we can correctly try to reproduce this...
My partitions:
mmcblk1p1: vfat
mmcblk1p2: EFI (vfat)
mmcblk1p3: EXT4 -> home directory
hint: put plenty of files in the home directory, MSX and non MSX, create some dirs, plemp there some files.
just run: wbass2 from a premade directory, use menu in active openmsx screeen change drive A (DirAsDisk) to ( ~ ), afterwards exit menu screen , at prompt do a dir "a:*.*" , dir "b:*.*" , and an dir "a:*.*" and load to, or save from wbass2, from home directory and I was as result almost throwing my pc to the wall!!
The advantage of Wbass2 is monitor, asm, dis, fill, move, reg, etc....in Real-time.. And can analyse direct the result of code.
Have not seen an PC, MSX emulator,monitor,debugger, which can do it all in real-time...
I am an old school coder, still using Wbass2, I just love it....
If WBASS2 could be converted to PC and use as plugin in OpenMSX/OpenMSX-catapult... A dream!
Yes I was using Wbass2 when this occurred, the file .asm file saving or loading (not compiled), was about 2.3Kb
I accidentally put the asm file in the home directory and in stead of copying to the right dir, I changed drive A: to the home directory...
Just checked.... Changing directory is switch A: B: A: to get results.
Isn't it time for a additional sub-number of OpenMSX?? 17.0.19242 or 17.0.deadbeef
That means 17 and calculation of patch numbers...
To know which exact version someone is running... and which updates/patches are applied
