Sorry andy, didn't see your post there. You're quite right, the short filename seems to be the way to go - why it worked on my home system I'm not sure. Anyway...
Memory cannot be written, huh? I wonder what bit. The dll overwrites some API functions [CoCreateInstance and CreateFileA] and patches the VTable of several COM objects as they are created, all of which might be refused, even though I'm calling VirtualProtect() to enable write access. I've just read up a bit on "DPE" for Windows Server 2003 (link (viz http://technet2.microsoft.com/windowsserver/en/library/b0de1052-4101-44c3- a294-4da1bd1ef2271033.mspx?mfr=true )) and it might actually be that I need to mark my ASM thunks as executable. I've just updated the dll with this bit changed - give it a try. This *shouldn't* be the fix, because the error you're reporting says "cannot be written", not "cannot be executed". But I've never really put much stock in windows error messages. -- <http://forum.pspad.com/read.php?2,40832,40937> PSPad freeware editor http://www.pspad.com
