n00b questions...

[Cannibal Corpse]

Hi All,

first of all I am glad to be part of these great forums, you guys know your stuff!

OK, I have a v7 PS2 (USA) system, no MOD chip installed, am using the exploit method via AR MAX EVO (w/ USB Pen Drive). I have some questions:

The original BADATA-SYSTEM.max that was posted by Dv8 contains the following files:

BOOT.ELF
EXECFTPS.ELF
EXTRACONF.DAT
IOMANX.IRX
IPCONFIG.DAT
PS2DEV9.IRX
PS2IPS.IRX
PS2LINK.ELF
PS2NETFS.IRX
PS2SMAP.IRX
TITLE.DB
history
icon.sys

1) Can I simply delete everything *except* BOOT.ELF and TITLE.DB and then replace this BOOT.ELF with ULanunchELF's BOOT.ELF?


2) Better yet, could you post the one that you are using yourself?

3) Since I have been using the exploit with AR MAX EVO with USB Pen Driver, is there an easier method to transfer these to my Memory Card? The process of "Uncrushing" the contents of the USB Pen Drive to my Memory Card is PAINFULLY slow!

I really appreciate your help!

[Cloudhunter]

Yes, you should be able to remove everything else

There is no better way, but with only the BOOT.ELF it shouldn't take too long. You only have to do it once anyway

[Cannibal Corpse]

Thanks! Funny thing is that my user name over at PS2HD is C0deHunter!

OK, I have the latest version of ULauncher.elf, the latest version of HDLoader .8b, provided I follow this tutorial, it should work, right?

http://exploitstation.com/articles/a...xploitUSB.html

[dlanor]

Yes, you should be able to remove everything else

No, not *everything* else. As that would also remove the system files "icon.sys" and "history". Those are preferably never to be touched by human hands, so to speak. "history" will be regenerated later anyway, even if removed, and in some circumstances so will "icon.sys". But the point is that without the "icon.sys" file the PS2 BIOS regards this folder as invalid. It's just barely possible that the exploit can continue working then, but I wouldn't bet on it.

The only reason why the exploit works is because the PS2 BIOS regards that folder as a valid system configuration save. And each such save (only one per MC) must have a special "icon.sys" file, quite different from the ones used for normal gamesave folders.

The minimum content for a valid exploit folder is:

icon.sys -- To validate this folder to the PS2 BIOS
TITLE.DB -- The exploit trigger code (really PS1 interpreter patch lookup)
BOOT.ELF -- The ELF to be launched by exploit

To this a fourth file will eventually be added:

history -- Automatically created by the PS2 BIOS for various operations

Best regards: dlanor

[Cloudhunter]

My apologies, wasn't thinking straight. I automatically assumed he meant all files aside from them.

Cloudy

[dlanor]

The original BADATA-SYSTEM.max that was posted by Dv8 contains the following files:

----- snip ----- re: file listing

These are the ones you should be using with uLaunchELF

BOOT.ELF -- Replace it with the one from uLaunchELF release
TITLE.DB -- This should work as-is even with a new BOOT.ELF
history -- Used by PS2 BIOS
icon.sys -- Required by PS2 BIOS
LAUNCHELF.CNF -- optional settings file (you may prefer "mc0:/SYS-CONF/")

1) Can I simply delete everything *except* BOOT.ELF and TITLE.DB and then replace this BOOT.ELF with ULanunchELF's BOOT.ELF?

Not quite, but the info above should clarify it.

2) Better yet, could you post the one that you are using yourself?

No, that would be a little messy, and also inappropriate, as I use a PAL console.

3) Since I have been using the exploit with AR MAX EVO with USB Pen Driver, is there an easier method to transfer these to my Memory Card?

Once you have uLaunchELF installed such things will be easy. You'll simply use the uLE browser to copy stuff directly off your USB drive, or directly from a networked PC (if you have a network adaptor).

The process of "Uncrushing" the contents of the USB Pen Drive to my Memory Card is PAINFULLY slow!

Doing it once to get started should be acceptable though.

After that, you'll probably never do it again. In fact that is what I recommend, as the ARMax methods are known to corrupt memory cards. And with uLE installed you have much better ways to handle gamesave backups anyway.

Best regards: dlanor

[Cannibal Corpse]

Thanks so much for your response, I really appreciate them!

The question that I have is, that I tried to create a Title.db file using this guide:

http://exploitstation.com/articles/a...xploitUSB.html

But no matter what I do, the this .max file is being read as NEW_FILE (instead of BADAT-SYSTEM).

The guide says you can name this .max file anything (well, exploit.max), but to be on the safe side, I even named it BADAT-SYSTEM.max (just like Dv8's file in his tutorial), with no luck.

Would you kindly let me know what I am doing wrong?

p.s. the reason I wanted to create a title.db, is that I wanted to follow exploitation.com's recommendation when they say "Exploitstation.com strongly urges you to generate your own TITLE.DB file", otherwise, I guess the BADATA-SYSTEM.max the Dv8 provided (with 800 titles) is OK?
Thanks in advance.

[ps2dragon]

No, not *everything* else. As that would also remove the system files "icon.sys" and "history". Those are preferably never to be touched by human hands, so to speak. "history" will be regenerated later anyway, even if removed, and in some circumstances so will "icon.sys". But the point is that without the "icon.sys" file the PS2 BIOS regards this folder as invalid. It's just barely possible that the exploit can continue working then, but I wouldn't bet on it.

Aren't the "history" and "icon.sys" files already present in the BEDATA-SYSTEM or BADATA-SYSTEM folder? These files are created when you update your "System Configuration" right?

[ps2dragon]

But no matter what I do, the this .max file is being read as NEW_FILE (instead of BADAT-SYSTEM).

The guide says you can name this .max file anything (well, exploit.max), but to be on the safe side, I even named it BADAT-SYSTEM.max (just like Dv8's file in his tutorial), with no luck.

Would you kindly let me know what I am doing wrong?

The instructions are right there in the image. It tells you to rename the "NEW_FILE" text to either BADATA-SYSTEM (NTSC Consoles) or BEDATA-SYSTEM (PAL Consoles). So replace "NEW_FILE" with "BADATA-SYSTEM", then click "Save".

p.s. the reason I wanted to create a title.db, is that I wanted to follow exploitation.com's recommendation when they say "Exploitstation.com strongly urges you to generate your own TITLE.DB file", otherwise, I guess the BADATA-SYSTEM.max the Dv8 provided (with 800 titles) is OK?
Thanks in advance.

The reason why they strongly recommend you create your own TITLE.DB file is explained on the site. I have tried using this 800 game TITLE.DB file myself and it never worked for me, even though my PS1 game was listed in the file (compared the region codes). I created my own TITLE.DB file and it worked fine. Creating your own should guarantee the file will work.

[dlanor]

Aren't the "history" and "icon.sys" files already present in the BEDATA-SYSTEM or BADATA-SYSTEM folder? These files are created when you update your "System Configuration" right?

Yes, of course.
And your point is... ?

Best regards: dlanor