Not if you are doing a ROM!!
They works on CPM as ther based on bdos calls...
IMHO you have at least 4 options:

1) include the data in the rom at link time (best solution, but you need a good reading of the linker section in the manual -pgs.175 and followings)
2) include the data at compining time (try #INCLUDE)
3) include the data at assembly time (try *INCLUDE)
4) develop the game in msxdos mode and then move
the ROM only at the end

If both INCLUDE in 2 and 3 are only for text file, you could develop
a simple filter program for PC
all you need is to do a conversion of a bin file in a text file where byte
are in text (hex is better) and comma separated....

Too bad.
Just wanted to use this during development.......
I'm going for BIN -> Text for now.

what about your filter?

I was thinking you could create a .bin of 8K and a
level of 8K and then append the two files in a ".rom"

copy hunter.bin + level.stg > hunter.rom

Well I converted the bin to txt and included it in the source.

I've send you an e-mail with my progress. I have some troubles with the controls. I hope you want to help me?

I'll do what i can, let me see

Humm...
Do I have the permission to play havoc with your code?

Sure. Maybe i'll learn something of it

About padding to have a 16k rom. As you have in the code a new ptsec

...

psect    pad
defb 01
        
#endasm

you have to add to the linker options this parameters

-ppad=0bfffh