Hrdina,
I have a similiar issue with my target setup. I have tried both the
serial route and the SINET route without success. After contacting NuMega,
and having several emails with the tech support person I was told that they
hadn’t seen it and it may be a dual processor bug. This was in November and
I haven’t heard anything since. So after using the SoftIce line for 10
years I had to give it up and go to windbg which, by the way, is finally
becoming usable. Attached are snippets from my emails to NuMega.
[snippets]
Soft-Ice Technical Issue 2:
Since the UVD driver did not work I attempted to setup remote debugging
using the ‘net’ commands. I followed the steps in the readme to reserve the
appropriate COM port. When the system first boots, I have control of the
target system, but once the initial laod is complete (the target screen
changes from text to graphics) I lose connectivity and the local debug
window closes automatically. This makes the product unusable for debugging
the target driver.
Issue 2:
I am trying to work around the video issue. The local machineis
the PC I am running sinet.exe on. The target machine is the one with
Soft-Ice installed on it. I have Soft-Ice set to start at boot time.
Under General Tab
I have no entries in the initialization string. I have a
History Buffer set to 256 and the video memory size set to 32768.
Under Remote Debugging Tab
I have Serial connection set to COM2. (nothing else set)
I reboot the target machine and wait for soft-ice to break in text mode.
on the target machine I type ‘net COM2 115200’
on the local machine I type ‘sinet COM1 115200’
I then get a new console window on my local machine displaying the
soft-ice info. At this time the display is on the target machine and the
local
machine and keyboard input works at both locations.
I then type ‘F5’ on the local machine to continue the boot process. The
screen on the target machine returns to the windows boot. No key presses
to break on the local machine work. If I hit the ‘CTRL-D’ on the target
machine the local sinet.exe window disappears and I get the video
problem described above. From the local machine I cannot re-establish a
connection to the target machine. Running sinet.exe again give an
“Authenticating…Unable to connect to target machine” error. Since I
cannot see any soft-ice output on the target machine I blindly typed
‘NET COM2 115200’ but could not get the connection back. If I hit ‘F5’ on
the target machine the OS continues running, but after several tries I could
not get the remote connection back. I am able to break and go on the target
machine, but this doesn’t do any good since I cannot see any output.
–
Dan
-----Original Message-----
From: Andrey Kolishak [mailto:xxxxx@sandy.ru]
Sent: Friday, January 05, 2001 3:34 AM
To: File Systems Developers
Subject: [ntfsd] Re: Serial debugging with SoftICE
Hello Hrdina,
readme.htm of SoftIce from DriverStudio 2.0 contains following:
"The new SoftICE Remote Debugging Protocol is accessed
through the NET command.
This protocol is much more efficient and robust than the existing
SERIAL remote protocol
USAGE: NET COMx baud -rate
To debug over a serial connection follow these steps:
1 - Connect two machines with a null modem cable
2 - Execute the NET COMx baud command line from within
SoftICE (either manually or from the INIT string) on the
target machine (the machine being debugged). This will cause
SoftICE to configure the com port and wait for a connection.
3- Run the SINET utility from a command prompt on the client
machine. Eg. SINET COM1 115200
4- At this point the connection has been made. Pop SoftICE up
on the target by typing Ctrl-Z from the SINET client.
5 - Break connection by typing NET STOP from within SoftICE
6 - To automatically configure SoftICE for a remote debugging
session, select a COM port, and check the Auto Connect (via
null modem) check box on the Remote Debugging tab under the
“Edit | SoftICE Initialization Settings” dialog in Loader32.
NOTE: this is only supported under NT and W2K for
DriverStudio 2.0. On Win9x systems, the NET COMx baud
command must be placed in the SoftICE INIT string.
Note: The SERIAL command has been renamed to OLDSERIAL. The
OLDSERIAL protocol will be removed from future releases.
"
So try use net insead of serial
HP> Hi all developers.
HP> Has everyone of you some experience with remote debugging
HP> (through serial port) using SoftICE ?
HP> I’m writing i8042prt filter for W2K and it is impossible to debug
HP> some portions of code using one computer.
HP> I have following problem. I can’t break into SoftICE once I use
HP> go command. I have successfully disabled keyboard patching by
HP> NullKeyboard registry value, in winice.dat I have set switching
HP> to serial in INIT=… and to this point everything is
working well.
HP> Additionally I can use tracing from remote machine. But once
HP> I use something like go, then I cannot break into SoftICE forever.
HP> Even if some breakpoint is set, debugged machine stops but
HP> serial console is no more correctly working.
HP> I think the problem is in client side (i.e. in serial.exe or
HP> serial32.exe)
HP> not in SoftICE itself. Or anyone has other experiences ?
HP> If someone can help me how to solve this problem I would
be very glad.
HP> Best regards
HP> Paul
HP> —
HP> You are currently subscribed to ntfsd as: xxxxx@sandy.ru
HP> To unsubscribe send a blank email to
leave-ntfsd-$subst(‘Recip.MemberIDChar’)@lists.osr.com
Best regards,
Andrey mailto:xxxxx@sandy.ru
-----BEGIN PGP PUBLIC KEY BLOCK-----
Version: 2.6.3ia
mQCNAzeUFgIAAAEEAOB2de/sEiBRVDNtMLxgS6fbS7x1MI24fDcjWh+njp7ywSe3
H0MmrMaKJx5Xx//7AINqJU3Nxm6hKxXCWmuu153ir0xgpgJuA6QSY0CgW/2WVbW9
8gY59eBrJdRQdm9qw2VIsTlAiYU06lonukPdRW3WwfuBpLDy2PVTaiqpF8flAAUR
tA1hbmRyQHNhbmR5LnJ1iQCVAwUQN5QWA/VTaiqpF8flAQFrDwQAt4e0/XxF9TBu
UnMBQzBQHK7vfFZWyHjU8kzLH9oXEZi3X07d7TCXXaBAFkboqayDHvGKpic0YvuV
hrKu8ANv7ZHMeU8EG5XGJGVV2DV+iqi2CyfYP1is1ncLZ2+Iy1YlqEu2l5XOf6pa
rl4HpwzHVSuoWjmC7X2rRR9m+tf5XWA=
=rFX3
-----END PGP PUBLIC KEY BLOCK-----
You are currently subscribed to ntfsd as: xxxxx@emc.com
To unsubscribe send a blank email to leave-ntfsd-$subst(‘Recip.MemberIDChar’)@lists.osr.com
You are currently subscribed to ntfsd as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntfsd-$subst(‘Recip.MemberIDChar’)@lists.osr.com