Problem statement : Understanding timestamps and date or calendar management in the context of computing systems...further to as detailed in the document referred below. refer to the documents viz. "opportunity_innovative_time_stamp_CMOS_clocks.txt", understanding the pros and con's of having peristant memory on the PCB usually termed as ROM (though oddly updatable), RAM ....in the context of personal computing Desktop/laptop ....etc ...viz. peristant settings also called BIOS settings. This individual was originally instrumental to introduce a battery on the PCB or mother board ....when MS-DOS versions 3x/ 4x /5x on bootable floppies of 5.8'inch on 286 computer's were in the market ....noticing the fact ...every time the computer was rebooted one needed to set the date and time i.e. timestamp wasn't persistant, suggesting introducing a small clock(the standard stop-watch or electronic wrist watch kind) kind be present on the pcb or inside the cpu ...which can maintain the time .....this was way back in 1994. ....the necessisity to be powered by a battery (oddly intended to power a BIOS clock) Opportunity A : Given the context of DC powered memory ...on PCB ....the scope for virus (Why ...rus ...argument ??? ...interpretations coinage ...lingustic ...meaning in circulation and the one in vogue) By removing the scope for a battery on the PCB ....the scope and context of surveilance, hacking ...compromising of systems ...few other vulnerabilities can be circumvented. ....alternative ...viz. the ability to maintain a timestamp ....is to use the NTP protocol ... pros and con's of using NTP ...refer to the document 'opportunity_perils_date_timetamp_management.txt", ...a ideal way is to ability to configure more than one ...geographically diverse NTP servers ... and set or configure the time-zone settings ....in the event there arises a difference or conflict ...rise a incident ...alarm ...ideally to a watched repository by law enforcement agencies or other ...paid subscription based organization ...this can similarly be extended to that of BIOS clocks powered ...PCB based computing environments ...a better way to remove scope for misuse is to make the BIOS clocks a pluggable ...units ...which have the battery embedded ....eliminate the scope of misuse the source of power or current (DC). ...use the what is usually termed as the 'boot-block' in the context of operating sytems that make use of disk as a medium for storage ....use the 'boot-block' for the persistant settings required in the 'BIOS'(mostly customized settings such as disk or device preferences ...bootup etc). Opportunity B: Deriving or how unix orginally maintained or used timestamp ....viz. the cpu....current clock-cycle. either on board pcb/motherboard based timestamp ....can be synced with clock-cycle of main-cpu at boot-up, or unpon ...boot-up ...the cpu-clock-cycle can sync-up ...with NTP-synchronization over-the network, given that most computer's used in business-computing environment operate in a networked environment ...where in authentication into or over the network is mandatory ....thus ...given the fact ...the vulnerabilities of BIOS compromization or those arising out BIOS ...RAM resident ...malware ...can potentially be tackled. Also the fact that 64 bit environments ...translating to a larger int size ...and thus a bigger timestamp that can include or span ...a larger timespan. Note: The above problem statement having been encountered in various scenarios and detailed in various 'Proof of concepts' as mentioned in http://uk.geocities.com/ravivenkatus/projects.pdf http://ravishankarkv.tripod.com/projects.pdf ....apply appropriate 'use-case' modeling, rationalize and arrive at a workable and feasible solution both commercially and techinically viable.