Print

[eh.]

No, there's nothing to worry about; if you've already ran it, thanks for kindly trying to help evolve the exploit further.  This isn't an attempt at "reverse psychology" aimed at the leechers either!  Here's where I'm coming from...

M$ will do everything they can to fix the known kernel and dashboard flaws, of course. The same will happen if the scans reveal something else, especially before Halo 2's released (just in time for the Holiday season...)!

Consequently, I've decided to stop my (futile) efforts to encourage scans, move back into the shadows and wait re UD-eh!

(Edit: changed time reference, a spelling and punctuation of the final remark eh.)

[Chicken Scratch Boy]

well... there is the whole PAL thing, but the current work around... works

how about the pal users find UDE3?

[Flame2k]

bitches FINE WE WILL find ude 3, we dont need ur help....much....

[OliG]

lol
It would be nice to find a usable xbe for PAL. I know we have a work around (which works just fine) but it would be nice to not have to mess with the bios settings at all.

I for one will continue to scan machines as people let me look at them. I'm sure M$ are very interested in the latest break throughs and are kicking themselves. We do need to keep people aware of scanning the hard disks for exploitable xbe's that way more chance of finding one.

OliG

[triggernum5]

I think he's making the point that now is a crucial time for MS..  With Halo 2 approaching it is definately in their best interest to force a dash upgrade that closes any possible exploits, as well as new kernels for new machines.  They'd like to stop softmodding as completely as possible, they will definately be hunting the forums to determine more holes to fix.  If new exploitable xbe's are found and made public MS will jump on them for the Halo 2 release.  If progress was kept a little more secretive, an exploit or two might be able to slip through the cracks.
Kinda boils down to that CIA expression, Our successes are private. Our failures are public.

This post has been edited by triggernum5: Aug 22 2004, 12:57 AM

[Flame2k]

trig, thats getting me worried abt running halo 2 on my box lol.

[triggernum5]

Its a big day for MS..  I'd wait for some guinea pigs to run it first if you're softmoded..  (I'll be a guinea pig, I don't care..).  I would only expect MS to try to totally reinvent themselves for the occasion.

[Flame2k]

yeh. they just have to spoil all the fun  

if u could see them re-inventing themselves, do u think we will see xbox 1.7?

who knows.
If they are watching us, a new dash and possibly new kernel will definatly come out by the end of this year in my opinion

[eh.]

The most recent softmods will very likely result in a new kernel being released before Halo 2.  M$ could remove the EEE from the dashboard too, but they've (surprisingly) chosen not to do that so far eh.

[Flame2k]

im sure we will be able to overcome whatever they throw at us.

[OliG]

QUOTE (Flame2k @ Aug 22 2004, 06:53 PM)

If they are watching us, a new dash and possibly new kernel will definatly come out by the end of this year in my opinion

Flame2k, your sounding paranoid. People watching us. This is a forum. : P

There is no doubt that they are keeping tabs on this and a few other sites.  

OliG

[eh.]

Absolutely, so don't let the scans potentially reveal something prematurely eh.

[triggernum5]

Who should PAL XBL users show interesting logs to under the table then?

[total_ass]

MS can't actually stop our current exploits from working can they? i mean without the original fonts, then no in-game updates, and if we're running X2 then no XBL updates. so if i never connect to xbox live am i completely safe forever?

[triggernum5]

Don't count MS out..  With their current techniques you are safe..  They could change that.  And the main point is that hopefully if MS isn't clued into target files, a hole might develop to softmod the next kernel too. Nothing you can do to change whether or not they manage to update your dash.