[Coco] Coco flash Mass flasher feedback

[RETRO Innovations]

On 11/3/2017 8:07 PM, My Email wrote:
> Hi
>
> I have a Beta of my mass flasher floating around and thought I would share some feedback
>
> The original flash menu reserved 8k and 50 entries using bank 0-1.   I have doubled that to a reservation of 16k and 99 entries using banks 0-3.   That being said we have found that the largest practical menu size is around 12k. Anything larger tends to cause an OM error when converting the MENU.BAS to a BASROM.BIN. So the user should be mindful, when adding there own ROMS, to the length of there name in the menu program. Remember that the phonics used to say the program paks name will double the size of the description (in K)
>
> Secondly   if you are flashing your own ROMS, in addition to the included set , you should flash them to the higher triple digit banks to prevent overwrite of the bins
>
> The mass flasher will flash the included. bins in alphabetical order and flash them sequentially thru the banks low to high
> If the flasher encounters a used bank it will simply erase and re flash that bank transparently to the user.   The original flasher would first warn of this conflict then prompt you to erase that bank.   The automated process of the mass flasher eliminates this warning
>
>
>
>
> Sent from my BlackBerry Passport Red Edition.
>
If someone is up for a small challenge, there is a working EEPROM on the 
board that is not currently in use (64kB) that is designed to hold 2048 
32 byte entries of data. With a bit of BASIC, you cna read and write to 
the EEPROM, store the ROM names there, and folks can reflash the menu 
app with different ones (to suite their preferences) without affecting 
their list of games/utils.


Happy to help someone (or someones) extend the menu to use this unused 
64kB of EEPROM.

-- 
RETRO Innovations, Contemporary Gear for Classic Systems
www.go4retro.com
store.go4retro.com