QUOTE
NKpatcher solves this but on coldboots still doesn't help (no XBL support)
Hmm, sure it can be worked around with the lesser font exploits, in the modded state, via hexed files or by having (i) nkpatcher (ii) an active ShadowC (iii) the retail fonts copied into the active ShadowC.
However, Ndure "solves it" (as do EEE and even audio exploits) but UXE doesn't and nor does nkpatcher ... "out of the box"!
QUOTE
Updates are prevented by filling up the C drive right? no probs there
Hmm, as posted numerous times, updates still run but are prevented from clobbering the softmod. With the "fonts" setup, no user followup is needed but with the "retail" setup some is (to re-establish the retail boot, as posted).
QUOTE
Can you explain that a bit more. I was under the impression that switching files back and forth were exactly the same using Ndure or UXE. (switching from modded to retail might be quick but from retail to modded still requires the gamesave or easter egg.)
Hmm, switching from modded to retail is faster plus easier and switching back is faster ... also since Ndure just has to rename files it doesn't have the level of disk corruption risk that UXE's workaround does!
QUOTE
The switching is "faster" because renaming files would be enuff. Indeed, the same hassle applies to getting unsigned code to run again.
Hmm, sure there are some "constants" in the process but it's the "variables" that differ.
QUOTE
But EEE fonts are already in place, so basicly with a few more renames/copy operations, this could toggle between a UEEE and Ndure retail setup without needing anything from another drive for example.
Hmm, it has nothing to do with UEEE and that won't be involved (as the Live console wouldn't be available if it was).
QUOTE
You're right bout the update, but emtpty xboxdashadat.du and font.du folders prevent this (but where left out in the retail setup since they can create alot of confusion). I almost forgot about that.
Hmm, he was close (for a change) and no they don't prevent it.
QUOTE
yeah I understand you need to rename stuff. I just wanted to know how this is different/faster then an UXE setup.
Hmm, then write out all of the steps involved and compare it with Ndure's fewer, quicker, easier ones ... you could see what's really quite obvious, if you weren't so narrow-minded!
QUOTE
Well you dont need file off another drive etc, thus making the process faster. Apart from that, UXE doesn't nativly offer the function (Ndure does since it really is just EEE but bootstrapped)
Hmm, actually the 'ure' (uber rmenhal exploit) bootstrap preceded its EEE usage (as UEEE) by some months, but the forum mods didn't release it ... why was that krayzie?
QUOTE
But the way Eh formulated is wrong, they both allow it. Ndure is just a better candidate for Live! given the one exploit "does it all", and it never loses update.xbe support.
Hmm, I didn't think so but I maybe didn't explain it clearly. Btw, I'm curious, is there
anything that UXE is a better candidate for?
QUOTE
No offense BTW, but instead of holding on to UXE, you could just modify/rebuild you installer to install a Ndure/EEE setup with switcher
Hmm, I doubt that he could!
krayzie
