I am balancing doing studio setup/refinements and outdoor/yard work (it is beautiful!). So:
Re: ID numbers/names: some numbers are reused; e.g. 17 is the MSB for the P2500 Composer ROM. Not sure where the name is stored--could be SIMM, could be OS checks something other than MSB. For my software, I used a lookup array based on MSB. Maybe someone else knows hows the OS does it. I don't see anything in the Hardware Configuration Request that directly gets at the version . I believe all MSB 17 have the same number of Simm Instruments. Other stuff is different. Maybe the OS gets the SIMM checksum and looks up the nsame from there, if its not on the SIMM. Maybe its in baby flash? P2500 Preset 127^3 is :default V1.0, so I doubt that provides SIMM identification. Maybe there's an undocumented sysex. Ages ago I discovered two for the Generic Name Request (7 = pattern, 8 = song) and why 3 = (arp)--in parentheses, but if there's a request sub-code for ROM Name [e..g. object type], I didn't find it!
I tried getting upper ROM banks with the non-direct method [through edit memory, IIRC]--it worked, so I didn't try your latest version--yet.
Thanks for ROM ID name for Flash SIMMs.
Using the E-Mu Librarian has really inspired to shift into productivity mode with an mind for doing multi-tracking. I think its been over a decade since I setup Cakewalk *.ins files so I can use those to select and keep preset/patch names in a DAW; but with E-Mu Lib, I am envisioning (1) finding presets I have long wanted to return to [updated versions of my tunes], (2) pruning and reorganizing them and integrating them into banks with new presets I have been working on [based on new performance modalities I probably have mentioned somewhere], (3) finding my last SONAR Master ins file and (4) reconstructing a new one based on the results of (1) and (2).
Again, thanks for the tool and your willingness to make tweaks and explain how to do things with it!!!
Steve