MegaFlash Rom Manager ROM

[Bryce]

I have to go out for a while, but I'll try both of them later and let you know.

Bryce.

[SyX]

Nice find redbox!!! 

If somebody can confirm that works (sorry, but i don't have LowerRom board), i'll publish the fixed versions.

[TFM]

Ok, just tried BCPL in slot 17. It initialises fine (ie: shows up in the list at boot), but it also crashes when you start it. I've a feeling that some ROMs just don't like being that far up the list.

I'll try Maxam 1.5 now...

Nope, Maxam 1.5 in slot 17: Initialises on boot but crashes when you start it.

Bryce.

This will not happen when using ROManager in ROM position 15 (the version with the Booster of course). That all works just fine. 

[Bryce]

Confirmed. At least for the Classic 6128 version. It now works fine and Maxam starts in upper slots too.

Edit: Confirmed working for the Plus version on Cartridge too. Enough testing for today, time for a beer

Bryce.

[redbox]

Confirmed. At least for the Classic 6128 version. It now works fine and Maxam starts in upper slots too.
Edit: Confirmed working for the Plus version on Cartridge too. Enough testing for today, time for a beer

Yay!  Am glad it worked.

I have uploaded the new image to the Wiki for the Plus and 6128.

@SyX - yes, you will need to patch KL FIND COMMAND and RST 3 in your Firmware 3.1 too.  I knew it couldn't have been that simple to start with 

[TFM]

Code Select Expand


KL FIND COMMAND
&02ed    &20

KL ROM WALK
&0327    1f

KL INIT BACK
&0337    20

RST 3 - LOW: FAR CALL
&048d    &20


I wonder if this would be also work with ROMs up to &7F (included), think I give it a try soon. Meanwhile thanks for the update!

[redbox]

I wonder if this would be also work with ROMs up to &7F (included), think I give it a try soon. Meanwhile thanks for the update!

Yeah, I wondered this...

It would also be nice to use ROM positions &84 to &87 on the Plus (and maybe higher) as then you could include some ROMs in the cartridge.

However, you'd need to avoid re-initialising &80, &81 and &83 as they contain the OS, BASIC and AMSDOS - so this would be beyond a simple patch.  But these routines could possibly be rerouted to jump somewhere else in the OS ROM to make use of available space for a better routine (like SyX did by removing the TAPE routines in the 6128 OS).

[TFM]

Well, it's not that bad. The BASIC is not a problem at all, it's a foreground ROM anyway (and it's located at any empty ROM number anyway), A patch in ROM 7 can be introduced to check if it was initialized before. Now only the firmware is left...it starts with &01 so the OS would recognize it as normal background ROM, a crash would be the result. So... patch RST 0 and that's it ;-)
Ok, it's some work, but it can be done amigo 

[arnoldemu]

I have updated the os.rom dissassembly on cpctech with comments for kl find command.

[redbox]

 

The BASIC is not a problem at all, it's a foreground ROM anyway (and it's located at any empty ROM number anyway)
A patch in ROM 7 can be introduced to check if it was initialized before.
So... patch RST 0 and that's it ;-)

That's a really interesting idea.  Will look into it.

I have updated the os.rom dissassembly on cpctech with comments for kl find command.

Thanks - this is a great resource and none of this would have been possible without it!

[SyX]

And i have applied the fix to the FW3.1, now is version 3.12, jejeje. TotO will upload the new versions to the thread.

Thanks again redbox!!! (And sorry, i only have seen now, your comment with the fix in the FW3.1 thread, but i never got a notification :/ )

[TotO]

Done.