PS2 FMCB/FHDB v1.9 series release thread

I wish 'the other person' who also has a full replacement, might add to that as well. :)
 
Does the installer check for free space when additional apps are added?

I mean, when I have only 2 MB free space, clean FMCB will install without a problem.
When there is only 1 MB free, there is a warning that the installation will not start?

When I have 2 MB free space normal FMCB (clean) should install without a problem,
but what will happens if I add additional 1 MB in APPS (FMCB+APPS=3 MB), should the installation starts?

I'm trying to make FMCB\FHDB noobie package, which will have:
I want to avoid errors in installation.

To be add.
Content of "BOOT-HDD" will be copied into "hdd0:/__sysconf/FMCB/".
Where the apps (APPS-HDD) for HDD are stored after installation?
 
Last edited:
I would hope for 'pages' (pressing left/right) and 'Dummy-OSD-Items' (like headings in between the actual programs, which are skipped while scrolling) to be implemented. ;)
 
ShaolinAssassin said:
128Mb PP.FHDB.APPS.
Click to expand...

You mean:
"hdd0:/FHDB/APPS"
or:
"hdd0:/__sysconf/FHDB/APPS/"?

Are sure not:
"hdd0:/__sysconf/FMCB/APPS"?

Because content from "BOOT-HDD" is been copied into "hdd0:/__sysconf/FMCB/".

TnA said:
I would hope for 'pages' (pressing left/right) and 'Dummy-OSD-Items' (like headings in between the actual programs, which are skipped while scrolling) to be implemented. ;)
Click to expand...

It's nice to see that you still have many fresh ideas.

BTW @sp193 I'v notice that USB drivers has been updated, so now latest FMCB\FHDB is from 05\11\2018.
 
jolek said:
You mean:
"hdd0:/FHDB/APPS"
or:
"hdd0:/__sysconf/FHDB/APPS/"?

Are sure not:
"hdd0:/__sysconf/FMCB/APPS"?

Because content from "BOOT-HDD" is been copied into "hdd0:/__sysconf/FMCB/".
Click to expand...

No, I mean hdd0:/PP.FHDB.APPS

SP193 said:
There is no APPS folder on the HDD unit, but an APPS partition (PP.FHDB.APPS).
Click to expand...

http://psx-scene.com/forums/f153/fmcb-v1-9-series-release-thread-116247/index68.html#post1205154

If APPS-HDD folder is empty, PP.FHDB.APPS is not created.
 
Here is FMCB\FHDB 1.965 noobie package test V1 with:

* only for FHDB.

Download V1:
It is advise to have 3.5-4MB free space on memory card.
If an installer will ask:
Do you want to keep "FREEMCB.CNF" or "FREEHDB.CNF", select "No".
Without updating these settings you'll not have shortcuts for new apps (e.g. OPL 1196).

I decided not to put (for now) apps for HDD in APP-HDD.
Apps for HDD will be in BOOT-HDD.
All apps will be copied into "hdd0:/__sysconf/FMCB/".

To be add.
If someone thinks that some of the apps are not needed, please let me know.
I'm thinking about remove SMS from this package to save space on memory card.

EDIT: Here is V2 without pad test & SMS for memory card to save space.
Theoretically no one uses SMS in these days, pad test "consume" ~200 kB,
so it might be to much for users with only one (8 MB) memory card.
These apps will only be copied on HDD (for FHDB).

Download V2:
 
Last edited:
Can all APPS for HDD be copied on the same partition as FHDB is?
I mean, currently when I add something in APPS-HDD folder for FMCB\FHDB installer,
installer will create additional partition "hdd0:/PP.FHDB/APPS" that takes 128 MB,
while "hdd0:/__sysconf" for FHDB have 512 MB.
It is enough space for many apps\tools and etc on this partition, so creating another is a bit "pointless".

Currently FHDB is stored in "hdd0:/__sysconf/FMCB/".
Why not store FHDB in "hdd0:/__sysconf/FHDB/",
BOOT in "hdd0:/__sysconf/FHDB/BOOT" (for BOOT-HDD),
APPS in "hdd0:/__sysconf/FHDB/APPS" (for APPS-HDD)?
It may also help to organize stuff (mainly for FMCB\FHDB nobie package).
 
jolek said:
Can all APPS for HDD be copied on the same partition as FHDB is?
I mean, currently when I add something in APPS-HDD folder for FMCB\FHDB installer,
installer will create additional partition "hdd0:/PP.FHDB/APPS" that takes 128 MB,
while "hdd0:/__sysconf" for FHDB have 512 MB.
It is enough space for many apps\tools and etc on this partition, so creating another is a bit "pointless".

Currently FHDB is stored in "hdd0:/__sysconf/FMCB/".
Why not store FHDB in "hdd0:/__sysconf/FHDB/",
BOOT in "hdd0:/__sysconf/FHDB/BOOT" (for BOOT-HDD),
APPS in "hdd0:/__sysconf/FHDB/APPS" (for APPS-HDD)?
It may also help to organize stuff (mainly for FMCB\FHDB nobie package).
Click to expand...

I think SP193 introduced the usage of hdd0:/PP.FHDB.APPS because some apps wouldn't work correctly when launched from HDD system partitions (the ones that has the double underscore as prefix). That's just a guess tho...
 
ShaolinAssassin said:
I think SP193 introduced the usage of hdd0:/PP.FHDB.APPS because some apps wouldn't work correctly when launched from HDD system partitions (the ones that has the double underscore as prefix). That's just a guess tho...
Click to expand...

I've tried to launch from HDD stored in "hdd0:/__sysconf/FMCB/APPS" following apps:
OPL 1196, wLe 05\11\2018, SMS 2.9 rev. 4, PSX Launcher, Cogswap, Padtest, MCA 2.0, GSM 0.38, power off (new), PS2ESDL_0825,
through FHDB browser & wLe.

ESR r9b also automatically lunches PS2 backup when it is placed in "hdd0:/__sysconf/FMCB/APPS".

Only PS2ESDL_0825 refuses to load Skin no matter if an app is in
"hdd0:/__sysconf/FMCB/APPS", "hdd0:/__sysconf/FMCB" or in "hdd0:/PP.FHDB.APPS".
When app is launched from USB Skin is loading.
Anyway app boots and a game can be selected and launched.

Maybe there are other homebrew that might have a problem, but I currently don't know which one, so I can't test it.
I remember that long ago I was having problems with launching few homebrew games:
Davegnukem, Flashback, Pang, PS2Invaders, Qbert, Xrick, Xump,
through FMCB\FHDB browser.
Although through wLe everything was fine.

When I'll have more time I'll test at least games when I"ll create "hdd0:/PP.FHDB.APPS".
Maybe some games can be launched only from USB or from MC (not from HDD)?
 
Last edited:
Those system partitions are not meant to be accessed by the user. Much like how you would not be encouraged to keep user files in C:\WINDOWS\SYSTEM32.
Most of those partitions are also supposed to be password-locked to protect them and they are also invisible to the HDD browser, so the user cannot manage content stored in there. __sysconf and __common are meant for access by any software, but they are meant for storing system configuration (including shared libraries like ATOK), while __common contains the user's save data.

I am not in favour of people messing with __system. FHDB is installed to __system, not __sysconf. Although it keeps its settings and USB modules in __sysconf.

There may be some free space check implemented, but it has been so long that I do not remember whether I made one. As with other devices, the free space check is likely an approximation.

Not all homebrew software support the HDD unit. This can only be solved by changing the source code and building a new copy.
 
sp193 said:
Those system partitions are not meant to be accessed by the user. Much like how you would not be encouraged to keep user files in C:\WINDOWS\SYSTEM32.
Click to expand...

Mostly user files for Windows are stored in "Users" or in "Documents and Settings".
Although... Windows XP keeps basic programs in SYSTEM32 e.g. Notepad, Paint, etc.

sp193 said:
Most of those partitions are also supposed to be password-locked to protect them and they are also invisible to the HDD browser, so the user cannot manage content stored in there. __sysconf and __common are meant for access by any software, but they are meant for storing system configuration (including shared libraries like ATOK), while __common contains the user's save data.

I am not in favour of people messing with __system. FHDB is installed to __system, not __sysconf. Although it keeps its settings and USB modules in __sysconf.
Click to expand...

I understand that messing with "__system" is not a good idea.
I was thinking that settings, USB modules, "FMCB_CFG.ELF", "endvdpl.irx" maybe can be stored in
"hdd0:/__sysconf/FHDB"
not in "hdd0:/__sysconf/FMCB".
It's only a cosmetic change, probably even not needed, since no one "complains" about it earlier.

Boot (BOOT) application like ESR or wLe can be stored in
"hdd0:/__sysconf/FHDB/BOOT" or in "hdd0:/__sysconf/FMCB/BOOT"
instead of "hdd0:/__sysconf/FMCB/".
Other application can be stored in
"hdd0:/__sysconf/FHDB/APPS", "hdd0:/__sysconf/FMCB/APPS".

Theoretically almost the same situation is on MC, where
APPS are in "mc?:/APPS", BOOT is in "mc?:/BOOT".

sp193 said:
Not all homebrew software support the HDD unit. This can only be solved by changing the source code and building a new copy.
Click to expand...

Unfortunately I know that not all homebrew software doesn't support HDD, but...
changing system setting path it is only a suggestion.
You probably know after many version that you've made, what will work as it should.
Thanks for feedback & support.
 
jolek said:
I was thinking that settings, USB modules, "FMCB_CFG.ELF", "endvdpl.irx" maybe can be stored in
"hdd0:/__sysconf/FHDB"
not in "hdd0:/__sysconf/FMCB".
Click to expand...

As for this, it makes sense. I don't know why I missed it in 2013. Maybe because the idea was that it was "FMCB on the HDD", so it was kept as "FMCB". Before I created the PP.FHDB.APPS partition, FHDB only used the FMCB folder.
But since 5 years has passed with the mistake, there has to be a proper procedure for handling the change in the directory's name in all affected software. So it will have to take a lower precedence than the more severe stuff, like features that do not work.

jolek said:
It's only a cosmetic change, probably even not needed, since no one "complains" about it earlier.
Click to expand...

I do appreciate how you have been willing to help to test and give suggestions, really. But, I cannot spend any more time on PS2 software than I currently am committing to every week - so I will have to contribute where I can and should. My focus now is on only bugfixes and maintenance of my own projects. Even so, bugfixes from me are also taking really long to come.

It's become like that because 2018 is the final year of my course. It went from having just 5 core modules to study for, to having the final year project that took up most of my time and the rest was given to studying... to now having a fulltime internship that requires me to be in office during office hours, everyday (by contract). I also refrain from doing anything related to the PS2 during work, as anything done with office resources becomes the company's property.
In the past, I used to be able to mess with the PS2 anytime I liked. Nobody could stop me from replying to messages on forums either.

So now, for those things that I cannot do, I would rather tell you that I cannot/will not do it, with an explanation if possible. I'm sure you deserve to know why I won't do things. Naturally, it will sound negative because the act of refusing something is inherently negative. But I think this is better than making empty promises or letting never-ending wishlists exist, regarding things that I have no intention of doing. I am really sorry for that.
 
sp193 said:
As for this, it makes sense. I don't know why I missed it in 2013. Maybe because the idea was that it was "FMCB on the HDD", so it was kept as "FMCB". Before I created the PP.FHDB.APPS partition, FHDB only used the FMCB folder.
But since 5 years has passed with the mistake, there has to be a proper procedure for handling the change in the directory's name in all affected software. So it will have to take a lower precedence than the more severe stuff, like features that do not work.
Click to expand...

Yea, fixing "real" bugs is more needed that doing "cosmetics", since you're very busy in real life.

sp193 said:
I do appreciate how you have been willing to help to test and give suggestions, really. But, I cannot spend any more time on PS2 software than I currently am committing to every week - so I will have to contribute where I can and should. My focus now is on only bugfixes and maintenance of my own projects. Even so, bugfixes from me are also taking really long to come.

It's become like that because 2018 is the final year of my course. It went from having just 5 core modules to study for, to having the final year project that took up most of my time and the rest was given to studying... to now having a fulltime internship that requires me to be in office during office hours, everyday (by contract). I also refrain from doing anything related to the PS2 during work, as anything done with office resources becomes the company's property.
In the past, I used to be able to mess with the PS2 anytime I liked. Nobody could stop me from replying to messages on forums either.

So now, for those things that I cannot do, I would rather tell you that I cannot/will not do it, with an explanation if possible. I'm sure you deserve to know why I won't do things. Naturally, it will sound negative because the act of refusing something is inherently negative. But I think this is better than making empty promises or letting never-ending wishlists exist, regarding things that I have no intention of doing. I am really sorry for that.
Click to expand...

You forgot to add:
funny-baby-23.jpg
8d2ad9671de3.jpg


I appreciate your work and wish you all the best, so that you'll get your dream job.
Thanks for all of your Homebrew, help & support.

Best regards.

BTW I really do not need any explanations.
Although thank you for sharing facts.
Real life comes first.
 
Last edited:
FMCB v1.965 (installer v0.985) released!

Changelog for installer v0.985:
  • Added font glyph caching, to improve on font-drawing performance.
  • Updated LaunchELF.

Changelog for FMCB:
  • N/A

Downloads/Links
FMCB + FHDB + installer project page: https://sites.google.com/view/ysai187/home/projects/fmcbfhdb

jolek said:
I appreciate your work and wish you all the best, so that you'll get your dream job.
Thanks for all of your Homebrew, help & support.

Best regards.

BTW I really do not need any explanations.
Although thank you for sharing facts.
Real life comes first.
Click to expand...

Thank you for your understanding.
 
Last edited by a moderator:
sp193 said:
Added font glyph caching, to improve on font-drawing performance.
Click to expand...
Thanks for this improvement. After quick check... everything should be fine.
image.gif

sp193 said:
Updated LaunchELF.
Click to expand...
What do you think about also publishing wLe from 24\11\2018 (commit 0ed4589) in wLaunchELF Release Thread?
Latest version in that thread is from 04\11\2018 (commit ff91651).
Automated daily build for OPL and wLe are broken... :(
 
sp193 said:
  • Updated LaunchELF.
Click to expand...

I've notice when I was installing newest FMCB on MC that there is "LAUNCHELF.CNF" in ".../INSTALL/BOOT/".
[181208]FMCB-1965-bin.7z.
When I run wLe, TV will switch into 480p and the buttons are swapped ("O" is for confirmation").
My config have previously 576i and "X" for confirmation.
This "issue" might cause black screen on TV's that do not support this mode.

"Fix" for this problem, will be delete "LAUNCHELF.CNF" from ".../INSTALL/BOOT/".

Everything is fine with FHDB, because there is no "LAUNCHELF.CNF" in ".../INSTALL/BOOT-HDD".
 
Last edited:
The issue had been reported before on another board and @Jay-Jay posted an issue about it on GitHub (as far as I read his reply in the thread).
 
You must log in or register to reply here.

Similar threads

Back
Top