BOOTCLOCK     INSTALL A SETCLOCK DISPLAY ONTO BOOTBLOCKS     17/07/94     
                                                                               
      CLI ONLY.         AND AS A COOLCAPTURE EVENT!                            
                                                                               
          BY:   DION VINGERHOETS             8 AYTON WAY                       
                                           DUNCRAIG WA 6023                    
          Only 1772 bytes long!            WESTERN AUSTRALIA                   
                                                                               
                                                                               
                                                                               
                                                                               
                                                                                


	 This program displays the current DATE and TIME. The mouse moves a
	pointer under each of the clock digits (except seconds). Pressing
	the Right Mouse Button will increment the digit where the pointer
	is. This sets the hardware battery backed-up clock. You will still
	need to have the command 'SetClock LOAD' in you startup sequence to
	let the system know that the time has changed. This program does
	not do this (yet). Pressing the Left Mouse Button will exit the
	clock.


	 CLI: BootClock [+|-b] [+|-c] [+a]

	There cannot be more than one flag at a time but there must be at
	least one flag.

   The 'b' flag: When the +b flag is set, the clock is written to the 
	bootblock of any disk so that the clock is displayed when you boot 
	the disk. You can change the date or just press the LMB to continue
	the bootup procedure.

	 Be warned that Virus Checker will see this as a virus. When VC
	displays the 'virus' for you, you will see my message stating that
	this is not a virus and is infact the BootClock.

	 I think, to safe guard myself, I should stress apon you 
    __________________________________________________________________
     NOT TO INSTALL BOOTCLOCK ONTO A GAME DISK WITH IT'S OWN BOOTBLOCK! 

	as the game will not load anymore and you would have thrown away
	$lots if you bought the game from a shop.

	 When '-b' is flagged, the bootclock is written to the bootblock
	but it is not active. Why you would want to do this I can't imagine
	but it is noteworthy to point out that in this mode Virus Checker
	does not see any virus. Is this a fault on VC's part or is this VC
	showing that it is able to detect a bootblock which will only boot
	a disk and nothing else?

	 This has (almost) the same effect as 'c:INSTALL df0:' which you
	may prefer to use to remove BootClock from the disk.


   The 'c' flag: When the '+c' flag is set, the bootclock is installed as
	a 'coolcapture' event. This means that when you boot your computer,
	reguardless of whether you boot from a harddisk or not, the
	bootclock is shown.

	 Why? If the BootClock program were the first command in your
	startup-sequence, you would see it quite early and it would serve
	it's purpose. But, if you were to be booting from another disk,
	BootClock would not run as it would not be in the startup-sequence
	of this new disk or even be on the disk. Having BootClock as a
	coolcapture event will keep it in memory until you either:-

			1). turn it off (Virus Checker can do this too)
			2). turn off your computer
			3). trash the system with a custom game
		or	4). crash your computer badly enough.


   When '-c' is flagged, BootClock will remove itself from the coolcapture
	vector so that next time you boot your computer, it is gone.


   The 'a' flag: This flag comes in only one flavour and that is '+a'.
	This flag causes the bootclock to be written to a disk's bootblock.
	The bootclock, when activated via a boot, will display the clock as
	per normal and will also install it as a coolcapture event so that
	every time you reset the computer the clock will be displayed even
	if you used another disk. This also includes a harddisk. Care has
	been taken to ensure that when a bootclock installed disk is booted
	with while the coolcapture is set, only one clock is displayed.

	Removal of a '+a' installed bootclock requires both the removal of
	the bootblock and the coolcapture event so -b and -c will be
	needed. Warning: I have noted a few times when -c does not work in
	this instance. Somehow, the coolcapture event re-installed itself!
	I cannot track down the cause and am humbled to say I've written
	something I have trouble controlling. Lucky this is not a virus :-)
	The best thing to do is to BootClock -c twice or until you recieve
	a message that the "Coolcapture is already cleared." For those who
	are worried about things that don't do as they are instructed may
	wish to turn their computer off. This will get rid of it for sure
	although it does seem a bit drastic.


   SPECIAL NOTE: As we all know :-) the Right Mouse Button is not
	available to us at the time the coolcapture event takes place. So
	what to about being able to use the RMB to change the date or time?
	One must wait until such a time arrives that the button can be read
	but how to do that? What I did was to set a one-time-only _LVODoIo
	patch. This patch gets all the DoIo calls rerouted thru it. If the
	call is not a trackdisk.device DoIo call, it is bypassed to the ROM
	routines. When the first T.D. call arrives, it is looking for a
	disk in DF0: to boot from. There may or may not be one there; it
	does not matter as the BootClock is displayed. When you are
	finished with it and press the LMB, the _LVODoIo patch is removed
	and the trackdisk DoIo routine is completed never to return to the
	patch. That is, of course, until you reset the computer when it
	will be patched again by the CoolCapture event to wait for the
	first T.D. DoIo. Make sense?


>>>>>	 Use this program at your own risk! I take no responsability for    
	custom bootblocks overwritten by idiots who did not read the warning
	above. Great care has been made to ensure that this program is not  
	destructive when installed into the coolcapture vector.            


	 BootClock has been tested on an Amiga 2000hd only. Users with other
	machines who find BootClock does not work are asked to write and let
	me know what happened.


	Dion
	    °