Problem using "DirAsDisk" function in OpenMSX (v.0.15.0)

Door defdanny

Master (174)

afbeelding van defdanny

20-07-2020, 00:09

Hi all,
could someone please explain the following behaviour to me:
I have different directories on the HD of my PC (FAT32), that represent copies of original floppy disks (no disc images!).
The PC I am running openMSX (with Catapult launcher) on uses Windows 10.
1. I start openMSX (with Catapult) with a MSX1 type profile (e.g. "Sony HitBit 75P") after I chose one of the Disk dirs by selecting "Disk A > Browse for disk folder (DirAsDisk)".
2. When the MSX1 system has loaded, i can list the content on the diskDir with "FILES".
3. I stop openMSX and restart it with a MSX2 type profile (tested with "Philips VG8235", "Philips NMS 8255" and "Sony HB-F700D", the same Directory is mapped to DISK A.
4. When I type "FILES" or "FILES "A:" I receive a "Disk offline".

What is the reason for that different behaviour? I need to open these DiskDirs with a MSX2 machine profile, because they contain MSX2 stuff...
Please help!

Aangemeld of registreer om reacties te plaatsen

Van Manuel

Ascended (17061)

afbeelding van Manuel

20-07-2020, 00:28

That should work just fine.

Did you try it with a simple dir with just a basic program in it, for example?

Can you share the dir content, so I can try myself?

Which extensions did you use? The Sony HB-75P doesn't have a disk drive built in.

Perhaps you still had that extension selected when booting the MSX2 which did have a built in disk-drive. Try to deselect that extension.

The problem with multiple disk interfaces is that they are assigned by the BIOS in a certain order. This order is not predicted by openMSX. So it is possible that the A: for the MSX is not 'diska' for openMSX. In this example, the external diskdrive may have become drive "A:", but openMSX still put the disk in the internal disk drive which is now "C:". Check with FILES "C:".

Van defdanny

Master (174)

afbeelding van defdanny

20-07-2020, 00:25

Hi Manuel,
I just found the "problem" by myself.... it sits in front of the monitor! ;-)
You are on the right track: I simply forgot to de-select the extension "Sony HBD-50" (the diskdrive that the MSX1 machine needed). With that still connected, no MSX(2) machine worked with its internal Disk drive.

Well: maybe this is something that should generate a warning message to the user?
I was not aware, that the extension was still selected... now I know.

Problem solved!

Van Manuel

Ascended (17061)

afbeelding van Manuel

20-07-2020, 00:28

It can be also the intention of the user to do this...

Van defdanny

Master (174)

afbeelding van defdanny

20-07-2020, 00:31

Got it! You are right.