XP & SICE probs
 

Is anyone running driver studio 2.6 or driver suite 2.6 successfully on XP. I can get it to load ok but as soon as I start debugging I get a system lockup. Done the videocard check and everythings reported as being fine.
As an alternative to SICE does anybody know of any other decent debuggers which will run in XP. Tried olly debug but find it confusing.
Any tips or hints anyone?

no problem for me !
 

I'm using driver suite 2.6 under XP pro and I've not encounter any problems.

XP...No problem??
 

caron.nico,

Try to load an exe and see if WInice stops at the Entry point. Then try to break on MessageBoxA or W and do a F-11 to return to callee, and tell us the results.

Reply ASAP pls. Thanks.

I'm using Driver Suite 2.6 with XP Pro, I got not problem to run.
But the only problem I got is when I want to setup a breakpoint for HMEMCPY.
SoftIce says "Symbol not defined".
I can set others breakpoint such as GETDLGITEMTEXTA, WM_DESTROY --> No problem

I cannot set a Breakpoint BPX HMEMCPY.

Thanks for your helps.

Seem to remember reading somewhere that you can't use hmemcpy as a breakpoint in XP or Win2000. It's not a recognised breakpoint on these OS's.

i think it's stiill not woking , the same as in v2.5 (i can trap ShowWindow but not MessageBox :confused: :confused: ).
Can't stop it on winmain, bpxpoints are cleared after exitprocess, symloader requires debug info etc. etc...

Reply goes here
 

HMEMCPY is NOT supposed to work in NTx since this is a 16Bits OS call used by the 9x Kernel and not found on NTx Kernel. So it is normal that this call wont work on XP.

_Servil_`s symptom seems to be the symptoms that the majority of people are experiencing under XP. "Can't stop it on winmain, bpxpoints are cleared after exitprocess, symloader requires debug info etc. etc..."

vt0008, pls do what i told DooGie o do and post back your results. I really want to figure out that S-ice+XP issue.

Thanks

Sorry I've not replied yet Int03h but at present I've not even got Driver Suite installed. After my probs I uninstalled & haven't had the urge to reinstall it yet. Will reinstall when I see an app to crack that I really want to use and go from there.

Hi DooGie...

When I first installed it I had a similar problem. It would load OK, but lockup my system after exiting the debug window. Tried many things to fix the problem with out any success. Then one day my system refused to boot (not sure if this problem was related or not). Anyway, in an attempt to get my system up and running (without having to purchase a new BIOS chip), I manually cleared my CMOS (by shorting the appropriate pins on the main board). Anyway, this (thankfully) got my system back up and running and strangly resolved the S-ICE problem as well. Anyway, you may want to try clearing the CMOS this way as well, and see if it works for you.

BTW: Clearing the CMOS through the BIOS Setup screen did not fix the S-ICE problem, as I had tried that previously, nor did re-installing or any other software related things I tried. Only manually clearing the CMOS via the main board worked.

Thanks NE1 I'll try that sometime. Seems a pretty weird solution to the problem though. After clearing your cmos did you set up all the bios settings the same as you had them previously or did you make some changes?

Yeah, I agree it is a strange solution. I tried every possible BIOS setting previously with no luck, and after clearing it, and seeing that S-ICE was now working, I did put the settings back to thier previous settings and S-ICE still worked. If this solution works for you, I would be curious too know what hardware you are running to see if maybe we have something in common.

My barebones hardware is as follows.

Asus A7V Mainboard with VIA Apolla KT133 chipset.
AMD Athlon 1 GHz CPU.
894 MB RAM.

Int03h,

I did what you told DooGie to do.
SI doesn't stop with the breakpoint messageboxa.

Hello,
I'm also having troubles with SoftIce(DriverSuite 2.6)+XP. bpx
MessageBoxA works very well, but when I try to step out to the
caller, the program keeps executing. It seems like breakpoints
are working, but not returns; that exits the debugger.
Also, If I don't start SoftIce before XP (first alternative) XP
bluescreens at boot in SIWVID.

/tar

Has anyone come up with some info on this problem? I cannot get it to stop at WinMain.

softice ( latest ) very weak in breakpoint handling
 

Yes, to verybody: SoftICE ( the latest: form Driver Studio 2.6 ) is still weak when it comes to breakpoints... ) doesn�t handle stop at winman properly, doesn�t handle step over properly ( it sometimnes works, sometimes not ), doesn�t handle pass until ret properly...

When I say properly I mean simply not working or working too few times xD.

And at last, breakpoints on hmemecopy and other API calls dont work simply because they don�t even exist in WinNT architecture cause of their 16 bit nature.

Plissssss, if someone has a workaround for this weak breakpoint handling win SICE&XP, let everybody know! ( quite CRUCIAL ).

Good Luck Reversing Warriors! :o

:) I've read some where that memcpy not hmemcpy works in Nt/XP. Never tried it yet.

The problems with pret or stepover.
 

The problems have more to do with the logistics of
the XP threading model. I doubt this will be fixed easily
or least of all quickly.

If you break within (for example) MessageBoxA, have a look at your stack ( d esp ) and set a break point at your return address.