Okay... here's a programming example. Since TIMER returns the number of seconds since midnight, you can derive the hour by dividing it by 3600, the minute by dividing the remainder of the hour division by sixty... and your seconds, well, they're the scraps that are left over. This is a crude approximation of the way things work - and not entirely accurate. You'll see what I mean if you run the following code. It will display the system time followed by your calculated time, based on the value of TIMER.
Notice how the calulated time is always about a half-second slower than the system time? Your assignment, should you decide to accept it, will be to synchronize these values.
This code sets the system time to two seconds before midnight to illustrate another problem. Notice how, when the system clock strikes midnight, both TIME$ and MyTime$ display the hour as 24 (is that a valid hour on the 24-hour clock?) and MyTime$ begins to display the seconds as a negative value (-.128, etc.). You might want to fix this nasty piece of midnight screwiness before you paste the code into some mission-critical application

.
[tt]
CLS
OldTime$ = TIME$
TIME$ = "23:59:58"
DO
t = TIMER
h = t \ 3600
m = (t MOD 3600) \ 60
s = t - ((h * 3600) + (m * 60))
MyTime$ = RIGHT$("0" + LTRIM$(STR$(h)), 2) + ":"
MyTime$ = MyTime$ + RIGHT$("0" + LTRIM$(STR$(m)), 2) + ":"
MyTime$ = MyTime$ + LEFT$(LTRIM$(STR$(s)) + "00000", 5)
LOCATE 1, 1
PRINT TIME$; " = "; MyTime$
IF INKEY$ <> "" THEN EXIT DO
LOOP
TIME$ = OldTime$
[/tt]
There are, undoubtedly, better, quicker, more efficient, more accurate ways to do this. Personally, I never derived much satisfaction from having somebody hand me a 100% working solution.
BTW: You might want to set your system clock after running this. It will be off by the number of seconds you run the code. That part of my post
is 100% accurate.