Answering msg from Al Pacheco to All,
on Tuesday April 11 1995 at 12:04
 AP>         DO
 AP>           KeyPress$ = INKEY$
 AP>         LOOP UNTIL LEN(KeyPress$)
 AP>         PRINT DATE$
 AP>         END
 AP>          If you compile to a stand-alone and let it run past midnight
 AP> at least
 AP>         twice it will mess up the date on the PC. The CMOS is not
    Long time to run a program just to test it! :-)
 AP> affected
 AP>         but you have to re-boot to reset the date. The computer
 AP> guru's
 AP> around
 AP>         the area here think it's a BASIC problem.  I doubt it. It
 AP> affects
 AP>         '286, '386,' 486 and doesn't care about DOS version either. I
 AP> hope
 AP>         someone knows the answer.
    This snippet from Ralf Brown's interrupt list explains it.
-------------------
INT 1A - TIME - GET SYSTEM TIME
 AH = 00h
Return: CX:DX = number of clock ticks since midnight
 AL = midnight flag, nonzero if midnight passed since time last read
Notes: there are approximately 18.2 clock ticks per second, 1800B0h per 24 
rs
 IBM and many clone BIOSes set the flag for AL rather than incrementing
   it, leading to loss of a day if two consecutive midnights pass
   without a request for the time (e.g. if the system is on but idle)
SeeAlso: AH=01h,AH=02h,INT 21/AH=2Ch,INT 62/AX=0099h
-------------------
---
---------------