User talk:Yellows8: Difference between revisions

Line 28:

it seems to be a long time for you to do all the documentations by yourself. (Orz i forgot my suggestion) --[[User:Syphurith|Syphurith]] 02:35, 15 April 2013 (CEST)

:I don't have any 3DS ramhaxx, I use software savegame haxx of course. "is there any access to get/purchase one? (if no i think i should learn how to diy one then)" You should be asking neimod about that instead, but [https://secure.flickr.com/photos/neimod/6238747088/in/photostream the] [https://secure.flickr.com/photos/neimod/6212627980/in/photostream soldering] for 3DS ramhaxx would be *really* difficult. I'm not sure what you mean regarding that tool either, are you referring to a tool which would locate the code for service commands in a binary? --[[User:Yellows8|Yellows8]] 03:10, 15 April 2013 (CEST)

::Thanks for reply. I will try to contact him for boards. About the tool~~, I hand you an example.~~

::Thanks for reply. I will try to contact him for boards. About the tool --sniff--.

::* --~~Configuration~~

~~:::%This line is a comment. Supports ":",";","#","%"~~

~~:::%The line below would mark binary 800001000100 as type 01 of cmdid 01.~~

~~:::80000100:0100:4~~

~~:::%This can mark out a 80000200 (without params) as type 01 of cmdid 02~~

~~:::80000200:~~

~~:::%This can mark out a 800014F0****** (with 6 half~~-~~bytes param) as type 02 of cmdid 03~~

~~:::800014F0:1CD000:6,Any:6~~

::* -~~-Example Binary~~

~~:::0140800002000156F30080000100010076EDD80000200~~

~~::* --Expected~~

~~:::0140'''80000200'''0156F300'''80000100'''''0100''76EDD'''80000200'''~~

~~::* --Expected Result File~~

~~:::0140<cmd_2 type_0>80000200</cmd_2>0156F300<cmd_1 type_1>80000100<param_type_1>0100</param_type_1></cmd_1>76EDD<cmd_2 type_0>80000200</cmd_2>~~

~~:::Then we can use CSS selector or other that correspondes to the format.~~

::* Exact output can be loaded in HTML or other UI that helps color the matched binary (To let you find some pattern that may not been identified). Users can adjust the Color setting themselves (including ForeGround and BackGround specified to any type of cmdid).

::* It can only mark out those you identified but it will leave the unknown code not colored. so i think that may help you find out new cmdid in the not-colored paras. also it will be designed to have the ability to load any size of file.

::* Cons: can not detect structures; may make mistake; need configuration file (can be made by writing the header code)

::* Pros: can visually color the matched patterns; can load unlimited size of file (result will be divided into segments of 1MB or other)

::It would not be too difficult to make. However may take one or two weeks. --[[User:Syphurith|Syphurith]] 03:49, 15 April 2013 (CEST)

:::I have no need for a tool which searches for service commandIDs, when I can just search for commandIDs etc in my text-editor for disassembled code. --[[User:Yellows8|Yellows8]] 04:04, 15 April 2013 (CEST)

::::Well thanks for reply. I removed the details above. I will left it undone. Have a good day.--[[User:Syphurith|Syphurith]] 04:21, 15 April 2013 (CEST)

@@ Line 28: / Line 28: @@
 it seems to be a long time for you to do all the documentations by yourself. (Orz i forgot my suggestion) --[[User:Syphurith|Syphurith]] 02:35, 15 April 2013 (CEST)
 :I don't have any 3DS ramhaxx, I use software savegame haxx of course. "is there any access to get/purchase one? (if no i think i should learn how to diy one then)" You should be asking neimod about that instead, but [https://secure.flickr.com/photos/neimod/6238747088/in/photostream the] [https://secure.flickr.com/photos/neimod/6212627980/in/photostream soldering] for 3DS ramhaxx would be *really* difficult. I'm not sure what you mean regarding that tool either, are you referring to a tool which would locate the code for service commands in a binary? --[[User:Yellows8|Yellows8]] 03:10, 15 April 2013 (CEST)
-::Thanks for reply. I will try to contact him for boards. About the tool, I hand you an example.
+::Thanks for reply. I will try to contact him for boards. About the tool --sniff--.
-::* --Configuration
-:::%This line is a comment. Supports ":",";","#","%"
-:::%The line below would mark binary 800001000100 as type 01 of cmdid 01.
-:::80000100:0100:4
-:::%This can mark out a 80000200 (without params) as type 01 of cmdid 02
-:::80000200:
-:::%This can mark out a 800014F0****** (with 6 half-bytes param) as type 02 of cmdid 03
-:::800014F0:1CD000:6,Any:6
-::* --Example Binary
-:::0140800002000156F30080000100010076EDD80000200
-::* --Expected
-:::0140'''80000200'''0156F300'''80000100'''''0100''76EDD'''80000200'''
-::* --Expected Result File
-:::0140<cmd_2 type_0>80000200</cmd_2>0156F300<cmd_1 type_1>80000100<param_type_1>0100</param_type_1></cmd_1>76EDD<cmd_2 type_0>80000200</cmd_2>
-:::Then we can use CSS selector or other that correspondes to the format.
-::* Exact output can be loaded in HTML or other UI that helps color the matched binary (To let you find some pattern that may not been identified). Users can adjust the Color setting themselves (including ForeGround and BackGround specified to any type of cmdid).
-::* It can only mark out those you identified but it will leave the unknown code not colored. so i think that may help you find out new cmdid in the not-colored paras. also it will be designed to have the ability to load any size of file.
 ::* Cons: can not detect structures; may make mistake; need configuration file (can be made by writing the header code)
 ::* Pros: can visually color the matched patterns; can load unlimited size of file (result will be divided into segments of 1MB or other)
 ::It would not be too difficult to make. However may take one or two weeks. --[[User:Syphurith|Syphurith]] 03:49, 15 April 2013 (CEST)
 :::I have no need for a tool which searches for service commandIDs, when I can just search for commandIDs etc in my text-editor for disassembled code. --[[User:Yellows8|Yellows8]] 04:04, 15 April 2013 (CEST)
+::::Well thanks for reply. I removed the details above. I will left it undone. Have a good day.--[[User:Syphurith|Syphurith]] 04:21, 15 April 2013 (CEST)