Thread: 32 Byte Hex Converted To 2 byte??

Hybrid View

Previous Post Previous Post   Next Post Next Post
  1. #1
    and the Hat of Guessing tabstop's Avatar
    Join Date
    Nov 2007
    Posts
    14,336
    Quote Originally Posted by Turbo7 View Post
    So if it's not reversible that mean I cant find out what I need?
    If you have the original, and the control string, then you can get to the result. But you need both of the inputs.
    Quote Originally Posted by Turbo7 View Post
    I want to put in:
    0431, 0000, 0000, 0000, 0000, 0000, 0000, 0000, 0000, 0000, 0000, 0000, 0000, 0000, 0000, 0000
    and get
    "The Correct Output"
    Can this not be done in C?
    Not without specifying the 0x80 00 (or whatever pattern you need).

  2. #2
    Registered User
    Join Date
    Nov 2018
    Posts
    9
    Quote Originally Posted by tabstop View Post
    If you have the original, and the control string, then you can get to the result. But you need both of the inputs.

    Not without specifying the 0x80 00 (or whatever pattern you need).
    So with me having BF FF and 0431, 0000, 0154, 0153, 0151, 0157, 0051, 0052, 0160, 1020, 0075, 2197, 0152, 0158, 0057, 0058 I cant find out the sequence on how BF FF equals 0431, 0000, 0154, 0153, 0151, 0157, 0051, 0052, 0160, 1020, 0075, 2197, 0152, 0158, 0057, 0058?

    So therefore I stuck, I know for a fact that someone has figured out the BF FF sequence but you know things like this people keep to themselves.

    As far as 80 00 that was some random sequence I picked. So a bit more info 00 00 mean off (do not display number) and BF FF mean on (display number in long hex string i.e. 0154), if want to not to display 0154 only would would need the correct BF FF sequence, therefor BF FF is no longer BF FF it is something else, and that else is what I am looking for.

  3. #3
    and the Hat of Guessing tabstop's Avatar
    Join Date
    Nov 2007
    Posts
    14,336
    Quote Originally Posted by Turbo7 View Post
    So with me having BF FF and 0431, 0000, 0154, 0153, 0151, 0157, 0051, 0052, 0160, 1020, 0075, 2197, 0152, 0158, 0057, 0058 I cant find out the sequence on how BF FF equals 0431, 0000, 0154, 0153, 0151, 0157, 0051, 0052, 0160, 1020, 0075, 2197, 0152, 0158, 0057, 0058?

    So therefore I stuck, I know for a fact that someone has figured out the BF FF sequence but you know things like this people keep to themselves.

    As far as 80 00 that was some random sequence I picked. So a bit more info 00 00 mean off (do not display number) and BF FF mean on (display number in long hex string i.e. 0154), if want to not to display 0154 only would would need the correct BF FF sequence, therefor BF FF is no longer BF FF it is something else, and that else is what I am looking for.
    I'm not sure I've got another different explanation in me, but I'll try. There are two inputs and one output:
    Code:
    input 1 (?????) : 0431 GGGG 0154 0153 0151 0157 0051 0052 0160 1020 0075 2197 0152 0158 0057 0058
    input 2 (BF FF) :  on  off  on   on   on   on   on   on   on   on   on   on   on   on   on   on
    ---------
    output  (above) : 0431 0000 0154 0153 0151 0157 0051 0052 0160 1020 0075 2197 0152 0158 0057 0058
    The on/off pattern from input 2 is just the binary representation of BF FF. The GGGG represent some input value that you haven't bothered to tell anybody; and because the whole point of this process is to mask off numbers and make them 0000, you can't tell just from the result what those original values were. The thing you need to realize before we can really go anywhere with this thread is that the long string you have is the output, not the input. As long as you think of them as input, we're just going to keep going around in this same circle.

  4. #4
    Registered User
    Join Date
    Nov 2018
    Posts
    9
    Quote Originally Posted by tabstop View Post
    I'm not sure I've got another different explanation in me, but I'll try. There are two inputs and one output:
    Code:
    input 1 (?????) : 0431 GGGG 0154 0153 0151 0157 0051 0052 0160 1020 0075 2197 0152 0158 0057 0058
    input 2 (BF FF) :  on  off  on   on   on   on   on   on   on   on   on   on   on   on   on   on
    ---------
    output  (above) : 0431 0000 0154 0153 0151 0157 0051 0052 0160 1020 0075 2197 0152 0158 0057 0058
    The on/off pattern from input 2 is just the binary representation of BF FF. The GGGG represent some input value that you haven't bothered to tell anybody; and because the whole point of this process is to mask off numbers and make them 0000, you can't tell just from the result what those original values were. The thing you need to realize before we can really go anywhere with this thread is that the long string you have is the output, not the input. As long as you think of them as input, we're just going to keep going around in this same circle.
    Ok this looks good, so

    Code:
    input 1 (?????) : 0431 GGGG 0154 0153 0151 0157 0051 0052 0160 1020 0075 2197 0152 0158 0057 0058
    input 2 (BF FF) :  on  off  on   on   on   on   on   on   on   on   on   on   on   on   on   on
    ---------
    output  (above) : 0431 0000 0154 0153 0151 0157 0051 0052 0160 1020 0075 2197 0152 0158 0057 0058
    To this:
    Code:
    input 1 (?? ??) : 0431 GGGG 0154 0153 0151 0157 0051 GGGG 0160 1020 0075 2197 0152 0158 0057 0058
    input 2 (BF FF) :  on  off  on   on   on   on   on   off   on   on   on   on   on   on   on   on
    ---------
    output 1 (?? ??) : 0431 0000 0154 0153 0151 0157 0051 0000 0160 1020 0075 2197 0152 0158 0057 0058
    output 2 (?? ??) :  on  off  on   on   on   on   on   off   on   on   on   on   on   on   on   on
    Also 0000 that you called GGGG i did not change that, it is there by default.

  5. #5
    and the Hat of Guessing tabstop's Avatar
    Join Date
    Nov 2007
    Posts
    14,336
    Quote Originally Posted by Turbo7 View Post
    Also 0000 that you called GGGG i did not change that, it is there by default.
    The 0000 is there only because the B byte masked it off; it is (almost certainly) not the original starting value.

  6. #6
    Registered User
    Join Date
    Nov 2018
    Posts
    9
    Quote Originally Posted by tabstop View Post
    The 0000 is there only because the B byte masked it off; it is (almost certainly) not the original starting value.
    As far as being original, it original according the .hex file I am working with. Here is snippet of what I am looking at. The big table on the right is a reference table only, the left table is the control. Now keep in mind when you change the table on the left does not change the right it just a reference table. I have tested this and when threw all the of the left table and change to 00 00 one by one (took forever lol) and tested on the bench I have (it shows certain numbers on the right table), therefore knowing that BF is one half and the FF is another and same for all the others, in short BF turns on or off 8 numbers in a row in the right table. I.E. BF controls 0431 to 0052 as stated before, but the right table does not change. So I cannot change one or any of the numbers in the right table and the and see the change in the left.

    This is why I was looking for some code to find the correct sequence.
    32 Byte Hex Converted To 2 byte??-table-png

Popular pages Recent additions subscribe to a feed

Similar Threads

  1. Replies: 5
    Last Post: 01-22-2016, 03:20 AM
  2. File Comparision byte by byte
    By anusha2489 in forum C Programming
    Replies: 12
    Last Post: 05-16-2011, 06:58 AM
  3. reading files byte by byte
    By cpsc in forum C++ Programming
    Replies: 12
    Last Post: 01-07-2011, 03:54 PM

Tags for this Thread