I download this Compuware SoftICE 4.3.0 Lite Edition, is the new and has only softice and no other things, and install, reboot and works well, only one thing for me this package hasn't and is a worry.

Dont have the wldr.exe for work with 16 bits files, i have downloaded the Compuware.SoftICE.Driver.Suite.3.0.1.StinkyD complete but i not wish install all the package, there are a form to extract the wldr.exe and other files if are necesary to work with 16 bits aplications?

Ricardo Narvaja

Those files are compressed inside the Huge file data.cab
WinRAR and other compression utils can read *.cab format and extract those files for you. But I am not sure if this was your question.

yes i try this but the files are type .ex_ , etcfor this reason i stop the process when i look this, i try again and see the complete files .

Ricardo

And all files are in the cab thanks only i need is the list of the files and the name and ubication of the carpet with the wldr.exe,
for extract the files needed to function properly, you have a list of a files of the carpet for softice in 16 bits i don't know if are many files, or few.

Sorry for my bad english

Ricardo

PM in spanish if you need

Is this what you are looking for?

Directory of D:\Program Files\Compuware\DriverStudio\SoftICE\Util16

11/22/2003 12:32 PM <DIR> .
11/22/2003 12:32 PM <DIR> ..
06/20/2002 11:49 AM 156,160 DBG2MAP.EXE
06/20/2002 11:49 AM 18,909 DLDR.EXE
06/20/2002 11:49 AM 1,763 DLOG.EXE
06/20/2002 11:49 AM 4,972 MSYM.EXE
06/20/2002 11:49 AM 16,529 Serial.exe
06/20/2002 11:49 AM 4,111 Util16.txt
06/20/2002 11:49 AM 116,272 WLDR.EXE
06/20/2002 11:49 AM 12,409 WLDR.HLP
9 File(s) 331,125 bytes
2 Dir(s) 58,501,451,776 bytes free

yes thanks.

Ricardo

just a quick question,

i have installed softice driversuite 3 on my winxp and it turns out thats it does not get detected by the progs does this happens to you as well??

Also, have you checked visual softice !?!?!

The answers are no and no, but could you expand a little on the not detected part? Which apps was iceExt used before and was it ineffective etc.

Gladly,

IceExt was not used at all !

Well, after installing driversuite 3, i started softice you know, played a bit with it, etc. Then i fired the docs, which in turn opened Acrobat reader 5 !
Funny, it worked! I remembered that my Softice 4 was detected by this app!
I run a few other programs that have some anti-ice, and none of them detected my debugger.

And no, i have not done any hex editing;

weird, i will check better when i get some free time

if you have any comments, please post.

softice 3 basically automatically defeats the meltice trick, however softice 3 is also kinda crap as it cant do global breakpoints (only process sensitive ones)

What are the most common situations in which you need process-global breakponts?

(I'm sure there are some, I just can't think of any really good ones right now, so it would be interesting to hear)

War is the only one I can think of at the moment. You always need to have "process-global breakpoints" in the event of war, or wasn't that what you were talking about?

Regards,

i use global breakpoints all the time, expecially for such things like safedisc, where the opcode handler and stuff is handled in a completely different process, to me its important, so i dont use sice3

If you're playing around with CreateProcess, CreateProcessAsUser or CreateRemoteThread and you know those new threads of execution are going to call something it really sucks to try and set a BP on a process that doesn't even exist yet!

How about network data? Often one process will recv() the data and another will process it. You ask yourself "Where did that data come from? Who wrote it there?" With global BPM you could just let 'er rip and see who was writing the data. If you don't know ahead of time which process is writing it, it takes HOURS to figure it out.

Using older versions of SICE there were a few times when I wanted to restrict a BP to a particular process or thread. It wasn't easy to do despite the old CSIP that never seemed to work right. But in just a couple of months I've cursed the lack of global breakpoints many more times than I ever did the inability to restrict them. It's a major pain in the a55 to not have global breakpoints.

All in all version 3 is an inferior product IMO.