Are you on Windows or Mac? You should have a text editor app that edits plain text files - files without any formatting. On Mac there’s the builtin TextEdit or the free CotEditor on the App Store.
You’re going to need such an editor to edit at least the OUTPORT and OUTCHAN lines in any definition file you find here.
Within that editor, create a new file, copy this minimal definition into the new window. I’ve omitted all comments to make it look less overwhelming.
VERSION 1
TRACKNAME MS2000
TYPE POLY
OUTPORT A
OUTCHAN 1
INPORT ALLACTIVE
INCHAN NULL
[PC]
[/PC]
[CC]
[/CC]
[ASSIGN]
[/ASSIGN]
[AUTOMATION]
[/AUTOMATION]
[COMMENT]
[/COMMENT]
Edit the OUTPORT according to which Midi out port on your Hapax it is connected to and set OUTCHAN to the MS2000s Midi channel. Next, start adding CC values.
Here’s the Pyramid definition: Korg MS2000 CC definition file
To convert a Pyramid CC list to Hapax format, all you need to do is replace the “:” with an empty space.
5:PORTAMENTO
=>
VERSION 1
TRACKNAME MS2000
TYPE POLY
OUTPORT A
OUTCHAN 1
INPORT ALLACTIVE
INCHAN NULL
[PC]
[/PC]
[CC]
5 PORTAMENTO
[/CC]
[ASSIGN]
[/ASSIGN]
[AUTOMATION]
[/AUTOMATION]
[COMMENT]
[/COMMENT]
So basically you can copy the whole list of CCs, do a search & replace and you’re done if CCs are all you care about. If you’d like to add automation parameters, knob assigments or add a list of your favourite presets to the program change (PC) section, then it’s a good idea to look up how they work because IMO these are personal choices. For most instruments though I only have the I/O header and CC section.