|vcontrol fp 0 will reboot the machine <- this is normal|
what is not normal is that the fpu is still enabled after the reboot instead of being disabled
vcontrol fp 0 works normally in 2.8 and earlier, but seems broken in 2.9
putting vcontrol fp 0 in the startup sequence would cause the machine to reboot forever.
its not an issue with workbench either... i tried it on a clean install of wb 3.1
can anyone else verify if they are able to disable the fpu on core 2.9?
and... just in case it is helpful to someone else, i wrote 2 tiny programs:
checkfpu -> returns 1 if an fpu is detected and 0 if there is no fpu detected
disablefpu -> will check if an fpu is detected and if it is will run "vcontrol fp 0" (which will reboot the system). if no fpu is detected the program doesn't do anything.
disablefpu will only work if vcontrol is somewhere in your path (ie, Workbench:C)
i wrote disablefpu so that i could put it in my startup sequence so that i could disable the vampire fpu by default (because of some fpu inaccuracies).
warning: if you put disablefpu in your startup sequence, the system will reboot forever with gold 2.9
it works well on 2.8 and earlier.
source included: EXTERNAL LINK