Editing User talk:Sandungas

<div style="float:right">[[File:Heatsink CECH-25xx metal cooling block (lapped detail).jpg|400px|thumb|right|Wiki hardware geek]]</div>

==My To Do wiki pages==

To fill (by me :P)... list of pages i started or i helped improving them but are not finished yet, with a temporal layout, needs a cleanup, or abandoned temporally for some reason.
===PARAM.SFO===
Neverending oddisey

===PARAM.PFD===
Dunno how

===ETC...===
I will make a better list when i find some time, sorry

==Lazy dog wiki tutorials==
===How to upload and display images (drunk spainglish saturday night edition)===
The purpose of this step-by-step tutorial is to use a method to upload images and display them in wiki in the most simple and fast way without the need to remember any wiki trick code or anything, the point is to have a solid procedure to remember and use always (is brainless and the fastest way i know)

The upload of images is simple, and the display depends of what you want to do with the image, are explained below

====Image upload====
*Step 1 '''Prepare the images in your PC'''
**Usually you need to upload several images to wiki custom made or found in internet, this explains the worst scenenario with multiple images and randon manes. Make a folder in your PC with any name is just temporal and in most cases is deleted at the end with all the images. Download the images in it and rename them conveniently. Is important to rename them at this point to simplify further steps
**The naming convention needs to be something most simple posible but also very explicit and keeping in mind that other images for the same "stuff" could be added later, as example for a hardware part dont name the image simply as this part, add to it a tail like "bottom view" "top view" etc... this way if someone in the future wants to upload another image for the same component they can name it starting with the component name and another tail like "perspective view", "detailed view", etc...
**This is also the time where you can crop the images (to keep only the interest area to make them smaller to improve wiki performance and display them better) rotate, or change the image format (.jpg preferibly, or .png if the images uses transparency) etc... even you can delete the EXIF information (usefull if you made the image from scratch to delete the track of the apps you used to create it). A great app for this small edition tasks is irfanview
**Warning !!! For some hardware components where is needed a detailed view (to identify traces, etc...) is better to dont make any edition to the image that could reduce the quality (so scale, rotation, or image format conversion are not a good idea to use if what you want to achieve is good quality, all them applyes an image filter)

*Step 2 '''Find an image in wiki that was uploaded before by another user and copy the footer'''
**Copypasting is the secret golden rule of wiki gurus, here what we need is to keep the wiki standards used to categorize images, long explain short... we use some categories to index the images but is a pita to remember them and how the tags needs to be added to the bottom of the pages so the easy solution (brainless, no need to memorize anything) is to copypaste them from another similar image, basically in wiki we use 2 categories for images that are "hardware" and "software" (and other for templates... different story though but the trick is the same, copypaste ftw)
**Personally what i do is to go to the main page, and take a look at the pages that appears in the main templates, you need to find one similar to the image you want to upload (and when clicking in it you need to be lucky for that page to use some image.... if not image is used then no luck and you need to try to find other)
**My favourites are:
***For software category - [[PlayStation 3 Theme (P3T)]] (the images used at top-right corner of the page)
***For hardware category - [[Motherboard Revisions]] (also, every one of the PS3 model pages and his motherboards)
**Go to one of that pages, click in one of the images (this makes your browser to jump to the image page), click in "edit" that page (you are not going to save the edit is for copypaste purposes), then copy the whole text, it will be something like: <nowiki>[[Category:Hardware]]PS3 - Motherboard - Multilayering</nowiki> (note how it starts with the categorizing)
**Click in the navigation links at left, out of the edition area, where it says "Upload file". Your browser opens the upload page

*Step 3 '''Upload the image, paste the footer and modify the description'''
**In the "Upload file" page, the first thing you need to do is to paste the footer you copyed before (the point is to paste it as faster as posible to dont lose it, probably you are copypasting other texts in your pc, or links to pages so is easy to lose it). Dont edit the description yet, by now is ok, following the example i used before what i need to paste is <nowiki>[[Category:Hardware]]PS3 - Motherboard - Multilayering</nowiki>
**Click in the "browse" button and select the first image (the image in my PC is named ''Panasonic MN864709 on a DYN-001 (perspective view).jpg'')
**The image is previewd in your browser (has not been saved yet to the server), and the "destination filename" is filled with the final image text. Copy this text
**Paste the text at the right of the footer you pasted before, so you will have something like: <nowiki>[[Category:Hardware]]Panasonic_MN864709_on_a_DYN-001_(perspective_view).jpg</nowiki>
**Restore the spaces, remove the file extension, so you will have something like: <nowiki>[[Category:Hardware]]Panasonic MN864709 on a DYN-001 (perspective view)</nowiki>
**Thats all, click in the "Upload file" at bottom of the page, profit, the image is uploaded to wiki, is using a good name, and follows the wiki category standards
**Repeat with the other images, remember, every time you want to upload a new image you need to copy the footer from another uploaded image to paste in the new one, this can be very confusing if done multiple times, it can be made fast but always keep an eye at the "summary" description it needs to match with the original name you used, also remove spaces and file extensions

====Display mode gallery====
*In wiki most of the times (most used as far i remember though im sure there are more) the images are displayed using 3 ways, as a "gallery" of images (used when is needed to display several images together), inside a <nowiki><div></nowiki> frame (used to display a single or couple of images in a bigger size displaced to right to serve as introduction to a page section or whole page), inside a table (for eyecandy, or to use the table contour as a frame limiter), or inside a template (to create wiki icons of small size)
*For the example im using, im uploading two photos using the <nowiki><gallery></nowiki> display mode, there are really a lot of pages in wiki using it, but im going to copy it from [[COK-00x|COK-001]] page (first hit in main page in one of the motherboard models)
*Click in the [[COK-00x|COK-001]] page, click in the "Edit" tab, scroll down to the edit area and copy one of the galleries completlly (all lines, lazy ass remember ?):
 <nowiki><gallery></nowiki>
 File:COK-001_TOP.JPG|COK-001 - top
 File:COK-001_BOTTOM.JPG|COK-001 - bottom
 <nowiki></gallery></nowiki>
*Go to the page where you want to add your shiny new gallery, click in "edit" the new page and paste the whole gallery (dont save your changes to the page yet)
*Now you need to replace the images by yours, go to the [[Special:RecentChanges]] page where you can see the links of the images you uploaded before, click in all them and open them in your browser in different tabs. In every image page, double click in the file name that appears on bold at top and copy (is the name with spaces, starting with ''File:'' and ending in the ''fileextension'')
*Paste the names in your gallery this way (is a double copypaste foe each image, and the most at right has been removed the ''File:'' and ''fileextension'')
 <nowiki><gallery></nowiki>
 File:Panasonic MN864709 on a DYN-001 (top view).jpg|Panasonic MN864709 on a DYN-001 (top view)
 File:Panasonic MN864709 on a DYN-001 (perspective view).jpg|Panasonic MN864709 on a DYN-001 (perspective view)
 <nowiki></gallery></nowiki>

====Display mode <nowiki><div></nowiki>====
*This is used mostly with a single image (or a couple) that works as an introduction to a whole page or to a section of a page, because the text is aligned to left what we do is to align the image to right-top (either top of a page, or top of a section). This doesnt works very well in wiki because there is an overlapping of text when the page is rendered at different screen resolutions, keep this in mind, we dont use images bigger than 300 or 400 pixels for this display mode and there are some wiki editors that are stricts with this rule so try to dont abuse much of this display mode, it breaks small screens
*The page i use to copypaste the code from is [[XMB]] (single image), [[PlayStation 3 Theme (P3T)]] (2 images horizontally), or [[Teensy%2B%2B_2.0|Teensy++ 2.0]] (several images vertically)
*Click in any of those pages, and click in "edit" tab, copy the line with the <nowiki><div></nowiki> (from start to end), something like:
 <nowiki><div style="float:right">[[File:Tex_classic_theme.png|200px|thumb|left|XMB Classic theme]]</div></nowiki>
*Paste in your new page and edit it properlly, you need to replace the image path in the server, the description, and choose a size, so it becomes for my example:
 <nowiki><div style="float:right">[[File:Panasonic MN864709 on a DYN-001 (perspective view).jpg|200px|thumb|left|Panasonic MN864709 on a DYN-001 (perspective view)]]</div></nowiki>
*If you find some problem of overlapping of texts, sections horizontal line separators, or disalignments you can add an empty page divider at bottom with <nowiki><div></div></nowiki> that works as a "page break" (preferably), or one or several <nowiki><br></nowiki> that works as a line feed (not preferably, this is too dirty)

====Display mode table====
*This is a dirty trick to display several images in big size perfectlly aligned horizontally or vertically, keep in mind that this also breaks small screens resolutions (but sometimes this is the only way to do it, so is a price we need to pay to have a nice display). If you consider the table of images is too big you can use an <nowiki><spoiler></nowiki> before the table and a <nowiki></spoiler></nowiki> after the table
*It works as a combination of a standard "wikitable" where you can choose to make the border lines transparent, use a font type, colors, etc... and inside each table cell is displayed an image with a defined size, you can see examples of this tables used at bottom of [[Motherboard Revisions]] page and some subsections of [[Teensy%2B%2B_2.0|Teensy++ 2.0]] page
*Im not going to explain how to create them exactlly because are a bit experimental, just practise a bit with them and be creative, other wiki users will copypaste your ideas and/or will improve your experiments

====Display mode icon====
*Wiki icons are made by including an image inside a template. Im not going to explain how templates works here (for an icon are very basic but templates are very complicated up to a point that admits arguments where are called)
*Basically you are going to create a very simple template that contains only two thing: the image itself, and a footer to categorize the page in wiki indexing, as before the first thing to do it to find a similar page to copypaste the footer, my favourite one (is the official Dr. frankenstein laboratory, feel free to use it to experiment) is [[TemplateTest]], for this examples we are going to use the subsection about [[TemplateTest#PS3_Buttons|PS3 Buttons]]. the reason why using this section for the examples is because i created templates for the buttons in two different ways based on the size of the images
*First, you need to decide if the icons you are creating are going to be used very frequentlly in a specific size, as example.... to be used inside text lines like this {{padps}} (note his size doesnt disalign previous or next text line). I decided to create specific templates to use dualshock button icons inside text lines to display button combos like in this page [[More_System_Information#How_to_get_this|More System Information]]. The standard font size of webbrowsers is 23 pixels size, so i made a set of templates at 23 pixel heigh to simplify the usage, this way you can call the template directlly without the need to specify the size of the icon
*Also, if you consider some other wiki editor eventually will need to display the icon at a different size, you can make another set of templates with the original size of the image (this works by not specifying the size when creating the template, it will be displayed as original size, not scaled)
*Nowadays, after practising a bit with templates i realize the solution to use a single template to display an icon at different sizes is by using an argument when calling it, it can be fixed in the icons i made but has not been done yet, and what i just explained is good enought to create icons in a easy way, works fine and has been using for a long time without problems so play with it a bit

== Dev_flash\vsh\resource ==
*http://www.psdevwiki.com/ps3/User_talk:Eussbot

{{Dev_flash\vsh\resource\sysconf\calibration}}

is not yet on an article page?

{{Dev_flash\vsh\resource\explore\user}}

is not yet on an article page


==Users suggestions, brainstormings, help, etc...==

===HDD regions table===
* http://www.psdevwiki.com/ps3/Talk:Harddrive#HDD_partitions
ps3dd HDD region is between 8 sectors of padding, in the space leaved empty by resizing ps3da, see how: http://gitorious.ps3dev.net/ps3otheros/scripts/blobs/master/create_hdd_region.sh<br>
The script is a facility to create a next region on free (from regions) space on HDD, with GameOS rights: same script for ALL models, it needs new drivers and new ps3sed.<br>
<pre>
ps3disk sb_03: accessible region 0 start 0 size 1250263728		//ps3da
ps3disk sb_03: accessible region 1 start 32 size 1212515008		//ps3db
ps3disk sb_03: accessible region 2 start 1212515040 size 4194296	//ps3dc
ps3disk sb_03: accessible region 3 start 1216709344 size 33554376	//ps3dd
ps3disk sb_03: ps3stor_probe_access:132: 4 accessible regions found

32 + 1212515008 = 1212515040		//ps3db end sector
1212515040 + 4194296 = 1216709336	//ps3dc end sector
1216709344 - 1216709336 = 8		//ps3dd begin pad
1216709344 + 33554376 = 1250263720	//ps3dd end sector
1250263728 - 1250263720 = 8		//ps3dd ending pad

note: no gap between GameOS regions
</pre>

*I added the padding you point of 0x8 sectors at the end of the table, and i also added some notes out of the table about the differences of padding between official layout and other methods (and maybe differences between NAND/NOR models)... is hard to know or represent in the table because there are differeces in the info people posted (included your displacement of 0x20 sectors before ps3db in your NAND console, that doesnt seems to match the total displacement of 0x18 sectors in graf NOR notes). By now for me this "small" problem with innacurate paddings in the table is fine (no idea if can be solved by modding an script of driver config), overall it looks the whole hdd is mapped so i finished with the table by now, the most important think to know about this areas out of the regions was to be sure if are padding (not other important data) --[[User:Sandungas|Sandungas]] ([[User talk:Sandungas|talk]]) 19:00, 1 April 2014 (EDT)

This table is copyed from: [[Hypervisor_Reverse_Engineering#HDD_device]] (i added the grey rows and usage column). The console was a NOR model (because it has vflash region) and in a firmware under 3.21 (because it has otheros region)
{| class="wikitable FCK__ShowTableBorders"
|-
! Region Index !! Start sector !! Number of sectors !! Usage
|-
| 0 || 0x0 || 0x950F8B0 || whole hdd
|- {{cellcolors|lightgrey}}
| colspan=2 | || 0x8 || HDD Partition table
|-
| 1 || 0x8 || 0x80000 || vflash
|- {{cellcolors|lightgrey}}
| colspan=2 | || 0x10 || Padding ? (0x80018 - 0x80000 - 0x8 = 0x10)
|-
| 2 || 0x80018 || 0x7C8F898 || gameos
|- {{cellcolors|lightgrey}}
| colspan=2 | || 0x8 || Padding (0x7D0F8B8 - 0x7C8F898 - 0x80018 = 0x8)
|-
| 3 || 0x7D0F8B8 || 0x3FFFF8 || gameos cache
|- {{cellcolors|lightgrey}}
| colspan=2 | || 0x8 || Padding (0x810F8B8 - 0x3FFFF8 - 0x7D0F8B8 = 0x8)
|-
| 4 || 0x810F8B8 || 0x13FFFF8 || otheros
|-
| 5 || - || - || -
|-
| 6 || - || - || -
|-
| 7 || - || - || -
|}

=== Regarding Boxwarning ===
I created a new one just for the [[RCOXML Objects]] page but you can edit the template if you need more lines etc. [[User:Roxanne|Roxanne]] 11:55, 19 November 2015 (GMT+1) 
* [[Template:BoxwarningRCOXMLObjects]]
* http://www.psdevwiki.com/ps3/index.php?title=RCOXML_Objects&curid=8887&diff=39840&oldid=39836

Thanks, the new template looks more scary and this is what i was trying to achieve. The broken templates (boxwarning and boxread variations, and maybe others) was made by me when i was learning how template works initially as experiments, but i made a few more that was working fine and i needed them for [[PARAM.SFO]] page (and later used in other pages)... so i forgot a bit about the broken ones but i guess at some point it will be needed to review and decide is fixing or deleting them --[[User:Sandungas|Sandungas]] ([[User talk:Sandungas|talk]]) 02:24, 20 November 2015 (UTC)
: If it's about making things scary then next time we will use a dark red color :) - When I get my left hand back I will check out the templates. [[User:Roxanne|Roxanne]] 10:03, 20 November 2015 (GMT+1)

* Does it worked? http://www.psdevwiki.com/ps3/Special:Log/rights
**No, i was trying to find the email of an user that forgot his account details to force a reset of his pass, but problem was solved anyway
*** Ok. Normally this isn't possible what you had done with your rights but this is probably because of the Database error on both PS3 and PS4 wiki, so we will keep this status.

== Might be interesting for Dungas ==
*from vsh.self

<pre>
GDAT - GD
GDTL - HG
DGAM - DG
GEXE - GameExec
GPS1 - PS1emu
GAME - unknown
</pre>


==Table Tests==
{| class="wikitable" style="font-size:small;"
|+ ps2_netemu.self versions
! Firmware !! Version !! <abbr title="Maximun number of supported commands">Commands</abbr>
|-
! [[3.70_CEX|3.70]]
| 15686 || rowspan="4" | 0x41
|-
! [[3.73_CEX|3.73]] ~ [[3.74_CEX|3.74]]
| 15936
|-
! [[4.00_CEX|4.00]] ~ [[4.01_CEX|4.01]]
| 16195
|-
! [[4.10_CEX|4.10]] ~ [[4.11_CEX|4.11]]
| 16361
|-
! [[4.20_CEX|4.20]] ~ [[4.23_SEX|4.23]]
| 16604 || rowspan="2" | 0x43
|-
! [[4.25_CEX|4.25]] ~ [[4.26_SEX|4.26]]
| 16740
|-
! [[4.30_CEX|4.30]] ~ [[4.31_CEX|4.31]]
| 16808 || 0x45
|-
! [[4.40_CEX|4.40]] ~ [[4.41_CEX|4.41]]
| 16916 || 0x46
|-
! [[4.45_CEX|4.45]] ~ [[4.46_CEX|4.46]]
| 17041 || 0x48
|-
! [[4.50_CEX|4.50]]
| 17179 || 0x4A
|-
! [[4.55_CEX|4.55]]
| 17277 || rowspan="2" | 0x4D
|- 
! [[4.60_CEX|4.60]] ~ [[4.76_CEX|4.76]]
| 17314
|- 
! [[4.78_CEX|4.78]] ~ [[4.81_CEX|4.81]]
| 17495 || 0x50
|}

{| style="font-size:small;"
|+ '''PS2 emulators config commands'''
|
{| class="wikitable" style="font-size:x-small;"
|-
! rowspan="2" | Command Name !! colspan="2" | Command id !! rowspan="2" | Command Data Length
|-
! ps2_gxemu.self !! ps2_netemu.self
|-
| Config terminator or TitleID enforcer || {{no}} || 0x00 || Nothing or 0xA bytes
|-{{cellcolors|lightgreen}}
| Hook function ? || 0x00 || 0x01 || 
|-
| ? || 0x01 ? || 0x02 || uint32_t
|-
| <abbr title="After the purpose of this command is identifyed, this word should be replaced either by DISABLE or ENABLE">Switch</abbr> something || 0x02 ? || 0x03 || {{no}}
|-
| ? || 0x03 || 0x04 || ?
|-
| <abbr title="After the purpose of this command is identifyed, this word should be replaced either by DISABLE or ENABLE">Switch</abbr> something ? || 0x04 (<abbr title="Used as game config data hardcoded inside ps2_gxemu.self by games: Tekken tag tournament SLUS-20001">example</abbr>) || {{cellcolors|lightgrey}} 0x05 (<abbr title="The config parser reads it, does nothing with it, and jumps to the next command of the config file">Not used</abbr>) || {{no}}
|-{{cellcolors|#ddddff}}
| Set something 0x14F80 || 0x05 || 0x06 || {{no}}
|-
| Set something (<abbr title="valid values found">Valid</abbr>: 8) || 0x06 ? || 0x07 || uint32_t
|-{{cellcolors|lightgreen}}
| <!--Patch EE memory with 4 * uint32_t-->? || 0x07 || 0x08 || 
|-{{cellcolors|lightgreen}}
| Patch EE memory with 2 * uint32_t || 0x08 || 0x09 || <abbr title="indicated by the first uint32_t, maximun number of entries: 32">entry_count</abbr> + (entry_count * 0x14)
|-{{cellcolors|lightgreen}}
| Patch EE memory with 1 * uint32_t || {{no}} ? || 0x0A || <abbr title="indicated by the first uint32_t, maximun number of entries: 32">entry_count</abbr> + (entry_count * 0xC)
|-{{cellcolors|lightgreen}}
| Patch game disc || 0x09 || 0x0B || <s><abbr title="indicated by the first uint32_t, maximun number of entries: 47">entry_count</abbr> + (entry_count * (0x8 + (patch_size * 0x8)))</s>
|-
| Set something (<abbr title="valid values found">Valid1</abbr>: 0, 1, 2 - <abbr title="valid values found">Valid2</abbr>: 0x63) || 0x0A ? || 0x0C || 2 * uint16_t
|-
| Set something (<abbr title="valid values found">Valid</abbr>: 0, 1) || 0x0B ? || 0x0D || uint32_t
|-
| Set something || 0x0C || 0x0E || uint32_t
|-{{cellcolors|lightgreen}}
| ? || 0x0D || 0x0F || <abbr title="indicated by the first uint32_t, maximun number of entries: 31">entry_count</abbr> + (entry_count * 0x8) ?
|-{{cellcolors|lightgreen}}
| ? || 0x0E ? || 0x10 || <abbr title="indicated by the first uint32_t, maximun number of entries: 31">entry_count</abbr> + (entry_count * 0x8) ?
|-
| ? || 0x0F ? || 0x11 || ?
|-{{cellcolors|lightgreen}}
| ? || 0x10 || 0x12 || 
|-
| Set something || 0x11 ? || 0x13 || uint64_t
|-
| <abbr title="After the purpose of this command is identifyed, this word should be replaced either by DISABLE or ENABLE">Switch</abbr> something || 0x12 || 0x14 || {{no}}
|-
| Set something (<abbr title="valid values found">Valid</abbr>: 2, 4) || 0x13 || 0x15 || uint32_t
|-
| ? || ? || {{cellcolors|lightgrey}} 0x16 (<abbr title="The config parser reads it, does nothing with it, and jumps to the next command of the config file">Not used</abbr>) || 
|-
| Set something (<abbr title="valid values found">Valid</abbr>: 1) || ? || 0x17 || uint32_t
|-
| ? || ? || {{cellcolors|lightgrey}} 0x18 (<abbr title="The config parser reads it, does nothing with it, and jumps to the next command of the config file">Not used</abbr>) || 
|-
| <abbr title="After the purpose of this command is identifyed, this word should be replaced either by DISABLE or ENABLE">Switch</abbr> something || ? || 0x19 || {{no}}
|-
| <abbr title="After the purpose of this command is identifyed, this word should be replaced either by DISABLE or ENABLE">Switch</abbr> something || ? || 0x1A || {{no}}
|-
| <abbr title="After the purpose of this command is identifyed, this word should be replaced either by DISABLE or ENABLE">Switch</abbr> something || 0x18 || 0x1B || {{no}}
|-
| ? || 0x19 ? || 0x1C || 4 * uint8_t ?
|-
| ? || 0x1A ? || 0x1D || 4 * uint8_t ?
|-
| ? || 0x1B ? || 0x1E || 4 * uint8_t ?
|-
| Set something || 0x1C || 0x1F || uint32_t
|-
| Set something || ? || 0x20 || uint64_t 
|-
| Set something (<abbr title="valid values found">Valid</abbr>: 0, 1, 2) || ? || 0x21 || uint32_t
|-
| <abbr title="After the purpose of this command is identifyed, this word should be replaced either by DISABLE or ENABLE">Switch</abbr> something || ? || 0x22 || {{no}}
|-{{cellcolors|#ddddff}}
| Set something 0x14E00 || ? || 0x23 || {{no}}
|-
| Set something || ? || 0x24 || uint64_t 
|-
| ? || ? || {{cellcolors|lightgrey}} 0x25 (<abbr title="The config parser reads it, does nothing with it, and jumps to the next command of the config file">Not used</abbr>) || 
|-{{cellcolors|lightgreen}}
| ? || 0x22 || 0x26 || 
|-{{cellcolors|lightgreen}}
| ? || 0x23 || 0x27 || 
|}
|
{| class="wikitable" style="font-size:x-small;"
|-
! rowspan="2" | Command Name !! colspan="2" | Command id !! rowspan="2" | Command Data Length
|-
! ps2_gxemu.self !! ps2_netemu.self
|-
| Set something (<abbr title="valid values found">Valid</abbr>: 0, 1, 2, 3) ? || 0x24 ? || 0x28 || uint32_t
|-
| Set something || 0x25 ? || 0x29 || 2 * uint32_t
|-
| <abbr title="After the purpose of this command is identifyed, this word should be replaced either by DISABLE or ENABLE">Switch</abbr> something || 0x26 ? || 0x2A || {{no}}
|-
| <abbr title="After the purpose of this command is identifyed, this word should be replaced either by DISABLE or ENABLE">Switch</abbr> something || 0x27 ? || 0x2B || {{no}}
|-
| Set something (<abbr title="valid values found">Valid</abbr>: 1) || 0x28 || 0x2C || uint32_t 
|-
| ? || ? || {{cellcolors|lightgrey}} 0x2D (<abbr title="The config parser reads it, does nothing with it, and jumps to the next command of the config file">Not used</abbr>)
|-
| Set something || ? || 0x2E || uint32_t 
|-
| Set something || 0x2B || 0x2F || uint32_t 
|-
| ? || ? || {{cellcolors|lightgrey}} 0x30 || 
|-
| ? || ? || {{cellcolors|lightgrey}} 0x31 || 
|-
| ? || ? || {{cellcolors|lightgrey}} 0x32 || 
|-
| ? || ? || {{cellcolors|lightgrey}} 0x33 || 
|-
| ? || ? || {{cellcolors|lightgrey}} 0x34 || 
|-
| Enable Force Flip Field || ? || 0x35 || {{no}}
|-
| ? || ? || {{cellcolors|lightgrey}} 0x36 || 
|-
| ? || ? || {{cellcolors|lightgrey}} 0x37 || 
|-
| ? || ? || {{cellcolors|lightgrey}} 0x38 || 
|-
| ? || ? || {{cellcolors|lightgrey}} 0x39 || 
|-
| ? || ? || {{cellcolors|lightgrey}} 0x3A || 
|-
| ? || ? || {{cellcolors|lightgrey}} 0x3B || 
|-
| ? || ? || {{cellcolors|lightgrey}} 0x3C || 
|-
| Config file revision (<abbr title="valid values found">Valid</abbr>: bigger than 15686) || ? || 0x3D || uint32_t
|-
| Disable something || ? || 0x3E || {{no}}
|-
| Set something || ? || 0x3F || uint32_t
|-
| <abbr title="After the purpose of this command is identifyed, this word should be replaced either by DISABLE or ENABLE">Switch</abbr> something || ? || 0x40 || {{no}}
|-
| Disable lwsync ? || ? || 0x41 || {{no}}
|-
| ? || {{no}} || 0x42 || uint32_t
|-
| Set something (<abbr title="valid values found">Valid</abbr>: 0, 1) || {{no}} || 0x43 || uint32_t
|-
| Disable Smoothing filter || {{no}} || 0x44 || {{no}}
|-
| <abbr title="After the purpose of this command is identifyed, this word should be replaced either by DISABLE or ENABLE">Switch</abbr> something || {{no}} || 0x45 || {{no}}
|-
| Enable L2H Improvement || {{no}} || 0x46 || {{no}}
|-
| Enable XOR CSR || {{no}} || 0x47 || {{no}}
|-
| Set VSYNC <abbr title="1=NoIPU, 2=IPU, 3=Anytime">IPU</abbr> & <abbr title="Conservative=0x4E20 (20000d), Normal=0x186A0 (100000d), Agressive=0x3D090 (250000d), or any other value up to 0xFFFFFFFF">Delay</abbr> || {{no}} || 0x48 || 2 * uint32_t
|-
| Set something 0xB,0,0  || {{no}} || 0x49 || {{no}}
|-{{cellcolors|#ddddff}}
| Set something 0x15100 || {{no}} || 0x4A || {{no}}
|-
| Set something || {{no}} || 0x4B || 2 * uint32_t
|-
| Set something || {{no}} || 0x4C || 2 * uint32_t
|-
| Set something || {{no}} || 0x4D || uint32_t
|-
| ? || {{no}} || 0x4E || 
|-
| ? || {{no}} || 0x4F || 
|-
| <abbr title="After the purpose of this command is identifyed, this word should be replaced either by DISABLE or ENABLE">Switch</abbr> something || {{no}} || 0x50 || {{no}}
|}
|}