Core 167 on ARM 32

Hi,

that was a glitch in an earlier stage of Core Update 167 (testing), and has been fixed meanwhile.

Thanks, and best regards,
Peter Müller