It seems Sharksym experiments with new flash chip.
(spotted download link for something called ENLOAD_v1.00.zip)
Oh NOOOOooo... please! Not another Flash programming utility just for flashing a different manufacturer's Flash chip!!!
Continue that trend, and you'll have half a dozen differently named utils for re-programming the Flash ROM, and the user needing to figure out what type Flash part is inside a cartridge he just bought... 
(no not everyone who has one of these will know what Flash part is in there, and the chances of that will lower as an interface becomes more popular - read: more newbie users).
These Flash ROMs (afaik ALL) have some sort of Product Identification mode, usually these return a byte indicating manufacturer, and another byte indicating device type. Apply the required command sequence for a few known parts, and you can identify in software what part it is / what programming algorithm to use. And thus support a number of different Flash parts in the same programming utility. And share any code besides the actual programming (like file handling, command line processing, user prompts etc) between all of those.
2nd: If you add support for other Flash parts, then PLEASE do so for popular, cheap and/or easily available types. What you have in your spares box as developer, doesn't matter. What other people might use to build their Flash interfaces, does. Suggestions: common 2, 4 or 8 Mbit parts from AMD, Intel, or say, Winbond (which are often found on old PC mainboards).
Hell, just define a sharp line between Flash programming utility's generic code, the Flash programming code, and put out its source code. That way anyone can add a well-defined section to add support for Flash part XYZ to 'the' Flash programming tool.