Hi,

first post here, go easy on me.

I've installed soft ice 4.05 for windows nt (I have win2k pro SP2)
Everything went fine. I can load SICE manually no problem.
I choose universal video driver with standard VGA card. (My ATI radeon 9000 isn't listed)

I read about setting SICE up on various places for about 4 hours now. Depending on the version of SICE, the options that need to be tweaked vary and most tutorials I found were under win98.
So far, the only thing I could manage to change were the exports where I added a bunch of dlls from system32 (user32, kernel32, etc)
Now I was wondering how i could get nms files for the symbol section. From what I could gather by searching these boards is that I need debug dlls to convert. I don't know which ones and how to differ a normall dll from a debug dll. I'm pretty sure I have some debug one since I think they are installed with MSVS6 but I dont know whcih ones i need to convert to nms or even where to find them in my system.
SoftIce pdfs completely ignore this topic. So I went along

For a start, I thought I would toy around with minesweeper in order to get familiar with SICE. I tried loading the MSweeper exe into the symbol loader. I get an error and am asked if i want to continue. I choose to continue, get the game window to open then ctrl-d to debug it. Sytem freezes but nothing comes up. I ctrl-d again to regain control of windows. I change video settings as i've seen in these boards, but nothing makes the SICE window to pop.

So, I've been wondering if this might not be all inter-related. Since I didn't load nms files, I might get this error when loading the exe and hence SICE can't break on a symbol since it can't find any.

I read about 50 posts here of people with similar problems but replies are inconclusive. I would appreciate any help.
Sorry if I put you to sleep with my long post.

Ð.

use softice from driver studio 2.7, i had the same problems you described, and it turned out to be dodgy video card drivers, and the /nofastrgui switch being required.. read the softice readme.txt for more info.. but well i'd recommend u just get softice from driver studio 2.7 which is softice 4.2.7 (build 62) works here on 2k+sp3 no problems

If you use DriverStudio 2.7, you can get NMS files right from Microsoft for all the system DLL's , using the tool that comes with DS 2.7, it's called "Symbol Retriever", and it works very very well.

Just load in the DLL you want into Symbol Retriever and click "Get Symbols", and also make sure the box labeled "convert to NMS" is checked and it'll do it for you after downloading. THen just go into SoftICE settings and tell it to load those NMS symbol files on startup.

You might also have to go into the "Advanced" settings and add the line "NTSYMBOLS = YES"

-nt20

May be "NTSYMBOLS=ON"

That too.

Regards.

I managed to get my hands on a rip of SICE from Driver suite 2.7 but I don't want to use it since it's a rip and it's probably not coming with that symbol loader I need.

Wading through dead links in russian and czeck, I got a full 2.6 driver suite,but I read here that there's some bug with it. Not sure if it's only under XP, so I might go on with it if I don't find better.

I also had an error uninstalling SICE 4.05. No idea why. I got a leftover isu and ini file, prolly some reg keys too.
Great day. . .
Thanks for your input guys, I just hope to get this s**t working.

Ð

Hi nt20,

I use SoftIce 2.7, Win 2k sp3, i run your patch, but it's always display :

IntService1 Fail, GetLast Error return 2.

how can i use this patch to patch Int1 ?

and How can i patch registry and rename ntice.sys as Mokan said ?

( i search in registry only two places have information about ntice.sys )

That's all.

Thanks

For the first question, search the board for "Hiding INT1 softice", there is a huge thread about it. Basically what it boils down to is this:...

go into softice
do an IDT command
notice the "IDT base" write down that address
do a "db <idt base address>"
change the 16th byte (I THINK, check the thread I was talking about) to 0x8E. Softice sets it to 0xEE, we don't want that.

That should do it.

About the second question, I don't know.

-nt20