0 Members and 1 Guest are viewing this topic.
Yeah, hot_dog, I don't think putting it in the boot code is a good idea, yet. We first need to know what kind of side effects this will have before we make it permanent. (Programs will no longer crash, they will freeze or go crazy.)
Quote from: thepenguin77 on June 28, 2011, 08:03:12 pmYeah, hot_dog, I don't think putting it in the boot code is a good idea, yet. We first need to know what kind of side effects this will have before we make it permanent. (Programs will no longer crash, they will freeze or go crazy.)Hmmm, that makes sense. It's for that reason that Crabcake relocks the C000-FFFF area upon shutdown
Quote from: Hot_Dog on June 28, 2011, 08:05:05 pmQuote from: thepenguin77 on June 28, 2011, 08:03:12 pmYeah, hot_dog, I don't think putting it in the boot code is a good idea, yet. We first need to know what kind of side effects this will have before we make it permanent. (Programs will no longer crash, they will freeze or go crazy.)Hmmm, that makes sense. It's for that reason that Crabcake relocks the C000-FFFF area upon shutdownWait, you mean you already implemented this? Because if that's the case, then you should save the previous values so that if a person has it permanently unlocked, crabcake won't relock it.Edit: Also with this, you don't to shut down the hooks.
Oh, no. Nevermind. I thought that you had already implemented the port 25/26 thing in CrabCake. I meant save those valuesAnd there's no reason to save the flash unlock state, flash gets relocked every time you archive/unarchive something or even run an app.