Question about WinDbg w/ COM port

Hi everyone!

This is my first post to the list. I?m just getting into the field of
Windows Device Driver programming.

I?m
trying?to?do?kernel?debugging?with?windbg.?Connect?two?machines?with?serial?
cable.?Debugger?is?win2k3?SP1,?debuggee?is?win2k3?R2.?Tried?the?whole?aftern
oon?but cannot?connect.

The?problem?is,?on?the?debugger,?I?used?to?have?some?self?created?drivers?th
ere?and?they?mess?up?the?serial?and?parallel?ports.?So?I?deleted?them.?One?o
f?them?is?a?PnP?driver.?What?I?did?is,?I?just?delete?all?the?files?from?syst
em32/drivers?and?delete?all?the?registry?entries?matching?the?names.?After?t
hat,?all?the?ports,?including?serial?and?parallel?ports?disappeared?from?dev
ice?manager!?I?can?see?them?in?System?Information/Components/Port.?And?I?can
?start?windbg?and?try?to?connect?this?port,?which?leads?to?the?reconnect…
?status.

On?the?other?hand,?when?booting?the?system?with?Debugging?Mode?&?debugger?co
nsole?both?on,?the?COM?port?that?is?supposed?to?be?used?for?debugging?disapp
eared.?However,?the?system?does?not?halt?on?the?booting?stage,?just?nothing?
happens.

I’m?sorry?to?write?so?much?in?detail?but?this?problem?is?crazing?me?for?a?wh
ole?afternoon.?If?luckily?any?of?you?are?expert?in?this?area,?please?give?me
?some?advice.

Thank?you!

First, let’s get some terminology straightened out. From what you said I
assume that you have Server 2003 installed on both systems. The host,
where WinDbg is installed, is Server 2003 SP1, and the target, where you
modified a line in the Boot.ini file with the switches to either debug
using serial or 1394, is 2003 Server. Is the target SP1? Sorry, R2 could
mean anything.

Second … if you did what I think you said you did … DON’T EVER DO
THAT!!! Did you really do the equivalent of “del
\Windows\System32\Drivers* /f”!?!?!? Or, did you only delete YOUR driver
files?

Third, which version of WinDbg are you using? The latest is 6.6.0003.5 and
I think is recommended.? Can you connect, without booting to the debugger
on the target, using HyperTerminal, between the two systems? Are you using
a NULL modem cable? Are both systems set too the same baud rate,
start/stop bits, and parity? Are you using true serial or going through a
USB to serial converter?

Gary G. Little

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Yiping Han
Sent: Thursday, March 16, 2006 5:51 PM
To: Kernel Debugging Interest List
Subject: [windbg] Question about WinDbg w/ COM port

Hi everyone!

This is my first post to the list. I?m just getting into the field of
Windows Device Driver programming.

I?m
trying?to?do?kernel?debugging?with?windbg.?Connect?two?machines?with?seria
l?
cable.?Debugger?is?win2k3?SP1,?debuggee?is?win2k3?R2.?Tried?the?whole?afte
rn
oon?but cannot?connect.

The?problem?is,?on?the?debugger,?I?used?to?have?some?self?created?drivers?
th
ere?and?they?mess?up?the?serial?and?parallel?ports.?So?I?deleted?them.?One
?o
f?them?is?a?PnP?driver.?What?I?did?is,?I?just?delete?all?the?files?from?sy
st
em32/drivers?and?delete?all?the?registry?entries?matching?the?names.?After
?t
hat,?all?the?ports,?including?serial?and?parallel?ports?disappeared?from?d
ev
ice?manager!?I?can?see?them?in?System?Information/Components/Port.?And?I?c
an
?start?windbg?and?try?to?connect?this?port,?which?leads?to?the?reconnect…

?status.

On?the?other?hand,?when?booting?the?system?with?Debugging?Mode?&?debugger?
co
nsole?both?on,?the?COM?port?that?is?supposed?to?be?used?for?debugging?disa
pp
eared.?However,?the?system?does?not?halt?on?the?booting?stage,?just?nothin
g?
happens.

I’m?sorry?to?write?so?much?in?detail?but?this?problem?is?crazing?me?for?a?
wh
ole?afternoon.?If?luckily?any?of?you?are?expert?in?this?area,?please?give?
me
?some?advice.

Thank?you!


You are currently subscribed to windbg as: unknown lmsubst tag argument:
‘’
To unsubscribe send a blank email to xxxxx@lists.osr.com

Dear Gary,

I just solved this problem this morning. It is the problem with the cable. I
thought it was because I delete my own pnp driver.

R2 is newer than SP1 and we did have new bugs popped out when running our
old drivers on the new R2 version.

I only delete my own driver. Can you tell me what is the best way to delete
a PnP driver? If I don?t remove my driver from system32 and registry, each
time I scan for new device, it is just applied to the serial port and takes
control.

Thank you very very much for your information!

  • Yiping Han

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of
xxxxx@seagate.com
Sent: Friday, March 17, 2006 10:17 AM
To: Kernel Debugging Interest List
Subject: RE: [windbg] Question about WinDbg w/ COM port

First, let’s get some terminology straightened out. From what you said I
assume that you have Server 2003 installed on both systems. The host,
where WinDbg is installed, is Server 2003 SP1, and the target, where you
modified a line in the Boot.ini file with the switches to either debug
using serial or 1394, is 2003 Server. Is the target SP1? Sorry, R2 could
mean anything.

Second … if you did what I think you said you did … DON’T EVER DO
THAT!!! Did you really do the equivalent of “del
\Windows\System32\Drivers* /f”!?!?!? Or, did you only delete YOUR driver
files?

Third, which version of WinDbg are you using? The latest is 6.6.0003.5 and
I think is recommended.? Can you connect, without booting to the debugger
on the target, using HyperTerminal, between the two systems? Are you using
a NULL modem cable? Are both systems set too the same baud rate,
start/stop bits, and parity? Are you using true serial or going through a
USB to serial converter?

Gary G. Little

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Yiping Han
Sent: Thursday, March 16, 2006 5:51 PM
To: Kernel Debugging Interest List
Subject: [windbg] Question about WinDbg w/ COM port

Hi everyone!

This is my first post to the list. I?m just getting into the field of
Windows Device Driver programming.

I?m
trying?to?do?kernel?debugging?with?windbg.?Connect?two?machines?with?seria
l?
cable.?Debugger?is?win2k3?SP1,?debuggee?is?win2k3?R2.?Tried?the?whole?afte
rn
oon?but cannot?connect.

The?problem?is,?on?the?debugger,?I?used?to?have?some?self?created?drivers?
th
ere?and?they?mess?up?the?serial?and?parallel?ports.?So?I?deleted?them.?One
?o
f?them?is?a?PnP?driver.?What?I?did?is,?I?just?delete?all?the?files?from?sy
st
em32/drivers?and?delete?all?the?registry?entries?matching?the?names.?After
?t
hat,?all?the?ports,?including?serial?and?parallel?ports?disappeared?from?d
ev
ice?manager!?I?can?see?them?in?System?Information/Components/Port.?And?I?c
an
?start?windbg?and?try?to?connect?this?port,?which?leads?to?the?reconnect…

?status.

On?the?other?hand,?when?booting?the?system?with?Debugging?Mode?&?debugger?
co
nsole?both?on,?the?COM?port?that?is?supposed?to?be?used?for?debugging?disa
pp
eared.?However,?the?system?does?not?halt?on?the?booting?stage,?just?nothin
g?
happens.

I’m?sorry?to?write?so?much?in?detail?but?this?problem?is?crazing?me?for?a?
wh
ole?afternoon.?If?luckily?any?of?you?are?expert?in?this?area,?please?give?
me
?some?advice.

Thank?you!


You are currently subscribed to windbg as: unknown lmsubst tag argument:
‘’
To unsubscribe send a blank email to xxxxx@lists.osr.com


You are currently subscribed to windbg as: unknown lmsubst tag argument: ‘’
To unsubscribe send a blank email to xxxxx@lists.osr.com

I won’t say it is the BEST way, but how I do it is to use Device Manager
to uninstall the driver. I then go to \Windows\INF and use findstr to find
a uniqueness about my driver in the oem?.inf files, and then delete oem?.*
for the OEM files that I find. Finally, I may, or may not, depending upon
what I am doing, go to the registry and purge the drivers from
CurrentControlSet.

The best way I have found is to create a System Restore checkpoint before
you install the driver the first time. When I really need the driver to be
gone simply, run System Restore and use that check point. A second best
way is to use imaging software to create an image for a bare-bones
restore.

Gary G. Little

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Yiping Han
Sent: Friday, March 17, 2006 9:29 AM
To: Kernel Debugging Interest List
Subject: RE: [windbg] Question about WinDbg w/ COM port

Dear Gary,

I just solved this problem this morning. It is the problem with the cable.
I
thought it was because I delete my own pnp driver.

R2 is newer than SP1 and we did have new bugs popped out when running our
old drivers on the new R2 version.

I only delete my own driver. Can you tell me what is the best way to
delete
a PnP driver? If I don?t remove my driver from system32 and registry, each
time I scan for new device, it is just applied to the serial port and
takes
control.

Thank you very very much for your information!

  • Yiping Han

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of
xxxxx@seagate.com
Sent: Friday, March 17, 2006 10:17 AM
To: Kernel Debugging Interest List
Subject: RE: [windbg] Question about WinDbg w/ COM port

First, let’s get some terminology straightened out. From what you said I
assume that you have Server 2003 installed on both systems. The host,
where WinDbg is installed, is Server 2003 SP1, and the target, where you
modified a line in the Boot.ini file with the switches to either debug
using serial or 1394, is 2003 Server. Is the target SP1? Sorry, R2 could
mean anything.

Second … if you did what I think you said you did … DON’T EVER DO
THAT!!! Did you really do the equivalent of “del
\Windows\System32\Drivers* /f”!?!?!? Or, did you only delete YOUR driver
files?

Third, which version of WinDbg are you using? The latest is 6.6.0003.5 and
I think is recommended.? Can you connect, without booting to the debugger
on the target, using HyperTerminal, between the two systems? Are you using
a NULL modem cable? Are both systems set too the same baud rate,
start/stop bits, and parity? Are you using true serial or going through a
USB to serial converter?

Gary G. Little

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Yiping Han
Sent: Thursday, March 16, 2006 5:51 PM
To: Kernel Debugging Interest List
Subject: [windbg] Question about WinDbg w/ COM port

Hi everyone!

This is my first post to the list. I?m just getting into the field of
Windows Device Driver programming.

I?m
trying?to?do?kernel?debugging?with?windbg.?Connect?two?machines?with?seria
l?
cable.?Debugger?is?win2k3?SP1,?debuggee?is?win2k3?R2.?Tried?the?whole?afte
rn
oon?but cannot?connect.

The?problem?is,?on?the?debugger,?I?used?to?have?some?self?created?drivers?
th
ere?and?they?mess?up?the?serial?and?parallel?ports.?So?I?deleted?them.?One
?o
f?them?is?a?PnP?driver.?What?I?did?is,?I?just?delete?all?the?files?from?sy
st
em32/drivers?and?delete?all?the?registry?entries?matching?the?names.?After
?t
hat,?all?the?ports,?including?serial?and?parallel?ports?disappeared?from?d
ev
ice?manager!?I?can?see?them?in?System?Information/Components/Port.?And?I?c
an
?start?windbg?and?try?to?connect?this?port,?which?leads?to?the?reconnect…

?status.

On?the?other?hand,?when?booting?the?system?with?Debugging?Mode?&?debugger?
co
nsole?both?on,?the?COM?port?that?is?supposed?to?be?used?for?debugging?disa
pp
eared.?However,?the?system?does?not?halt?on?the?booting?stage,?just?nothin
g?
happens.

I’m?sorry?to?write?so?much?in?detail?but?this?problem?is?crazing?me?for?a?
wh
ole?afternoon.?If?luckily?any?of?you?are?expert?in?this?area,?please?give?
me
?some?advice.

Thank?you!


You are currently subscribed to windbg as: unknown lmsubst tag argument:
‘’
To unsubscribe send a blank email to xxxxx@lists.osr.com


You are currently subscribed to windbg as: unknown lmsubst tag argument:
‘’
To unsubscribe send a blank email to xxxxx@lists.osr.com


You are currently subscribed to windbg as: unknown lmsubst tag argument:
‘’
To unsubscribe send a blank email to xxxxx@lists.osr.com

Note that if you use a MSI to install your driver (i.e. use DIFx or
something like it), a system restore point will be created for you
automagically.

wrote in message news:xxxxx@windbg…
I won’t say it is the BEST way, but how I do it is to use Device Manager
to uninstall the driver. I then go to \Windows\INF and use findstr to find
a uniqueness about my driver in the oem?.inf files, and then delete oem?.*
for the OEM files that I find. Finally, I may, or may not, depending upon
what I am doing, go to the registry and purge the drivers from
CurrentControlSet.

The best way I have found is to create a System Restore checkpoint before
you install the driver the first time. When I really need the driver to be
gone simply, run System Restore and use that check point. A second best
way is to use imaging software to create an image for a bare-bones
restore.

Gary G. Little

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Yiping Han
Sent: Friday, March 17, 2006 9:29 AM
To: Kernel Debugging Interest List
Subject: RE: [windbg] Question about WinDbg w/ COM port

Dear Gary,

I just solved this problem this morning. It is the problem with the cable.
I
thought it was because I delete my own pnp driver.

R2 is newer than SP1 and we did have new bugs popped out when running our
old drivers on the new R2 version.

I only delete my own driver. Can you tell me what is the best way to
delete
a PnP driver? If I don’t remove my driver from system32 and registry, each
time I scan for new device, it is just applied to the serial port and
takes
control.

Thank you very very much for your information!

- Yiping Han

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of
xxxxx@seagate.com
Sent: Friday, March 17, 2006 10:17 AM
To: Kernel Debugging Interest List
Subject: RE: [windbg] Question about WinDbg w/ COM port

First, let’s get some terminology straightened out. From what you said I
assume that you have Server 2003 installed on both systems. The host,
where WinDbg is installed, is Server 2003 SP1, and the target, where you
modified a line in the Boot.ini file with the switches to either debug
using serial or 1394, is 2003 Server. Is the target SP1? Sorry, R2 could
mean anything.

Second … if you did what I think you said you did … DON’T EVER DO
THAT!!! Did you really do the equivalent of “del
\Windows\System32\Drivers* /f”!?!?!? Or, did you only delete YOUR driver
files?

Third, which version of WinDbg are you using? The latest is 6.6.0003.5 and
I think is recommended.? Can you connect, without booting to the debugger
on the target, using HyperTerminal, between the two systems? Are you using
a NULL modem cable? Are both systems set too the same baud rate,
start/stop bits, and parity? Are you using true serial or going through a
USB to serial converter?

Gary G. Little

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Yiping Han
Sent: Thursday, March 16, 2006 5:51 PM
To: Kernel Debugging Interest List
Subject: [windbg] Question about WinDbg w/ COM port

Hi everyone!

This is my first post to the list. I’m just getting into the field of
Windows Device Driver programming.

I’m
trying to do kernel debugging with windbg. Connect two machines with seria
l
cable. Debugger is win2k3 SP1, debuggee is win2k3 R2. Tried the whole afte
rn
oon but cannot connect.

The problem is, on the debugger, I used to have some self created drivers
th
ere and they mess up the serial and parallel ports. So I deleted them. One
o
f them is a PnP driver. What I did is, I just delete all the files from sy
st
em32/drivers and delete all the registry entries matching the names. After
t
hat, all the ports, including serial and parallel ports disappeared from d
ev
ice manager! I can see them in System Information/Components/Port. And I c
an
start windbg and try to connect this port, which leads to the reconnect…

status.

On the other hand, when booting the system with Debugging Mode & debugger
co
nsole both on, the COM port that is supposed to be used for debugging disa
pp
eared. However, the system does not halt on the booting stage, just nothin
g
happens.

I’m sorry to write so much in detail but this problem is crazing me for a
wh
ole afternoon. If luckily any of you are expert in this area, please give
me
some advice.

Thank you!


You are currently subscribed to windbg as: unknown lmsubst tag argument:
‘’
To unsubscribe send a blank email to xxxxx@lists.osr.com


You are currently subscribed to windbg as: unknown lmsubst tag argument:
‘’
To unsubscribe send a blank email to xxxxx@lists.osr.com


You are currently subscribed to windbg as: unknown lmsubst tag argument:
‘’
To unsubscribe send a blank email to xxxxx@lists.osr.com

Thanks for the points from both of you!

– Yiping

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Jeff Henkels
Sent: Friday, March 17, 2006 3:10 PM
To: Kernel Debugging Interest List
Subject: Re:[windbg] Question about WinDbg w/ COM port

Note that if you use a MSI to install your driver (i.e. use DIFx or
something like it), a system restore point will be created for you
automagically.

wrote in message news:xxxxx@windbg…
I won’t say it is the BEST way, but how I do it is to use Device Manager
to uninstall the driver. I then go to \Windows\INF and use findstr to find
a uniqueness about my driver in the oem?.inf files, and then delete oem?.*
for the OEM files that I find. Finally, I may, or may not, depending upon
what I am doing, go to the registry and purge the drivers from
CurrentControlSet.

The best way I have found is to create a System Restore checkpoint before
you install the driver the first time. When I really need the driver to be
gone simply, run System Restore and use that check point. A second best
way is to use imaging software to create an image for a bare-bones
restore.

Gary G. Little

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Yiping Han
Sent: Friday, March 17, 2006 9:29 AM
To: Kernel Debugging Interest List
Subject: RE: [windbg] Question about WinDbg w/ COM port

Dear Gary,

I just solved this problem this morning. It is the problem with the cable.
I
thought it was because I delete my own pnp driver.

R2 is newer than SP1 and we did have new bugs popped out when running our
old drivers on the new R2 version.

I only delete my own driver. Can you tell me what is the best way to
delete
a PnP driver? If I don’t remove my driver from system32 and registry, each
time I scan for new device, it is just applied to the serial port and
takes
control.

Thank you very very much for your information!

- Yiping Han

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of
xxxxx@seagate.com
Sent: Friday, March 17, 2006 10:17 AM
To: Kernel Debugging Interest List
Subject: RE: [windbg] Question about WinDbg w/ COM port

First, let’s get some terminology straightened out. From what you said I
assume that you have Server 2003 installed on both systems. The host,
where WinDbg is installed, is Server 2003 SP1, and the target, where you
modified a line in the Boot.ini file with the switches to either debug
using serial or 1394, is 2003 Server. Is the target SP1? Sorry, R2 could
mean anything.

Second … if you did what I think you said you did … DON’T EVER DO
THAT!!! Did you really do the equivalent of “del
\Windows\System32\Drivers* /f”!?!?!? Or, did you only delete YOUR driver
files?

Third, which version of WinDbg are you using? The latest is 6.6.0003.5 and
I think is recommended.? Can you connect, without booting to the debugger
on the target, using HyperTerminal, between the two systems? Are you using
a NULL modem cable? Are both systems set too the same baud rate,
start/stop bits, and parity? Are you using true serial or going through a
USB to serial converter?

Gary G. Little

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Yiping Han
Sent: Thursday, March 16, 2006 5:51 PM
To: Kernel Debugging Interest List
Subject: [windbg] Question about WinDbg w/ COM port

Hi everyone!

This is my first post to the list. I’m just getting into the field of
Windows Device Driver programming.

I’m
trying to do kernel debugging with windbg. Connect two machines with seria
l
cable. Debugger is win2k3 SP1, debuggee is win2k3 R2. Tried the whole afte
rn
oon but cannot connect.

The problem is, on the debugger, I used to have some self created drivers
th
ere and they mess up the serial and parallel ports. So I deleted them. One
o
f them is a PnP driver. What I did is, I just delete all the files from sy
st
em32/drivers and delete all the registry entries matching the names. After
t
hat, all the ports, including serial and parallel ports disappeared from d
ev
ice manager! I can see them in System Information/Components/Port. And I c
an
start windbg and try to connect this port, which leads to the reconnect…

status.

On the other hand, when booting the system with Debugging Mode & debugger
co
nsole both on, the COM port that is supposed to be used for debugging disa
pp
eared. However, the system does not halt on the booting stage, just nothin
g
happens.

I’m sorry to write so much in detail but this problem is crazing me for a
wh
ole afternoon. If luckily any of you are expert in this area, please give
me
some advice.

Thank you!


You are currently subscribed to windbg as: unknown lmsubst tag argument:
‘’
To unsubscribe send a blank email to xxxxx@lists.osr.com


You are currently subscribed to windbg as: unknown lmsubst tag argument:
‘’
To unsubscribe send a blank email to xxxxx@lists.osr.com


You are currently subscribed to windbg as: unknown lmsubst tag argument:
‘’
To unsubscribe send a blank email to xxxxx@lists.osr.com


You are currently subscribed to windbg as: xxxxx@falconstor.com
To unsubscribe send a blank email to xxxxx@lists.osr.com