Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!unix.cis.pitt.edu!dsinc!bagate!cbmvax!jesup From: jesup@cbmvax.commodore.com (Randell Jesup) Newsgroups: comp.sys.amiga.programmer Subject: Re: dos.library ACTION_SET_DATE question. Message-ID: <20503@cbmvax.commodore.com> Date: 10 Apr 91 06:17:52 GMT References: <182@atesysv.UUCP> Reply-To: jesup@cbmvax.commodore.com (Randell Jesup) Organization: Commodore, West Chester, PA Lines: 31 In article ben@epmooch.UUCP (Rev. Ben A. Mesander) writes: >Arg1 = unused >Arg2 = lock to parent dir (BPTR) >Arg3 = name of file (BSTR) >Arg4 = CPTR to date stamp > >Thanks to you and Randall Jesup, I patched my copy of PickPacket. It works >fine for ACTION_SET_DATE (aside from the fact that I can only set the time >of a file to the "beginning of time") That's no big deal though, I can >always "touch" it later. Note that SetComment and SetProtect are similar to SetDate. >Now that's strange - I thought that I had to put a lock on the parent >directory in the SET_DATE packet, not a lock on the file itself. You have it right (though you can use a lock on the file and a null name). >Also, I can set the date of a file using shared locks? That seems odd to >me also... Since the lock is on the parent, it's ok. -- Randell Jesup, Keeper of AmigaDos, Commodore Engineering. {uunet|rutgers}!cbmvax!jesup, jesup@cbmvax.commodore.com BIX: rjesup Disclaimer: Nothing I say is anything other than my personal opinion. Thus spake the Master Ninjei: "To program a million-line operating system is easy, to change a man's temperament is more difficult." (From "The Zen of Programming") ;-)