Here's some libxenon goodies to help people get started. I hope this is "newbie friendly" (because n00b sounds offensive
).
Tools:
So once you have XeLL Reloaded (latest version at time of this post is v0.991), you're probably wondering what to do with it. You have two options from here:
- Update the XeLL portion of your NAND
- Use XeLLLaunch (part of DashLaunch) to run the XeLL binary
I should point out that if you update that portion of the nand, then you will be unable to use XeLLous' built-in nand flashing feature, as it hasn't been added to XeLL Reloaded (yet). There is xex for flashing JUST the XeLL portion of the NAND, however I'm not sure if it's XDK or not, so I won't upload until I'm sure.
If you're unsure of which to do, then go with option 2, as that won't change your NAND at all. Your XeLL binary file must be in the same folder as xelllaunch. Your libxenon/homebrew files, on the other hand, will go elsewhere.
Setting up libxenon files:
If you are using a MS/Internal hard drive, then you will need to get a USB stick or USB hard drive to run any libxenon homebrew, right now. It must be formatted as FAT32.
Any libxenon application you put on the drive will need it's program folder to be in the root of the drive. For example, Mupen64 comes with a folder called 'mupen64-360', and a file called 'xenon.elf'. Pcsxr-xenon comes with a folder called 'pcsxr' and a file also called 'xenon.elf'. You will need to rename both of the .elf files to whatever you want, but extract everything so your usb drive looks like this:
CODE
pcsxr/ (Directory)
Mupen64-360 (Directory)
pcsxr.elf *renamed from xenon.elf*
Mupen64.elf *renamed from xenon.elf*
Now, let's also add the 'kboot.conf' file (found in XeLL download) to the root of the USB drive, and then open it in a text editor. Ignore the beginning, and towards the end you will see 'Linux/ELF BootMenu'. This is where we will edit the file:
QUOTE
# Linux/ELF BootMenu
# Supplying boot-entries is optional - you can delete those from the config to just set "General XeLL options"
; label of the default bootentry -
; If no value is set/set invalid/commented, XeLL defaults to first bootentry
default=zlx_browser
; timeout of the bootmenu in seconds - timeout=0 skips user input completely!
timeout=10
; Kernel / Bootentries
; ! first parameter: kernel path !
pcsxr="sda:/pcsxr.elf"
zlx_browser="sda:/zlx_browser"
nullDC_usb="uda:/nulldc-360.elf"
Mupen64="uda:/Mupen64.elf"
As you can tell, I removed quite a bit from the bottom, and changed my menu entries. The 'default=' entry above is what you can have it auto-launch when your timer reaches 0 (set the timer in the 'timeout' section below it). It looks for the name according to the menu you setup below, so for my example, valid choices for a default launch item would be 'default=pcsxr' or 'default=Mupen64', etc.
One last note about pcsxr-xenon and using bzip'd isos:
Ced2911 has done an excellent job on this emulator so far, and despite all the things it does wonderfully, there are still quite a few issues to sort before it's perfect. The most common problems are freezing during long/multiple loads, audio glitch(ier), and RSOD errors. If you're backups are uncompressed, then the solution is to run cdrcimg on them. Just put cdrcimg.exe in a folder with your psx images, and drag an image file onto the program and it will auto-run. When it is complete, you will have 2 new files: a compressed bin image of your iso, and a table file. The reason cdrcimg creates such a big improvement in performance is not because it's compressing the iso, but because it gives a nice table to help anything trying to execute the information in that iso, to help it find all the addresses easier.
I hope that helps get a few people started; if you have questions I will try and help, but you may want to create an account on the libxenon forums or at least bookmark them to keep up with certain developments.
Author
Topic: PCSXR Xenon v0.62 (Read 2704 times)