GNIREENIGNE
January 30th, 2011, 12:06
I have a target that automatically runs after I load it in to Olly. It loads all of the modules and stops on dciman32.dll. The Olly screen is blank and remains that way until I close the target. When I hit cancel/close on the target application, I can, then, see information in Olly. Of course, I can see that it's running from the main thread, but has stopped on module ntdll (which is not included with the target; i.e. it's a system file).
I have checked PEID, and there appears to be no protection.
Any ideas?
I am running Vista 32bit Home Premium Service Pack 2 on this current machine (with OllyDRX). I have also tried on Windows 7 Professional 64bit (with Olly 2.01 Alpha). The target application is a 32bit application with a 15-day trial. Opening the application as a standalone and/or with Olly attached, presents the application's main GUI with a nag screen in front. The nag screen gives the option for inputting a serial, selecting 'try' (for 15 days) and/or hitting cancel. The program closes out if you cancel, and does not function unless you select 'try'. The registration/serial function does state that the serial must be 16 characters long (minus dashes).
Thank you.
I have checked PEID, and there appears to be no protection.
Any ideas?
I am running Vista 32bit Home Premium Service Pack 2 on this current machine (with OllyDRX). I have also tried on Windows 7 Professional 64bit (with Olly 2.01 Alpha). The target application is a 32bit application with a 15-day trial. Opening the application as a standalone and/or with Olly attached, presents the application's main GUI with a nag screen in front. The nag screen gives the option for inputting a serial, selecting 'try' (for 15 days) and/or hitting cancel. The program closes out if you cancel, and does not function unless you select 'try'. The registration/serial function does state that the serial must be 16 characters long (minus dashes).
Thank you.