Free Vast on Memor32.. AU PS2

[Paradigmsick]

Can some1 tell me step by step how to install FreeVast onto Memor32.. My game discs are becoming increasingly scratched and i got ot the point where I need to take images of them otherwise they cant be copied any further. Memento was a disappointment, why cant they tell ppl the truth on their website.
I have:
1. Australian Ps2 slim console
2. Memor32 with Memento 1.1 firmware on it.

I can load elf files from USB or the MC itself... can some1 give me a step by step procedure to what I can do to play backups with this seemingly very expensive memory card (memor32)! with Free Vast or Free MC boot (ps i dont know the difference)...

kind regards.

[coolaan]

Get FMCB 1.5 , run it .

Get ESR r9 . Rename the dvd direct version to BOOT1.ELF and put it in your mc0:/BOOT/ directory.

Now switch of the console. put a memento patched or ESR patched dvd disk . Close the lid. push and hold R1 and switch on ur console. Ur back up shd boot just fine...

After you have all these, experiment with ur self for diff options in FMCB cnf .

[codone]

FYI, I installed FMCB and ESR R9 on my Memor32 (it has Memento 1.1 installed) last night and ran into a problem. When I tried to install FMCB 1.5, it locked up at some point. I powered the PS2 off and on, and loaded the install for FMCB again, and this time used the "format MC" option. Then it installed fine on the Memor32.

It seems that sometimes the FMCB install can conflict with the Memento firmware (or files). You might also have to format, and re-flash Memento 1.1to it, to keep the Memento "R1" boot functionality. I setup the FMCB config to default to BOOT.ELF (which is ESR R9), and then I setup the R1 (in FMCB) to be BOOT1.ELF which is ULaunch.ELF. So if I boot up without pressing anything it boots ESR, if I hold R1 it goes to Ulaunch. I never boot the actual Memento code anymore, but Memento was necessary to initially get the files (ESR, Ulaunch, and FMCB installer) onto the card (using the "Memor32 Savegame Manager"), and get Ulaunch.ELF going the first time.

If you can't get it all figured out, I will try to help you step by step. coolaan has laid it out the basic steps already.

[Paradigmsick]

ok, I have managed to install FMCB on my memor32 using uluanch... and its successfully completed.... Now i have a mortal kombat backup that I would usually play with memento firmware. But now, its not working... what is this ESR r9 thingy... what does it do... do i need it to load the games...?

[clemsche]

I tried to install FMCB 1.5 on my Memor32 with FW 1.2e and all I got was a black screen. I think they both conflict because they're using nearly the same technology to start homebrew/ELFs.
So the best thing would be to get another MC (they're quite cheap around 10€ for 16MB) and put FMCB on it and sell the Memor32 or keep it as a backup solution when FMCB fucks up... Which would never go happen, I think :lol:

[TnA]

FYI, I installed FMCB and ESR R9 on my Memor32 (it has Memento 1.1 installed) last night and ran into a problem. When I tried to install FMCB 1.5, it locked up at some point. I powered the PS2 off and on, and loaded the install for FMCB again, and this time used the "format MC" option. Then it installed fine on the Memor32.


I think, this is due to the corrupted FAT by Memento.

[Paradigmsick]

dude this is what u do
1. backup then format memor32 (to eliminate errors)
2. Flash the memor32 with the memento firmware
3. Find a Ulaunch.elf file somewhere and download the .elf file for FCMB
4. after flashing memor32 with memento... upload a BOOT folder with savegame manager.. and rename the Ulaunch.elf file as BOOT.elf also put the .elf file for FCMB
5. put the memory card in ur PS2 and hold down R1.
6. A grey screen should come up with a directory tree... browse to find the other .elf file that is the FMCB elf file... load it.. press select to erase the memory card... then select normal install

[codone]

ESR is like the Memento firmware, it runs a PS2 game that's been patched with the Memento ISO patcher, or bootsector's Java ISO patcher. It's what "runs" the PS2 game. FMCB is what boots ELF files (like ULAUNCH or ESR). So when you power on, FMCB takes control and launches BOOT.ELF, which you should have as ESR. Then ESR runs and does all kinds of magic and runs the PS2 game.

The Memor32 does work just fine with FMCB and ESR, I'm using mine now. I absoultely love this card since it has 32mb of space, and it is easy to pop onto the USB port and backup/restore my PS2 saves.

Just a little hassle of needing to format it first, and reflashing it with Memento to get things rolling. Okay, I am going to try to lay out step by step of one way to do this!

(1) Get the Memor32 in a state where it's able to use the Memento ELF booting
functionality (need to be able to hold R1 to boot the BOOT.ELF file).
(2) Use the SaveGame Manager on the PC to:
---(a) First make a BOOT directory
---(a) Copy ULAUNCH.ELF to card as BOOT\BOOT.ELF
---(b) Copy FMCB15.ELF to card as BOOT\FMCB15.ELF
(3) Boot the PS2 holding R1 which will activate BOOT.ELF (ULAUNCH.ELF)
(4) In Ulaunch, browse to BOOT where FMCB15.ELF is and start it (hit the O button)
(5) Install FMCB - if it hangs, you need to restart, get back to this step
but instead of installing FMCB, choose the Format MC option. Then try
re-flasing the Memento 1.1 firmware and try again to install FMCB. (I had the lockup here, and did this.. fixed it for me)
(6) Now FMCB is installed, and it's all set to boot "BOOT.ELF if you don't push any
buttons, and if you hold R1, it's set to boot BOOT1.ELF. Now we need to setup these
two files.

(6a) Using the SaveGame Manager, copy the ESR.ELF (ESR beta r9 dvdv direct.elf) as BOOT.ELF -- this way it will just autoboot your PS2 game backup if when you power on the PS2.
(6b) Copy ULAUNCH.ELF as BOOT1.ELF -- this will allow you to hold R1 and get into ULAUNCH, in case you want to mess around with copying files or something in the future. This step isn't required, it's just a good idea.

THATS IT... you are ready to go! You will know it's working because you will see the ESR splash screen (yes, the splash screen is very handy)... Also, be sure to hold R1 and test that ULAUNCH comes up instead!

[TnA]

Just a thought,...
It should be possible, to have both updates on 1 Memor32-MC (and also are able to load both).

[coolaan]

@codone,

if u put FMCB and BOOT.ELF in ur mc:BOOT first and then try to format ur mc, wont there be any issues??

I would recommend booting til ULE screen.
then
Put the FMCB in a pendrive or something, also keep the BOOT.ELF ( ULE or ESR as u wish) along with ur FMCB. Now start FMCB, format, install. ur boot.elf will be automatically copied. If u put ULE as BOOT.ELF , then copy ESR direct version as BOOT1.ELF to the BOOT directory of ur mc.

Now either can boot ur backup(patched) directly by switching on the console with R1 held or u can start ULE and browse to the ESR elf and start it . Both methods will work.


Of course this method removes r memento s/w from ur card. U need to reflash it suing memnto again for it to come back. But then again r FMCB dies if u do that ;)

[Paradigmsick]

dude i do that .. put a memento patched game and it first shows the sony corpartion splash screen then blank screen

[coolaan]

Just a thought,...
It should be possible, to have both updates on 1 Memor32-MC (and also are able to load both).

Tna, an mc can have only one osdmain.elf which the console boots. Another suggestion would be install memento and use its func to boot ESR. I am not sure if Memento contains the cd initialization routines that ffg implemented. But I think it does. Then again I may be wrong ;-)

[coolaan]

dude i do that .. put a memento patched game and it first shows the sony corpartion splash screen then blank screen

Can u start ur console with no dvd in the tray and lid closed? Do u boot to the ULE u put as BOOT.ELF ?

[TnA]

Tna, an mc can have only one osdmain.elf which the console boots. Another suggestion would be install memento and use its func to boot ESR. I am not sure if Memento contains the cd initialization routines that ffg implemented. But I think it does. Then again I may be wrong ;-)

I think, we can have multiple encrypted elfs on mc (<-- matching the Id) and start it:

1st: Load encrypted ELFs through OSDSYS (<-- ...with available given source. It may possible to load not encrypted later,... I don't know yet.)

2st: Use Memento and FMCB on 1MC.


How?:

Load OSDSYS --> Patch "MC-Update" location to given path, where the new "Update" should be (<-- This was the old way, how the "Loop" in old FMCB-Versions, when trying to start the Original OSDSYS, was fixed.).

So,... If someone wants to try,...

I can give some instructions (PM?), on how to do.

...
After that, FMCB has priority on card, but Memento and settings could/should still auto-boot, if well configured.
Only press a button, that is mapped to OSDSYS, or map OSDSYS to auto-boot and it auto-starts Memento.

[Paradigmsick]

No it doesnt

[TnA]

No it doesnt

You might should give a few more info.
Btw: You have no ELF, other than the OSDMAIN.ELF installed?

[Paradigmsick]

Where does the ESD BOOT.ELF GO.... into the mc:\ BOOT\BOOT.ELF ???(just the same way the elf files are run in the memento firmware? )
or is it mc:\ BOOT.elf

[Paradigmsick]

Whats happening now.. after FRee mc boot being installed on my memor32... I put Ulaunch as BOOT.elf.... but it doesnt boot.... what happens is it loads to the main menu where it has browse memory card, system configuration and Launch Free MC boot... but that doesnt work... if its selected it just restarts the playstation.

[TnA]

Rename it to "BOOT1.ELF" and place it on "mc?:/BOOT/".
Press R1, when you boot up.

Edit: Use "RESCUE.ELF" on Mass, to boot-up again (no need of re-flashing all. FMCB is sucessfully installed!)!

Rename the ELF from uLE to "RESCUE.ELF" and place it on USB-Mass.
uLE should auto-start, (equal/)regardless of what you're doing.

Then just do, what said above.

...or maybe you can copy it with Memor32's Save-Manager easily. ^^

[Paradigmsick]

Rename it to "BOOT1.ELF" and place it on "mc?:/BOOT/".
Press R1, when you boot up.

Edit: Use "RESCUE.ELF" on Mass, to boot-up again (no need of re-flashing all. FMCB is sucessfully installed!)!

Rename the ELF from uLE to "RESCUE.ELF" and place it on USB-Mass.
uLE should auto-start, (equal/)regardless of what you're doing.

Then just do, what said above.

...or maybe you can copy it with Memor32's Save-Manager easily. ^^

BLANK SCREEN! thats all it loads... nothing... are u sure free mc boot works for australian ps2's.. its different from the US crap

[TnA]

It should, if you have seen the third OSD-Entry.

How did you do it?
Did you tried the RESCUE.ELF?
Does FMCB still boots, or only BSOD yet?

[Paradigmsick]

How did you do it?
Did you tried the RESCUE.ELF?
Does FMCB still boots, or only BSOD yet?

dude... I tried the rescue.elf in the usb flash drive and it went to blank screen...
FMCB i dont know if that has ever booted... it just boots to the ps2 menu to either browse, system configuration and the third option... "Launch Free MCBoot"

[TnA]

Eeeerm,... There is a Quote-Button in the right corner of every post.
It is very useful, for better visibility. ;)
Is it named with "CAPITAL LETTERS"?
Did you tried the different "BOOT(x).ELF"s? x=1-4
Do you have a FMCB-CNF-Icon (<-Config) in your "MC-Saves"?

[Paradigmsick]

Eeeerm,... There is a Quote-Button in the right corner of every post.
It is very useful, for better visibility. ;)
Is it named with "CAPITAL LETTERS"?
Did you tried the different "BOOT(x).ELF"s? x=1-4
Do you have a FMCB-CNF-Icon (<-Config) in your "MC-Saves"?

Nah I dont see config of anything... i see nothing that says ESD or FMCB except that menu option that says "launch Free MC boot" Do u think i should try like 1.4 instead of 1.5 or something

[TnA]

I mean under Save-Icons.

[Paradigmsick]

I mean under Save-Icons.

yea i see the freemcboot under the saves icon and its like 100kb or some thing

[TnA]

Can you also see FMCB-CNF? (<--CONFIG)
(...only a few KB, not that big. :-/ )

[Paradigmsick]

Can you also see FMCB-CNF? (<--CONFIG)
(...only a few KB, not that big. :-/ )

yea its there

[TnA]

You can delete it.
But beware, that it is the Config-Folder (CNF) and not the Exploit/Loader-Folder!!

[Paradigmsick]

and that will make it work >

[matt_nz]

Rename it to "BOOT1.ELF" and place it on "mc?:/BOOT/".
Press R1, when you boot up.

Edit: Use "RESCUE.ELF" on Mass, to boot-up again (no need of re-flashing all. FMCB is sucessfully installed!)!

Rename the ELF from uLE to "RESCUE.ELF" and place it on USB-Mass.
uLE should auto-start, (equal/)regardless of what you're doing.

Then just do, what said above.

...or maybe you can copy it with Memor32's Save-Manager easily. ^^

I was having the same problem as Paradigmsick (I'm using AU/NZ PS2 also btw) and copying RESCUE.ELF onto a USB drive and then booting with that got it working for me.

I then copied BOOT.ELF and BOOT1.ELF from the USB drive across to the memory card using uLE and now all is working fine from the memory card.


It seems like the Memor32 save game manager doesn't want to transfer the ELF files in the BOOT folder after installing the FMCB for some reason. You can see in the Memor32 save game manager that the BOOT folder size is only 6k even after you try to do a restore with the 2 boot ELFs.


Anyway thanks for all the posts in this thread. Was a great help! :)

[TnA]

@Paradigmsick:

If you have BOOT1.ELF in BxDATA-SYSTEM, or BOOT and hold R1 while restart, it should.
You can also try to reconfigure the CNF, if you get it in a way (like Memor32s Savegame-Manager.)

Edit: Oh,... I see...
I really doubt, it (<--the Savegame-Manager-Issue) is because of the "proper" filesystem from FMCB, or was FAT-Trick from FMCB involved?

Btw.: @Paradigmsick: Is the ELF really renamed to "RESCUE.ELF" in BIG CAPITAL LETTERS? :D

It also reminds me to the "Issues", someone mentioned with uLE.
I know this effects from elsewhere, but my doubts surly can be wrong.

[remax]

I was having the same problem as Paradigmsick (I'm using AU/NZ PS2 also btw) and copying RESCUE.ELF onto a USB drive and then booting with that got it working for me.

I then copied BOOT.ELF and BOOT1.ELF from the USB drive across to the memory card using uLE and now all is working fine from the memory card.


It seems like the Memor32 save game manager doesn't want to transfer the ELF files in the BOOT folder after installing the FMCB for some reason. You can see in the Memor32 save game manager that the BOOT folder size is only 6k even after you try to do a restore with the 2 boot ELFs.


Anyway thanks for all the posts in this thread. Was a great help! :)

I have perhaps an idea about your problem : if you use M32 SGM to transfer files to your BOOT folder on your MC,

this is the method YOU MUST NOT FOLLOW :
1) Download the BOOT folder on your MC onto your computer (create a BOOT folder on your PC)
2) Put any file (let say EXAMPLE.ELF) in the BOOT Folder on your PC
3) Delete the BOOT folder on your MC
4) Upload back the BOOT Folder.

You would expect to upload the EXAMPLE.ELF with this method, but in a fact, there is a little file (can't remember the name) with Folder information in it so that i won't take the added EXAMPLE.ELF into account when uploading, resulting in no EXAMPLE.ELF on your MC.

The trusted way is to erase this little file BEFORE uploading back!

[matt_nz]

I have perhaps an idea about your problem : if you use M32 SGM to transfer files to your BOOT folder on your MC,

this is the method YOU MUST NOT FOLLOW :
1) Download the BOOT folder on your MC onto your computer (create a BOOT folder on your PC)
2) Put any file (let say EXAMPLE.ELF) in the BOOT Folder on your PC
3) Delete the BOOT folder on your MC
4) Upload back the BOOT Folder.

You would expect to upload the EXAMPLE.ELF with this method, but in a fact, there is a little file (can't remember the name) with Folder information in it so that i won't take the added EXAMPLE.ELF into account when uploading, resulting in no EXAMPLE.ELF on your MC.

The trusted way is to erase this little file BEFORE uploading back!

Ahh.. Yes I think I did what you describe above (trying not to lose anything in the BOOT folder).

I can see there are a couple of small 1k files m32info and icon.sys.memsomething that both look to contain a list of the files in the directory.. must be one of those right?

[codone]

It seems like the Memor32 save game manager doesn't want to transfer the ELF files in the BOOT folder after installing the FMCB for some reason. You can see in the Memor32 save game manager that the BOOT folder size is only 6k even after you try to do a restore with the 2 boot ELFs.


Anyway thanks for all the posts in this thread. Was a great help! :)

I also had a problem copying the new files using the SaveGame Manager, but I fixed it by loading the SaveGame Manager, selecting the Boot directory on the MC, deleting it... Then doing the "restore" from the PC, then it worked (just trying to restore over the Boot directory didn't work). I tihnk I did clean out the "extra" files, and left the ELFs only!

So be SURE on the PC side that you only have the BOOT directory, and the ELF files!!! Be sure to delete the BOOT directory off the MC when you go to transfer it over from the PC.

[Paradigmsick]

OK boys, this is how I got it working,


1. Use memento to install FREE MC BOOT 1.5

2. Use savegame manager to delete the BOOT folder on memor32... and upload a BOOT folder that has the two elf files... BOOT.elf as ule and the other BOOT1.elf as ESR r9 and bang it works


Now i hope I can back up vice city stories and see if that works... cos memento couldnt run the backup...

Oh also.. does any1 know, if I can run memento.elf the 1.2e version through Ule although 1.2e is for NTSC ps2s thanks

[coolaan]

OK boys, this is how I got it working,


1. Use memento to install FREE MC BOOT 1.5

2. Use savegame manager to delete the BOOT folder on memor32... and upload a BOOT folder that has the two elf files... BOOT.elf as ule and the other BOOT1.elf as ESR r9 and bang it works


Now i hope I can back up vice city stories and see if that works... cos memento couldnt run the backup...

Oh also.. does any1 know, if I can run memento.elf the 1.2e version through Ule although 1.2e is for NTSC ps2s thanks

Use can kiss that idea bye bye for the time being coz that file is encrypted and still now we have been able to break the sony encryption. But we do have a decrypted version but Im not sure if anyone had success in launching it.

[codone]

You won't ever want to run Memento to boot a PS2 backup again after you use FMCB+ESR !! :)

[tallpaul]

Ok Paradigmsick, thankyou for finding the Answer
Now can you make it nice and simple,
for someone new who has just bought a Memor 32 card
Like the link to download the files ( i found this one out)
1) http://www.4shared.com/dir/1945566/e6c9e655/sharing.html

then do I burn the fee mc boot 1.5.rar file to cd after unzipping it
then use memor32 in ps2 to load (fee mc boot 1.5.rar on cd)
run it & load it onto mem32
then do i unplug from ps2 goto PC and use gamesave manager to put
esr beta 9 onto memor 32 card, after deleting the boot file I just put on ?

It would be nice if you could write out a simple step by step post so when anyone wants to do it they just goto your post.

or a link to the files we just use gamesavemanager to load onto memor32

I found another link that got ulancher onto a 8mb memory card & it comes up with ulauncher on the ps2 browser, but then it does not boot my backups,
comes up with
"this dick cannot be played due to regional restrictions"
I did the open/close tray trick, goto m/c card data before inserting disk
nothing works still get "this dick cannot be played due to regional restrictions"

So Im starting to think im just not smart enough to follow these instructions

Regards tallpaul:mad::wow::yawn::cry:

[remax]

Ahh.. Yes I think I did what you describe above (trying not to lose anything in the BOOT folder).

I can see there are a couple of small 1k files m32info and icon.sys.memsomething that both look to contain a list of the files in the directory.. must be one of those right?

yes the m32info is certainly the file you must delete ;)

Perhaps also the icon.sys.blahblah (don't know, have to test).

Myself i just create a new folder everytime i upload something to my MC just to be sure.

[dlanor]

yes the m32info is certainly the file you must delete ;)
Yes, that one is obviously specific to the Memor32.

Perhaps also the icon.sys.blahblah (don't know, have to test).
NO!, "icon.sys" is the standard filename used by Sony (and all who follow Sony specs) to define an icon and game title to be shown in the Sony browser. The icon itself is normally stored as a separate file, with only its name appearing in "icon.sys" (with exception for B?DATA-SYSTEM). If the "icon.sys" file is removed from any MC folder, then that folder will be shown as corrupt in the Sony browser.

Myself i just create a new folder everytime i upload something to my MC just to be sure.
That's OK for most stuff, but if you want it visible in the Sony browser you should add an icon definition too. This can be done in the uLE FileBrowser, using its "New Icon" command.

Best regards: dlanor

[remax]

Yes, that one is obviously specific to the Memor32.

NO!, "icon.sys" is the standard filename used by Sony (and all who follow Sony specs) to define an icon and game title to be shown in the Sony browser. The icon itself is normally stored as a separate file, with only its name appearing in "icon.sys" (with exception for B?DATA-SYSTEM). If the "icon.sys" file is removed from any MC folder, then that folder will be shown as corrupt in the Sony browser.


I know that but i'm affraid it contains information relative to the folder in it. It's not a standard icon.sys but a file named icon.sys.something. There must be the history in it too and perhaps other information normally not in the icon.sys file. I haven't had a look at it. That's why in order to be sure to avoid the problem of file not taken in account when uploading, i say that it might be necessary to erase this file too (though not probable in my opinion).

That's OK for most stuff, but if you want it visible in the Sony browser you should add an icon definition too. This can be done in the uLE FileBrowser, using its "New Icon" command.

Best regards: dlanor

Ah! don't know about the new icon command nice one. When i do what i mentionned (new folder), i add a real icon.sys each time too. I know my icon.sys don't have information in it, i'm not sure it's not the case of the icon.sys.something of the SGM ;)