Right, this is now sorted, I figured I'd post back in case anyone else runs into this issue.
It turns out, if you don't know the engineers code to these alarms, wiping the EEPROM out and letting the alarm reset itself (re-writing the blank EEPROM NVM) only 'mostly' works...
Noticed in Wintex...