Adding directory as Harddisk | MSX Resource Center (Page 1/4)

By Manuel

Ascended (19462)

29-03-2023, 23:31

Please see https://github.com/openMSX/openMSX/issues/1061

By Accumulator

Champion (331)

30-03-2023, 01:34

What is result or conclusion? My vote is clear....
Is it adopted or still in progress?

By Manuel

Ascended (19462)

30-03-2023, 07:41

As the ticket is not closed, it has not been implemented (yet).

By wouter_

Hero (522)

30-03-2023, 10:06

Just to set expectations straight: this is an open feature request, but as far as I know, nobody is actively working on it.
As always: help would be appreciated.

By Grauw

Ascended (10768)

30-03-2023, 10:50

You can use diskmanipulator instead, from a startup TCL script that’s passed with -script on the command line, or as individual -command parameters:

diskmanipulator create /tmp/new-hd.dsk 32M
hda /tmp/new-hd.dsk
diskmanipulator import hda my/directory

Of course this will not write back to the PC file system (you have to explicitly export for that), but personally I see this as a benefit, if there’s a bug in the code and something gets badly messed up on the MSX, it can’t corrupt the files on the PC.

This is what I do in almost all my projects.

By Accumulator

Champion (331)

30-03-2023, 21:16

I am thinking practical to implement. Hard disk can also been seen as SD card and vice versa or should directory be defined as Hard disk and SD card separately in for eg catapult?
Can we implement some code from RomWBW, to access FAT 12/16/32?

By giuseve

Paladin (786)

31-03-2023, 07:41

Grauw wrote:

You can use diskmanipulator instead, from a startup TCL script that’s passed with -script on the command line, or as individual -command parameters:

diskmanipulator create /tmp/new-hd.dsk 32M
hda /tmp/new-hd.dsk
diskmanipulator import hda my/directory

What is max size of the .dsk image? I tried using 4096M with no results. Maybe it works only with fat12 images?

Of course this will not write back to the PC file system (you have to explicitly export for that), but personally I see this as a benefit, if there’s a bug in the code and something gets badly messed up on the MSX, it can’t corrupt the files on the PC.

This is what I do in almost all my projects.

By Grauw

Ascended (10768)

31-03-2023, 11:51

giuseve wrote:

Grauw wrote:

You can use diskmanipulator instead, from a startup TCL script that’s passed with -script on the command line, or as individual -command parameters:

diskmanipulator create /tmp/new-hd.dsk 32M
hda /tmp/new-hd.dsk
diskmanipulator import hda my/directory

What is max size of the .dsk image? I tried using 4096M with no results. Maybe it works only with fat12 images?

Currently it supports FAT12 only, next release adds FAT16 support.

By Accumulator

Champion (331)

31-03-2023, 11:54

A table:
Wch is the FAT system MSX should be working with?
FAT12: 32 MB (256 MB for 64 KB clusters)
FAT16: 2 GB (4 GB for 64 KB clusters)
FAT32: 2 TB (16 TB for 4 KB sectors)
Can those drives being partitioned depending on clusters and thus only FATx Directly) and via OpenMSX other sysfs like btrfs, ext, ntfs etc?

By djh1697

Paragon (1702)

31-03-2023, 20:27

There is a FAT16 driver, or you can use NEXTOR for FAT16 support.

I seriously think that the processing power of MSX would not support FAT32, however, that doesn't mean it cannot be done. Maybe with a complete rewrite of Nextor? or a FAT32 driver.

Whoever thought we would be able to use flashcards and some USB devices with our humble 8-bit machine.