Yes I had to be the person to raise the issue hehe. Since it has been released for a couple of weeks now. Anyway I am curious what changes people have noticed in general and for XP. And if it is worth getting, etc. Any info is appreciated.

Snatch

Resurecting old threads is fun. But anyway I just want to confirm one thing: Win XP with or without SP1 breakpoints work flawlessly. It now resolves things fine. This is one quality release from Numega. Get Softice Driversuite 2.7 you will not regret it. In fact all platforms should get it. My only question now: when will we have a new Icedump .

Snatch

Oy silly me.

2002.09.09 released icedump 6.026 and nticedump 1.14. added support for SoftICE 4.27 build 562, PBPM (courtesy of ^DAEMON^). this is the last public release in the foreseeable future.

known bugs:
icedump: BPINT 3 ends up in a system crash since 6.019 when an int3 with EBP='KHCB' is executed

Too bad it could be the last public release. Wonder if that means Numega isnt going to be releasing anything for a while? Anyway its ready .

Snatch

Snatch Please Check Your PM

This thread was edited by ME.

You got a problem with that

Peace, Woodmann

Naw just wish they would stop dissappearing

lol in the email notification it said JMI replied not you

Athlon:

Sometimes I'm Dr. Jeckle, sometimes I'm Mr. Hyde. Why, I'm getting so good at anonymous surfing, I can even send fake email on this forum.

"Who knows what evil lurkes in the minds of men,
the Shadow do."

Regards.

*scary music* lol

I just installed DS2.7, but got a BSOD at startup (on WinXP).

I had installed it on an NTFS drive. Uninstalled it, then reinstalled it to a FAT32 drive (same as the one where WinXP was installed on) and then it worked.

Anyway.. it's been a loooong time since I did anything with SI, so forgot most of it (and never really did that much with it.. just used it a few times to get the feel of PC cracking.. being an old Amiga scener U know the kind)

So now I have this really stupid problem (almost ashamed to ask), but how do I start an .EXE again under SI control?! LOADER32 doesn't seem to break to SI, so I probably missed something (shame shame)

I've your same problem sintax .... dunno how to resolve it :/

Are we both morons? or are we missing something

Anyway I get around it by BPM'ing an API function.. or patching the .EXE -- but there are better ways for sure.. and I'm pretty sure it used to work in W95 with loader32.

Heh export breakpoints work at least . Breakpoint on entry point? Who wants that? I never do hehe. I guess this function is still broken or being used improperly? We should investigate this further by disassembling loader32 and see if the breakpoint in Softice is being set properly.

Snatch

Make sure you're allocating enough video memory in the settings. (This can definitely cause a BSOD)

disavowed: how much is enough though? I have a Quadro4 900XGL 128MB DDR and I have 1.5GB of RDRAM800 but where does that place the amount of video RAM I need for softice. Right now it is set to 2048MB. I got reboot bluescreens with 2.6 that went away with 2.7 the IRQL_NOT_LESS_OR_EQUAL only on a restart not shutdown oddly enough. Thank god its fixed .

Snatch

Read the entire message The solution was in the same message.

His solution was to change his file system. If other people read this thread, I'd hate for them to think that was their only option if they were getting BSOD's.

Snatch: I have a Geforce2 with 32 MB RAM. Setting the memory to 32768 KB still gave me a BSOD from SICE_VID.SYS (or whatever the KMD is that hooks into the video chain (I'm not on my home computer now, so I can't lookup the exact filename)). I bumped up the memory to 40000 KB in the Softice config, and no more BSOD

Thats interesting disavowed that you need so much when I get away with 2048kb. Guess it is very hardware dependent.

One interesting problem I have is when debugging certain games and what not since the screen mode is being changed the debugger either is invisible or shows up with messed up colors. Is there any good solution to this?

are you using the universal video driver for softice, or a video-card specific one? (i use the universal, which may be why our memory requirements are different)

I use universal too. Softice has very limited nVidia card support hehe.

Snatch

Breakpoints seem to work flawlessly for me, but skipping through back to a call(F12/P RET) doesn't seem to work at all, it just kicks me out and continue.. Anyone ideas?
I'm using XP.. :\

F12 can cause continue and rightfully so in certain instances. This happens a lot in system code. But if you are debugging an application unless you F12 out of a messagebox routine or the likes it should return properly.

Snatch

It seems it's back to the drawing board for Numega as far as it concerns NVidia chips under XP.
The 2.7 release works fine in Win2K with an NVidia GeForce2.
Under an XP system with a GeForce4 TI-4600, it's back to the dark screen.
In this case, it takes 5 seconds to do that. The monitor displays a countdown timer while it switches modes and it shouldn't do that.
A Ctrl-D takes you back to the desktop.
Softice has been set to use the Universal Driver and it passes its test. Nevertheless it doesn't seem to detect this NVidia card (it's stuck on Standard VGA) and probably that's why it tries to switch modes.
Any ideas for getting around it or do I wait for 2.8?
Thanks in advance.

Universal video mode doesnt select a manufacturer or model. Full screen mode you choose that and they only support one nVidia model there so its basically useless to try fullscreen without going standard VGA which should work. Maybe your memory setting is not enough that is most likely the problem. I have a Quadro4 900XGL(equivalent to Geforce4 but for workstations) and it works flawlessly.

Snatch

No luck yet.
If I select full screen mode, I get some distorted patterned background.
Raising the memory to 131072 (the card is 128MB) didn't make a difference either.
I suspect what the problem might be but if I'm right, I don't like the solution.
Since it works on other NVidia models, it might be dependent on reference drivers from NVidia.
The non-working system is the only one I have that uses manufacturer-modified drivers (Asus). I keep them because they have some extra 3D-glasses functionality.
I'll try the reference drivers tomorrow out of curiosity and post the results then.

I am running the Detonator 40 drivers that work very well. They are the latest and greatest just released.

Snatch

I tried with a different set of drivers.
v2.7 works under XP with the NVidia Detonators 40.41.
It seems they work fine as long as the drivers are reference ones and not manufacturer-specific.
Also, maybe somebody can verify this, v2.7 might have a small bug concerning the allocated video memory.
My card has 128MB on it and I run it at 1600x1200x32.
I set up Softice's video memory at 16MB (I tried 128MB too) and Ctrl-D into it.
I tried to save my sight and set the font=3. I also increased the number of lines to 60.
Softice refused to do that, claiming that I need to allocate around 3MB of video memory. I had 16MB.
I dropped the allocation to 8MB, tried again, and it worked.
It looks like it has some sort of upper limit on this and defaults to 2MB (maybe 1MB) if the specified value is over that upper limit.

Yes I have noticed that video memory and Softice have never been to consistant or explainable. I am at 2048kb of memory when I am at 1280x1024x32 and I can use 60 lines fine. I have no idea whats making all that happen. nVidia will release new Detonator 40 drivers soon so look out apparently 40.41 has some issues that cause games like UT2003 to not work to top performance .

Snatch