>Just for my own information, is it really true that DmWrite handles
>locking and relocking of the memory? I didn't know that. If so, I've
>been wasting calls all this time...
DmWrite turns memory-protection off and on around the call to MemMove that
changes the contents of the record. This is different from MemHandleLock and
MemHandleUnlock (which is what I'm assuming you're talking about). You have to
call MemHandleLock because, after all, how else will you get the pointer to pass
as the first parameter to DmWrite?
-- Keith
