If you have 720KB disk, then you need 1MB ROM to make it fit inside. I'm sure you can take an emulator save state and start packing that to ROM-file as well, but it is much easier just to take assembler & the original files and rewrite the loader.ĭoing packing may help a bit, but anyway more conversion you make -> bigger it gets. This is absolutely the best method and minimizes the overhead caused by using standard containers and heck of a lot of logic glue. Usually the size does not change lot since you replace routines instead of just adding emulation layers. Unfortunately it also requires some manual work. If you want to use the tools then best that you can do is to use fresh DSK-file where you put the files. This will make the DSK-file easier to compress and therefore it may compress more. t is much easier just to take assembler & the original files and rewrite the loader. If you take some small cassette game it will be matter of coffee break to make it a ROM-file, but if you take some huge disk game that loads in between you better buy a lot of coffee to home before you even start. The biggest difference in ROM is that it is all available to use at the very moment you power on your MSX. You don't need to load it or anything like that. Handling disks is actually quite a complex task.
#SDLTRS ROM FILES DRIVER#
The MSX disk handling takes 13KB even without the low level driver routines! This space is used to initialize RAM variables, handle file system, file names, file control blocks etc. Most of this stuff is completely useless for the games and could be just as well left away if the game would be in ROM. Because the DSK2ROM tries to emulate disk drive all this is included to ROM-file as well.
0 kommentar(er)
