>>Integer is a four-byte number. So your integer should look like this:
>>first three bytes should contain zeros, the last byte should contain 1 (chr(1))
>
>The data type integer varies by situation; having dealt with scales before, it's extremely doubtful that it's a 32 bit unsigned long. Also, the order of presentation varies according to how the hardware implements the data type, for example, while Motorola-based 32 bit processors represent a 0x00000001 memory as (0x00)(0x00)(0x00)(0x01), an Intel 32 bit x86 machine would represent it as (0x01)(0x00)(0x00)(0x00) (this is the Big Endian/Little Endian representation issue.)

Thank you, Ed, for reminding me of that difference in representation. I started my programming career on a main-frame which used Motorola-based representation.
The old knowledge sometimes seeps through, this is how subconsience tries to return us to the good old years.
Best regards.