PSP-Tribe Downloads: DAX ZISO Loader 0.62

Benvenuto visitatore. Se non lo hai ancora fatto registrati qui.

PSP Homebrew Downloads

PSP TRiBE Files :: Loaders and Individual Launchers :: DAX ZISO Loader 0.62

DAX ZISO Loader 0.62

This is a tool that lets you load isos(backuped from your original umd's) compressed in dax
format (a custom format, compressor and decompressor are included).

Requeriments:

- 1.50 firmware

- UMDEMULATOR 0.8c (optional, daxziso already incorporates in his core the UMDEMULATOR core)

- Optional: RUNUMD (for some 2.XX games) A modified version of MPHGL is included.

Instructions:

- Copy the folders PSP and DAXZISO in the root of your mem stick.

- Compress your iso with the DAX Creator tool that is in this package.

- Copy your compressed iso (.dax) to ms0:/ISO or alternatively to ms0:/UMD

- Execute DAX ZISO Loader. Select your iso (normal or compressed) or "Run inserted UMD", press
X to start inmediatly the iso/umd with the previously saved config, or press square to go to
the configuration screen.

Configuration screen: you'll have to choose the emulation mode and other parameter.

* Explanation and compatibility of differents emulation modes:

- Off: the iso won't be emulated and the program will exit to the system menu. This method
only has sense if you want to emulate the flash0 & flash1.

- System menu. It returns to the system menu, letting you to load the game through the system
menu or another loader like mphgameloader or FastLoader("Start inserted UMD").
This is one of the most compatible modes, it is more compatible than the UMDEMULATOR
system menu.

- Direct load. It will directly load your iso. At the moment, it seems that this mode is
less compatible than the "System menu" and "Direct LoadExec" ones. Be always sure
that you try the different modes to see which one is the best for your games.

- Copy load. It will copy the game boot.bin file to ms0:/DAXZISO/DBOOT.BIN and it will
load-exec it.

- MPHGL Direct. This mode needs the file "ms0:/DAXZISO/mphloader.prx" of the
MPHGameLoader application, which is already included.

Note that this is a modified version of mphloader.prx which will search the flash0 and
flash1 in ms0:/DAXZISO/flash0 and ms0:/DAXZISO/flash1. If you want still use the older
folders at ms0:/MPHGameLoader/flash0 and ms0:/MPHGameLoader/flash1, simply replace the
mphloader.prx of DAXZISO with the original one from ms0:/MPHGameLoader/mphloader.prx

It seems to be the less compatible mode of all.
It's more compatible to use the system menu one and execute mphgameloader, or the modes
"MPHGL System", "MPHGL VSHExec" and "MPHGL LoadExec".

- UMDEmulator:

This mode requires the file ms0:/DAXZISO/UMDEMU.PBP, which is already included.

This mode will load the original umdemulator letting it to load isos in dax format.
The compatibility of different load modes inside UMDEMULATOR should be more or less the
same that those from DAXZISO, although it may have some differences.

- MPHGL System. This mode returns to the system menu: in that moment you can run
your emulated umd from the system menu. Instead of executing the disc, the firmware will
execute the file "ms0:/DAXZISO/MPHGL.PBP" which will load your 2.XX game.

The required file "ms0:/DAXZISO/MPHGL.PBP" is already included.

The compatibility of this mode is greater than "MPHGL Direct" and exactly the same than
exiting to the system menu and then running mphgl.

- MPHGL VSHExec. With this mode your psp will reboot and after that it will auomatically
run MPHGameLoader ("ms0:/DAXZISO/MPHGL.PBP").

The compatibility of this mode is greater than "MPHGL Direct" and exactly the same than
exiting to the system menu and then running mphgl.

- Direct LoadExec. This mode looks like "Direct Load", but instead of using the
sceKernelLoad/StartModule functions, it uses sceKernelLoadExec; because of that, the system
will have more free memory, and this makes it more compatible than "Direct Load" and almost
as compatible as "System Menu". The only problem is that it always will run the BOOT.BIN
file (even if that option is in off), because sceKernelLoadExec fails with EBOOT.BIN.
If you have one of those game that in umdemulator only worked with copy load, try this one,
it loads faster and there are chances that it work.

- MPHGL LoadExec. This mode is as compatible as "MPHGL System" and
"MPHGL VSH Exec", but it loads faster. However it has a problem: it doesn't work depending
on the wlan switch position. In my psp, it works with the wlan position in on, but it may be
different on your psp, or even different from a game to another.

This is NOT a DAXZISO bug. I've tried to execute the mphgl eboot.pbp with other homebrews
programs that also use the sceKernelLoadExec function, and without iso emulation (original
umd), and the results where the same: depending on the wlan switch position it worked or not.
I cannot solve a bug that it's not mine.

- RUNUMD LoadExec. This mode will run RUNUMD, and it will let you load isos with it.
Because of a special patch that is applied in this mode to the UMDEMULATOR core to fix a
compatibility issue with RUNUMD, the flash0 and flash1 emulation are broken in this mode.

This mode requires the runumd pbp (folder without %) to be in ms0:/DAXZISO/RUNUMD.PBP
This file is NOT included, you'll have to provide it.

- RUNUMD System. This mode returns to the system menu. After that, you can run RUNUMD
with the disc icon of the firmware. You can also start runumd from the your memory stick if
you want.

This mode also requires the file ms0:/DAXZISO/RUNUMD.PBP and it also has the flash
emulation broken.

Note: if you use one of the other "System Menu" modes and you start runumd, it will gives
you the famous error of "patcher failed", because daxziso doesn't apply the special patch
to those modes in order to keep compatibility with flash emulation.

- RUNUMD Direct. This mode is like "RUNUMD LoadExec", but it doesn't reboot the firmware, so
it loads faster and it doesn't delete a background program from memory. The compatibility
should be less than "RUNUMD LoadExec", although it seems still to be very good.

Remarks:
* After having exited a game that you have run with a MPHGL mode, if you want to run again
the game, you can simply click the firmware UMD icon. (from this version, this applies to all
mphgl modes).

* The same for RUNUMD modes.

- Option "Allocate tables in RAM". If your game worked well in version 0.3, leave this parameter
to "on", because decompression will be faster than in "off". If you game didn't work in version
0.3, set it to off: that will decrease memory use and increase compatibility.

- The other parameters are handled by the UMDEMULATOR core and their meanings are the same than
in UMDEMULATOR.

- To quit ISO emulation, execute the loader and press triangle.

The loader will remember the configuration of each iso (in umd it will only have a configuration
for all umd's at the moment).
The configuration files are saved in the ms0:/DAXZISO/CONFIG directory, with the name
"[name of iso including extension/s].ini" (example: megaman.iso.dax. -> megaman.iso.dax.ini)

If you want to share the settings of your games with your friends, you can zip the config
folder and send it to them, but remember that all of you have to use the same file names.

You can also have a custom background for each iso.
Backgrounds can be stored now in a lot of manners to make things easier, in either the folder
ms0:/ISOMISC or ms0:/DAXZISO/BACKPIC

Better an example than an explanation. If you have an iso called "Tales_Eternia.iso.dax", the
program will search a background in the following order:

ms0:/ISOMISC/backpic_Tales_Eternia.iso.dax.bmp
ms0:/ISOMISC/backpic_Tales_Eternia.iso.bmp
ms0:/ISOMISC/backpic_Tales_Eternia.bmp
ms0:/ISOMISC/Tales_Eternia.iso.dax.bmp
ms0:/ISOMISC/Tales_Eternia.iso.bmp
ms0:/ISOMISC/Tales_Eternia.bmp
ms0:/DAXZISO/BACKPIC/backpic_Tales_Eternia.iso.dax.bmp
ms0:/DAXZISO/BACKPIC/backpic_Tales_Eternia.iso.bmp
ms0:/DAXZISO/BACKPIC/backpic_Tales_Eternia.bmp
ms0:/DAXZISO/BACKPIC/Tales_Eternia.iso.dax.bmp
ms0:/DAXZISO/BACKPIC/Tales_Eternia.iso.bmp
ms0:/DAXZISO/BACKPIC/Tales_Eternia.bmp

The background must be 24 bits color bmp's, and with a resolution of 480x272 pixels.
Otherwise, the program will paint a white background to let you know that the file was in
an incorrect format.

FAQ:

- Q: Will support DAX ZISO Loader more common formats of compressed files like .zip, .rar, .gz?
- A: NO. I already did testings with .zip and .gz files, and the EXIT JAP iso was still loading
after more than 10 minutes. The problem with those files is that the seeking is really slow.
That was the main reason behind creating an own format. The DAX format is very similar to
the .Z/.Z.table concept, except that it's only one file and other few changes.

-Q: Can DAXZISO load normal (non-compressed) isos?
-A: Yeah, no problem.

-Q: Can i have inserted a video UMD instead of a game UMD?
-A: yes, but you need a special configuration. In disctype ISO, select the type of your iso, not
your real umd. In disctype UMD, select the type of your real umd (in this case video).
Set regioncode override to on, and put all region codes to regionfree.

Changelog:

- 0.62. May, 18

* A bug originally from the UMDEMULATOR core has been found. UMDEMULATOR didn't handle the
case where the string pointed by the parameter file (sceIoOpen, sceIoOpenAsync), or dev
(sceIoDevctl) was not aligned to 4 bytes, causing an exception when that happened.
That caused incompatibility with some games (Coded Arms, Mahjong Fight and maybe others),
and some homebrews (FileAssistant++, Irshell and maybe others).
Fixed. People, try again all the games that worked with fastloader and not with umdemu to
see if they work now. Thanks a lot to the person who discovered the bug, well done!!

* Now daxziso prx's and default backgrounds are in ms0:/DAXZISO. Also, moved from newlib to
pspsdk libc to reduce the size of the executable.

* Added an "experiment" to play games via usb in Direct Load, MPHGL Direct, and RUNUMD Direct
modes.
This need files from psplink, which are not included. (you only need usbhostfs.prx in
the psp part, and a driver and usbhostfs_pc in your computer, and edit the daxziso.ini file).