I wanted to make a custom tool for myself to do a bunch of things on ROMs including computing the Fluke 9010a signature.
I have been suing KI4SWY's ROM ident page which is awesome, but I wanted to make a tool on my ROM burning machine (which often doesn't have internet access) that could do a bunch of things and needed the fluke algorithm which I could not find ANYWHERE.
I found a post to 2000 which suggested it's simply an XOR across each byte, which it's not (though it does mainly use xors, but not just XORing every byte)
I know KI4SWY must have figured it out, so I emailed him, he kindly pointed me to calcsign and a .net decompiler and suggested it decompile/reverse engineer it, so I did.
anyway I think it's dangerous that this really useful tool (fluke 9010a) not have any documented how it performs the checksum... so here you go.
http://www.paladingrp.com/brianb/fluke_9010a/checksum.txt
it's in perl the main function is doChecksum which takes a perl scalar which should be the string of the ROM to be checksumed, that's the algorithm, the entire program itself is mainly just a perl rewrite of calcsig by the quarterarcade folks, which when ran scans a directory and performs the algorithm on each file in the directory.
anyway I hope this might help someone else in the future and ensure the algorithm stays documented so if anything ever happens to the quarterarcade people or KI4SWY, then the algorithm won't be lost. I know the fluke people have not supported the 9010a for probably 20+ years.
-brian
I have been suing KI4SWY's ROM ident page which is awesome, but I wanted to make a tool on my ROM burning machine (which often doesn't have internet access) that could do a bunch of things and needed the fluke algorithm which I could not find ANYWHERE.
I found a post to 2000 which suggested it's simply an XOR across each byte, which it's not (though it does mainly use xors, but not just XORing every byte)
I know KI4SWY must have figured it out, so I emailed him, he kindly pointed me to calcsign and a .net decompiler and suggested it decompile/reverse engineer it, so I did.
anyway I think it's dangerous that this really useful tool (fluke 9010a) not have any documented how it performs the checksum... so here you go.
http://www.paladingrp.com/brianb/fluke_9010a/checksum.txt
it's in perl the main function is doChecksum which takes a perl scalar which should be the string of the ROM to be checksumed, that's the algorithm, the entire program itself is mainly just a perl rewrite of calcsig by the quarterarcade folks, which when ran scans a directory and performs the algorithm on each file in the directory.
anyway I hope this might help someone else in the future and ensure the algorithm stays documented so if anything ever happens to the quarterarcade people or KI4SWY, then the algorithm won't be lost. I know the fluke people have not supported the 9010a for probably 20+ years.
-brian

