I tried the NBX3 image editor, and it triggered two different bugs:
1) The MSX mouse pointer is totally out of sync with the host mouse pointer.
2) If you drag the files to the files to the webMSX window (files mode), it creates a disk that contains only the MSX-DOS1 bootsector. This way, the MSX-DOS2 on the disk won't boot on the MSX TurboR configuration.
The correct approach is to always generate the newer version of the bootsector code that is compatible with both MSX-DOS1 and MSX-DOS2. This bootsector is generated when you format a disk on a real MSX TurboR computer, (or any previous generation running MSX-DOS2).
I tried the NBX3 image editor, and it triggered two different bugs:
1) The MSX mouse pointer is totally out of sync with the host mouse pointer.
2) If you drag the files to the files to the webMSX window (files mode), it creates a disk that contains only the MSX-DOS1 bootsector. This way, the MSX-DOS2 on the disk won't boot on the MSX TurboR configuration.
The correct approach is to always generate the newer version of the bootsector code that is compatible with both MSX-DOS1 and MSX-DOS2. This bootsector is generated when you format a disk on a real MSX TurboR computer, (or any previous generation running MSX-DOS2).
NBX31.zip