page%ulowell.csnet@CSNET-RELAY.ARPA (11/28/85)
From: Bob Page <page%ulowell.csnet@CSNET-RELAY.ARPA>
If you haven't seen it yet, the disk-validate routine (that runs whenever
you insert a disk) not only checks the status of the disk (name, blocks
free, etc) but also looks at the dates of all the files in the top
directory. If the 'youngest' file has a date that is past the current
system date, the validator decides that the date somehow got out of sync
and changes the date to the date on the disk.
Try this: make the date, oh, lets say 28-nov-75. AmibaDOS stores dates
starting at 1978, so '75' is really the year 2075. Now copy a file from
RAM (anything) to your top level directory... we'll say DF0: for now. OK?
Now take out the disk (I like how the drive honks at you when you take the
candy out of its mouth), but before you do, change the date back to today
(this year). Ok, *now* take it out & put it back in again. The drive is
happy that you are feeding it (honk honk) and voila! The date is changed
from today's date to 2075. Amazing. No, not really. In fact, Amiga saw
this coming and if you set the date back to the real date and look at the
creation date of the file with LIST, it reports that the file was created
in the FUTURE. ("Bob, my mind is going. I can feel it. I can feel it.")
So now the answer is, why? Why not leave it alone? Will I have to check
my date every time I insert another disk?
Bob Page
PS Have you figured out how to pass parameters to a program that you have
loaded with LoadSeg and are about to CreatProc? I'm hot on the trail,
but if you can save me some time...
--------
UUCP: ...!decvax!wang!ulowell!page USPS: Computer Science Dept
ARPA: page%ulowell.csnet@csnet-relay University of Lowell
CSNET: page@ulowell Lowell MA 01854 USA
BIX: page PHONE: 617/452-5000x2233