Open zmixnyc opened 4 months ago
Hi Chuck,
Synergia ignores rom filenames, and instead recognizes them from their MD5 checksums. any luck if you simply copy the four 8192 byte rom files to ~/Library/Application Support/Synergia/roms
folder ?
Synergy version 3.21 and 3.22 roms are supported, with the MD5 checksums below. pls PM me at jariseon - at - yahoo.com if it did not work out. unfortunately there are also non-rom related issues which i've been unable to resolve. those may prevent it from booting up. i should really decap my code.
roms321 = {
"0b1570927f9b929438e021370e65466d",
"98336749dcfbfdd5f5f22b7cb2493d55",
"21b3949acff422acf73b6373ffe3c6bd",
"6be6d7a393c60d4133a27b46c75f2051"
};
roms322 = {
"0b1570927f9b929438e021370e65466d",
"98336749dcfbfdd5f5f22b7cb2493d55",
"801d160c74c8bd38bc2cb820749450d6",
"ca90e6d4f3456bc77dc42a9fda8ab4f1"
};
Hi Jari,
Thanks so much for the reply.
I have everything up and running (using the .dat files) and I suspect that the issue may have been due to the fact that I was trying to use the version 2.45 ROMS from the FB Synergy group)
.bin files are the universal standard for EPROM readers and burners. I have all the Synergy FW in that format, but the Synergia requires ".dat’ file format which appears top only exists on the groups.io Synergy group.
Is there a possibility of updating Synergia so that the .bin files can be used in Synergia directly?
I am running macOS Sonoma on an intel Mac.
PS: I have not tried re-naming the ‘bin’ to ‘.dat’ to see if that has any effect.