Topic: Anyone Played With Dxt Files? (Read 127 times)

azninvasion · « **on:** June 20, 2003, 03:12:00 PM »

I think the E:dxt directory is only on debug xbox's and i believe there is a tool in the dev section that uses a fdrive.dxt file to add the fdrive to the xbox, it hooks onto the xbox kernal somehow, perhaps if you get in touch with who made it you'll get more nfo.

[KaZuYa] · « **Reply #1 on:** July 31, 2003, 09:55:00 AM »

QUOTE (Voltaic @ Jun 20 2003, 12:50 AM)

I've been playing a bit with these files and I'm wondering if anyone else looked into this. DXT(dynamic extensions?) are normal Xbox programs but compiled with /LD (or /LDd) and linked with /DLL (there's a bit more to it, but that's the basic).

I looked for the loader but it seems it isn't in the Xbox API. The xbdm.dll (which is loaded by the kernel) iterates the E:DXT*.DXT files and load 'em up one by one. I'll look at re-creating the API used to load these into the process space. This will enable us to have a plug-in like feature for the Xbox. I plan on using this to load features into a hacked version of the MS Dashboard.

Anyway, I just wanted to see if someone looked into this already. The searches return nothing on the subject.

-Volt.

DXT1 to DXT5 or 4 are texture compressions..

maybe you got it wrong? Or did I? Just wanna help, so if you know what u are talking about, never mind. k?

Voltaic · « **Reply #2 on:** July 31, 2003, 04:00:00 PM »

It's Debug Extension, and they are just (somewhat) normal EXE files.

-Volt.

Wishi · « **Reply #3 on:** August 01, 2003, 04:39:00 AM »

DmLoadExtension() surely would be what you were looking for (declared in xbdm.h and uses xbdm.lib). When one debug extension is loaded, all other it depends on are also loaded in.

Author Topic: Anyone Played With Dxt Files? (Read 127 times)