That won't work, the Xbox/XDK only support running one process at a time (there's not underlaying OS) so once you start a game or whatever your xbe and all it's functions get's cut off. Only way it's possible is if you can figure wound how to incoperate it into the BIOS (like Xecuter2 BIOS's IGR (In Game reset) or how EvoX patches the BIOS with their IGR) to make it resistant in memory in a protected area that does not get cut off.
The following are results from the testing I have done.
If you boot to evox, run xbmc, override the fan speed, and start a game the fan speed is reset.
BUT,
If you boot to evox, run xbmc, overide the fan speed, go back to evox (using L+R+Back+Bl) and start a game the fan speed does not change.
QUOTE(chief7 @ Feb 25 2005, 02:44 PM)
The following are results from the testing I have done.
do you think i will pretty safe? i don't want to screw my xbox up
only the memory is changed so no effects should remain after a reboot, right?
i have been analyzing how xbmc changes the fan speed and i think i understand it.
i have also been learning some c/c++
i am currently waiting for the xdk to finish downloading so i can start developing my app. i will probably try to use openxdk for the final product, but i figured $m will have some good documentation for me to learn from first
one thing i have not been able to find is a list of the kernel functions available for use or the includes necessary to execute a .xbe on the xbox. are there any?
no one ever answered the question from my last post either, which i will now revise:
do the halwritesmbusvalue/halreadsmbusvalue functions change only the ram memory? can i screw up my xbox?
You could try using Frosted Bios Loader... I'm not sure how long the change lasts, but it allows the fan speed to be set even if you're simply launching an XBE through it.