iwannacrack
June 30th, 2005, 20:24
First, I am an extreme newbie, so please try to ignore my ignorance.
That being said, I am attempting my first crack. The exe has references to the standard dlls, but from what I can tell, once launched it loads a few more using the Kernel32.LoadLibraryA. One of these files has the code for the registration dialog and the code to validate the serial.
I have been able to find the jne where the loaded dll displays success or failure of the serial and have cheated by changing this to je and got the success message. But it was short lived celebration, as the file was not cracked. So obviously somewhere upstream it is doing more work and I am not cracking these spots.
But I am very green. I cannot seem to find, or find on search engine, hint on how to find where the EXE file transfers control to the dll. The dll is very big and is more than likely used for many of the vendor's products so not all routines pertain to my EXE. And as the dll is not loaded till after the launch of the EXE, there are no references to it in the EXE to see where it is called.
Can someone provide a hint how I can tell where the main EXE calls the DLL and how to determine the exact entry point into the dll.
Hopefully this is not an obvious or stupid question.
Thanks
That being said, I am attempting my first crack. The exe has references to the standard dlls, but from what I can tell, once launched it loads a few more using the Kernel32.LoadLibraryA. One of these files has the code for the registration dialog and the code to validate the serial.
I have been able to find the jne where the loaded dll displays success or failure of the serial and have cheated by changing this to je and got the success message. But it was short lived celebration, as the file was not cracked. So obviously somewhere upstream it is doing more work and I am not cracking these spots.
But I am very green. I cannot seem to find, or find on search engine, hint on how to find where the EXE file transfers control to the dll. The dll is very big and is more than likely used for many of the vendor's products so not all routines pertain to my EXE. And as the dll is not loaded till after the launch of the EXE, there are no references to it in the EXE to see where it is called.
Can someone provide a hint how I can tell where the main EXE calls the DLL and how to determine the exact entry point into the dll.
Hopefully this is not an obvious or stupid question.
Thanks