BMMS (Bigger Memory Mapper Selector)

Pagina 3/5
1 | 2 | | 4 | 5

Van Grauw

Ascended (8387)

afbeelding van Grauw

22-12-2018, 13:54

It doesn't need to work I think, but if it detects that and disables itself, you can just leave the cart inserted.

Van gdx

Prophet (2978)

afbeelding van gdx

22-12-2018, 14:22

Does MSX-DOS2 not already select itself the largest Mapper? If this is not the case, an MSX-DOS2 version will be required but I'm working on the MSX-DOS1 version first. After I will see if it is necessary.
Current BMMS works from Basic. MSX-DOS1/2 can run next but I not sure the DOS2 perfectly works after. I can not test all the possibilities and BMMS is not intended for DOS2. It is for this reason that I ask for feedbacks.

Van Grauw

Ascended (8387)

afbeelding van Grauw

22-12-2018, 15:46

Ah okay, I mistook the header for a ROM Smile.

Van NYYRIKKI

Enlighted (5365)

afbeelding van NYYRIKKI

22-12-2018, 18:09

gdx wrote:

Does MSX-DOS2 not already select itself the largest Mapper? If this is not the case, an MSX-DOS2 version will be required but I'm working on the MSX-DOS1 version first.

Yes it does... Only exception to this rule is MSX tR where the internal mapper is always selected. This also makes sense as it is a LOT faster than using external mapper.

Van NYYRIKKI

Enlighted (5365)

afbeelding van NYYRIKKI

22-12-2018, 23:09

Actually this DOS2 stuff bothered me so much that I just had to take another look... Now it seems to work at least somehow... As you can see the COMMAND2.COM is still left behind to internal memory, so I have to investigate this a bit more... The code is also in VERY experimental stage and not much testing has been done.

https://youtu.be/Kv3ec-o8fx4

EDIT: Ah, naturally it is not COMMAND2.COM, but the fact that I have not remembered to reserve/free TPA pages, stupid me.

Van gdx

Prophet (2978)

afbeelding van gdx

23-12-2018, 11:58

NYYRIKKI wrote:
gdx wrote:

Does MSX-DOS2 not already select itself the largest Mapper? If this is not the case, an MSX-DOS2 version will be required but I'm working on the MSX-DOS1 version first.

Yes it does... Only exception to this rule is MSX tR where the internal mapper is always selected.

Therefore when the MSX starts on the Basic, since the bigger mapper is already selected on bank 2 and 3 (c000h~ffffh). BMMS causes no problem. It's looking for the Mapper for nothing but performs POKE-1,(15-PEEK(-1)\16)*17. I can add a condition to avoid looking for the mapper when the ROM-Disk 2.xx is present.

Grauw wrote:

Ah okay, I mistook the header for a ROM Smile.

What? oO

Van saccopharynx

Master (135)

afbeelding van saccopharynx

23-12-2018, 13:21

NYYRIKKI wrote:
gdx wrote:

Does MSX-DOS2 not already select itself the largest Mapper? If this is not the case, an MSX-DOS2 version will be required but I'm working on the MSX-DOS1 version first.

Yes it does... Only exception to this rule is MSX tR where the internal mapper is always selected. This also makes sense as it is a LOT faster than using external mapper.

I would appreciate some clarification regarding MSX tR computers: Even though the internal mapper is always selected, these machines still read back registers from the external mapper, in contrast with MSX2+. Is that right? If that is the case, it would be possible, at least under MSX-DOS1, to select the external mapper and play those cracked games that read mapper registers.

Van Grauw

Ascended (8387)

afbeelding van Grauw

23-12-2018, 13:49

With Nextor you can keep the “4” key pressed during boot-up to make it select the biggest mapper as primary, rather than the internal one.

About read-back, I haven’t tested myself but the wiki says they don’t read back from the external mapper. They use the same MSX-ENGINE, so that’s why probably.

However since the turboR has either 256K or 512K of memory, I can imagine it does not matter as much. I think the biggest use case is European 128K games, and those should have no (mapper) problems on a turboR. For cracked games, those are a thing of the past if you ask me, there are plenty of cartridges like the MegaFlashROM that you can use conveniently to play the original ROMs.

Van gdx

Prophet (2978)

afbeelding van gdx

23-12-2018, 13:57

BMMS is maintly made for MSXs without MSX-DOS2 and that has RAM in a slot lower than its cartridge slots because it is always this RAM that is selected. A lot of software does not work because of that. BMMS fixes it and replace the "universal poke" in loaders. The Turbo R is not concerned.

Van NYYRIKKI

Enlighted (5365)

afbeelding van NYYRIKKI

23-12-2018, 14:23

As gdx inspired me to take a look at the DOS2 problem again and here is first version for MSX tR & MSX-DOS2 that you can test. This is not competing version, but maybe in future it can be combined with gdx tool for MSX-DOS1 (?)

There are anyway few things that you need to take in to consideration:

  • This is still early version and does not ie. check errors situations like if there is no enough free segments (6) on the biggest mapper. Therefore (and anyway) I recommend running this before creating ie. large ramdisk or loading drivers.
  • If you plan to use INCRAM or any other tool related to MSX tR DRAM-mode, please use them before running this tool.
  • If you use your computer in R800 mode, the programs will work slower after running this tool.
  • This tool violates at least half a dozen rules in the ASCII provided MSX-DOS2 documentation, so use at your own risk. Any promises with future version compatibility can and will not be given.

This tool is primary intended to help if you are planning to run MAP2 & some memory hungry MSX2 game under MSX-DOS2.

Download: TRBIGMAP.COM

Ps. AFAIK Nextor has possibility to force big mapper by holding a key down during boot. This is the recommended way to do it in order to keep compatibility also with future versions, but I think this should work also. (at least with current version) I can recommend using this only in case you need to run some DRAM-mode related tool first.

Pagina 3/5
1 | 2 | | 4 | 5