Folder as Hard Disk? | MSX Resource Center (Pagina 2/3)

Paragon (1159)

26-07-2016, 10:57

You could mount a DSK file (even FAT12) with OSFMount and there you have your folder. Use the DSK image in OpenMSX. Or isn't this what you meant?

Van AuroraMSX

Paragon (1902)

15-08-2016, 13:06

What about implementing a virtual HDD interface/"cartridge" for this? The ROM in the cartridge could contain DOS2 + FAT16 support. DOS2 file-level routines can be routed directly to host OS disk routines, low-level disk routines can be stubbed. Then you do not need to work around or even bother with the peculiarities of existing HDD interfaces.

openmsx -ext dirashdd ~/msx/my_msx_hdd

Van Manuel

Ascended (18879)

15-08-2016, 19:13

Neh...

Van AuroraMSX

Paragon (1902)

15-08-2016, 20:59

Manuel wrote:

Neh...

OMG! That is the most qualified disqualification of a proposal I've ever read!

Van Manuel

Ascended (18879)

15-08-2016, 21:26

Hahah, it was especially for you! IRC?

Van Mafcase

Master (256)

15-08-2016, 23:44

'the most qualified disqualification'

Van DarkSchneider

Paladin (944)

16-04-2017, 10:47

IMO this would be one of the most useful features for developers. Sharing files with the PC (the development machine) is a pain. Using folder as FDD is also a pain because slow access and size limit (fragmentation of your files and versions of these in many disks).

Van AxelStone

Prophet (3121)

19-04-2017, 08:56

Issue opened, it should be really great for developers since the file sharing with PC should be fast: graphics, music, code... everything in realtime.

Van Wolverine_nl

Paragon (1159)

19-04-2017, 10:39

I stick to what I use, mount the dsk image on the pc with OSFMount and share the image with OpenMSX. Then I can work in a folder and see results in OpenMSX directly.

Van Manuel

Ascended (18879)

19-04-2017, 23:16

DarkSchneider: if the slow access is bothering you, you probably don't have the "fullspeedwhenloading" setting enabled? See http://openmsx.org/manual/commands.html#fullspeedwhenloading

Size limit remains, but why is that a problem? You do the development in your own git repo (or whatever you like) and your build-script will output a disk image or file-structure that can be used as disk as if it's ready for a real MSX and then you start openMSX with that disk.... You don't need *all* your dev files in that folder for openMSX, only the ones you need to run on the MSX itself, of course.