Okay so i got my hands on this supposedly nifty tool, installed it, startet it, and opened symbol loader (after downloading some symbols like winsock and so on)

loaded my "project to crack" into it, then hit "load"

the game startet, and ... nothing..

what am i supposed to do with this tool ? isnt there supposed to start some debugging screen or something in the background showing what the game is doing or ?

i tryed seaching for some tutorials on how to use it on winxp and so on, but found nothing useful.

i did try searching this forum also.

(note softice is startet, since i can see symbols that have been loaded in the left side of symbol loader)

am i supposed to do/start something else ?

SoftICE ships with a manual in pdf format, you should read it first.

New trend: Saying you have done your research, but really haven't.

hint, I HAVE READ IT..

but i dont get anything its saying, all about network debugging and crap, i dont need that..

i just need to debug on this single machine..

btw, i got it to popup during a game when it crashed (it poped inside the game window)

but what i need is it to run constand in the background, checking everything, not only when a game crashes.

new trend : bashing people instead of actually helping.

or maybe you just dont know the answer to the question no?

in IDA it was simple, load the exe, hit the "debug file" option, and wrooms, but sadly this program detects that, so IDA is useless.

a simple search on this board returned 25 matches for topics relevant to what you want. Maybe you should refine your search by using keywords such as:

softice break WinMain
Break and Enter

"Using SoftICE.pdf" also contains everything you need.

The fact that this same question has been asked dozens of times already just proves that you didn't search for more than 5minutes, like the others.

This is about the most simple thing you can do with softice, yet it's the one that generates the most (identical) questions.

The reason softice poped up when your game crashed is because you have FAULTS on.

Furthermore, if the app you are debugging detects IDA's debugger, it will probably also detect softice. You will have to investigate that too before you say that SoftICE is also "useless". Plenty of documention on this forum for that as well.

Again proving that the "brain" is the most important reversing tool. You need to "think" what your problem is and the what terms may apply, and then search for information on your topic.

Regards,

thanks you, i didnt know it was softice break WinMain that might be the problem was all you had to say

search for softice break WinMain.

and that would been it..

i didnt mean to offend anyone, but it seems lately people are more busy making a jery springer show out of everything then actually just post a quick reply..

im here because im not good at this, thats why i asked, i really had no idea it was about winmain.

but if thats because im dumb them im sorry, but some people are dumb, cant change that

Bmsfx:

You need to clearly understand the difference between being "dumb" and being "lazy." You were being teased for at least appearing to be "lazy." We generally don't tease people who have actually tried to help themselves but "just don't get it."

Part of the problem is that you either did not read the FAQ listed at the top of the Forums, or chose not to follow it's directions. We can't tell which from what you post. You were supposed to explain what you had already done to try to help yourself.

Softice is a complex tool and it is NOT suprising that you would not completely understand how it works the first time you tried it, but it is also NOT reasonable that you did not give ANY indication that you had taken the most basic step of self-help, reading the manual, before you posted your question.

The second thing is that your problem with softice not breaking on entry of the program is an issue that has been previously discussed in many threads. This again means that you appeared not to have followed the FAQ instructions on doing a search here and possibly on the net for the solution to your problem before expecting someone else to solve it for you.

You will protest that you didn't know "what" the problem was to search for the right topic, but you fail to recognize that the main reason you didn't know what you might need to look for was that you failed to take the time to do adequate research before you started "cracking." This is a fairly common problem with those who lack the patience to attempt to learn how reverse engineering actually works before the actually start "reversing." For example, you know we have a "Tools of the Trade Forum" and if you had actually spent any significant time simply reading threads about problems using softice, you would have seen many, many threads discussing the issue of Softice not breaking on winmain and how to try to solve it.

So here's a test for you. Pretend you actually know how to reverse engineer, after having spent considerable time actually reading materials on the subject and having gotten your feet wet by trying many different protection systems. Now read the actual words you wrote in your first post, and tell us whether or not you would have concluded that the author of that post had demonstrated any personal effort at solving his own problem.

Then observe that, even though the poster did not evidence any self-help effort, he was actually told how he could find the answer to his question, and you will see that he responded with complaints that he was asked to do some of the finding and studying of that information "on his own first." Then see if you would have much patience with his complaints that someone didn't take him by the hand and spoon feed him what should have been an easy answer to discover with a little more effort.

Regards,

That concludes my closing statement, you Honor. Unless the defense calls for further discusions, I move for a prompt bench decision.