Hi,
I'm a total newbie with cracking and stuff. But here's my question, is there a way to skip a screen and go straight to the program. For example, everytime I open this software a screen comes on saying to put your code in, I put the code in and it comes on. It's a rather long code and very annoying to put it in everytime, so is there a way to skip the code screen and go straight to the program? And if so how?
Thanks

Before JMI stops by to flame you for not doing your homework, let me give you the quick answer. Yes, more than likely it is possible. If you know nothing of debugging, or assembly language, it's probably more work than you want to take on. If you DO do assembly language programming, then you should just grab OllyDBG debugger, load the application into it, and single step it for a while until you see the box pop up. Once that happens, you know where the code is that does it, you just need to examine it, and make it not do it.

The choice is yours, the blue pill, or the red pill.

Now, put on your asbestos suit, as JMI will be along shortly to flame you on.

Moi?

Consider yourself flamed.

Regards,

Alternatively, you may want to check out some of the various Windows automation tools. Whilst they will not skip the screen, they could possibly type in the code for you and hit the OK button, depending on how the program asks for such code.

You should get support from the software's vendor since having to enter your valid, purchased serial number every time you start the program sounds like a bug that should be brought to the author's attention to fix

Ok thanks everyone, I thought maybe you just had to hex edit the .exe or somthing, but you're right FrankRizzo, it probably IS more work than I want to take on, but.... if there is a tutorial or somthing that I could follow. As of now I think I might just try to learn assembly language programming and find out what is and get an OllyDBG. Any more tips would be appreciated.

And sorry bout not doing my homework or whatever *goes off to learn assembly language and OllyDBG stuff* Thanks again.

Ah, if only I were flamed by JMI as well.

With the freezing temperatures I'm having here in my deserted hut, it would give a heavenly sensation on my flame retardant skin and weary old bones.

Damn, I mastered the FAQ. I just can't ask a flame inducing question.

Maybe some straying, off-the-point posts would trigger it too. I'll see.

Ok I've got the OllyDBG and run the program, in it. Well I've found the line where the screen comes up and now I have no idea what to do. Any help?

OK, what does the line look like?

Notes:

* Don't post the name of the program, or any identifying info (executable names, that kinda thing).

* If you post code, enclose it in the code tags. (Check the icon bar at the top of the full editor).

* Be patient, normally, you'll get an answer, sometimes, it might take a bit.

Ok there are several screens within the OllyDBG so I'll post several lines. The first line in at the top left and is and there are vertical lines between 765161F5 and C2 3000 and RETN 30. Then just below that is . Then on the bottem right is These are the lines on which the screen I don't want came up. Not sure if it's exactly what you need but it's what I came up with.

P.S. Now I'm not sure that the .exe is that I'm examining is the right one because I've noticed that in the program's file directory there's another .exe file which is named slightly different and if you run it, it comes up with the same code screen and after that the same program. However, if I run it in the OllyDBG and step into it finally an error comes on saying the program has stopped working and gives you the option to close the program, I close it and then when I exit the OllyDBG an error comes on saying "Unable to terminate process 'the program.exe'. Operating system reports error ERROR_ACCESS_DENIED". Maybe I just confused you and this .exe isn't important, but I thought I'd mention it.

Do these codes help, or should I try and get more?

You should do it on your own. Get a copy of "a reversing tutorial for newbies by lena151", you can find it on the internet as "snd-reversingwithlena", or alternatively i have them and a few more tools mirrored here: mediafire.com/?sharekey=695cd36b5754a754d5a101cf914073b4f6132e344c97ab37 The tools include OllyDBG DeFixed Edition modified by Team FOFF, which makes bypassing anti-debugging tricks easier, but i suggest that you follow the tutorials with a standard OllyDBG, as lena does show you how to do those tricks by yourself.

Of course, scan the files with your own antivirus. I know that they were clean at the time i uploaded them, but you never know what may happen.

No. Those aren't right. Graphical APIs are described in the User32.dll. You have functions from kernel32.dll.

Thanks everyone for your kind help, but I have what I want now... I got help through PM.

In case you guys are wondering, his target was a Wild Tangent app that the ARTeam's unpacker wouldn't touch.

Pretty nice progress they've made as far as anti-debug goes. They use SEH to catch all breakpoints, they check the debug registers, and throw a "Game is not installed properly" message if they're set. They set themselves up special so that you can't do an "OpenProcess" even if you're the parent, etc. LOTS of good ideas.

But, and this is almost laughable, when the app runs, it checks for D3D, and if not found, it crashes. As in seg faults, and lets you load a nice debugger, and save the contents of memory out. I really appreciate them doing that for me. It was really kind! :-)

Very nice of the programmers to leave such a vital crash logger in their Release build
Not only for reporting the crashes back to them but to help us find what we need.

LOL @ Crash