The goal would be to find out the way to connect the vhd player to this c9d card properly. As it seems nobody has this c9c/c9f card and the connecting cable toward vhdplayer.
But even with correct cable, if this card does not support the needed commands to play the game, then if openmsx could be used to debug what io addresses are called and with what data. Of course the final goal could be to have this vhd game playable in openmsx. That of course needs video dump from that vhd disk also.
I opened the file in openmsx with nms8250 profile, but it give flashing effect same as when tried to run the cassette in real toshiba hx20. So it needs to have those superimpose commands in i/o space
/rom.
So what happens if you dump the ROM from the interface and insert it in a slot on NMS8250 (in openMSX)?
I tried openmsx 18.0 with victor hc-95a roms. The _super0/1/2/3/4 basic commands are there. But when trying to run this vhd game, the screen just flashes constantly. I would have expected to get that same error screen as in real hardware, because that outcome was not depending on this vhd card.
I tried to add the vhd card rom, but error comes:
"Maching switching failed. Vhd card: invalid rom position: interval [0x0000, 0x8000) must fit in [0x0000, 0x7fff]"
Why?
The config xml part about that addition inside h95a xml:
primary slot="2">
ROM id="Vhd card"
connectionstyle Victor
mem base="0x0000" size="0x7FFF"
rom
filename VICTOR_C9D.ROM
sha1 9faa8f8cfcba35c7b5f33013d914900ab09ae364
p.s. how these xml settings can be shown in this forum as i had to now remove those / marks and so on to get it shown somehow the content here ?
Yes that is to be expected. What happens if you load the tape now? With the ROM the I/O ports used can be determined (by someone with the right knowledge).
The game does not show that error screen, but just makes that constant flashing maybe 1s interval (bluescreen, light bluescreen, normal basic view where there is those function keys listed at the bottom of screen).
By the way, in the cas file dump in binary file there can be seen _VP basic commands used, is that normal to see from binary file?
so all of these are valid basic command when changing syntax from ÊVP to _VP.
and it shows that _VP("G00000") is used to go to track number 00000, so any track number can be given.
and _VP("G",T) is used to get current track number. Or is this called frame number.
In cas file there is header for that bin file:
1F A6 DE BA CC 13 7D 74 D0 D0 D0 D0 D0 D0 D0 D0 D0 D0 53 54 4F 52 4D 20 1F A6 DE BA CC 13 7D 74 00 87 FF DF 83 A0 3E 87 56 87 6E 87 86 87 9E 87
I assumed the header begin, end, and start are these bytes:
00 87 FF DF 83 A0
so i made file that has 0xFE as starting byte, and then same bytes starting from this 00 97 FF FD 93 A0 onwards. So this would be the correct binary file, only the actual size (not the end address) i am not sure as there are many zeros at the end of cas file.
The game does not show that error screen, but just makes that constant flashing maybe 1s interval (bluescreen, light bluescreen, normal basic view where there is those function keys listed at the bottom of screen).
By the way, in the cas file dump in binary file there can be seen _VP basic commands used, is that normal to see from binary file?
so all of these are valid basic command when changing syntax from ÊVP to _VP.
and it shows that _VP("G00000") is used to go to track number 00000, so any track number can be given.
and _VP("G",T) is used to get current track number. Or is this called frame number.
Sometimes a binary loaded file is still a BASIC program. Another possibility is that it is a compiled BASIC program.
