Modifying system-wide DLL's in memory
-
On Windows XP, I've observed that modifying in-memory code in system DLL's only affects the current process. Does the same hold true on all versions of Windows from Windows 95 to the present?
-
On Windows XP, I've observed that modifying in-memory code in system DLL's only affects the current process. Does the same hold true on all versions of Windows from Windows 95 to the present?
zildjohn01 wrote:
On Windows XP, I've observed that modifying in-memory code in system DLL's only affects the current process. Does the same hold true on all versions of Windows from Windows 95 to the present?
Yes. Each process gets it's own copy of the operating system environment.
A guide to posting questions on CodeProject[^]
Dave Kreskowiak Microsoft MVP Visual Developer - Visual Basic
2006, 2007, 2008 -
On Windows XP, I've observed that modifying in-memory code in system DLL's only affects the current process. Does the same hold true on all versions of Windows from Windows 95 to the present?
In Win 9x, all memory from 0x80000000-0xFFFFFFFF is shared and writable to all processes. System DLLs (and other interesting bits like shared memory sections) reside there. This is not the case on NT-based OSes.
--Mike-- Visual C++ MVP :cool: LINKS~! CP SearchBar v3.0 | C++ Forum FAQ "That's what's great about doing user interface work. No matter what you do, people will say that what you did was idiotic." -- Raymond Chen