Not Recognizing ROM

[jpscharf]

I have several ROMS and Medusa will not recognize any off them, even though they work with sheepshaver.

[jpscharf]

After checking each ROM with Mac ROMan 1.2.3b Medusa recognized them.

[sentient06]

Hello,

That's a weird bug, I'll investigate in a virtual machine without MacROMan. Thanks!

I don't have a complete list of New World ROM image checksums. If you know which ROM it is, you can find the MD5 and send to me, so I can add it to the code.
Most of the missing ones probably won't work anyway, they would be there only for information purposes. MacROMan and Medusa share the same checksums list.

The missing ones are the following:

Mac OS ROM 3.6 (Mac OS 9.0.3 bundled on iMac)
Mac OS ROM 3.7 (Mac OS 9.0.4 Retail/Software Update or Mac OS 9.0.4 installed on PowerBook)
Mac OS ROM 3.8 (Extracted from Ethernet Update 1.0)
Mac OS ROM 4.6.1 (Mac OS 9.0.4 installed on iMac 2000)
Mac OS ROM 4.9.1 (Mac OS 9.0.4 installed on Power Mac G4)
Mac OS ROM 5.2.1 (Mac OS 9.0.4 installed on Power Mac G4 Cube)
Mac OS ROM 5.3.1 (Mac OS 9.0.4 installed on iBook)
Mac OS ROM 5.5.1 (Mac OS 9.0.4 installed on Power Mac G4)

All the best!

[rodneyrod]

This bug is affecting me as well, tried four different ROMs (Quadra 650, 900, Macintosh Plus and a NewWorldRom) and none of them have been recognised.

[AdrienJonquet]

Hello,
I also have that bug with any rom I've tested. Most of them are recognised by Mac ROMan but not by Medusa...

[EricFromCanada]

For me, Medusa will only recognize a ROM file if its "Open With" setting is set to Mac ROMan. If the file (or all files with the .rom extension) is set to open with anything else, e.g. Mini vMac, it gets rejected. I use RCDefaultApp to show which app is currently set for each extension.

[sentient06]

Hello EricFromCanada, can you give me the OS version you are using? Is it above 10.9? Thanks!

[EricFromCanada]

I'm on OS X 10.11.6.

[sentient06]

Okay, I found the issue. It is way more confusing than I thought. Anyway, there was a method to figure out what file was being dropped in Medusa, but that method was changed by Apple since Yosemite and since the code changed, this problem exists.
So, there is an extension check I will remove in the next release. Apart from that, it is supposed to accept "Unix Executable File", "ROM Image" and "Mac ROMan.app Document" files.
If you have nothing set up, it defaults to "Unix Executable File" (which is the most common case). So I suggest that, until the new release is available, open RCDefaultApp, browse to the extensions tab, locate the "rom" extension and delete it from that list. Then if you feel like it or still have issues, you can clean the "open with" list of applications everywhere by executing this in the console: /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/LaunchServices.framework/Versions/A/Support/lsregister -kill -r -domain local -domain system -domain user. This should remove all associations with rom files and make it work. If you use any application for rom files, please let me know which is it so I can add its file types to Medusa. I will also keep a log for failures, so it is easier to debug in the future.

Oh yes, remember that if you create an app association in the info window on Finder, that particular file will be bound to that app, creating inconsistent behaviour. So if that be the case, before changing stuff in RCDefaultApp, you might be interested in choosing a random application in the info window and clicking "change all".