So I configured openMSX to use Nextor with Sunrise IDE and that starts.
Now: I would like to have a 100MB partition with FAT16. I can't get it to work.
Nextor _FDISK can create a partition of 100MB but can not format it.
Nextor _FDISK can create a partition of 32MB and can format that FAT12
Is Sunrise limited to 32MB? If not, how can I create a 100MB FAT16 HD image?
Nextor _FDISK can create a partition of 100MB but can not format it.
Hmm, that should work, I’ve done just that a few months ago. Once you add the partition in FDISK and save it, iirc there’s no need to separately format it, it will already be FAT16 formatted and you can start to copy files on it.
Alternatively, if you are on a recent development version of openMSX, the diskmanipulator
command now supports FAT16 and you can use it to create FAT16 partitions:
diskmanipulator partition hda -nextor 100M
And also to import files onto the partition:
diskmanipulator import hda my/files
However the last official release doesn’t support that yet, only FAT12.
Ok, got that partition of 100MB done, thanks. Now I need to update my openMSX version because diskmanipulator says No (or invalid) partition table. I suppose 18.0 isn't the version with native FAT16 support yet. Fixato's site is down, when I write this. Also hope he has a Mac build.
These are the latest builds on GitHub: https://github.com/openMSX/openMSX/actions/runs/4545343925
Thanks, but I can't find a download for the most recent build. You can only see the yaml files and other build statistics unless I do not recognise the download button.
On Mac you work around the diskmanipulator by changing the extension to .img. Mac will use the diskmounter so you use finder to copy/paste files.
You don't *have* to work around that feature. You can use it or not, at your own convenience.
These builds are probably only visible (at the bottom of the screen) when you are logged into GitHub.
I think https://nightly.link/ is a workaround. For instance, currently the latest build is https://github.com/openMSX/openMSX/actions/runs/4548308118 and this results in https://nightly.link/openMSX/openMSX/actions/runs/4548308118
You don't *have* to work around that feature. You can use it or not, at your own convenience.
So the message " No (or invalid) partition table " when you try to import files and directories through diskmanipulator and it fails, is a feature? In my book, thats an error message indicating the reason something doesn't work.
True, you can choose to use Mac diskmounter or diskmanipulator to import files, but if diskmanipulator fails (for whatever reason), diskmounter is a good alternative.
So the message " No (or invalid) partition table " when you try to import files and directories through diskmanipulator and it fails, is a feature? In my book, thats an error message indicating the reason something doesn't work.
Yes, I was talking about the diskmanipulator itself. Which can handle Nextor partitions fine in the latest development builds.
True, you can choose to use Mac diskmounter or diskmanipulator to import files, but if diskmanipulator fails (for whatever reason), diskmounter is a good alternative.
Of course.