Log in

View Full Version : SoftICE vs. Detonator 29.40


B-Boy
May 20th, 2002, 03:35
Just curious about this one..

I had my Win98SE system set up with NVidia's Detonator 21.85 drivers, and when starting up SoftICE, everything went fine.
Now I saw the new Detonator Drivers and thought "Hey, why not update my system?", and installed the 29.40 drivers. Of course this was a bad idea because of the "Never touch a running system" rule. Yet, at first everything seemed fine again. *But* when I tried to start SoftICE with the new drivers installed, i got a nice black screen showing a "Error in IOS..blabla.. Real mode memory allocation" message (sorry for my bad translation).
Well, I then removed the 29.40 and reinstalled the 21.85 Detonators, and, oh holy sh*t, it works again.

Has anyone experienced the same problem or has a solution so SoftICE and the new Detonators will work together again?

Ah, I forgot:
I tried fiddling around here and there a bit to find the error. And I actually managed to get SoftICE working with the 29.40 drivers, by removing/renaming "c:\windows\system\viagart.vxd". *But* (oh no, not again) this resulted in a rather high loss of performance, so thats why I think this can't be *the* solution.

Kilby
May 24th, 2002, 10:17
To say that there have been some problems with drivers for the VIA chipset is a little bit of an understatement.

I spent a very unhappy time with one of the first VIA chipset motherboards, that supported 133 SDRAM.

These problems revolved around the AGP drivers, and it is always worth checking the VIA site for new drivers.

Kilby..

B-Boy
May 26th, 2002, 22:35
I have tried it with the VIA 4in1 4.28 and 4.39(beta) drivers. And concerning the SoftICE vs. Detonator issue, they seem to behave the same: 21.85 = ok, later versions = crash

robber804
June 29th, 2002, 00:09
The problem could be from Nview, I think nview was introduced sometime in the 27.x series, but I could be mistaken. Did you try to disable it in the 29.x drivers?

SilSaLaMaTa
June 29th, 2002, 08:10
I'm using TNT2 and I tried to upgrade my drivers , I have the same problem (on XP) .