Thanks for the feedback.
I was am hoping to get some discussion going on in this topic & thread.I was always confident that the bright sparks in the forum would be able to
combine the exploits to solve any issues (as they always have

). I authored my
Dashboard Exploit Summary post to aid and encourage this

I'm assuming that, by the time you've performed all the XBOX!Live updates to the latest Dashboard/XBOX!Live console, the final xodash\update.xbe would be far newer than the 4290 update.xbe - and the font overflow bug fixed - meaning that if the
latest xodash\update.xbe was launched by the xonlinedash.xbe, and was denied all fonts except C:\bert_ate_ernie.xtf, the exploit wouldn't fire - I
do wonder what would happen.
A best-case-scenario is that the additional check simply steps over loading an overflowing font, and carries on looking and loading the remaining fonts what match the *.xtf wildcard. Since rmenhal has found that the 4290 update.xbe only loads one font, it may possible to the put the two retail fonts
and bert_ate_enie in C:\ and force the order of the *.XTF file enumeration. Either by file
renaming (relying on a sort order), or re-writing the raw directory sector.