PS2 (WIP) XtremeEliteBoot+ (a powerful alternative for FMCB)

[TatsumaYakoshi]

And yes, tomorrow you all will have a little something.

R.I.P Monday.

 

[Fanhais]

if this was real by now we had it already XEB+

 

[TnA]

Well... It is Thursday... Worldwide...

 

[MALK]

Well... It is Thursday... Worldwide...

don't worry he does have something to release but life happens i guess anyway he shouldn't have put a date i always told him to never put a date that he can't stick with he is very busy at the moment but i am certain that we are gonna have something soon Believe me the project is legit just wait...
and @HWNJ please don't tell people dates next time this just lowers the trust that people have for you or have had for you if you have something just do it don't tell people when to expect something.
and guys wait just wait for hwnj and amazing things will happen

 

[TnA]

Well, I know it's legit.
I know that you along with the others even created 'a new place'.

I fully agree on the statement, that it is better to not say any fixed dates for a release.

 

[STLcardsWS]

I Can Confirm that XEB might be Real.

Well, I know it's legit.
I know that you along with the others even created 'a new place'.

I fully agree on the statement, that it is better to not say any fixed dates for a release.

We know its real and files have been shown to some.

Thread is permanently closed @HWNJ when ready to make a release create a new thread for the release.

#NoMoreCircus

 

[El_isra]

Things that were originally part of FMCB will have to stay close-source.

What about releasing HDDLOAD.IRX and how you operate with it

 

[ElSinGao]

Things that were originally part of FMCB will have to stay close-source.

Why? FMCB is open source at GitHub https://github.com/TnA-Plastic/FreeMcBoot
@TnA made the release and by looking at https://github.com/TnA-Plastic/FreeMcBoot/commits/master it seems to be the latest 1.8 version which means everything else added to the code after that is not original from FMCB, instead, it is your own code.
You can go ahead and pull request your changes to that repository and you will be submitting only your code.

What about releasing HDDLOAD.IRX and how you operate with it

Documentation should not be needed if source is provided, right?

 

[El_isra]

Documentation should not be needed if source is provided, right?

HDDLOAD.IRX is a small but complex one...

Mostly because it seems to be "uncontrollable". You only run it with the appropriate arguments and it does it's job on a separate thread.

The rest of the job is done on EE Side...

I've manage to reverse a certain portion of the driver and FreeMcBoot code...

I'm missing information about the second argument required by the driver and of course how to determine if the driver finished it's job, so the program proceed.

 

[HWNJ]

@TnA made the release and by looking at https://github.com/TnA-Plastic/FreeMcBoot/commits/master it seems to be the latest 1.8 version which means everything else added to the code after that is not original from FMCB, instead, it is your own code.
You can go ahead and pull request your changes to that repository and you will be submitting only your code.

You've made a good point...

Documentation should not be needed if source is provided, right?

No. Even with open source code, reverse engineer it in order to understand it is not the best

HDDLOAD.IRX is a small but complex one...

Mostly because it seems to be "uncontrollable". You only run it with the appropriate arguments and it does it's job on a separate thread.

The rest of the job is done on EE Side...

I've manage to reverse a certain portion of the driver and FreeMcBoot code...

I'm missing information about the second argument required by the driver and of course how to determine if the driver finished it's job, so the program proceed.

Why don't you get every string from the code and start guessing around?

 

[El_isra]

You've made a good point...

No. Even with open source code, reverse engineer it in order to understand it is not the best

Why don't you get every string from the code and start guessing around?

because i cant find where they come from...

on ghidra I have the strings all stacked up on a certain part of the decompilation.

all references to strings arent directly linked on IOP code (and only in few cases on EE code) most of the time, they are represented as GP pointer substractions... (Example: &gp - 0xb00b5)

also, the argumment i'm missing is not a hardcoded string. its a string calculated from some binary data on stack...

the argumments are -stat 0x0010000 -osd ????

When HDDLOAD finished it's job I simply do ExecPS2(0x0010000, NULL, argc, argv);

But the problem is, how do I know it finished it's job?

 

[HWNJ]

As someone from Vox Machina said: *#$@/&*)=

 

[Psyringe]

As someone from Vox Machina said: *#$@/&*)=

@HWNJ with respect,

Observation is that your setup is pulling newcomers down a path that isn't optimal and you're leaving it open ended for long durations under heavy promotion - not healthy for these types of scenes. Users have tried portraying this to you; it's a scene filter issue, not a talent issue.

(holding peace; the new image naming conventions aren't friendly.)

Release Pages aren't clear about the functionality of POPStarter and Internal HDDs.
...as if intentional for promotion.

While looking up how to mod a PS2 it's HWNJ's Forum Promotions VS Project Phoenix Media's Videos.

etc.

SELL SLIMS | MOD PHATS; after studying the tools have stuck with 2019 Console Methods & 2022 OS Tools.
IMO: USB IS OBSOLETE AND SHOULD NOT BE TRAINED ON NEW WAVES OF USERS.

etc.

Being said, figure it'll be similar to the Rocky5 deployment. That's why.

etc.

XEB+ (with Plugins), PS2SX, and POPSY currently* (8/24/2023) have no utility on a PHAT PS2, only the SLIM Playstation 2.

meta meta meta

 

[Berion]

XEB isn't finished yet in meaning of all goals assumed, so in theory XMAS preview shouldn't be even published. However I was very annoying, so ultimately convinced HWNJ to do that anyway. ^^

Once project be hosted on GitHub, this issue will perish. But still there is some work to must be done before that. Not to mention jumping on newer Enceladus.

POPSY currently* (8/24/2023) have no utility on a PHAT PS2, only the SLIM Playstation 2

I don't understand that sentence.

 

[Psyringe]

Enceladus

Yes, saw that in action and did some testing of my own. More questions than answers.

I don't understand that sentence.

The sentence is to imply Software Utility VS Human Usage after unlocking XEB+ as the boot menu. Couldn't find a reason to keep the software; I sell my SLIMs to local traders. They're tinker toys at the moment, not the target hardware for this experience.

Bluntly: The entire deployment is distracting on how to get a PS2 mod installed. When users look up Popstarter guaranteed they're finding these software deployments, mixing information from five years ago and today due to the large promotional effort.

 

[Berion]

@Psyringe I still don't understand You because You mixing various of not connected to each other issues. Setting up bootloader and/or exploit is one thing, setting up any apps is another. Setting up XEB Dashboard is third thing between those two.

For now there is no tutorials etc. how to make XEB "bootable" because it wasn't released as let's say 1.0. You can set it via PS2BBL or FMCB, as RESCUE.ELF from USB for autoboot or as manually booting from menu entry, from USB. From MC it works too, but it is not recommended due to huge I/O load in themes (it will be very slow). But that will be fixed in future with reading icons from archive, so not only it will be available with installer but also as OpenTuna. And plenty of video guides explode too. For now, it is not ready, so it is something which devs can do easily for their own need and You cannot have grudge for that.

BTW: Soon I will release XEB PUPPY, a pre-configured XEB Dashboard with stuff ready to use for any John Doe. Soon means in around half of September I believe.

Yes, saw that in action and did some testing of my own. More questions than answers.

It is SDK so not for end user.

 

[Psyringe]

@Berion A piece of software has been developed and released publicly in a modding scene. That same piece of software has been advertised as unlocked and usable, here. The software has been well promoted across multiple threads including video content promoted by third parties. Furthermore, to clear up any confusion by previous users, the XEB+ software can be considered "proprietary" due to the nature of the license in the compression; discussed here.

IMO, after everything that has unfolded since publish, putting the sentence 'Keep in mind it is not a final build and it is extremely limited.' is insufficient. The entire deployment needs to be finished or updated to prevent damaging the influx of new users (myself being a new PS2* modder) - assuming neither will occur have created these posts for the time being. This is a meta issue, not a content issue.

THIS IS A PS2 SLIM MOD

• The listed software's only support USB and Popstarter.
• HDD loads Popstarter faster and supports PS2 games, therefor OPL is better on PHAT. (in all cases)
• MX4SIO loads PS2 games faster, however does not support Popstarter. (suggested for SLIM PS2)

This concept ignores loading a second menu after powering on the console or removing a device from the console for additional functionality.

Was persuaded to become part of this community over this software deployment, and willing to remain a member until the end of time. This software deployment will be of great interest for years to come, either as a comeback story or a learning scenario.

The software being a USB utility on the PS2 challenges the nature of the software's utility at this historical stage of PS2 modding.

 

[El_isra]

• MX4SIO loads PS2 games faster, however does not support Popstarter. (suggested for SLIM PS2)

.

POPStarter is abandoned thanks fo OPL 10th anniversary/Daily Builds. So no MX4SIO support available now, or in any future...

HDD loads Popstarter faster and supports PS2 games, therefor OPL is better on PHAT. (in all cases)

HDD Support is on development, I've even contributed to that by adding HDD Support to Enceladus

 

[Berion]

@Psyringe

• XEB have nothing to do with POPStarter.
• XEB have nothing to do with OPL.
• POPStarter have nothing to do with OPL.

Each of them are separated projects, handled by mostly different people, and each have different purpose.
What I understanding, You expecting that all be one symbiotic organism - which will never happen and which is not even possible. XEB is a dashboard, let's call it operating system for simplify term, while OPL is PS2 game loader and POPStarter is PSX emulator.

• XEB doesn't currently support HDD, i.Link and MX4SIO but will in future. Project is living.
• OPL support all devices and all filesystems. Project is living.
• POPStarter support only HDD (APA/PFS) and USB (FAT32) and never will suport anything else. Project is dead.

So You, as user, must build "from LEGO bricks" Your own environment, fitting to Your own needs.

 

[Psyringe]

You're cherry picking content from three connected posts, @Berion, while they're a single "organism" discussing marketing/seo and software utility. Might be a culture barrier. Considering the many years of discussion, hopefully this was helpful.

@El_isra Thanks, informative.

Have been satisfied and hopefully contribute to helping users decide how to mod their PS2.