CloneClock DOCUMENTATION ** PREFACE If you don't have two computers set up in Parnet, you dont need this program, so go delete it NOW! ** WHAT THE H**L IS IT? Now that you ask so nicely I might as well tell you!! I have a A2000/030/882 + FPU and lots of other stuff, AND a CDTV. These two computers are set up in a Parnet Network. In contrast to my A2000 The clock in the CDTV has a bad habit of resetting itself to some odd time like 09-oct-88 and the clock on the front display says: 12:00. As time went by I got kind of tired of that, so CLONECLOCK WAS EVENTUALLY BORN!!! CloneClock simply copies the exact time on the computer on which the proggy is executed and installs this time on the other one. And you have the correct time on both computers. ** REQUIREMENTS 1. The program CloneClock ;-) 2. A running Parnet network 3. 'Netcmd' on the Amiga where you run CloneClock (tm)!! 'Netcmd' is a command within the Parnet Package if you didn't know! 4. The AmigaOS commands 'Date' and 'Setclock' on the amiga where you DO NOT RUN Cloneclock , -namely the one with the f**ked up time!! 5. Bad timing on one of your computers. :-) ** PARAMETERS There can be only one!! Parameter that is!! The parameter in question is a number between 0 and 9 which is used to specify a delay in seconds. This delay is however crucial for otherwise the Netcmd command might gets too many jobs on its hands. If you care to read the PROBLEMS section you will know why this delay is so important. You're free to choose a number between 0 and 9 in order to specify the delay. On my two Amigas 4 seconds works fine - every time!! The delay naturally depends on whether the command has to be loaded from a shitty diskdrive or a wonderful harddisk. Since my CDTV unlike my A2000 does not have 560HD space I have to wait for the disk drive to finish. Then again, if you code a VERY quick loader you might want to set the delay to 0!!! ** PROBLEMS *I have however observed a remarkably great instability during transferring the commands to the other Amiga using Netcmd. SnoopDOS points out that some weird background task (probably some effect from Netcmd) tries to execute a file called command.pkt twice. The way I see it, there seems to be a BIG problem with the timing in the Netcmd command. It saves a file in net:ram/ called command.pkt as a result of the first command. If this command.pkt has not been removed when the 2nd arrives things f**k up and you get a message saying something like: 'Can't open command packet'. I'm not sure Netcmd checks for another command being issued before creating another one - I dont thing it has anything like a chain or waitup mode! *If anybody finds out how to check for Netcmd being done issuing the command and when it has removed the command.pkt file, then I would be very grateful if you'd tell me - so that I could release a Watching-out-for-bug-in-netcmd version. ** SHIT YOU NEED TO KNOW *I have included the source in ASM in case you have problems and want to change it yourself. You dont need to be an assembler freak who remembers all OP codes in hex for the instructions sets on all motorola processors to firure out what it does!!! *I didn't try it out the other way around from CDTV to A2000 because the code is totally system friendly. There should be now problems coz I execute it from a 030/KS 2.04 to 000/KS 1.3, so I mean, if anything could go wrong it probably would have already!! ** ME Email: d1v@dc5101.aalborges.dk Address: Gorm Sørensen Kjeldgaardsgade 2,v5 9000 Aalborg Denmark