Topic: Further Looking Into Default.xbe (Read 61 times)

BiMP · « **on:** July 04, 2003, 01:12:00 PM »

Upon loading the XBE with Dexbe, I get this:

"We got a Problem here - > [TLS] - >00008000"

then

"I/O Error 131"

-------------------------------

Using XbeTool I get:

"XbeTool v0.3 - loser july 2002
Error opening default.xbe!"

-------------------------------

Using Cxbx I get:

"Could not locate Thread Local Storage"

------------------------------

Final Thoughts: Free-x corrupted the Thread Local Storage system inside of Default.xbe

Dexbe: [TLS] = Thread Local Storage
Cxbx: Thread Local Storage = Thread Local Storage

That's two programs with detailed error messages saying it has a problem with Thread Local Storage

I'll keep working on it.

newb0x · « **Reply #1 on:** July 04, 2003, 01:48:00 PM »

Idont think you'll get very far without an XDK. Let the pro's handle this one. I'm sure the Evo-X team will release something soon.

jlm5151 · « **Reply #2 on:** July 04, 2003, 01:51:00 PM »

Are you insinuating that there is no one one these boards that knows what they are doing? Many of these people are "pros" and I doubt Evox will touch this one, your lucky to see a dash update every 6 months from them.

Rasenmaehen · « **Reply #3 on:** July 04, 2003, 02:45:00 PM »

Hrmm... the default.xbe from dayX exploit does boot on a modded box as usual, unlike xbe files prepared for the 007 exploit I might add. So, there are no significant hash changes that would affect booting on an already modded machine. Which means we're not really looking for a way to sign executables (at least the same way we have to sign 007 ones).

Oh, I tried it on a box using Evox 2.2 (never felt the need to upgrade

).

d3tr0it · « **Reply #4 on:** July 04, 2003, 02:58:00 PM »

My guess is rather that free-x made a lock within the fonts so that it would only run his xbeboot copy... I dont know if it differs from the original xbeboot, but somebody might want to check it up.

Author Topic: Further Looking Into Default.xbe (Read 61 times)