for games more than 64k this loader make some mistakes confusing some DATA with CALL (IN/OUT) that is why usually big games need to be PATCHED (Fixed by hand with a lot patience and motivation).
NYYRIKKI, maybe your MegaROM loader AI ("Self aware, self modifying artificial intelligence for separating program code from other type of data") approach can be used for SMS ROM loading on Franky?
maybe but i have enjoyed every game i had modified for MSX Franky VDP. by the way i have used always Dennis Koller first Loader (SCONV.BAS) because that loader help a lot when i have started a Franky fixing project.
Well, this new version just load a maximum FRANKY GAME with 4096KB - 80KB = 4016KB and fix the problem with users using OCM-PLD Firmware Ver 3.7.1 and OCM-SDBIOS <2.7 + FRANKY/PLAYSONIQ.
USAGE:
F4096P2 frankygame.sms
https://drive.google.com/open?id=14JqkQsYwPTgBuoi1nIUjUok22z...
Well, this new version just load a maximum FRANKY GAME with 4096KB - 80KB = 4016KB and fix the problem with users using OCM-PLD Firmware Ver 3.7.1 and OCM-SDBIOS <2.7 + FRANKY/PLAYSONIQ.
Not only for OCM-PLD v3.7.1 but for all versions of OCM-PLD and any SDBIOS.
About the use of F4096P2.COM:
My Franky Loader (F4096P2) make use of the Memory Mapper the Msx Bios initialized it at boot.
I have noted the Zemmix Neo Bios doesn't count the Playsoniq Extra Memory.
but the Extra Memory from playsoniq is there.
so playing with MEM.COM
I can see it report at Normal Speed:
Mappers Found: 4
Slot 1-0 4080K
Slot 3-0 4096K
Slot 1-2 4080K
Slot 1-1 4080K
but at Turbo Mode (F12 Key twice at boot) MEM.COM report :
Mappers Found: 1
Slot 3-0 4096K
The slot clock is 10MHz in turbo mode. It is normal for external mappers not to work in that mode if they were not designed to support such a high clock. You can force the external clock at 3.58Mhz with a limit on F12 of two steps 3.58MHz + 5.37MHz. The MSX-DOS2 commands are "SETSMART -40" or "EXTCLOCK -3".