Sharing Violation on Drive A~
We saw this error when a person was loading a DLL and an EXE
through WLDR. The WLDR command line was like DLL NAME; EXE Name
Apparently, WLDR was loading the DLL into memory thus causing the
sharing violation to occur. The only solution was to load the DLL
seperately making sure to click on the symbols only button.