zeilemaker54

May be something like: If 16kb rom Read init entry If init >0x4000 and 0x8000 and Do you have a suggestion how openMSX could detect whether the 16k ROM is...

Hello Wouter, Of course I understand your hesitation to change the behavior of the ROM type detection. But if you develop a 16KB extension ROM, using the INIT entry (and...

According to the files on the bluemsx site: BIOS 0000-7FFF slot 0 RAM 0000-FFFF slot 3-0, no memorymapper SUB 0000-3FFF slot 3-1 DISK 4000-7FFF slot 3-2 FIRM 4000-7FFF slot 3-3...

About the mapper of the HX-34, it seems there is a register 07FFFH (slot 3-3). From what I have deducted from the firmware: b7 unknown, something related with interrupthandling b6...

But about the Toshiba FDC, I think the diskrom of the HX-34 could be also the diskrom of the double sided HX-F101 version. Because of the version strings of both...

mars2000you schreef op 2019-05-02 09:36: > A little precision: according my Japanese source, the firmware rom in > HX-33 and HX-34 is not exactly a megarom but a ROM with...

Manuel Bilderbeek schreef op 2019-05-05 14:26: > So, did I understand correctly we cannot emulate the HX-34, at least > due to a missing ROM dump? > > @zeilemaker54 [1]...

Snel gedaan zeg! Groet, Arjen Manuel Bilderbeek schreef op 2019-05-14 21:55: > FYI: Wouter implemented the missing features of the Toshiba FDC in > b5ed0f3 [1] > > -- >...

I already did write a program to dump the rom. Attached is the MAC file (renamed as TXT) to create the MSX-DOS COM file. It is untested on the real...

Hello Manuel, Here is the dump program, including the source file. It is a MSXDOS 1 program, I am not sure this will work in a MSXDOS 2 environment. [hx3xdump.zip](https://github.com/openMSX/openMSX/files/5740062/hx3xdump.zip)...