Submitter
File Information
- Submitted: juil. 22 2009 16:58
- Last Updated: juil. 22 2009 16:58
- File Size: 27,52 Ko
- Views: 29
- Downloads: 6
Download XDFSExtract05
XDFSExtract v0.5a: X-Box .iSO File Extractor
--------------------------------------------
Release Date: 06.22.2002
Source: IPS/Team PS2Ownz
Usage: XDFSExtract <iso file> [extract path]
Notes: Don't put spaces in the filename or extract path. Extract path is
optional. If it isn't there it'll use the current running directory.
Example #1:
-----------
XDFSExtract MyHelloWorldProgram.iso x:\temp\repack\ will extract
MyHelloWorldProgram.iso located in the current working directory to
the x:\temp\repack directory
Example #2:
-----------
XDFSExtract x:\temp\MyHelloWorldProgram.iso will extract
x:\temp\MyHelloWorldProgram.iso to the current working directory.
Example #3:
-----------
XDFSExtract x:\temp\MyHelloWorldProgram.iso z:\repack will extract
x:\temp\MyHelloWorldProgram.iso to the z:\repack directory.
Description: This project began as an XDFSLister for 'Extract Tool' which will
print out the contents of a XDFS formated iSO file in a format 'Extract Tool'
can use. As of today, this latest utility (v0.3) is NO LONGER a lister... it's
now an *extractor* to aid in pulling data from .iSO format files. Enjoy! =]
/IPS & Team PS2Ownz
Changes in v0.5
---------------
- New file I/O routines implemented
- Now tells you what its extracting while it goes
I almost completely rewrote all the I/O routines so it *should* extract most
XDFS ISOs out there. (I haven't tested them all but I did test a few problem
cases and it worked fine on them so I can hope ![]()
Problems with the previous version is that it didn't work on some images. The
reason being that you cannot use standard I/O calls to do these images. Any
attempt to seek past a signed long data type (ie past approx 2,147,483,645 bytes)
will fail using standard I/O calls.
Changes in v0.5a
----------------
- Bug fix in file I/O routine
Found small bug where I forgot to use a 64bit number in one routine (doh!) and
it failed after it tried to access anything over approx. 4,294,967,295 bytes. I
fixed it so now its handling all the files I have thrown at it. ![]()











