mix-fx 1.04


I lost the way to find the serial, somebody help?

Give us a break. Show that you've done some work on reversing the protection on your own, or that you are interested in learning the techniques in general, else this is a crack request pure and simple and will be ignored or deleted.

You'll get the benefit of the doubt and have a chance to try again. The apparent lame crack requests are getting a little too numerous lately. Nobody learns anything from them and they add nothing of substance to the board.

Please, let's go for quality posts people, not quantity!

Kayaker

:00405CD1 55 push ebp
:00405CD2 8BEC mov ebp, esp
:00405CD4 68935C4000 push 00405C93

* Possible Reference to Dialog: DialogID_0C82<-------**1**
|
:00405CD9 68820C0000 push 00000C82
:00405CDE E83DBCFFFF call 00401920 <-------**2**
:00405CE3 83C408 add esp, 00000008
:00405CE6 5D pop ebp
:00405CE7 C3 ret


**1** ref

Name: DialogID_0C82, # of Controls=003, Caption:"Invalid Key", ClassName:""
001 - ControlID:0001, Control Class:"BUTTON" Control Text:"OK"
002 - ControlID:FFFF, Control Class:"STATIC" Control Text:"This is not a valid MIX-FX key. Please make sure you are copying the entire k"
003 - ControlID:0006, Control Class:"BUTTON" Control Text:"Buy Now!"

**2**

when I pass this call, it shows the message "invalid key"

notes:
the register is in your C:\WINDOWS\MIX-FX.ini, but if your key is invalid, the register will be deleted next time you run the program.

questions:

how can i trace the proc the serial be

A little better

If the key is in an ini file, as I understand it, try breaking on GetPrivateProfileStringA. Look up this API in the Win32 Programmers Reference and display in Softice the parameters to monitor what is being read and where it is stored, i.e "dd esp.C" will show the 4th parameter
lpReturnedString, // points to destination buffer

When you find where your key string is stored then you can set a "read" BPR on that address range and Softice should break when the key string is first manipulated. Begin your tracing from there.

Try running an API monitor on the program, if the 'key' section of the ini file is being removed after it detects the bad key, this may show up how it's being done, perhaps with a WritePrivateProfileSection call. This will further help isolate the code you're looking for.

Hope this helps,
Kayaker

thanks kayaker