ok guys... i searched many stuff about it.. and came to the conclution that this answer did not apply to any thread already done... maybe?? but i did search without results!

yesterday i installed Driver Suite 3.0, used to have 2.7 in other machine and the same happends except that this new driver suite don't freeze up my system and looks like running ok. the only think don't work is the mouse which dosen't do nothing at all.. and other stuff is that i set any bpx, even having many exported system .dll set, i can't get any bpx to work in WinXP

the real problem, which i consider, is that after installing it i can't longer see the Scandisk progress when i scheduled a check for Disk C:/ or D:/

i can't longer see the progress window while scandisk is running.. i know is running because windows takes longer to load but just a dark screen stay there reading

used to be blue.. looks like Driversuite modify some of the WinXP boot files.. i wonder if someone has experienced this problem before and how i can resolve this... i really don't want to install XP for this.. i'm short of time for that.. and still i would like to have Driver suite running and working....

this never happend with any application except with driversuite

anyone please?

1. Open Windows Explorer
2. See boot.ini
3. Right click and remove the read-only permissions
4. Open it in notepad
5. Remove the /nogui option
6. Right click and put the read-only permission again
7. Reboot
Now you can see everything.

Have Phun

yeap! that did the job!! anyone would tell me how to get the bpx's to work and break? is there something i should set up as additional option or something to download as additional component to make Driversuite work Under WinXP?

i really apreciated your help Aimless

Best regards!

In older versions of SoftICE:

bpx MessageBoxA

would allow softice to popup whenever ANY program calls the MessageBoxA API

In newer versions of Driver Studio/SICE Studio:

bpx MessageBoxA will NOT work. You will have to:

1. addr notepad (Assuming notepad is where you want to capture the breakpoint)
2. Bpx MessageBoxA

Intentionally or unintentionally, the bpx will work only and only when they are triggered in the CONTEXT where they were set. So you will routinely have to change context to your application using ADDR command and supsequently place the breakpoint.

Have Phun

you mean to set a Bpx under WinXP using Driver Suite 3.0

i'll have to write in SICE

addr "the program name"

then

bpx "some API function"

is this correct?


Best regards!

Yes.

A good idea is to let the SYMBOL LOADER load the application, stop at the ENTRYPOINT (it does all this automatically) and then put in your breakpoints.

Alternatively:

ADDR <your_application_name>
BPX <whatever...>

Have Phun

cRk: This has also already been discussed several times here. Had you actually read the threads on the latest versions of SICE you would have already known this requirement.

Regards.

sorry brother and thanks for all your efforts to make everyone go in the right way but i didn't found it. excuseme for mi mistake if i did a wrong step by making this thread

In addition to the ADDR command there are also the ATTACH and DETACH commands. The ATTACH command lets you set the default address context and symbol table to change to when SoftICE pops up. This avoids the necessity of having to set the ADDR each time you want to define the context in which breakpoints are to operate.

You will find a discussion of these issues here:

http://www.exetools.com/forum/showthread.php?s=&threadid=2548&highlight=sice

Regards.

To solve the mouse problem just goto the troubleshooting options in the softice settings and select

1. Disable num lock and caps lock programming
2. Do not patch keyboard driver
3. Disable USB mouse patching


compuboy_r