1 Assembly is derived from machine language, and each assembly language is specific to the type of computer you are using. If you want to crack most software, you will need to have a good grasp on assembly, which is a low-level programming language. It's an application design issue.Įdit: Also see Stephane's answer for a possible solution that might work, depending on how your specific application responds to its DLL changing. Learn Assembly programming and hex code manipulation. This has nothing to do with the OS you're running. You can update DLLs that applications use in Windows without terminating the process, but the application must have been written in such a way that it can be signaled to unload the assembly, wait for the update to finish, then reload the DLL. Windows locks it for a good reason.Įdit: I need to clarify something since some people seem intent on blaming Windows for what is actually an application design issue, not an OS design issue. Portions of DLLs (and even executables) can be mapped into RAM while other bits of it stay on disk, and may be read in at a later time.Ĭhanging the file on disk while Windows has bits of it mapped in RAM would not end well. Even though a DLL may be entirely mapped into physical memory while the application runs, there is definitely no guarantee of that.
0 kommentar(er)
