QUOTE(Angelsh @ Aug 18 2005, 05:32 PM)
You are really entering a value that goes to a binary key.
The value 3 in binary is '0000 0011'.
That means that the first bit (on the right side) is set to 1 and activates the time presentation in the task bar. The second bit activates the date presentation.
When you mention that there is a repeating sequence as u increase the numbers, this is not useless. What are u doing is changing other bits that has other meanings and functions.
For instance: Value 4: '0000 0100' Date and time are not displayed since bits 1 and 2 are set to 0. But 3rd bit is set to 1. Don't know what is the meaning, but you can bet it has some function.
Accordingly, if you set a value of 7: '0000 0111' will display date and time, but third bit is activated.
I don't recommend to play that way with the registry values since you may have unforecasted results. However if anybody knows the meaning of the other bits, it will be welcome.
Bro Angelsh,
Heh, u are quite right. Basically, what we are doing is just changing the bit values of the binary set. I left out that explaination of where those digital numbers arose bcos I thought it would be more platable for bros here = didnt want to provide any excessive information lest anyone falls asleep

. However, I now see that I should have explained myself more clearly and I do apologise for any confusion caused

.
------------
Anyway, let me iterate to all what Bro Angelsh meant:
For starters, the single digits I suggested to change the 'TBOpt' value to (i.e. 0, 1, 2, 3, ..., 8, etc) are really in 'decimal' mode = our normal numbers that we use.
However, in this particular case, these are converted to 'binary' mode for programming purposes. Binary numbers exist in sets of numbers, where each number is EITHER a '0' or '1' in value and is called a 'bit':
- '0' = bit is "off" or unactivated.
- '1' = bit is "on" or activated.
For simplicity, we shall just consider the 4 least significant bits (i.e. the last 4 numbers on the right side). For e.g., 0101 in binary:
- bit #1 (from left) = 0 (called the most significant bit)
- bit #2 = 1
- bit #3 = 0
- bit #4 = 1 (called the least significant bit)
This implies that bit #1 as well as the bit #3 are "off", while bit #2 and bit #4 are "on".
Converting decimal to binary isnt that complex actually, but might not be so important to understand here (anyway for those who are interested, lets look at converting binary to decimal first, just remember the reference number = '8421', e.g. '0101' in binary = bit #2 and bit #4 are "on" = add 4 and 1 together from the reference number, '8421' = 0101 in binary = 5 in decimal. Likewise, '1111' in binary = 8+4+2+1 from the reference number (as all bits are "on") = 15 in decimal. To convert binary to decimal, simplest methods are to work backwards using the '8421 method' or just to use a base calculator

).
Decimal <=> Binary
0 = 0000 (bit #1 = 0, bit #2 = 0, bit #3 = 0, bit #4 = 0)
1 = 0001 (bit #1 = 0, bit #2 = 0, bit #3 = 0, bit #4 = 1)
2 = 0010 (bit #1 = 0, bit #2 = 0, bit #3 = 1, bit #4 = 0)
3 = 0011 (bit #1 = 0, bit #2 = 0, bit #3 = 1, bit #4 = 1)
4 = 0100 (bit #1 = 0, bit #2 = 1, bit #3 = 0, bit #4 = 0)
5 = 0101 (bit #1 = 0, bit #2 = 1, bit #3 = 0, bit #4 = 1)
6 = 0110 (bit #1 = 0, bit #2 = 1, bit #3 = 1, bit #4 = 0)
7 = 0111 (bit #1 = 0, bit #2 = 1, bit #3 = 1, bit #4 = 1)
8 = 1000 (bit #1 = 1, bit #2 = 0, bit #3 = 0, bit #4 = 0)
etc, etc
Now that we got those boring parts covered, lets go on to say that each binary bit represent an action. For our registry tweak of 'TBOpt':
0 = 0000 (bit #1 = 0, bit #2 = 0, bit #3 = 0, bit #4 = 0) = Remove date and time altogether
1 = 0001 (bit #1 = 0, bit #2 = 0, bit #3 = 0, bit #4 = 1) = Display only Time
2 = 0010 (bit #1 = 0, bit #2 = 0, bit #3 = 1, bit #4 = 0) = Display only Date
3 = 0011 (bit #1 = 0, bit #2 = 0, bit #3 = 1, bit #4 = 1) = Display both Time and Date
4 = 0100 (bit #1 = 0, bit #2 = 1, bit #3 = 0, bit #4 = 0) = Remove date and time altogether
5 = 0101 (bit #1 = 0, bit #2 = 1, bit #3 = 0, bit #4 = 1) = Display only Time
6 = 0110 (bit #1 = 0, bit #2 = 1, bit #3 = 1, bit #4 = 0) = Display only Date
7 = 0111 (bit #1 = 0, bit #2 = 1, bit #3 = 1, bit #4 = 1) = Display both Time and Date
8 = 1000 (bit #1 = 1, bit #2 = 0, bit #3 = 0, bit #4 = 0) = Remove date and time altogether
etc, etc.
From the above illustration, what happens is:
- the least significant bit (i.e. rightmost number) = controls the time ('1' = time on, '0' = time off)
- the 2nd least significant bit (i.e. 2nd number from the right) = controls the date ('1' = date on, '0' = date off)
If u guys havent fallen asleep by now

, I think most should be able to see that only 2 bits are involved if we need to:
1) Display only Time = make sure that the least significant bit is '1'.
2) Display only Date = make sure that the 2nd least significant bit is '1'.
3) Display both Time and Date = make sure that the least significant bit and the 2nd least significant bit are both '1's.
4) Remove date and time altogether = make sure that the least significant bit and the 2nd least significant bit are both '0's.
Bro Angelsh doesnt like the part about changing the 3rd least significant bits, etc, bcos he is worried about unforecasted results and he is quite right to feel that way

. Bits usually each have a function and could have adverse effects if wrongly manipulated.
------------
However, when I posted my findings about the continued sequence being useless much earlier, I had suspected the other more significant bits to be 'null bits' = not used at all. This arose bcos I had previously tested combos from '0' to '15' and had verified that there were no unwarranted problems by messing with alarms, time settings, regional time settings, etc, with each of these. As a matter of fact, I just realised that I am still using a TBOpt value of '15' (i.e. '1111' in binary = 2 extra bits activated) since May? = no ill effects yet.
Still, the section where I had previously included some time ago for changing TBOpt's values to either '4', '5', '6', '7', '8', etc, is hardly useful as '0', '1', '2', '3' will suffice.