Fran�ois Van Emelen writes: > Sorry,my question didn't refer to your animation. I'll rephrase it. > The slave blocks grab some memory and DEL_DEFB releases some. Is the > released memory the one grabbed by th slave blocks? > fran�ois Van Emelen
DEL_DEFB deletes all drive defininition blocks in memory, having the effect of flushing slave blocks and resetting all directory devices to the state they were in before they were read first time, ie it forces a re-read of all directory devices next time theyre used. This prevents problems with drives, that may have been removed meantime, and Smsq getting its information from the slave blocks rather than the actual drive itself. It is a blunt instrument! WIN_DRIVE w,d,u,p appears to do a similar job for an individual drive, while WIN_REMV (when working) may not discard slave blocks used for read-buffering but forces data to be written immediately and the driver to re-check the hardware on every new open call to that device. For lack of detailed hard documentation the above is based on advice, and assumptions drawn from usage tests. Per
