User talk:Euss

From PS3 Developer wiki
Jump to: navigation, search

EussNL.jpg

"Fool climb tree to get cherry. Wise man spread limbs."

dev/random[edit]

lol
Euss (Talk | contribs | block)‏‎ (bureaucrat, oversight, administrator) [1,337 edits in the last 30 days]
omfg
    
ID    nick    Created Date           User Touched Date      Last Edit Date         Edit Count
13    Euss    02:59, 8 April 2011    16:05, 6 April 2013    14:30, 6 April 2013    10080

Links[edit]

Experimental Main Page

http://pastie.org/9784204

Messageboard[edit]

Changed the capcha to simple and added this: http://www.mediawiki.org/wiki/Extension:SyntaxHighlight_GeSHi Let me know if there are any other extensions that could be handy - defyboy

Thanks - euss

Templates[edit]

  • Templates

Something looks broken in some templates (e.g. the ones that are using this image: Imbox content.png, and some others that are using the other icons that appears at the bottom of Category:Templates <-- those are imports from wikipedia or others.

After looking at most of them... i think all the templates needs a revision/update, i imagine you or other members of the staff are aware of it (there are logs of changes in lot of them), and also i imagine is not an easy task, but there are some easy to fix:

^ all above are new 'experimental' formatted using templates to make sure page structure stays uniform while making auto menus more easier


Some icon templates has been replaced by a new ones with better resolution icons, and the names of the files/templates follows a new "naming convention", the new ones are "icon category xxx"

Also, the names for "icon content xxx" templates has been changed, but not the names of the files (can be erased and uploaded again but this is for paranoid ordering)

Another templates for icons that can follow this "naming convention" are the "icon media xxx" (the 4 templates with tiny disc icons used in emulation page mostly)... and "icon controller xxx" (the dualshock and move buttons that are a lot, but are not used too much in other pages)

sandungas

Uncomfirmed Filesystem mountpoints[edit]

Hi euss.. i found these FS supported by the PS3 on the net. they aren't listed on the wiki:
CELL_FS_ADMINFS // ???

CELL_FS_DUMMYFS , /host_root , /app_home
CELL_FS_HOSTFS
CELL_FS_PSEUDO

CELL_FS_EFAT, /dev_usb000 (what is the difference between this and CELL_FS_FAT?)
CELL_FS_PFAT, /dev_usb000 (what is the difference between this and CELL_FS_FAT?)

CELL_FS_LOOP

Listed on the wiki
CELL_FS_UFS
CELL_FS_ISO9660
CELL_FS_UDF
CELL_FS_FAT
CELL_FS_SIMPLEFS

i only need to know if they are real or not and what they do.
Here are the Mountpoints that are listed on the wiki Files on the PS3.. maybe a new page with them can be really useful!
Deroad 16:07, 28 June 2012 (MSK)

shop firmware[edit]

Euss, have you used 4.3X shop firmware before? As the 4.3X still uses the same method that pre 4.3X firmwares to stub all XMB items except those "sel://" calls, stubbing those is done by the modules which prevent them from working.--Ps3hen 15:34, 19 November 2012 (MSK)

Actually I was referring to CEX/Retail and the default MFW tasks used to add Install Packages. Didnt look far into it, was just glad to see wiki was up, saw your edit and it reminded me of something in my backlog of that day, so I thought, lets add that note before I forget Euss

About the naming of Shop FW. Terms like "SEX" are just pseudonyms, shop firmwares are technically CEX firmwares, they only work on ps3s with a retail (CEX) Target IDs, and the term "shop" is only mentioned in the index.dat, version.txt, vsh.self(update URL). The term "SEX" is never mentioned in Shop FWs. In the UPL.xml, shop FW uses the same <Product> value as retail FW (CEX-ww). I personally think it is incorrect to exclusively refer to retail FW as CEX FW, and then to say shop FW is SEX firmware as if it is SEX is another kind of target ID. It's more correct to say Retail FWand Shop FW and class them both under CEX Firmware, or Firmwares made for CEX consoles. And as a side note, because they are both made for CEX PS3s, it is relatively easy to install either retail or shop fw on a CEX PS3 regardless of which one is already installed. Just generally, naming FWs after target IDs is incorrect, it just so happens that for all PS3 types (except CEX) there is only one FW type which can be used with it.--Ps3hen 09:18, 22 November 2012 (MSK)

The SEX shortcode is just a made up name. It saves you from writing "CEX/Retail patched to Shop/Kiosk/Demonstration by adding promo_flags in root of PUP or a firmware officially downloaded from Shop updater server which updates independant from normal CEX/Retail server" - see also Target ID Euss
I see, well perhaps having a note next to SEX Firmware in the software settings table, just so people understand it's a CEX firmware too. Yes I have seen the Target ID page recently.--Ps3hen 10:18, 22 November 2012 (MSK)


DEH-H1001-D[edit]

Hi,
if you have a NAND-Dump of this console, try to get the auth-id's of some selfs, then compare them with the auth-id's of the installed FW (original PUP/ROM), then you know which FW is installed. (e.g vsh (DEX): 10700003FF000001; vsh (CEX): 10700005FF000001)
Regards, Strike Venom 16:25, 16 December 2012 (CET)

Havent looked at authIDs, but I know both ROS where filled with 0.85.009 which is a DEX preretail FW - thus I assumed it was the DEH/cookie13 (it is a cookie13 for sure). But looking at the TargetID 83 made me doubt and it seemed a CEX preretail. Perhaps it is a CEX QA flagged, capable of runnning DEX - like that CBEH.
Euss
It could be a special QA Token Flag that allows installing of FW for other Target-IDs or the FW just doesn't check the Target ID. (Or: Maybe it's a preretail CEX FW?; The CBEH (CECH Prototypes) that I know do have CEX Target ID)
Strike Venom
These are the 085.009 AuthIDs
Euss
OK, it's the "normal" 085.009 ROM -> Either it's not checking the Target-ID (If you look at the ebootrom structure, there's no way for the installer to determine for which Target ID this Update is) or a special QA-Flag is required.
Update: I asked someone who owns a DEH-H1001-D and he says that the PS3 accepts only DEX Updates (even 4.30+!), so if this is a valid dump from a DEH-H1001-D, there must be something else that allows installing DEX FW on CEX.
Strike Venom

Is it me or DEH-H1001-D (COOKIE-13) 0x1 metldr revision key just changed ? O_o

-Mathieulh


This is how I have it:
Offset(h) 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F
00000000  00 00 2A 7F 12 1D 73 39 4A F2 98 81 F8 D6 B1 8C  ..*...s9Jò˜.øÖ±Œ
00000010  00 00 2A 7F                                      ..*.
  
00040840  00 00 0E C0 66 45 66 FA 77 88 F8 43 2F B7 AA 62  ...ÀfEfúwˆøC/·ªb
00040850  00 00 0E C0                                      ...À
  
00080870  00 00 00 01 00 83 00 01                          .....ƒ..
  
0F000000  00 00 2A 7F 12 1D 73 39 4A F2 98 81 F8 D6 B1 8C  ..*...s9Jò˜.øÖ±Œ
0F000010  00 00 2A 7F                                      ..*.

which is that COOKIE-13 board with CEX tid added in Talk:Flash:asecure_loader&diff=next&oldid=18285 Euss br />Euss

OK, it's the "normal" 085.009 ROM -> Either it's not checking the Target-ID (If you look at the ebootrom structure, there's no way for the installer to determine for which Target ID this Update is) or a special QA-Flag is required.

logged in/off discrepancy[edit]

<sandungas> i realized why happens the problem i commented the other day about wiki main page not displayed in my browser
<sandungas> it happens ALLWAYS when you are "logged off"
<sandungas> because i dont use autologin in my browser... i always have the problem :)
<sandungas> ...is also because i have the link stored in my browser as http://www.psdevwiki.com/ps3
<sandungas> instead of http://www.psdevwiki.com/ps3/Main_Page
<sandungas> when you are logged in..... and you click in navigation links at left... for "PSdevwiki"... note the link points to http://www.psdevwiki.com/ps3
<sandungas> but you are automatically redirected to http://www.psdevwiki.com/ps3/Main_Page (because you are logged in)
<sandungas> this redirection doesnt happens when logged off :'(

Problem solved--Sandungas (talk) 03:14, 15 December 2014 (EST)

TSL.elf (contains dwarf symbols)[edit]

here's something for you https://mega.co.nz/#!8gFmVISS!YVoW6We6sRKQVIh8UJdb08LJaUByl2dVLQUDZNhLjIk

gift[edit]

https://dl.dropboxusercontent.com/u/35197530/coolstuff/gift.7z

Back on board[edit]

Board load[edit]

Sorry about the lack of updates, I'm back on board to tidy a few things up. I've doubled the RAM on this box so it's much faster but the main page is still dog slow, I propose we update to a much simpler template to lighten the load. Example: http://www.psdevwiki.com/ps3/Template:Main/sandbox Thoughts? Next order of business: spam Admin (talk) 18:21, 1 April 2015 (EDT)

I've fixed the caching and pages are alot quicker. Main page is also quick now Admin (talk) 06:17, 5 April 2015 (UTC)
that really fixed it, reaching the below quarter second serving again! Euss (talk) 13:46, 5 April 2015 (UTC)
Current NewPP/Served reports[edit]
PS4 PS3
Preprocessor visited node count: 14347/1000000
Preprocessor generated node count: 15041/1000000
Post‐expand include size: 519913/2097152 bytes
Template argument size: 225069/2097152 bytes
Highest expansion depth: 17/40
Expensive parser function count: 0/100
Served in 3.727 secs (before)
Served in 2.714 secs (after cachefix)
Served in 0.161 secs (after disabling {{Recent Changes}})
Preprocessor visited node count: 32997/1000000
Preprocessor generated node count: 22189/1000000
Post‐expand include size: 1318573/2097152 bytes
Template argument size: 788722/2097152 bytes
Highest expansion depth: 25/40
Expensive parser function count: 0/100
Served in 8.540 secs (before)
Served in 0.199 secs (after cachefix)
PS4 /minimalistic PS3 /minimalistic
Preprocessor visited node count: 364/1000000
Preprocessor generated node count: 7327/1000000
Post‐expand include size: 12252/2097152 bytes
Template argument size: 3321/2097152 bytes
Highest expansion depth: 12/40
Expensive parser function count: 0/100
Served in 0.151 secs (before)
Served in 0.143 secs (after cachefix)
Preprocessor visited node count: 409/1000000
Preprocessor generated node count: 7393/1000000
Post‐expand include size: 11391/2097152 bytes
Template argument size: 5491/2097152 bytes
Highest expansion depth: 12/40
Expensive parser function count: 0/100
Served in 0.361 secs (before)
Served in 0.139 secs (after cachefix)
PS4 /iconic PS3 /iconic
Preprocessor visited node count: 338/1000000
Preprocessor generated node count: 7157/1000000
Post‐expand include size: 14244/2097152 bytes
Template argument size: 3629/2097152 bytes
Highest expansion depth: 13/40
Expensive parser function count: 0/100
Served in 0.155 secs (before)
Served in 0.144 secs (after cachefix)
Preprocessor visited node count: 324/1000000
Preprocessor generated node count: 7115/1000000
Post‐expand include size: 9302/2097152 bytes
Template argument size: 2718/2097152 bytes
Highest expansion depth: 13/40
Expensive parser function count: 0/100
Served in 0.314 secs (before)
Served in 0.234 secs (after cachefix)

crosscomparison:

new vs hosted NewPP/Served reports + webpagetest.org bench[edit]
temp::PS4/User_talk:Euss/sandbox hosted::PS4/User_talk:Euss/sandbox
NewPP limit report
CPU time usage: 29.183 seconds
Real time usage: 29.258 seconds
Preprocessor visited node count: 124113/1000000
Preprocessor generated node count: 33737/1000000
Post‐expand include size: 157131/2097152 bytes
Template argument size: 23830/2097152 bytes
Highest expansion depth: 9/40
Expensive parser function count: 45/100
webpagetest.org:
First View (Run 2)	16.301s
Repeat View (Run 2)	1.395s
NewPP limit report
Preprocessor visited node count: 124073/1000000
Preprocessor generated node count: 33737/1000000
Post‐expand include size: 157131/2097152 bytes
Template argument size: 23830/2097152 bytes
Highest expansion depth: 9/40
Expensive parser function count: 45/100
Served in 20.684 secs
webpagetest.org:
First View (Run 1)	15.450s
Repeat View (Run 2)	2.279s
  1. the above page is handpicked to be a worstcase scenario for the parser as well as HTML/render elements (flag IMG)
  2. there is a significant difference between the NewPP reported time and the realworld
  3. imo, the performance could possibly improved by Localisation Caching and/or some form of page cache, like Varnish/Squid or File_Cache

Spam[edit]

It seems QuestyCapcha is still the preferred option as all the other Capchas are broken but it needs to be updated regularly to be effective. I will likely write a script to rotate the questions weekly and preload it with a large list. 101.98.201.24 18:45, 1 April 2015 (EDT)

Can be added a new "reason" when deleting a page for "Spamming" ?. Because we have been banned spambots accounts argumenting the reason "Spamming", but when deleting the pages they created in the predefined reasons the most close is "Vandalism"... but it looks a bit weird to give 2 different reasons for cleaning up the mess made by the same user. Is better to use the same reason "Spamming" for both banning the user and deleting his pages --Sandungas (talk) 03:08, 9 April 2015 (UTC)
http://www.psdevwiki.com/ps3/edit/MediaWiki:Ipbreason-dropdown
http://www.psdevwiki.com/ps3/edit/MediaWiki:Deletereason-dropdown
Euss (talk) 14:15, 9 April 2015 (UTC)
Also, is posible to display the "Other/additional reason" as empty when deleting a page ?... because by default it displays the "content was: <spam here>" so is needed to delete it, otherway if not deleted it works as spam and we are recording it in the wiki deletion logs and appears in the "recent changes" page --Sandungas (talk) 03:08, 9 April 2015 (UTC)
I understand your issue, but not always it needs complete removal (only in the case of spam, in which case I 'CTRL-A "SPAM" TAB TAB ENTER or script it) Euss (talk) 14:21, 9 April 2015 (UTC)
 # Sample script spambot
 TAG POS=1 TYPE=SELECT ATTR=ID:mw-input-wpExpiry CONTENT=%infinite
 TAG POS=1 TYPE=SELECT ATTR=ID:mw-input-wpReason CONTENT=%Spamming
 TAG POS=1 TYPE=INPUT:TEXT ATTR=ID:mw-input-wpReason-other CONTENT=SPAM
 TAG POS=1 TYPE=INPUT:CHECKBOX ATTR=ID:mw-input-wpAutoBlock CONTENT=YES
 TAG POS=1 TYPE=INPUT:CHECKBOX ATTR=ID:mw-input-wpDisableEmail CONTENT=YES
 TAG POS=1 TYPE=INPUT:CHECKBOX ATTR=ID:mw-input-wpConfirm CONTENT=YES
 TAG POS=1 TYPE=INPUT:SUBMIT ATTR=VALUE:Block<SP>this<SP>user
 # Sample script spampage
 TAG POS=1 TYPE=A ATTR=TXT:Delete
 TAG POS=1 TYPE=SELECT ATTR=ID:wpDeleteReasonList CONTENT=%Spamming
 TAG POS=1 TYPE=INPUT:TEXT ATTR=ID:wpReason CONTENT=SPAM
 TAG POS=1 TYPE=INPUT:SUBMIT FORM=ID:deleteconfirm ATTR=ID:wpConfirmB
Euss (talk) 17:25, 9 April 2015 (UTC)

Daily Dumps[edit]

seen a new dump being made, hope it is not onetimeonly

Hopefully not, ps3 database still freezes the script which is a huge PITA so I will try and narrow this one down. Running some maintenance on the ps3 database at the moment. 101.98.201.24 23:23, 5 April 2015 (UTC)

Still not able to get dumps consistently, sometimes the script freezes indefinitely and locks access to the wiki. I have written a script to terminate this after 60 seconds if it fails so you will atleast get dumps _somtetimes_ 101.98.201.24 00:19, 6 April 2015 (UTC)

Elevation user rights @ xbdevwiki[edit]

Could you elevate my user rights on xbdevwiki to e.g. Check users + Administrators, Bureaucrats - that way I can help out cleaning the spam there - Euss (talk) 15:45, 5 April 2015 (UTC)

Added, WOW that ones been spammed bigtime. Was there any actual content on there? Perhaps we should just remove or re-start it. - Admin

I can clean the spams there too if needed --Ada L0ve Lace (talk) 17:18, 5 April 2015 (UTC)
Elevated both Ada L0ve Lace‎ and Roxanne - the former is already a sysop/Administrator on PS4+vitadev wiki, the latter can use use the xbdevwiki for some experience as sysop/Administrator, optionally also to get elevation later on PS4 wiki - Euss (talk) 03:22, 6 April 2015 (UTC)
Cleaned up "some" spam :) Euss (talk) 03:22, 6 April 2015 (UTC)
Blocked more than 800 spam users today on xbdevwiki (spam users registered from 25th February 2015 until now). Roxanne (talk) 22:56, 7th April 2015 (GMT+1)

Server Move[edit]

That time again, I'm ditching this host. Hopefully this won't create too much hassle. It would be best to update to the latest MediaWiki and PHP at the same time however. I will build up the server and get an instance copied over there for testing. Where would be the best place to communicate over this? 203.114.137.32 00:51, 8 April 2015 (UTC)

IRC efnet private messaging or #xbdevwiki
http://www.vitadevwiki.com/index.php?title=User_talk:Euss#psdevwiki (is hosted by GregoryRasputin from http://playstationhax.it/)
email as used by wiki
Euss (talk) 02:26, 8 April 2015 (UTC)

User / rights DB collision[edit]

There is no 100% seperation of User rights between ps3/ps4/xone. getting higher privs on any increases rights on all (without even being logged on the others) - imo this is a security risk
When trying to recreate the issue, user:Sampleuser was made on xbdevwiki and given "bot" rights, to be rechecked on ps/ps4 devwiki:

at this moment, the issue does not recreate on all wikis, it is a bit erradic.

The issue came to attention when user:Roxanne was given Check User rights on xone and also had Check User on ps3/ps4 without given officially

as you can see, it is a bit erradic in how many wikis are going to be affected, sometimes 1, sometimes all Euss (talk) 23:16, 11 April 2015 (UTC)


Front Page Links[edit]

Hey man, I just wanted to suggest changing the dead links on the front page under Reverse Engineering → Emulation to their respective PSX/PS2/PSP _emu page section. Alternatively, it would garner more attention to have the PS2 Classics Emulator Compatibility List and the (recently created) PSP Emulator Compatibility List linked on the front page. I'm sure more people would contribute and they would be adapted as the "official" ones in the community. Just some thoughts, cheers! ~Derf Jagged

  • Done, but it could take 24 to 48 hours that it will be displayed correctly on the front page (and all other pages who shares this template) - Roxanne (talk) - 05th June 2016 - 23:47 GMT+1

Hard Drive Page[edit]

Hey Euss, I noticed that the hard drive page was locked, but needs some cleaning up. For instance, 1.5TB support was added in some firmware update (between 3.56 and 4.55?) and definitely works in current OFW, and also models are listed in the table, but in the "temporal notes" says it is missing. Could you unlock this page for edits? ~Derf Jagged

  • Which page exactly? According to the logs, the Harddrive page should be already unlocked since 5th February 2014, 12:17h - Roxanne (talk) - 01st November 2016 - 18:19 GMT+1
  • The "temporal notes" below the table are listing some PS3 models that we had no idea (because nobody reported it and was not posible to find info in google about them) wich hdd model had at release date from factory (the PS3 models with unknown hdd's are: CECHMxx 80GB, CECH-21xxA 120GB, CECH-21xxB 250GB, CECH-25xxA 120GB, CECH-25xxB 250GB, CECH-40xxA 12GB, CECH-40xxB), at the right of those PS3 models appears a posible hdd model that sony was using at that date but are speculative though. After verifyed can be removed from that list and added to the table--Sandungas (talk) 19:08, 1 November 2016 (UTC)
  • Also, at this point probably the table is missing some hdd models used by sony in new PS3 models (the newer ones from PS3 superslims) if exists are needed to be added in rows in between the table, the table is a bit hard to edit (it uses lot of rowspans and separation cells) if you need some help to edit it i will take a look--Sandungas (talk) 19:08, 1 November 2016 (UTC)