Amiga.org
Amiga computer related discussion => Amiga Software Issues and Discussion => Topic started by: dannyp1 on November 22, 2009, 09:02:29 PM
-
I was just setting up BlizKick on a fresh OS3.9+BB1&2 and everything seemed to be going fine until I was trying to load the updates from BB2 with BlizKick and ran into a problem. All of the modules loaded fine except for "shell". It took about a half hour of trial and error to figure out which module was messing things up. Has anybody ran into this before? I have done this same thing before on other computers and can't recall having this problem.
Dan
-
I was just setting up BlizKick on a fresh OS3.9+BB1&2 and everything seemed to be going fine until I was trying to load the updates from BB2 with BlizKick and ran into a problem. All of the modules loaded fine except for "shell". It took about a half hour of trial and error to figure out which module was messing things up. Has anybody ran into this before? I have done this same thing before on other computers and can't recall having this problem.
Dan
Did you try the "extresbuf" option?
-
You should always run BlizKick WITHOUT "quiet" option first to see if it works with your choice of modules. After you see that it kickboots nicely and doesn't halt to some error, then you can add "quiet" to the end of the whole commandline. I remember "shell" giving some error, but that was maybe a fault of a too small "extresbuf" setting as Damion suggested.
-
Try this: C:SetPatch SKIPROMMODULES shell >nil: QUIET
x303 :D :D :D