HB-F1XDJ machine

By Dustin Pease

Resident (50)

Dustin Pease's picture

20-12-2015, 14:31

has anyone had any luck getting this to work in openMSX? I dont seem to be able to get it to work. I have the actual machine, just trying to reduce the wear and tear on it if i can. Thank you for any assistance! Smile

Login or register to post comments

By Wild_Penguin

Hero (641)

Wild_Penguin's picture

20-12-2015, 15:36

Hi Dustin,

AFAICS I can boot this machine just fine. Are you missing the roms? What is the problem specifically, does not openMSX recognize the ROMs? Are you trying to do the ROM dumps yourself? Do you use catapult for launching, or some other frontend?

By Dustin Pease

Resident (50)

Dustin Pease's picture

20-12-2015, 17:39

I am having no luck with the roms i have downloaded can you pm me where you got your set and i will see if i can get it working with those. Thank you for the quick reply

By Wild_Penguin

Hero (641)

Wild_Penguin's picture

20-12-2015, 18:24

Hi Dustin,

Hope you found some ROMs or got them dumped yourself! Smile

FWIW, you can find the sha1sums (or sometimes md5sums, I think) of the ROMs openMSX is looking for in the machine specification files. You didn't mention your platform, but for example, on my linux computer:

$ grep -in '\.rom\|sha1\|md5' /usr/share/openmsx/machines/Sony_HB-F1XDJ.xml
26:        hb-f1xdj_kanjifont.rom
27:        218d91eb6df2823c924d3774a9f455492a10aecb
87:          Sony_HB-F1XDJ_main.rom
88:          f2a1d326d72d4c70ea214d7883838de8847a82b7
92:          hb-f1xdj_basic-bios2p.rom
93:          e2fbd56e42da637609d23ae9df9efd1b4241b18a 
106:            hb-f1xdj.rom
107:            ade0c5ba5574f8114d7079050317099b4519e88f
134:            Sony_HB-F1XDJ_main.rom
135:            f2a1d326d72d4c70ea214d7883838de8847a82b7
139:            hb-f1xdj_msx2sub.rom
140:            fe0254cbfc11405b79e7c86c7769bd6322b04995 
146:            Sony_HB-F1XDJ_main.rom
147:            f2a1d326d72d4c70ea214d7883838de8847a82b7
151:            hb-f1xdj_kanjibasic.rom
152:            1ef3956f7f918873fb9b031339bba45d1e5e5878 
164:            Sony_HB-F1XDJ_main.rom
165:            f2a1d326d72d4c70ea214d7883838de8847a82b7
169:           hb-f1xdj_disk.rom
170:           12f2cc79b3d09723840bae774be48c0d721ec1c6
171:           c9500da2151881ea40b005f383b8602450129bf3 
180:            Sony_HB-F1XDJ_main.rom
181:            f2a1d326d72d4c70ea214d7883838de8847a82b7
185:            hb-f1xdj_fmbasic.rom
186:            aad42ba4289b33d8eed225d42cea930b7fc5c228 

EDIT:Haha, the forum likes to try to interpret the < sha1 > and < filename > tags i got in the [ code ] tags above, and also removes the comment tags... well you get the idea, you can find the information in your openMSX installation in any case.

If your ROMs sha1 sums are different, it is possible it is a bad dump. If you are sure it is a good dump, you may try to change the sha1sum (or make your own hardwareconfig.xml).

The file name is irrelevant, btw (except maybe for .rom, and openMSX might even look inside zip files?). Just put the ROMs in the right dir and it should work. Search dirs are slightly different on different platforms, and I think it is all in the documentation.

By Dustin Pease

Resident (50)

Dustin Pease's picture

20-12-2015, 19:23

im on linux too, so this is perfect! i will track these down. Cheers!

By Dustin Pease

Resident (50)

Dustin Pease's picture

21-12-2015, 03:56

got it working, thanks again!

By Manuel

Ascended (18233)

Manuel's picture

21-12-2015, 11:07

Wild_Penguin wrote:

The file name is irrelevant, btw (except maybe for .rom, and openMSX might even look inside zip files?).

The filename is indeed completely irrelevant, openMSX purely looks a the sha1sum of the file. I'm not sure by heart whether it looks into zip files. If it does, it surely only looks at the first file in it. So, better just unzip them in the right folder and it will certainly work.

By tvalenca

Paladin (747)

tvalenca's picture

21-12-2015, 16:44

I'm not sure how it happened, but once I needed to calculate and replace the sha1sum on the configuration file of openMSX in order to boot on a specific machine. Maybe it was a slightly different ROM file.

By Manuel

Ascended (18233)

Manuel's picture

21-12-2015, 22:32

Then you use a different ROM file, for which we have not checked that it's the correct one.