Difference between revisions of "MegaFlashROManager"

From CPCWiki - THE Amstrad CPC encyclopedia!
Jump to: navigation, search
Line 6: Line 6:
 
<br>
 
<br>
  
−
'''MegaFlashROManager provides the following functions:'''  
+
'''MegaFlashROManager 1.8 provides the following functions:'''  
  
 +
*Automatically detect which Flash expansion is connected (X-MEM, MegaFlash, FlashGordon, MF EX, MF Bübchen etc).
 
*Park or Unpark ROMs: This is done by manipulating the Byte at &C000. A parked ROM will not be initialized by the firmware.  
 
*Park or Unpark ROMs: This is done by manipulating the Byte at &C000. A parked ROM will not be initialized by the firmware.  
 
*Load ROM(s) (one or all 32): This function allows to load a 16 KB (ASCII) or 17 KB (Binary) ROM (or all 32 ROMs of 16 KB each at once) and to install it in the MegaFlash.  
 
*Load ROM(s) (one or all 32): This function allows to load a 16 KB (ASCII) or 17 KB (Binary) ROM (or all 32 ROMs of 16 KB each at once) and to install it in the MegaFlash.  
Line 14: Line 15:
 
*Shift ROM(s): Shifts a 16 KB ROM from one ROM select to another, the old ROM select will be filled with &FF bytes.  
 
*Shift ROM(s): Shifts a 16 KB ROM from one ROM select to another, the old ROM select will be filled with &FF bytes.  
 
*Erase ROM(s): Deletes a 16 KB ROM with &FF bytes.  
 
*Erase ROM(s): Deletes a 16 KB ROM with &FF bytes.  
−
*Test ROM(s): Provide information about a ROM like Type, Version, Mark, ROM name etc. Further you can install the correct checksum to a changed ROM. The ROMs at position 0 (usually the BASIC ROM) and 7 (usually AmsDOS) are protected.
+
*Test ROM(s): Provide information about a ROM like Type, Version, Mark, ROM name etc. Further you can install the correct check sum to a changed ROM. The ROMs at position 0 (usually the BASIC ROM) and 7 (usually AmsDOS) are protected.
 
*Protect Flash: It will switch on the Software-Data-Protection (SDP), it renders the Flash inaccessible.
 
*Protect Flash: It will switch on the Software-Data-Protection (SDP), it renders the Flash inaccessible.
−
*Initialize Flash: Now, this function deactivates the SDP, so the Flash can be freely written. This function is especially important if you use a new Flash, which factory setting is: SDP = on.
+
*Test Flash: This protocol is intended to check the integrity of the 512 KB Flash in a relatively sophisticated way. But it takes 6 minutes. Further, currently this function can't be used due to interference's which corrupt ROMs.
−
*Test Flash: This protocol is intended to check the integrity of the 512 KB Flash in a relatively sophisticated way. But it takes 6 minutes. Further, currently this function can't be used due to interferences which corrupt ROMs.
+
*EDIT ROM: This function allows you to display a ROM in ASCII and hexadecimal. You can alter bytes in the hexadecimal system (Feature only available under FutureOS).
−
*EDIT ROM: This function allows you to display a ROM in ASCII and hexadezimal. You can alter bytes in the hexadecimal system (Feature only available under FutureOS).
+
*Erase complete Flash chip: This should only be done for initialization purposes.
−
 
+
*Automatic SDP management: Not visible for the user, the SDP gets switched off for burning, but remains active at all other times.
 +
*Enhanced error checking: You can see if the last Flash operation was successful or not.
  
 
For loading and saving ROMs you can directly enter device and name, so you can access files even on exotic devices.
 
For loading and saving ROMs you can directly enter device and name, so you can access files even on exotic devices.
Line 27: Line 29:
 
The version for [[FutureOS]] is slightly advanced and more quick than the version for [[BASIC]]. The differences in comfort and speed are OS dependent (file handling f.e.). In addition the EDIT system of FutureOS can be used to edit ROM contents.
 
The version for [[FutureOS]] is slightly advanced and more quick than the version for [[BASIC]]. The differences in comfort and speed are OS dependent (file handling f.e.). In addition the EDIT system of FutureOS can be used to edit ROM contents.
  
−
The 128 KB version has a multi language interface for: English, French, German, Dutch and Spanish. In addition a version that fits in an single 16 KB ROM has been released. If desired this ROM can in addition contain the BOOSTER routine ([[Inicron]]) to initialize all 32 ROMs.
+
The 128 KB version has a multiple language interface for: English, French, German, Dutch and Spanish. In addition a version that fits in an single 16 KB ROM has been released. If desired this ROM can in addition contain the BOOSTER routine ([[Inicron]]) to initialize all 32 ROMs.
−
The 64 KB version - mainly developped for the CPC464/664 - allows to select the language at startup.
+
The 64 KB version - mainly developed for the CPC464/664 - allows to select the language at startup.
  
−
File-names must be entered in the format "0A:filename.ext". The number is the user number followed by the drive letter and a semicolon":". Then 8 lettes filename, a dot "." and finally the 3 letters extension.  
+
File-names must be entered in the format "0A:filename.ext". The number is the user number followed by the drive letter and a semicolon":". Then 8 letters filename, a dot "." and finally the 3 letters extension.  
 
With Control-TAB you can switch the editing mode to overwrite.
 
With Control-TAB you can switch the editing mode to overwrite.
  

Revision as of 12:40, 8 September 2014

The program MegaFlashROManager for FutureOS and AMSDOS/BASIC (on disc or as ROM) allows the management of the 512 KB Flash-ROM (=Pseudo-ROM) of the MegaFlash developed by Bryce of FutureSoft. It also supports the FlashGordon from PulkoMandy and the MegaFlash EX from Nilquader. Since version 1.8 is also supports TotO's X-MEM boards (Winbond or SST Flash).

You can load/save all 32 ROMs at once. And every single 16 KB Flash-ROM can be managed individually. This software was developed by TFM of FutureSoft. Versions for both OS and 64 KB or 128 KB CPCs are available.

MegaFlashROManager


MegaFlashROManager 1.8 provides the following functions:

  • Automatically detect which Flash expansion is connected (X-MEM, MegaFlash, FlashGordon, MF EX, MF Bübchen etc).
  • Park or Unpark ROMs: This is done by manipulating the Byte at &C000. A parked ROM will not be initialized by the firmware.
  • Load ROM(s) (one or all 32): This function allows to load a 16 KB (ASCII) or 17 KB (Binary) ROM (or all 32 ROMs of 16 KB each at once) and to install it in the MegaFlash.
  • Save ROM(s) (one or all 32): Saves one or all ROMs to disc or hard disc. This feature can be used to create backups.
  • Copy ROM(s): Allows copying the content of one ROM select (16 KB) to another. You can use this function for example to copy the BASIC ROM to all free ROM selects.
  • Shift ROM(s): Shifts a 16 KB ROM from one ROM select to another, the old ROM select will be filled with &FF bytes.
  • Erase ROM(s): Deletes a 16 KB ROM with &FF bytes.
  • Test ROM(s): Provide information about a ROM like Type, Version, Mark, ROM name etc. Further you can install the correct check sum to a changed ROM. The ROMs at position 0 (usually the BASIC ROM) and 7 (usually AmsDOS) are protected.
  • Protect Flash: It will switch on the Software-Data-Protection (SDP), it renders the Flash inaccessible.
  • Test Flash: This protocol is intended to check the integrity of the 512 KB Flash in a relatively sophisticated way. But it takes 6 minutes. Further, currently this function can't be used due to interference's which corrupt ROMs.
  • EDIT ROM: This function allows you to display a ROM in ASCII and hexadecimal. You can alter bytes in the hexadecimal system (Feature only available under FutureOS).
  • Erase complete Flash chip: This should only be done for initialization purposes.
  • Automatic SDP management: Not visible for the user, the SDP gets switched off for burning, but remains active at all other times.
  • Enhanced error checking: You can see if the last Flash operation was successful or not.

For loading and saving ROMs you can directly enter device and name, so you can access files even on exotic devices.

ROM files with and without an header can be loaded and installed.

The version for FutureOS is slightly advanced and more quick than the version for BASIC. The differences in comfort and speed are OS dependent (file handling f.e.). In addition the EDIT system of FutureOS can be used to edit ROM contents.

The 128 KB version has a multiple language interface for: English, French, German, Dutch and Spanish. In addition a version that fits in an single 16 KB ROM has been released. If desired this ROM can in addition contain the BOOSTER routine (Inicron) to initialize all 32 ROMs. The 64 KB version - mainly developed for the CPC464/664 - allows to select the language at startup.

File-names must be entered in the format "0A:filename.ext". The number is the user number followed by the drive letter and a semicolon":". Then 8 letters filename, a dot "." and finally the 3 letters extension. With Control-TAB you can switch the editing mode to overwrite.

Downloads

The Source Code to Flash a 16 KB ROM can be found here:

- Media:Flash.dsk

Weblinks

Latest Release date was March 5, 2013. The version number is 1.45.

Retrieved from "https://gryzor.info/index.php?title=MegaFlashROManager&oldid=91216"