How does one convince SoftIce to work on NT4 SP6?
I have installed the 4.01 update from NuMega’s web site which
is described as supporting NT4 SP5.
Still, when run on SP6, the keyboard is dead at logon screen.
I understand that SoftIce hooks into the keyboard driver when it initializes
and that there is a very close coupling required to get this done
– meaning, SoftIce has to be updated and this hasn’t been done yet.
Okay - what files do I replace with older ones to work around.
This then begs the question: Why hasn’t MS keyboard driver author coded
in a hook API to let the debugger get to keyboard a bit more gracefully.
Also - can the remote user interface stuff be configured to work
when SoftIce loads at boot time (e.g. Ethernet). Conviently, I have
the proper 3COM ethernet card that the docs call for, but don’t see
how to configure things to get this going at boot time.
Thanks in advance for any enlightenment.
Joe Nord
> I have installed the 4.01 update from NuMega’s web site which
is described as supporting NT4 SP5.
Still, when run on SP6, the keyboard is dead at logon screen.
Open the Symbol Loader. Goto Edit->SoftICE Initialization Settings.
In the troubleshooting tab, select “Do not paych keyboard driver”.
This is mentioned in the troubleshooting section of the Using SoftIce pdf
manual.
Of course, if you’ve set the driver to startup on “Automatic”, then its too
late and you wont be able to log on. Try rebooting to another OS, or using
floppy, and delete the driver file ntice.sys. You’ll then be able to boot
into NT and fix your problem.
Just had this problem this morning, and fixed it now.
Mark.
> Also - can the remote user interface stuff be configured to work
when SoftIce loads at boot time (e.g. Ethernet). Conviently, I have
the proper 3COM ethernet card that the docs call for, but don’t see
how to configure things to get this going at boot time.
Remote SoftICE allows you to use the SoftICE debugger across a standard IP
network using special NDIS drivers. Currently, both NE2000 compatibles and
3Com 3C90X cards are supported.
At this time, the Remote SoftICE capability cannot be used at boot time.
Obviously, Remote SoftICE requires an ethernet card and driver. SoftICE
cannot use the ethernet card and driver until it is loaded (which is always
AFTER SoftICE when SoftICE is loaded as a boot driver). We are working
towards a mode where Remote SoftICE can be configured at boot time before
the NDIS driver is loaded, but even still, the Remote SoftICE capabilities
won’t be activated until the NDIS driver is loaded and running.
To start Remote SoftICE, you must use the NET START command. At this time,
the NET START command attempts to locate the Remote SoftICE capable NDIS
driver. If the driver hasn’t been loaded and started yet, SoftICE will not
be able to find and use the card.
Your comments and suggestions about the Remote SoftICE capabilities are
welcome.
Patrick Klos
Network Software Engineer
NuMega Lab / Compuware Corporation
> Remote SoftICE capability cannot be used at boot time.
Obviously, Remote SoftICE requires an ethernet card and
driver. SoftICE cannot use the ethernet card and driver
until it is loaded (which is always AFTER SoftICE…
Yes, a tough problem.
I’m up and chasing bugs again.
Thanks everyone for your help.
Joe Nord
Crystal Semiconductor