Hi,

i have a little problem: I just installed SI4 on my German Win2k. Then i placed my winice.dat into its folder. SI is supposed to popup when i press STRG+D...but nothing....the machine hnags i cant move the mouse anymore and cant hit any more keys...if i press again STRG+D everything is back to nromal...so i think STRg+D works well but SI just wont show its Window.

I already chekced this /NOGIUBOOT option in the boot.ini and switched to standard vga driver und enable UVD...no success at all.

Any1 has some ideas left ?

Tia & Merry christmas from Germany

Rayden

Sounds like youre experiencing similar problems to me. (see thread about Guillemot).

Can I ask what gfx card youre using ?

Carpathia

I Have a Elsa Eraotr III Pro with TNT 2 Chipset. I also treid to use the TNT Setting in Softice' Graphic-Setup but it dont help either

Rayden

Same problem here... in both win2k and Whistler. My card is a GeForce2 MX, appearantly it's a specific NVidia problem :/

actually, 2 ;-)

1. in which startup mode(s) did you (try to) load ntice?

2. when ntice starts up, it executes the commands from the INIT line in winice.dat. at this point you should see the ntice screen appear/disappear for split moments. can you actually observe this happen? (if different startup methods result in different behaviour, then please specify)

The NVidia drivers have stopped working with SoftIce some months ago. The last version I know to work with it is 5.32 which you can get at http://www.reactorcritical.com/download.shtml
I didn't try the new 7.xx drivers though, perhaps you can try them and tell me if they work, I don't dare to

Oops, I haven't read this in a while... but here the answers to your questions.

1. What startup modes: Manual. I allways used manual and serves well... I prefer this mode above all others and have never even bothered to try another.

2. Yes, I've seen a window pop up shortly... But I couldn't see what window and the contents.

Actually, I'll install Windows2000 again tomorrow perhaps (soon anywayz) and will let you know more about it...

Take care

Try this:

get ntoskrnl.dbg for your win2k build. translate it to nms and make NTICE use .nms for symbol lookup by adding to winice.dat this statement

NTSYMBOLS=ON

if this does not work , please post a msg here with your NTICE build , video card brand you have
and version of video drivers you have + whatever you use UVD or targeted display mode in ntice.. You would help us a lot with this to track down the problem with this information.

I tried your advice with regards to the ntoskrnl.dbg and it seemed to work fine at first... I got the softice screen and work with it. But then after a few minutes it was gone, the softice screen wasn't shown nemore (it was still there since ctrl^d would freeze the system and another ctrl^d would 'enable' it. Also when typing "bpx getlocaltime" in freeze-mode the system would freeze few times after ctrl^d, indicating that the bp's triggered).

So I don't know, maybe I don't have the correct .dbg file. Can anyone send me/mail me/tell me where I can get the ntoskrnl.dbg file for windows2000 Professional Final Edition. Also, where do I have to put the .nms file... in winnt/system32 or the softice dir itself?

I used the driverstudio2.0 release from softice, with detonator v6.49 drivers, using the Universal display driver. My card is a geforce2 mx from Asus ( v7100).
WHat IS the newest softice version? The one I'm using now... or should I go for the 4.05 version...

I would really LOVE to solve this issue as well...

DGR

customer support center:

http://www.microsoft.com/WINDOWS2000/downloads

follow the Other Downloads/Customer Support Diagnostics link.

.nms has to be where the file it refers to is, but i think loader32's translation mechanism will put it into the right directory for you.

btw, where did you get your .dbg files from?



4.05.526 from DS 2.0 (maybe there are newer beta builds since then).

as for my previous questions: does ntice pop up briefly when it executes the INIT line? or not even then?

Ah tnx, downloading it now....

I found the file by doing an ftp search and with the help of a helpful friend I also only got the ntoskrnl.dbg file, no others...

As for your question, yes... softice does pop up while executing the ini line. It even seems to work (a bit) now, meaning I DO see the softice window for a while, it pops up on ctrl^d as it's supposed to do and also at breakpoints. Now I don't know if it is because of the ntoskrnl.dbg and .nms file or maybe the newest version (Driversuite 2.0) or even the drivers (Det3 6.49). I'll have to look at that. But where before I never saw the softice screen it now acts normal for a while...

After a few minutes of use however it 'snaps back' to the original problem this topic is all about but as I said, it could be that the .dbg file I have is not the right one.

I'll give you some more info asap once I finished this download.

Take care,

DGR

And ehm... DS2.0, is that DriverStudio 2.0 or DriverSuite2.0

Still no luck,

Reinstalled everything, used softice from Driverstudio 2.0. I got the ntoskrnl.dbg file (from the location pointed out by The Owl) and translated it to a .nms file. Added it to the Softice Initialization Settings using the symbol loader and started praying. However, no luck...

Again it seems to work for a very short while, window pops up and u can use it normally... however suddenly the window stops popping up and the problem is back. I also tried it without the symbol file (that is, without the procedure above) and with the exact same result. It works for a very short while and then... problem.

The fact that before I never even could use softice my guess is that the 6.49 drivers (or the softice version from the Driver Suite 2.0) fixed some things.I'll try installing some older Detonator drivers to see if I can verify this.

If u need ne more info feel free to mail me...

Take care,

DGR

Well, I just keep on trying...

Appearantly switching the colour depth can help with this problem... (desktop/display->properties) I used 32-bit, got probs with the si-screen not popping up, switched to 16-bit and suddenly it appeared. Also, probs in 16-bit were solved by changing to 32-bit.

It's not as if it's default working on a certain depth, but changing it while running softice (so without rebootign the puter to let it take affect) works atleast temporarily.

I'll just keep fewling around to see if there's a way to fix it or work around, and I'll just keep posting it here even tho noone reads it

If you revert back to the old detonator 5.32 drivers it will work fine.

Only problem is that they suck for DirectDraw and Direct3D Performance, even MS Powerpoint presentations start to run slow!