If you're using OS 3.9 BoingBag 2, on some machines SetPatch assumes your fast ram is "volatile" (not of type MEMF_KICK) on reset, hence it will avoid this kind of ram to load the ROM updates into. Normally this means the updates go into chipram, which is fatal for exec.library for example, which will *crawl* there.
SetPatch AVOIDMEMFKICKFORPATCHES will avoid this -- as will BlizKick, if you tell it to load the ROM Update, because it knows the fastram will stay.
Anyway, BlizKick is one of the most useful programs since sliced bread and will allow you to patch a lot of bugs in the kickrom or optimize the speed, which SetPatch doesn't care about.
Thanks, Piru
