What does "user mapped Section open" mean
Posted: Sat Mar 08, 2008 3:12 am
Hi
I did a streaming restore of my C Drive and ended up with errors for 37 files "The requested operations could not be performed as a file with a user-mapped section is open".
Now I thought I understood what that meant...a file in use could not be replaced, but a lot of the files were fonts (.ttf) and others were files I didn't recognise (.nls and some .dll's). If AIS was going to lock anything I thought they would be critical OS files, which I guess the .nls and .dll's could be, but a bunch of obscure fonts? In any case doesn't AIS implement file-locking that permits overwriting of active files?
My problem of course is that given such cryptic advice I can't tell if the restore is safe or not...it works, but who knows when it might stop.
As it happens the problem I wanted to fix and that had prevented the system booting other than in Safe Mode still existed after the restore (I restored a back-up that pre-dated the occurrence of that problem). I'd very much doubt that the faulty needed to be locked as I'd think (by definition) it could not be active having been by-passed by the Safe Mode start-up
Thanks
Patrick
I did a streaming restore of my C Drive and ended up with errors for 37 files "The requested operations could not be performed as a file with a user-mapped section is open".
Now I thought I understood what that meant...a file in use could not be replaced, but a lot of the files were fonts (.ttf) and others were files I didn't recognise (.nls and some .dll's). If AIS was going to lock anything I thought they would be critical OS files, which I guess the .nls and .dll's could be, but a bunch of obscure fonts? In any case doesn't AIS implement file-locking that permits overwriting of active files?
My problem of course is that given such cryptic advice I can't tell if the restore is safe or not...it works, but who knows when it might stop.
As it happens the problem I wanted to fix and that had prevented the system booting other than in Safe Mode still existed after the restore (I restored a back-up that pre-dated the occurrence of that problem). I'd very much doubt that the faulty needed to be locked as I'd think (by definition) it could not be active having been by-passed by the Safe Mode start-up
Thanks
Patrick