run PS2Browser from uLaunchElf

[zx16384]

Edit: New version in post #66

Ok, at least for my PS2 model v10 PAL [ger] i found a method to run the original OSDSYS from uLaunchElf after booting from "free McBoot" :cool:

This does need a "compatible" OSDSYS in your PS2 rom having the "feature" i use, so if it works for you - great - if it doesn't work there's nothing i can do... this uses something already present, so no patching done at all - just standard ELF loading. If the "feature" is not present you will probably get a reboot into uLaunchElf because OSDSYS will then look for updates, invoking free McBoot, ...

Attention: Do not have a disc in the drive while launching... as it is starting the unmodified, unpatched, built-in rom:OSDSYS that one will then immediately try to launch the disc instead of going to the browser. Strangely we will then get the same drive problems as in uLaunchElf. If your drive is empty and you insert the original game disc after OSDSYS has launched then the original game will run fine.

Best place to put is into the boot folder and then link it to some button in uLaunchElf instead of MISC/PS2Browser.

As I said before: No guarantee at all that this works for you, but for my PS2 it does.

[spkleader]

Well.. I tried it and it worked.
It even loaded a dvd video without booting with a disc in the drive, on a v9 machine, ntsc-u

[suloku]

Nice one, I have v9 too, so i hope that'll work for me too.

[TnA]

Works great on my PS2 V7 PAL. ;)
I leave DVD-Video-Disc in my drive and it imeadetly starts.

[zx16384]

Thanks for the feedback. I think it should work on most PS2 versions, at least the fat ones. And definitely those with ROMVER 190.

So far we have:
v7 PAL - working
v9 NTSC-U - working
v10 PAL - working

I leave DVD-Video-Disc in my drive and it imeadetly starts.

Yes, that's how it works.

It's just that if I have my Amplitude disc in the drive while booting up the PS2 with free McBoot and then go into the browser, then that original Amplitude will freeze just the same as if launched from uLaunchElf or HDLoader. If there isn't a disc in drive while launching, then the drive will get initialised correctly and Amplitude will not freeze.

[hakr007]

ok just tested it on both of my PS2s
-works on my v7 NTSC-U (fat)
-doesnt work on v14 NTSC-U (Slim)

[PALGamer]

Works on my FAT PAL PS2 (v3 or v4, dunno for sure)

Can I use this to set up my FreeMCBoot as the following?
MC in Slot 1 -> boot to browser (using ur app)
MC in Slot 2 -> boot to ulaunch

I tried it doing the following:

insert the RUNME file from lukasz blog (he updated it btw to ffgriever's file)
create a folder named BESLES-00000 MP, and fill it with RUNME1.ELF (ps2browser.elf) and RUNME2.ELF (ULE 4.13(!!))

I got a red(!?!) screen, about to try again...

[PALGamer]

Works on my FAT PAL PS2 (v3 or v4, dunno for sure)

Can I use this to set up my FreeMCBoot as the following?
MC in Slot 1 -> boot to browser (using ur app)
MC in Slot 2 -> boot to ulaunch

I tried it doing the following:

insert the RUNME file from lukasz blog (he updated it btw to ffgriever's file)
into OSDMAIN.ELF
create a folder named BESLES-00000 MP, and fill it with RUNME1.ELF (ps2browser.elf) and RUNME2.ELF (ULE 4.13(!!))

I got a red(!?!) screen, about to try again...

[zx16384]

Can I use this to set up my FreeMCBoot as the following?
MC in Slot 1 -> boot to browser (using ur app)
MC in Slot 2 -> boot to ulaunch
[...]
I got a red(!?!) screen, about to try again...

The RUNME from lukasz needs the RUNME.ELF in the "BESLES-00000 MP" folder to find out from which memcard it was booted (it just checks on which memory card the file exists!).

So you should do the following when you embed lukasz' MEMPLUS_LOADER3:

First, have a RUNME.ELF file in the "BESLES-00000 MP" folder, because if there isn't one found you get the red screen. This could be uLaunchElf, because the RUNME.ELF will be executed if there is no EXECUTE<the Slot #>.ELF found.
Then, rename the PS2Browser.ELF to EXECUTE1.ELF and put it in the same folder.

Now, when the card is in Slot 1, the PS2 Browser will run.
When the card is in Slot 2, you will get uLaunchElf ;-)

[zx16384]

ok just tested it on both of my PS2s
-works on my v7 NTSC-U (fat)

As expected.

-doesnt work on v14 NTSC-U (Slim)

Then there is nothing that can be done with my method... because that means the option to skip loading osd-updates from memory card and hard disk is not implemented in the osd of the PS2 slim.

That makes sense, as the hard disc is only available for fat models and i read somewhere on the main discussion that the slim-models got most (if not all) hard disc functions removed.

This would mean that for the slim PS2 another more sophisticated loader would be needed, which would have to load the "rom0:OSDSYS"-Image into memory (via SifLoadElf), find the place where the string "BREXEC-SYSTEM" is stored and patch it to something else, i.e. "_REXEC-SYSTEM" so the osdmain.elf couldn't be found. After patching the memory image would just be started with ExecPS2-function... Similar to what the MEMPLUS_LOADER3 from lukasz is doing to patch the datel tool to NTSC (source available at his blog (http://lukasz.dk/2008/04/22/datel-memory-plus-64-mb/)). Oh, and you wouldn't need the unpack-function his loader is calling, because the OSDSYS is unpacked after the SifLoadElf call.

I don't do any patching at all, so my source wouldn't help here.

[Mozgus]

Works on my v12 Slim. Thank you.

[Horscht]

Does not work on my PAL V4
Browser: 1.20
CD-Player: 1.20
Playstation Driver 1.10
DVD Player 1.30E

Works on my PAL V14
Browser: 1.40
CD-Player: 2.00
Playstation Driver 2.10
DVD Player 3.11E

I wonder why my PS2s behave counterwise... normaly i'd expect it to be the other way around, but clearly the V4 reboots to ule, whereas the V14 launches the PS2Browser. :confused:

[l_oliveira]

Solution:

1- Go to uLE menu "MISC" choose PS2Browser but press nothing
2- Pull memory card.
3- Press button.
4- Enjoy your PS2 browser. :P


Edit: Oh and if you need different configurations, just buy more memory cards ... Have one with your programs and the OSD boot software and let the ones for savegames alone.

[dragon131]

Not work in my v3 pal. :(.

[zx16384]

It turns out that on PS2 older than around v4 or newer than around v14 the PS2Browser launcher tool does not work, as the option to skip checking for osd-updates on memory card / hard disc is not implemented in the OSDSYS of those machines.

[hakr007]

is there any way possible to skip loading the updates from just the memory card so that it will check the hdd (in the event that we do have a hdd w/ the hdd-OSD or BBNavi)?

[TnA]

It should possible to load OSD2 and BB.Navi with MC inserted.
If Free HDBoot is possible on other HDs, than original-Sony and without MC, I'm not sure about.

[hakr007]

by your post TnA, im taking the assumption, correct me if i'm wrong, that the order it checks for updates is HD->mc->ROM. if thats the case, how would we boot w/ free McBoot if we have the hard drive?

[l_oliveira]

Actually the correct order is:

ROM > MC > HD.

The ROM OSD is aways run. When you hit the PS2browser option on uLE MISC it boots the ROM OSD which in turn finds an MC update and runs it. It never get to try booting from the HDD as it never gets to that part.

The OSD tries to detect an HDD as the words "Sony Computer Entertainment Inc" appears on the sceen with the transparent cubes plus foggy blue background.

And on my understanding this patch it does start the ROM OSD with a parameter "SkipMc" to force it skipping that process. Indeed only OSDs that can boot from "osdmain.sys" have that "feature".

This means the fix by zx16384 will only work on V4 and newer consoles. I hope this clarifies his original post about not working on some consoles.
They seem to support also a "SkipHdd" parameter as well.

<Please disregard this post as zx16384 explained everything a few posts above.>

[hakr007]

so if i have free mcboot and want to boot from the hdd osdmain, being the browser update or bbnavi, i would have to remove the MC, unless there is an option to skip checking updates only from mc.
on second note, using Zx's ps2browser, would it still check the hdd?

[TnA]

If the sectors on Disc do not match, and the HD isn't recognized as Original-Sony, it wouldn't start the Update from HD.

Power-On -->Loads OSD from ROM -->OSD searches for update on mc-->if not found start browser and search for HD-Upgrade, or Browser-Extention.
You will not need FreeMCB, as if FreeHDB will work.

AFAIK, this one skips ALL CHECKS, but I'm not sure.

[hakr007]

ok, so let me just confirm this, using ZX's ps2browser ELF, which skips the MC check, it will boot in the order of:
Power-On -->Loads OSD from ROM -->start browser and search for HD-Upgrade, or Browser-Extention.

[l_oliveira]

It looks for a file called hosdsys.elf on the "__system" APA partition.
The file hosd.sys is MG encrypted (obviously) making the HDD MG region specific

[hakr007]

ok so it will boot the update from the HDD, thanks for confirming that for me.

[TnA]

It will boot, if this "PS2Browser.elf" just skips MC-Update-Check.
I think it'll be also possible to load HD-Update with a loader (placed on MC).

[hakr007]

with a loader like the one jimmi made for freemcboot?

[TnA]

Maybe,...
And it will may be able to load from USB-HD,... :)
Only, if it will be possible to get some workarounds,...
Lets see, what the future will bring.

[zx16384]

Actually the correct order is:
ROM > MC > HD.


Yes, that's correct. And as it seems that happens very early before cdvd modules gets initialised, so that's why we get problems with uLE and disc access.


The ROM OSD is aways run. When you hit the PS2browser option on uLE MISC it boots the ROM OSD which in turn finds an MC update and runs it. It never get to try booting from the HDD as it never gets to that part.

And on my understanding this patch it does start the ROM OSD with a parameter "SkipMc" to force it skipping that process.


:shhh: That's why I said "no patching" :cool: :D


Indeed only OSDs that can boot from "osdmain.sys" have that "feature".


The order is ROM > MC "osdxxx.elf" > MC "osdmain.elf" > HD.


They seem to support also a "SkipHdd" parameter as well.


And that makes sense using it, as the ATAD from bios is known not to work with any hard disc except the official one (it does check the drive hardware)... so the PS2 Bios will never boot from any other hard disc. And spinning up the drive just to let it shut down immediately is big stress for the drive mechanics.

If at some time there would be a need for not skipping the check of hdd-update, it could be easily re-enabled in the PS2Browser.elf.

[jerrymh]

To zx16384

Excuse zx16384, there is a way to load the PS2Browser.elf whit the smooth option ON, on the ps1 driver to play PSX1 backup games whit smooth textures?

[remax]

I confirm that i had no succes lauching PS2Browser.elf on my v4, even as BOOT.ELF.

I'm a bit disapointed, as it's a feature i find very very interresting. Hope someone will find a way to fix this...

[Billkwando]

I confirm that i had no succes lauching PS2Browser.elf on my v4, even as BOOT.ELF.

I'm a bit disapointed, as it's a feature i find very very interresting. Hope someone will find a way to fix this...

Yeah, it looks like for now, we're stuck pulling the MC whenever we wanna boot to the native browser. Oh wel, no biggie.

I'll just be happy when they get backups working, so I don't have to pull the mc to use swap magic.

[TnA]

You don't need to unplug your mc.
Use atchuss's loader 3, configure it well/properly and you'll be fine.

[remax]

You don't need to unplug your mc.
Use atchuss's loader 3, configure it well/properly and you'll be fine.
As far as i know, no options of these ones allows to go to the native browser without using PS2Browser.elf...

- If you start pressing R1 then the program runs "mcX:/BOOT/R1.ELF (if exist)
- If you start pressing R2 then the program runs "mcX:/BOOT/R2.ELF (if exist)
- If you start pressing L1 then the program runs "mcX:/BOOT/L1.ELF (if exist)
- If you start pressing L2 then the program runs "mcX:/BOOT/L2.ELF (if exist)
- If you start without pressing R1,R2,L1,L2 (or the elf don't exist) then the
program runs "mcX:/BOOT/PS2.ELF (by default it can be the PS2Browser.elf to
emulate memento)

Correct me if i'm wrong!

[TnA]

Oh I see,... PS2Browser.ELF is not compatible with yours. ST.
Not with this ELF, but it is possible, to integrate this into Loader3, without the need of an external app.

Thinks this works really easy.

Load OSDSYS from rom -->
Patch Offset-Locations (of Update-Search) on the fly-->
Execute load-patched OSDSYS.

Did you tested it with loader3-method?
(afaik) You should run into an infinite-loop, if it won't work.

[remax]

Not with this ELF, but it is possible, to integrate this into Loader3, without the need of an external app.

Thinks this works really easy.

Load OSDSYS from rom -->
Patch Offset-Locations (of Update-Search) on the fly-->
Execute load-patched OSDSYS. :P

Thank you!

...but to be honest, that's far too difficult for my poor capacities as a PS2 programmer :D

[remax]

Did you tested it with loader3-method?
(afaik) You should run into an infinite-loop, if it won't work.

The only tests i did are :

-Try to launch it directly from my mc or HDD : no success, it boot back to uLE
-Try to replace the uLE BOOT.ELF by the PS2Browser BOOT.ELF : no success, it run into an infinite loop.

I think that i might have no results with loader3-method as it's quite the same as the second one...

(by the way, what default launcher is embedded by the FMB install? ffg's one or Neme's one? are these two launchers really differents?)

[TnA]

Yes I assume, this is the case. :-/

I'll take a look at some sources today.

[remax]

Yes I assume, this is the case. :-/

I'll take a look at some sources today.

thanks in advance! :)

[curtis2k8]

I have found out a way to quickboot original games by experimenting with memento but i need someone to create a ps2disc.elf. any help will be appreciated

[zx16384]

Edit: New version in post #66

This is a changed PS2Browser.ELF which does not skip hard disc booting... (and :shhh: it might work on consoles where it did not previously).

No guarantee at all that this works for you, but for my PS2 v10 [ger] and for my older v3 it does, but as the first one does work very fine for me, this newer one has only been tested very briefly (i myself don't need it). If this goes into a red screen that means it is incompatible and you should just use the "older" PS2Browser.

[jvhellraiser]

Hi everyone i would like to know exactly what use do we have when we use this how does it work or better for what? just curios.

[Billkwando]

This is a changed PS2Browser.ELF which does not skip hard disc booting... (and :shhh: it might work on consoles where it did not previously).

No guarantee at all that this works for you, but for my PS2 v10 [ger] and for my older v3 it does, but as the first one does work very fine for me, this newer one has only been tested very briefly (i myself don't need it). If this goes into a red screen that means it is incompatible and you should just use the "older" PS2Browser.

Yay! That file worked.

Thanks! :)

Edit: Oh and what's hard disk booting? I mean, it sounds obvious, but I'm just wondering about the context.

[zx16384]

Edit: Oh and what's hard disk booting? I mean, it sounds obvious, but I'm just wondering about the context.

"Hard disc booting" is only useful for people having the official genuine PS2 hard drive.

Most of us - including myself - won't need it at all. This hard disc boot will not work with any other hard drive than the "official" one and for that reason it was disabled in the "older" PS2Browser loader. In the newer version only the memory card booting is disabled, so those having the official hard drive could still use it.

Just to clarifiy:
PS2Browser.ELF ist still nothing else than a tool to launch the built-in PS2 browser from your console ROM. If you launched "MISC/PS2Browser" from uLaunchElf you would just load the same PS2 browser, but then it would first check for updates from memory card, find freeMcBoot, run it (and so uLaunchElf) again...

So this is a solution to load the original PS2 browser so that it doesn't load the freeMcBoot from memory card again, entering an endless loop.

It does nothing else, so if you have an original - genuine - game disc in the drive tray while loading PS2Browser then the built-in PS2 browser would launch that game, as that what's it supposed to do.

[Billkwando]

"Hard disc booting" is only useful for people having the official genuine PS2 hard drive.

(kind explanation)

.

Thanks man. :)

It does exactly what I hoped it would do (get me to the browser) and you definitely answered my question in the first line.

As you correctly surmised, I don't need hard disc booting at all. :)

[remax]

This is a changed PS2Browser.ELF which does not skip hard disc booting... (and :shhh: it might work on consoles where it did not previously).

No guarantee at all that this works for you, but for my PS2 v10 [ger] and for my older v3 it does, but as the first one does work very fine for me, this newer one has only been tested very briefly (i myself don't need it). If this goes into a red screen that means it is incompatible and you should just use the "older" PS2Browser.
Can't wait to test it!

[remax]

It worked like a charm! Thank you!!!

I don't understand how the Hard disc thing would prevent to launch the browser, but well now it works... It's becoming very interresting.

[zx16384]

I don't understand how the Hard disc thing would prevent to launch the browser

It didn't :cool:. The hard disc thing and the "enhanced" compatibility are two separate things. There were some requests to keep the browser looking for updates on hard disc, so this got changed, too. The other part - making PS2Browser launching work on more consoles - was much more work.

[remax]

It didn't :cool:. The hard disc thing and the "enhanced" compatibility are two separate things. There were some requests to keep the browser looking for updates on hard disc, so this got changed, too. The other part - making PS2Browser launching work on more consoles - was much more work.

Okay it's more understandable :D

[speedfly]

This is a changed PS2Browser.ELF which does not skip hard disc booting... (and :shhh: it might work on consoles where it did not previously).

No guarantee at all that this works for you, but for my PS2 v10 [ger] and for my older v3 it does, but as the first one does work very fine for me, this newer one has only been tested very briefly (i myself don't need it). If this goes into a red screen that means it is incompatible and you should just use the "older" PS2Browser.

nice work:)

[Mozgus]

PS2Browser stopped working in FreeMC v1.4.

[zx16384]

PS2Browser stopped working in FreeMC v1.4.

Hmmm... just tested the newer PS2Browser and it worked (the older one is almost the same). Did you have a disc in drive while loading PS2Browser? If so, please try without a disc. If it works then, it could be an issue of cdvd initialisation (where PS2Browser cannot do anything as its just launching OSDSYS from rom0 while disabling updates from memory card)... cdvd is initialized by the loader inside free McBoot.

Did it work before? Which PS2Browser are you using, the first one or the newer one from post #40? What version is your console? (mine is a v10 PAL).

@all:
Please, post your console version when giving feedback, thanks!

[Mozgus]

Hmmm... just tested the newer PS2Browser and it worked (the older one is almost the same). Did you have a disc in drive while loading PS2Browser? If so, please try without a disc. If it works then, it could be an issue of cdvd initialisation (where PS2Browser cannot do anything as its just launching OSDSYS from rom0 while disabling updates from memory card)... cdvd is initialized by the loader inside free McBoot.

Did it work before? Which PS2Browser are you using, the first one or the newer one from post #40? What version is your console? (mine is a v10 PAL).

@all:
Please, post your console version when giving feedback, thanks!
v12 USA NTSC Slim. I tried both versions of the tool. Both fail with no disc in, and work with a disc in. They worked fine in v1.3d, but started having this issue in v1.4.

[zx16384]

v12 USA NTSC Slim. I tried both versions of the tool. Both fail with no disc in, and work with a disc in. They worked fine in v1.3d, but started having this issue in v1.4.

Ok. The "newer" one does basically the same as the "older" one, just doing things a little bit different so it actually works on more PS2 versions... So both should behave either totally the same or the newer one should stop on a red screen if the OSDSYS is not compatible.

How does it fail? Does it return to free McBoot or does it freeze? Does it get to the startup sound/animation from the PS2Browser?

Do you launch directly from the new integrated v1.4 launcher as BOOTx.ELF (did not try that one!) or do you launch from uLE (as I do)? The new integrated launcher looks totally different compared to the older sources.

[zx16384]

They worked fine in v1.3d, but started having this issue in v1.4.

Just seen your post in the main thread:

My system is now sticking at a black screen about half of the boots. What's the deal? When did random failure come into the equation?

This should be sorted out first, as that could also be the reason why PS2Browser does not work for you anymore...

[spkleader]

zx16384: It's probably his memorycard. PS2Browser it's working fine here. SPCH-500001 / NTSC-U, FreeMCBoot (with fries and coke!) v1.4

[Mozgus]

zx16384: It's probably his memorycard. PS2Browser it's working fine here. SPCH-500001 / NTSC-U, FreeMCBoot (with fries and coke!) v1.4

Why would it be my memory card? I bought it brand new a few months ago. Official 8MB.

[spkleader]

Mozgus: not to sound rude or anything. Did you tried to reformat your mc and then install again? I told that because my pirated memorycard (that looks EXACTLY like a official one from sony outside) acts exactly the way you described.

[slicer74]

Cool, it works, but how do we come back to ULE after, without shuting down the PS2 ?

[malak2]

Hi all, does PS2browser start the disc if it's inserted (like normal boot) ?

[remax]

Hi all, does PS2browser start the disc if it's inserted (like normal boot) ?
Yep.

EDIT : In fact no, you have to select in manually under the browser...

[malak2]

It would be REALLY nice to have an elf that simulates the standard PS2 boot behaviour (booting directly the disc if it's present or the browser when it isn't).

Used as a default boot.elf for FMB (without any button pressed) we could have a 'transparent' boot, just pressing R1 (or other) if ulaunchelf (or other) is needed.

Would that be possible ???

[TnA]

@malak2: As Jimmi said, he'll implement this in the loader. ;)

[Mozgus]

Mozgus: not to sound rude or anything. Did you tried to reformat your mc and then install again? I told that because my pirated memorycard (that looks EXACTLY like a official one from sony outside) acts exactly the way you described.

I format everytime I reinstall the exploit.

[zx16384]

Hi all, does PS2browser start the disc if it's inserted (like normal boot) ?

It's supposed to do.

EDIT : In fact no, you have to select in manually under the browser...

Hmmm... does PS2Browser boot directly into the memory card browser? This seems to happen on some consoles which were not compatible with the "first" PS2Browser.elf. Maybe this can be fixed...

Cool, it works, but how do we come back to ULE after, without shuting down the PS2 ?

We can't. Because it is the original browser from your console's rom. (Except if you installed the other exploit on the same memory card and then insert a PS1 disc)


@all:
I assume no one got the "red screen" when running the newer PS2Browser?

[zx16384]

I format everytime I reinstall the exploit.

Maybe your memory card has a bad block? The instructions for free McBoot say that then formatting with the installer will not work correctly.

[zx16384]

This is the third release of PS2Browser.ELF. This is like the second one (not skipping hard disc check and also working on more consoles than the first release) but with a small fix for those consoles where it booted directly into the memory card browser.

I did a short test on my v10 PAL [ger] and my v3 PAL [ger], but as the first one does work very fine for me, this newer one has only been tested very briefly (i myself don't need it). If this goes into a red screen that means it is incompatible and you should just use the PS2Browser in the first post.

Please, when giving feedback also include what version your PS2 is.

[remax]

Hmmm... does PS2Browser boot directly into the memory card browser? This seems to happen on some consoles which were not compatible with the "first" PS2Browser.elf. Maybe this can be fixed...


Yes.

This is the third release of PS2Browser.ELF. This is like the second one (not skipping hard disc check and also working on more consoles than the first release) but with a small fix for those consoles where it booted directly into the memory card browser.

I did a short test on my v10 PAL [ger] and my v3 PAL [ger], but as the first one does work very fine for me, this newer one has only been tested very briefly (i myself don't need it). If this goes into a red screen that means it is incompatible and you should just use the PS2Browser in the first post.

Please, when giving feedback also include what version your PS2 is.

Thank's i'm gonna test it.

[remax]

ok now it work exactly like if i boot my PS2 mémory without card :)

My PS2 : V4 Europe.

[Neme]

I would like to see this included in uLaunchELF, coz i don't want to have any more ELFs cluttered on my mc... Why no source code included? Anyway, now that i know the right parameter to pass to the OSDSYS (and i'm not talking about SkipMc), thanks to zx16384, i've made my own version. Hope zx doesn't mind if i post it here. :) It just replaces the B?EXEC-SYSTEM strings to B?EXEC-OSDSYS so the bowser will look in that folder instead of the default. Tested also with Jap V1 bios in pcsx2.

[zx16384]

I would like to see this included in uLaunchELF, coz i don't want to have any more ELFs cluttered on my mc... Why no source code included?

Because the source code is very ugly. Never did anything for PS2 before, and this was before including the folder-name-patch just a very quickly done thing. I would have rewritten the whole thing (two thirds of source is debug code/different approaches) and then released the source for the final version (but as you've seen, I still had a little bit to fix this morning).

Anyway, now that i know the right parameter to pass to the OSDSYS (and i'm not talking about SkipMc), thanks to zx16384, i've made my own version.

If we both mean the same parameter than that's the one what made my patching approach evolve into many different versions until i saw that it worked right from the beginning but the OSDSYS crashed on my older v3 because of that missing argv[0] and not due to changing the folder-name :oops:

Hope zx doesn't mind if i post it here. :)

No, of couse not. :):):)

It just replaces the B?EXEC-SYSTEM strings to B?EXEC-OSDSYS so the bowser will look in that folder instead of the default. Tested also with Jap V1 bios in pcsx2.

Well, that's almost the same release 2 and 3 do. Only B?EXEC-SYSTEM to B?EYEC-SYSTEM... but you're doing the unpack-patch-exec_OSDSYS differently and more universal - and in a way i never would have thought possible (hook-exec_OSDSYS-(unpack)-patch-exec_again). Only thing I do additionally is an IOP reset.

[suloku]

I think Dlanor won't have any inconvenience adding this to ule when it is fully tested and working with all ps2 models.

That last thing is what isn't clear for me, does your version 3/neme's program work for all ps2 models? For what you said and how does it patch, it should right?

[dlanor]

I would like to see this included in uLaunchELF,
EP and I'll have to check it out and consider if it is suitable for inclusion in uLE. For one thing, it needs work on all PS2/PStwo models, which I'm not sure if this method does.

coz i don't want to have any more ELFs cluttered on my mc... Why no source code included? Anyway, now that i know the right parameter to pass to the OSDSYS (and i'm not talking about SkipMc), thanks to zx16384, i've made my own version. Hope zx doesn't mind if i post it here. :) It just replaces the B?EXEC-SYSTEM strings to B?EXEC-OSDSYS so the bowser will look in that folder instead of the default. Tested also with Jap V1 bios in pcsx2.
I'm not sure I understand you correctly. As I see it the whole point of this program is to invoke the PS2 browser without invoking the content of the normal B?EXEC-SYSTEM folder, so the B?EXEC-OSDSYS folder name is just one you made up, to avoid getting a successfull search for it (thus avoiding relaunch of Free McBoot). And we should therefore never make such a folder on the MC.

Is that correct ?

Best regards: dlanor

[Mozgus]

3rd version still doesn't work for me.

[zx16384]

I think Dlanor won't have any inconvenience adding this to ule when it is fully tested and working with all ps2 models.

That last thing is what isn't clear for me, does your version 3/neme's program work for all ps2 models? For what you said and how does it patch, it should right?

Well, i think both should work the same. And as no code (only the path where the OSDSYS should look for updates) is patched after unpacking it should work on all PS2 models. At least i got no report of the "red screen" for version 2/3 which gets forced when unpacking fails. The rest is just different strategies for the same goals :) neme's version has a better chance to find the unpack entry point.

I will still continue to use version 1 because it can skip spinning up the hard drive where the OSDSYS wouldn't find anything to boot - this keeps unneeded stress from the hard drive. But that one works with no patching at all but by using command line parameters ("SkipMc", "SkipHdd") which is only recognised by some PS2 models.

[zx16384]

EP and I'll have to check it out and consider if it is suitable for inclusion in uLE. For one thing, it needs work on all PS2/PStwo models, which I'm not sure if this method does.

I think neme's unpacker should work on all models, as he is hooking on a very generic entry point (a syscall) which should not be version specific. My version does look directly for a jal/lui (and gets its parameters for the unpacker).

I'm not sure I understand you correctly. As I see it the whole point of this program is to invoke the PS2 browser without invoking the content of the normal B?EXEC-SYSTEM folder, so the B?EXEC-OSDSYS folder name is just one you made up, to avoid getting a successfull search for it (thus avoiding relaunch of Free McBoot). And we should therefore never make such a folder on the MC.

Is that correct ?

Yes, that's correct. Any folder name goes, that's why my version just made the X to Y (just one byte to patch) ;)

[coolaan]

I'm not sure I understand you correctly. As I see it the whole point of this program is to invoke the PS2 browser without invoking the content of the normal B?EXEC-SYSTEM folder, so the B?EXEC-OSDSYS folder name is just one you made up, to avoid getting a successfull search for it (thus avoiding relaunch of Free McBoot). And we should therefore never make such a folder on the MC.

Is that correct ?

Best regards: dlanor

Dlanor,
I think what Neme wanted to tell was his new app (elf) loads the PS2 Browser (osdsys) even if there is a valid bootable osdmain.elf on the mc. So people using the bootable mc trick cant use the functionality of Ulaunch MISC-> PS2Browser bcoz that boots back to their mc elf.

So if a mc hack person wants ps2 browser , he is forced to use another elf or remove his mc.

But if this trick used here is implemented for MISC->PS2 Browser, then a person having ulaunch as his boot elf can easily go to Ps2 Browser also, avoiding the necessity of one more elf just for Ps2 browser... :)

correct me if im wrong neme....

[remax]

That's what i understood too. The problem is that it will skip the check for an update so that people with REAL osd update won't have it activated if they use this function and i don"t think dlanor want to release two versions of uLE (one for FMB and one for regular users).

[Billkwando]

This is the third release of PS2Browser.ELF. This is like the second one (not skipping hard disc check and also working on more consoles than the first release) but with a small fix for those consoles where it booted directly into the memory card browser.

I did a short test on my v10 PAL [ger] and my v3 PAL [ger], but as the first one does work very fine for me, this newer one has only been tested very briefly (i myself don't need it). If this goes into a red screen that means it is incompatible and you should just use the PS2Browser in the first post.

Please, when giving feedback also include what version your PS2 is.

It worked exactly the same as the last one. Was it supposed to land me a screen earlier at the Browser/System Config screen?

If so, it didn't.

I believe my PS2 is a V4 but if someone can remind me how to check I gladly will.

[zx16384]

I think what Neme wanted to tell was his new app (elf) loads the PS2 Browser (osdsys) even if there is a valid bootable osdmain.elf on the mc.

Yes, that's what this whole thread is about... loading the PS2 Browser even when there is free McBoot (or any other valid bootable osdxxx.elf) installed on any inserted memory card.

There's PS2Browser.Elf in the first post, which does this in a very clean way but down not work on all consoles. It just runs the OSDSYS with two parameters telling it to skip checking memory card and hard disc for browser updates.

There's PS2Browser.Elf (PS2Browser_3.zip) in post #66 which only blocks memory-card checking with very little patching and seems to work on most (if not all?) consoles. It patches one byte in the path where to search for memory card updates, making B?EXEC-SYSTEM to B?EYEC-SYSTEM.

And now there's Neme's execosd.elf in post #69 who did basically the same as my PS2Browser_3 but with better code. It patches the path where to search for memory card updates, making B?EXEC-SYSTEM to B?EXEC-OSDSYS. So anybody really having an update to OSDSYS could try to place that in this folder!

The first PS2Browser.ELF still has a use for those where it is compatible because the hard disc will not be started and then immediately shut down if it is not an genuine one, which means the hard disc will last longer because every start/stop-cycle is very huge stress for desktop hard drives.

Neme's execosd.elf can perfectly replace my PS2Browser_3 which means i will not make anymore changes to that. :cool:

I too would like to have integration into uLaunchElf, but as Dlanor wrote it then the launch method must be perfectly compatible with all ps2 models. And that's where Neme's solution looks better.

[Billkwando]

<excellent explanation>

So if we don't have an official PS2 HDD we should use Neme's and it won't stress the HDD as much?

Edit: Or the 1st one?

[zx16384]

So if we don't have an official PS2 HDD we should use Neme's and it won't stress the HDD as much?

No, the other way around: Only the PS2Browser.ELF from the first post in this thread will not stress the HDD.

All newer ones (PS2Browser_2.zip, PS2Browser_3.zip) and Neme's execosd.elf do the same thing: They only change the folder where the OSDSYS looks for updates on memory cards, but do not stop the browser from looking for updates on the HDD, which means the HDD will be started, will fail the hardware check for an official HDD and then be immediately shut down.

There is no easy universal way to prevent the HDD from starting without the command line parameters (used in the first release of PS2Browser) which are not supported in every ps2 version. That's why i myself still use my first PS2Browser.ELF and not the later ones... i do not want the hard drive to start.

[Billkwando]

No, the other way around: Only the PS2Browser.ELF from the first post in this thread will not stress the HDD.

All newer ones (PS2Browser_2.zip, PS2Browser_3.zip) and Neme's execosd.elf do the same thing: They only change the folder where the OSDSYS looks for updates on memory cards, but do not stop the browser from looking for updates on the HDD, which means the HDD will be started, will fail the hardware check for an official HDD and then be immediately shut down.

There is no easy universal way to prevent the HDD from starting without the command line parameters (used in the first release of PS2Browser) which are not supported in every ps2 version. That's why i myself still use my first PS2Browser.ELF and not the later ones... i do not want the hard drive to start.

Understood. As you can see from my edit, I got it right before you posted it.

I appreciate you explaining all this because obviously everyone wants to avoid stressing their hard drive, and I didn't understand until your last post that the HDD check should be avoided if you don't have an official Sony HDD.

[Billkwando]

No, the other way around: Only the PS2Browser.ELF from the first post in this thread will not stress the HDD.

All newer ones (PS2Browser_2.zip, PS2Browser_3.zip) and Neme's execosd.elf do the same thing: They only change the folder where the OSDSYS looks for updates on memory cards, but do not stop the browser from looking for updates on the HDD, which means the HDD will be started, will fail the hardware check for an official HDD and then be immediately shut down.

There is no easy universal way to prevent the HDD from starting without the command line parameters (used in the first release of PS2Browser) which are not supported in every ps2 version. That's why i myself still use my first PS2Browser.ELF and not the later ones... i do not want the hard drive to start.

I see the problem for me now. If you notice my first post (#31) the first file didn't work for me, so I'm back to no browser unless I wanna stress my HDD.

Sorry for the double post.

[suloku]

That's good information there, I assumed ps2browser 3 was better than 1 and 2, but as you say, it's nearly a different application for the same matter.

This being added to ule will be good, but I don't think adding it to current ps2browser is a good idea, as people who don't use freemcboot and have osdsys updates will be afected negatively.

In any case, I'd always prefer having an elf around there able to do just that, for example to load it from another app other than ule, as free mcboot little loader, of course only in case improvements are made to the app.

[remax]

No, the other way around: Only the PS2Browser.ELF from the first post in this thread will not stress the HDD.

All newer ones (PS2Browser_2.zip, PS2Browser_3.zip) and Neme's execosd.elf do the same thing: They only change the folder where the OSDSYS looks for updates on memory cards, but do not stop the browser from looking for updates on the HDD, which means the HDD will be started, will fail the hardware check for an official HDD and then be immediately shut down.

There is no easy universal way to prevent the HDD from starting without the command line parameters (used in the first release of PS2Browser) which are not supported in every ps2 version. That's why i myself still use my first PS2Browser.ELF and not the later ones... i do not want the hard drive to start.

A little question : my uLe launch the hard drive at startup. Does the HD stop between the end of the check and the launch of uLE, or as it is few time after the check it stay on so that i avoid an unnecessary cycle of power?

[suloku]

HDD starts at boot if connected, then it switchs off. It's been said earlier in this thread.

So yes, if possible you should use version one to avoid this unneeded checking, it's better for the drive, but my ps2 has been checking the hdd at boot for 4 ages now and nothing happened.

[dlanor]

Dlanor,
I think what Neme wanted to tell was his new app (elf) loads the PS2 Browser (osdsys) even if there is a valid bootable osdmain.elf on the mc. So people using the bootable mc trick cant use the functionality of Ulaunch MISC-> PS2Browser bcoz that boots back to their mc elf.
Naturally I understood most of that from the start. The intent of my post was only to have someone confirm that nothing in Neme's code required the user to have an MC folder named "B?EXEC-OSDSYS", and this was later confirmed by zx16384 in post #75.

Best regards: dlanor

[remax]

HDD starts at boot if connected, then it switchs off. It's been said earlier in this thread.

So yes, if possible you should use version one to avoid this unneeded checking, it's better for the drive, but my ps2 has been checking the hdd at boot for 4 ages now and nothing happened.
Yes i know what you said. What i want to know is "does it immediatly switch off?" as uLE launch my hard drive few seconds after.

I have no other choice to use the version that check the hdd as the first ver doesn't work on my console ;)

[Billkwando]

Yes i know what you said. What i want to know is "does it immediatly switch off?" as uLE launch my hard drive few seconds after.

I have no other choice to use the version that check the hdd as the first ver doesn't work on my console ;)

Same here. If it's added to a general release, won't that mean that HDDs will be firing up all over the land for no reason?

[zx16384]

Yes i know what you said. What i want to know is "does it immediatly switch off?" as uLE launch my hard drive few seconds after.

You can confirm yourself that it does so. Remove all memory cards and any discs from your ps2 and turn your console on. You can hear the hard drive starting, and less than a second later shutting down. If the hard drive does not pass the check for official hardware the ps2 seems to send the poweroff command.

[dlanor]

A little question : my uLe launch the hard drive at startup. Does the HD stop between the end of the check and the launch of uLE, or as it is few time after the check it stay on so that i avoid an unnecessary cycle of power?
In fact uLE itself does not start the HDD at boot unless something in the CNF requires a file to be loaded from HDD, or if uLE was booted from HDD (modchip Dev2). In other cases uLE does not even load the HDD drivers unless the user attempts to access the HDD, either in FileBrowser or HddManager or by using the launch button for some program stored on HDD.

As for 'stopping' the HDD, that is not handled by uLE itself, but by timeout in the drivers.

Best regards: dlanor

[suloku]

Ok, it seems I didn't make myself clear.

PS2 always looks for an update on the hdd, even on an unmodded ps2 using official sony drive with a non-hdd compatible original ps2 dvd game, the console will start the hdd, look for the update, shut it down and then launch the disc.

This is it's normal behavior and yes, it's not the best sony could do with it's hdd, but no one complained until now that we know we can skip that on some models, which will benefit from it with a little less stress for the hdd.

Answering your question: yes, ule will power on the hdd again when it first accesses it.

[dlanor]

Same here. If it's added to a general release, won't that mean that HDDs will be firing up all over the land for no reason?
No it won't. The extra HDD startup will only occur each time you use the new "MISC/PS2Browser" command to open the Sony Browser. Whenever you don't do that uLE will work as usual. So the choice is up to the user, where it belongs.

Best regards: dlanor

[zx16384]

If it's added to a general release, won't that mean that HDDs will be firing up all over the land for no reason?

Everytime the PS2 browser loads (even without free McBoot) the hard drive gets fired up, with or without free McBoot. There is nothing in these PS2 browser loaders (mine or Neme's) that is "firing up the hdd" - it's the PS2 browser from your console's ROM itself that does it.

That "SkipHdd" command line parameter preventing this could also be added to the newer more compatible (folder-name patching) ps2 browser loaders but would do just nothing on those consoles where the first PS2Browser.ELF release did not work... as these SkipMc and SkipHdd parameters have to be used by the OSDSYS in your consoles rom...

So there are two options: A) If your console is compatible with the first PS2Browser.ELF, then you can use this to not starting the hard drive. B) If your console does not work with this, there is no easy way to stop the browser from doing that, so use either Neme's loader or my PS2Browser_3.elf.

[coolaan]

Naturally I understood most of that from the start. The intent of my post was only to have someone confirm that nothing in Neme's code required the user to have an MC folder named "B?EXEC-OSDSYS", and this was later confirmed by zx16384 in post #75.

Best regards: dlanor

oops!!:D

[remax]

You can confirm yourself that it does so. Remove all memory cards and any discs from your ps2 and turn your console on. You can hear the hard drive starting, and less than a second later shutting down. If the hard drive does not pass the check for official hardware the ps2 seems to send the poweroff command.

ok i'll have to live with that :D

EDIT : ok i understand now : it does just the usual HDD check like every time, not an additionnal one. Ok so no problem for me!

Thanks everybody for this answer!

[Billkwando]

Everytime the PS2 browser loads (even without free McBoot) the hard drive gets fired up, with or without free McBoot. There is nothing in these PS2 browser loaders (mine or Neme's) that is "firing up the hdd" - it's the PS2 browser from your console's ROM itself that does it.

That "SkipHdd" command line parameter preventing this could also be added to the newer more compatible (folder-name patching) ps2 browser loaders but would do just nothing on those consoles where the first PS2Browser.ELF release did not work... as these SkipMc and SkipHdd parameters have to be used by the OSDSYS in your consoles rom...

So there are two options: A) If your console is compatible with the first PS2Browser.ELF, then you can use this to stop the hard drive from starting and stopping. B) If your console does not work with this, there is no easy way to stop the browser from doing that, so use either Neme's loader or my PS2Browser_3.elf.

I see. So the skipping of the HDD is something we've all lived without all this time, so for people who can't use the first file, we're no worse off than we've ever been.

I'll just have to remember to only use the browser when I must, unless one of you guys eventually figured out the mystery. [Edit: I know it's not technically a "mystery" per se]

Thanks for the efforts. :)

[Neme]

If we both mean the same parameter than that's the one what made my patching approach evolve into many different versions until i saw that it worked right from the beginning but the OSDSYS crashed on my older v3 because of that missing argv[0] and not due to changing the folder-name :oops:


I started to write my version a few weeks ago and it worked fine until the point where the last ExecPS2 was called, then the osdsys just didn't start. So i put the whole thing to rest. I took a closer look into memento - apparently it didn't use any param but applied several patches to the osdsys which didn't look like a compatible way. I was surprised when i tried this param and the osdsys started, never heard or read about it anywhere before - nice find. :)

Anyway my code should be viewed only as an example, there are several ways to implement this feature and I'm hoping one day something like this will be included in uLE with some switches and options, now that the source is available. :)

[zx16384]

This is just a clean-up release for PS2Browser.ELF, this time source included :cool:

Also the path now gets changed to the same folder Neme's tool does (i.e. B?EXEC-SYSTEM -> B?EXEC-OSDSYS) as that enables anyone having real osd-updates putting them in the B?EXEC-OSDSYS-folder (? being your correct memory card region), hope Neme doesn't mind ;). So both tools have the same result but done in a very different way.

Compatibility should be the same as with PS2Browser rel. 3, so no need to redownload.

[suloku]

This is just a clean-up release for PS2Browser.ELF, this time source included :cool:

Also the path now gets changed to the same folder Neme's tool does (i.e. B?EXEC-SYSTEM -> B?EXEC-OSDSYS) as that enables anyone having real osd-updates putting them in the B?EXEC-OSDSYS-folder (? being your correct memory card region), hope Neme doesn't mind ;). So both tools have the same result but done in a very different way.

Compatibility should be the same as with PS2Browser rel. 3, so no need to redownload.

Nice, what about adding the code for skip hdd argument to it, so this code can be put into another app (neme's, ule, freemcboot or ESR)?

Or release version's 1 source ^^

EDIT:

Nevermind, I've seen skipping hdd is a compiling option for release 4, is it enabled on your provided binary? You said if the option is on and the ps2 doesn't support it, it will just work as if the argument wasn't provided. Well, thinking about it, the function should just ignore the argument as it doesn't make use of it.

BTW is it as simple as it seems, just adding the argument to the call function? I say this in order to be able to add it to neme's code, as you said it's method was likely to be compatible with more ps2 modes.

[zx16384]

Nice, what about adding the code for skip hdd argument to it, so this code can be put into another app (neme's, ule, freemcboot or ESR)?

Or release version's 1 source ^^

Well, the code is in main.c, just not compiled-in (so the PS2Browser.ELF in the PS2Browser_4.zip does not send "SkipHdd").

But - in the Makefile there's a variable at the top:

# OPTIONS
SKIP_HDD = 0


If changed to

SKIP_HDD = 1

then the code for the "SkipHdd" will be compiled in after a "make clean" and a "make". This was just left off for the compiled elf because there were requests to not skip hdd... and if you want that feature just use the PS2Browser.Elf in the first post - that works with all consoles supporting "SkipHdd".

Thus, the source contains it all :)

[suloku]

Thanks for your reply, I had just edited my previous post when I took a look at the code, but now there are no doubts at all.

[zx16384]

You said if the option is on and the ps2 doesn't support it, it will just work as if the argument wasn't provided.

On my v3, having the unsupported option active did boot directly to the memory card browser. So, maybe there are side-effects, that's why i removed "SkipMc" in release 3 (that was still in release 2). This helped my v3 booting to the osd menu.

BTW is it as simple as it seems, just adding the argument to the call function? I say this in order to be able to add it to neme's code, as you said it's method was likely to be compatible with more ps2 modes.

Yes, "SkipHdd" is a command line parameter.

And regarding compatibility: Neme does the patching process of the folder-name very different, hooking his patcher into the osdsys after the unpacker has unpacked it, while PS2Browser first locates the unpacker, calls it, nop's it, does the patching and then executes OSDSYS. PS2Browser searchs for a jal to unpacker, execosd looks for a syscall. execosd's patch routine actually gets called by OSDSYS. PS2Browser calls the unpack function directly, does its work and then completely gives control to OSDSYS. I think both methods work the same with all current PS2 versions.

Also his version does not do an IOP reset which i think should be done to clean up the machine from previously loaded things. I just found out that on my v10 i get no sound from the osd when run with execosd.elf. This was another reason for my rel. 4... so there's an option in case i would not be the only one having that problem ;)

[d3adliner]

Just tried the 1st file and it works great.

My question is, is it possible in any way to force the PS2 to either NOT autoload a disc if one is already inserted when running ps2browser.elf, or to force it to go directly to the mem card screen?

[TnA]

Yes, it should. :)

[d3adliner]

But it doesn't. :)

If I have any sort of disc at all in the PS2, then run ps2browser.elf from within uLE... it goes to the screen with "Browser" & "System Configuration" then immediately autoboots whatever disc is in the drive, gets to the "Playstation 2" logo, and then stays on an all black screen never booting the disc wether it's an original dvd, original game, backup, or whatever.

I'd like it stay on the Browser/System Configuration screen and not autoboot any disc that may be in the dirve. Is it possible?

[TnA]

Aaar,... It should be possible, due browser-hack.
-Autoload MC-Manager
-Prevent Disc-Startup

It doesn't have it yet.

[d3adliner]

Any estimate on when this feature could possibly be integrated? Or instructions on how to do it myself?

[suloku]

Any estimate on when this feature could possibly be integrated? Or instructions on how to do it myself?

If you need instructions you can't do it. But I discovered how to make ps2browser go straight to the browser screen without booting inserted disc. Does this interest you? If you want to launch fmcb you have to exit this screen, but I see no reasont to boot the browser if it isn't to access this screen, and you can boot the disc from there. I haven't tried but opening and closing the tray should boot the disc as always at the hacked screen.

[d3adliner]

If you need instructions you can't do it. But I discovered how to make ps2browser go straight to the browser screen without booting inserted disc. Does this interest you? If you want to launch fmcb you have to exit this screen, but I see no reasont to boot the browser if it isn't to access this screen, and you can boot the disc from there. I haven't tried but opening and closing the tray should boot the disc as always at the hacked screen.

Yes, I am greatly interested.

[suloku]

Sorry, I've been away for more than a week, gonna upload it when i check the forums and get up to date.

[d3adliner]

Still waiting on how to do this. I don't want it to autoboot whatever disc I have in the tray when I use ps2browser.elf from within ule. I just want it to stay on the main screen, or the mc screen.

[kevstah2004]

Still waiting on how to do this. I don't want it to autoboot whatever disc I have in the tray when I use ps2browser.elf from within ule. I just want it to stay on the main screen, or the mc screen.

If you decrypt your osdmain.elf with HDProjectX can't you re-launch it with ULaunchELF?
Why do you want to re-launch the browser after ULaunchELF anyway to load PS1 titles or normal dvd-v's? PS1DRV can be extracted from the bios and be loaded as an normal ELF file with ULaunchELF without intercepting OSDSYS also if you have an update dvdplayer disc you can decrypt dvdplayer.elf without intercepting OSDSYS in the same fashion.

[dlanor]

Still waiting on how to do this. I don't want it to autoboot whatever disc I have in the tray when I use ps2browser.elf from within ule. I just want it to stay on the main screen, or the mc screen.
The latest FMCB beta version has a new configuration variable which allows us to choose whether the Sony browser (modified) should be opened by going to the 'outer' menu, which does boot a disc automatically if present in tray, or by going to the 'inner' menu, where you can see the MC and CDVD device icons and choose which to use.

Most likely this feature will be kept for the upcoming non-beta release of FMCB v1.6

Best regards: dlanor

[d3adliner]

@kevstah2004, because I prefer to use Sonys MC browser to manage my save data rather than something like mcmanager.elf & I don't always want to HAVE to remove whatever disc is in the drive before I do so. If there's any disc in the drive, I cannot use ps2browser.elf to manage my saves via Sonys MC browser, as it goes to the "not a valid ps2 disc" screen. If it didn't autorun the disc, I could manage my saves then go back into ule via the hacked osd and run whatever elf I wanted from there.

@dlanor, thanks for the info. I tried the beta but it still autoboots the disc when going directly to the 'inner' menu.

[TnA]

Btw.: Do you have a mod-chip installed?
I have some problems with my DMS3.

[d3adliner]

Nope, no chip.