[Melba59]

just want thank you for your work....
__________________

[sandungas]

I remembered there has been a problem in the ATTRIBUTE table from the begining that is related with the way the table is build

The problem is with "PSP Remote Play in MPEG4 AVC/AAC "... is an cummulative flag (it needs "PSP Remote Play in MPEG4 SP/ATRAC " activated)
This is what "SFO editor" by hellcat says... but i never tested it

The consequence is that you need both remote play modes activated for the MPEG4 SP/ATRAC (in high quality) to work
Something similar happens with NEOGEO (it needs PCengine activated to work)

The table has been separated all this time in rows with 1 flag each (and this problem with remote play modes ignored and explained in the descriptions out of the table)... maybe is needed to add rows with severall flags

----------------------------------------------

Please ada post here your test from today as you did in the last message, tomorrow i will verify if the remote play mode flags are cummulative, and maybe a few more as you said keeping a proper SFO for this kind of content (the 2 errors i saw with hidden mini-icons are suspect and reading what you are saying are suposed to be X1 and X2), also i didnt tryed X3

[Lady Anne Blunt]

In fact, to got NEOGEO appear on your xmb, you don t really need PCEngine.

Try this for the 4 byte:
00 00 20 04 : you got your NEOGEO with "half" PCEngine.
For the X category: three conditions: Parameters-the 3byte set as 20 (in this case we can said it used as a flag) and after that, PS3 will only look to the last content of the last byte.
This is the X maker.

In this example, it s 4= PS3 get this HG (even not sur if the name code category will matter, will test) as X4.

Others examples (tested on the laboratory side):
00 00 20 14: still X4 for the system. A weirdos X4 with errors but still X4.

Try this:
00 00 20 00 : you ll get PCengine.
(because the 4byte said 0 so = X0. Same if you try 00 00 20 10)

It s because PS3 got enough to believe it s PCEngine.
If in "reality", it s something more like 20 00 60 00 for PCEngine, it s because the first 3 byte are still used as a flag.
And for X0&X4, first flag "XMB in game" is just set automatically.
the N23 (40) flag is used as "disable system boot logo (i didn t have seen it because i don t have a working X0 or X4 / or need to go back to 2.70 because it s probably the system boot logo)

If you try:
00 00 20 08: system go back to X0---so there are no X8
00 00 20 09: system go back to X1---so there are no X9
00 00 20 10: system believe it s X0 because of the last content.

One more thing i need to make sur it s the position folder and if we can have differents X category (without considering X0&X4) at the same time (i just tested over same game again and again but probaly yes)

From here, i think the last bytes was never really used as flag, but for X category. Your update on wiki (chronologically column) help a lot to understand them. But we can t be so sur about the dates since since somes are from commercial purpose (NEOGEO was release a little after 3.55 was out but if i understand right you even have it on 3.41) and not when it was implatend on the system.

But it s more like this:

Click here to see full text

00 00 01 00 00 01 00 00 00000000 00000001 00000000 00000000 Install Disc (containing only Install Packages)
00 00 02 00 00 02 00 00 00000000 00000010 00000000 00000000 Install Packages (from folders PKGDIR or INSDIR in Discs)
00 00 04 00 00 04 00 00 00000000 00000100 00000000 00000000 Unknown !
00 00 08 00 00 08 00 00 00000000 00001000 00000000 00000000 Game Purchase Enabled
00 00 10 00 00 10 00 00 00000000 00010000 00000000 00000000 Unknown !
00 00 20 00 00 20 00 00 00000000 00100000 00000000 00000000 Flag for activate X category Jul 15, 2009
00 00 40 00 00 40 00 00 00000000 01000000 00000000 00000000 License Text hidden
00 00 80 00 00 80 00 00 00000000 10000000 00000000 00000000 Move Controller Compatible fw 3.40 (Jun 29, 2010)
For the 4 bytes, it s not anymore flags (or not only)
00 00 00 00------------------------------------X0 PCEngine
00 00 00 01------------------------------------X1
00 00 00 02------------------------------------X2
00 00 00 03------------------------------------X3
00 00 00 04------------------------------------X4 NEOGEO (it s also the 3 third flag but don t matter here)
00 00 00 05------------------------------------X5
00 00 00 06------------------------------------X6
00 00 00 07------------------------------------X7
00 00 00 08------------------------------------X0 (because there are no X8 or at least not in 3.55
00 00 00 09------------------------------------X1 (same reason)
00 00 00 10------------------------------------X0 (because there are no X10 and the system will just care about the 0, not the 1 on the 10. And will complain because the system still paid attention about the 4 bytes as possibles flags.
00 00 00 11-------------------------------------X1 again.

-----------------

One bad news is my X category i believed was under Minis folder is in fact just a broken "corrupted data" sfo (under fake HG but still the ps3 can identify as MN because the X maker on the 3 byte is missing. Probably because she found something else on game structure who belong to MINIS ( EBOOT.PBP , MINIS.EDAT or anything else ), and classify as default under MINIS but don t like it anymore and give error when trying to boot) so.... that is bad new.

-----------------------

We can think X5, X6, X7 are not use yet but X1&X2&X3? something between PCengine and NEOGEO and not necessary "release" untill now.

And from PSP side (since we know psp export is working) ...there are no more catgeory who can be copied to PSP (PCEngine, NEOGEO, MINIS, Playstation1)
or i missed.
It can be also the psp export working without complaining (because under MINIS game structure) and no real connection with X category.

Also if you don t have same result as i described... blame your "retail" PCEngine or NEOGEO sfo file (i didn t really check yet if there are differences with my creatures, but if so...my creatures are more trustable.

--------------------

When i said the 4 bytes are not anymore flags (or not only):
00 00 20 08-------------so the system believe it s X0 (because after X7, nothing more yet so come back to the first category) but after that....he see the flag N28 activated (08) and make him confuse because X0 don t need that.

------------------
trying to compensate my poor vocabulary with more details anyone really need but flags N25 to N32 (to don t make it complex for the moment but worst scenario:we can imagine also all the others flags) are not only read as binary in the case of X category but also as simple value in little endian.

About flags cumulatives: i may have other example (but need more test) and may be can also depend on category (but only fews case and not necessary real dependance)

Sorry in advance for the edits on wiki, and the new column "N" is may be not necessary (i ll edit if you think it s too much)

----------------------
Little humor: in fact i wasn t sur to speak about thoses X category (especially others than X0&X4) on the wiki was a good idea but since someone else can test them fully ( with ps vita) to make sur they aren t really usefull but...anyway, if you got something usefull with them, please remember Sandungas s work on that page.
For the wiki reader(s) who make apps, sorry but for the moment X category are useless (and bad idea) in case you still wonder to update your stuff.
--------------------
other example

Click here to see full text

(because i not really good about explanations and i was a lot confuse for fews days about theses X category )
Under fake HG parameter,
22 00 60 01: Ps3 will classify as X1 category because there are the X maker read as binary, psp export (this one can be view even we can t boot the game, give XMB music ( i described this flag as XMB in game, sorry for the mistake), give also attribut N23 "disable boot logo" by the system (but not yet verify). The "boot logo disable" can be the old flag used previously (ofw 2.80 or older) but you can still have your X category without it (but for being more correct, let s say it better to have it)

But now in theory (not yet tested untill i got real working X0 or X4) if you try this:
22 00 60 11: you got X1 NEOGEO appear on XMB (because of last 1), music in game, psp export, boot logo disable (let s say only on 2.80 or older) but also a possible unknowns attributs flags N25& N29 (at least the system will paid attention in that way also)

[deroad]

sandungas asked me to build a simple homebrew that it's fast to delete/install to test SFO stuffs. here it is: http://www.mediafire.com/?325cq3iea259c3j

[sandungas]

Thanks deroad, i thought in this severall times (to use a tiny program as an "standard" for experiments), and i remembered it when i saw you

From now on... i will use it for all the tests with "bootable" contents, content information files (ICON0.PNG etc...), HIP/HIS, and to experiment with patches later
For all the other contents (that are not bootable)... well, there is no standard i think, so cant be "standarized for experiments" like this

So now that we have our monster i was training him a bit, by now it knows all this flags

All are verifyed before, working, and documented in the wiki
But the ones marked in blue are the ones i could test in your program
For the others... i have problems
-Move Controller Compatible <----- probably i can just enter and pressing "X" in the move controller is enought, but i was bored
-Calibration notification screen <----- this is a menu for calibration of the move controller, to make it appear first is needed to "de-calibrate"... i was bored
-3D warning screen <--- is only visible in 3D tv's and i dont have one
-the ones related with XMB In-Game... as i said you in the IRC... i cant see the XMB In-Game in your program... i never saw this error, is something related with the program (i use to make this tests in a SD tv)

But like i said... all this files are fine and verifyed before in other contents/games
I didnt included the 2 ones related with blue-ray discs because obviously will not work, but these are verifyed too

I zipped all them (and another folder with the "unknown" ones) + your program and uploaded here ---> http://www.sendspace.com/file/ix9iun

Please all the people that is experimenting with this use this program when possible... and upload a proper files for it if you find new flags or tweaks

---------------------------------------------------------

Ada, im not sure yet if the correct way to order this X0/X7 is exactly as you said
Note in this files the "PCengine Classics Game" flag works alone (is not a combination of 00002000 + 00000001)

If we find another content that uses this method (another X displayed as different in XMB)... this can be decisive to take a decission... but for this maybe we need to wait for sony to implement new formats... and this can be long

-----------------------------------------------------------

While testing this files i remembered there are another "cummulative" flags... (the ones related with move), so well... i imagined how to edit the table in the wiki
As cummulative there are:
1 psp remote play mode
2 warning screens from move
1 neogeo

[Lady Anne Blunt]

----------Deroad,

Thanks you a lot

------------

Sandungas,
It s confusing because i m really bad about explanations and there are still the possibility the 4bythes (flags N25 to N32) can be used also as binary/ flag (i doubt now) but so far my tests show the 4bythes isn t used in that way but as bit value.
I m preparing 8 files (it will take time) and send by PM with SFO set in that way.
And in that way, NEOGEO don t really use the flag N27 but the last bit value (04 or 14 or 24 ...)
The position folder can give us something, not good as RCO or Name for the category
-------------------------------------
This time, double check for all of them, and i got this (at the same time so i needed fews mores games)

Playstation 3
minis
Playstation 2
Playstation
X1: -
X2: -
X0: PCEngine
X3: -
X4: NEOGEO
X5: -
X6: -
X7: -
Unknown (when sfo got too much errors)

X1-X2 / X3 position folder---?

When using sfo with differents bits values as 8 or 9 , it still unclear, probably because of the breaking point (3 possibles folder after tested: PS3-MINIS or Unknown) when on the laboratory side it was supposed to end at X0 or X1 (i believed i tested fews days ago and it was that the result)
For others bits, between 0 to 7: still fine and go to the last number category (12---X2)
( I send you couples of files on PM)

[deroad]

Originally Posted by Lady Anne Blunt ----------Deroad, Thanks you a lot ------------ Playstation 3 minis Playstation 2 Playstation X1: - X2: - X0: PCEngine X3: - X4: NEOGEO X5: - X6: - X7: -

For what?

anyway, i still don't understand this: PCEngine & NEOGEO emu comes from psn or they are homebrews that uses those categories?

[Lady Anne Blunt]

NEOGEO & PCEngine are from PSN and haves theirs little specifics grey icons from the ps3.
NEOGEO games come probably with emulator in built (Same probably for PCEngine)
page 12 Samson posted a link for somes of them #111)

[deroad]

i see.
i never downloaded those emulators from PSN

[Lady Anne Blunt]

Originally Posted by sandungas If we find another content that uses this method (another X displayed as different in XMB)... this can be decisive to take a decission... but for this maybe we need to wait for sony to implement new formats... and this can be long

got inside EBOOT.PHP sfo using same attribut than the laboratory X1.
Using the SFO s Tool test of Deroad to load this sfo and it went inside near the other X1 laboratory.
Checked one other minis in that way (eboot.php from minis installed on ps3, openning the eboot and check the sfo ) and also have.

It can explains why X1 don t have rco or name on xmb since it not suppose to be loaded at that point, the sub category and also the position folder (if we got official X2----1P?)

I didn t go more deep on the psp side, but there are probably a conversion/creation or mod of this sfo once he s on psp side.

The PM i sent has thoses hidden X1 SFO.

The Deroad s test tool can work even under X category (but not under 2G) when my minis were not allow (80010006)
It s really convenience, thanks you again for that.
(don t have XMB in game also from both pkg)