How to debug a Windows Me test system

NTDEV
1

Hello everyone,

I want to debug a device driver running in a Windows Me test system through
debug tools, such as debugger, windbg or others. Can anyone give me help on
how to do it, especially

(1) how to set up a connection between development system and test system;
(2) if I can use different OS in development system, such as Windows 98.

Thanks in advance for your help!

Regards
Shunnian

2

You can find the necessary info on how to setup the debugger and the
debuggee on the latest ddk. You may have different OS on the dev and test
machines as long as you have the symbols loaded correctly. Check the details
on ddk or microsoft web site

Suyash Sinha

-----Original Message-----
From: xxxxx@asia.adaptec.com [mailto:xxxxx@asia.adaptec.com]
Sent: Tuesday, November 14, 2000 4:00 PM
To: NT Developers Interest List
Subject: [ntdev] How to debug a Windows Me test system

Hello everyone,

I want to debug a device driver running in a Windows Me test system through
debug tools, such as debugger, windbg or others. Can anyone give me help on
how to do it, especially

(1) how to set up a connection between development system and test system;
(2) if I can use different OS in development system, such as Windows 98.

Thanks in advance for your help!

Regards
Shunnian

You are currently subscribed to ntdev as: xxxxx@microsoft.com
To unsubscribe send a blank email to $subst(‘Email.Unsub’)

3

> (1) how to set up a connection between development system and test

system;

For Win9x/Me, you can use either WDEB386 (free from the DDK) or SoftICE
(IIRC about $800 from NuMega).
WDEB386 is a DOS TSR which must be launched before the VMM is started. It
uses the null modem to connect to the host part. The host part can run any
terminal app - HyperTerminal is OK. WDEB386 is a command-line tool.
SoftICE is installed on a target machine only (it allows single-machine
debugging). It uses a hotkey to break the Windows execution (including the
interrupt handlers) and to pop up its “window”. It is a pseudographic UI
tool.
I personally prefer SI for Win9x debugging.

(2) if I can use different OS in development system, such as Windows 98.

Yes. I used NT4 for this.
(my own opinion is that Win9x/Me is not suitable for a professional desktop
at all - this OS is for secretary girls :slight_smile: )

Max

4

Goto http://www.microsoft.com/ddk/W2kDDK.htm

And download the Windows ME DDK with debugging support.

It has all of the necessary instructions to enable debugging with a remote system.

Rick

-----Original Message-----
From: Maxim S. Shatskih [mailto:xxxxx@storagecraft.com]
Sent: Wednesday, November 15, 2000 2:34 PM
To: NT Developers Interest List
Subject: [ntdev] Re: How to debug a Windows Me test system

(1) how to set up a connection between development system and test
system;

For Win9x/Me, you can use either WDEB386 (free from the DDK) or SoftICE
(IIRC about $800 from NuMega).
WDEB386 is a DOS TSR which must be launched before the VMM is started. It
uses the null modem to connect to the host part. The host part can run any
terminal app - HyperTerminal is OK. WDEB386 is a command-line tool.
SoftICE is installed on a target machine only (it allows single-machine
debugging). It uses a hotkey to break the Windows execution (including the
interrupt handlers) and to pop up its “window”. It is a pseudographic UI
tool.
I personally prefer SI for Win9x debugging.

(2) if I can use different OS in development system, such as Windows 98.

Yes. I used NT4 for this.
(my own opinion is that Win9x/Me is not suitable for a professional desktop
at all - this OS is for secretary girls :slight_smile: )

Max

You are currently subscribed to ntdev as: xxxxx@ontrack.com
To unsubscribe send a blank email to $subst(‘Email.Unsub’)

5

Hello Max, rick and Suyash,

Thank you all for your helpful information.

I used to use SoftICE to debug the drivers, and it is really a good tool.
But, now the driver I am debugging makes the system hang when I want to do
shut down or restart. Because all programs almost exit at that time, I can
not run the SoftICE. What I am thinking is to try to capture the whole
shut-down procedure through another PC. I wonder if it is possible to debug
the problem with WDEB386 or others.

Since I never use WDEB386 before, pls give me the detailed instruction on
how to set up the development and test system and how to debug the drivers
running in the test system.

Thanks again for your kindly help!

Regards,
Shunnian

On 11/15/00, “xxxxx@ontrack.com” wrote:

Goto http://www.microsoft.com/ddk/W2kDDK.htm

And download the Windows ME DDK with debugging support.

It has all of the necessary instructions to enable debugging with a remote system.

Rick

-----Original Message-----
From: Maxim S. Shatskih [mailto:xxxxx@storagecraft.com]
Sent: Wednesday, November 15, 2000 2:34 PM
To: NT Developers Interest List
Subject: [ntdev] Re: How to debug a Windows Me test system

> (1) how to set up a connection between development system and test
>system;

For Win9x/Me, you can use either WDEB386 (free from the DDK) or SoftICE
(IIRC about $800 from NuMega).
WDEB386 is a DOS TSR which must be launched before the VMM is started. It
uses the null modem to connect to the host part. The host part can run any
terminal app - HyperTerminal is OK. WDEB386 is a command-line tool.
SoftICE is installed on a target machine only (it allows single-machine
debugging). It uses a hotkey to break the Windows execution (including the
interrupt handlers) and to pop up its “window”. It is a pseudographic UI
tool.
I personally prefer SI for Win9x debugging.

> (2) if I can use different OS in development system, such as Windows 98.

Yes. I used NT4 for this.
(my own opinion is that Win9x/Me is not suitable for a professional desktop
at all - this OS is for secretary girls :slight_smile: )

Max

You are currently subscribed to ntdev as: xxxxx@ontrack.com
To unsubscribe send a blank email to $subst(‘Email.Unsub’)

6

Shunnian,

I understand the problem you have and you do require to have another machine
to debug. You will find all the necessary information in windows2000 DDK
under content heading “Debugger Documents”. The whole hardware and software
config has been explained. You can either use Windbg (UI) or Kdbg (console)
debugging tools. These will tell you exactly what is happening to your
driver if you set proper breakpoints and dbgprints in the checked version of
your driver.

Docs are big and can’t be sent over the email;) No attachments, remember!

Suyash Sinha

-----Original Message-----
From: xxxxx@asia.adaptec.com [mailto:xxxxx@asia.adaptec.com]
Sent: Wednesday, November 15, 2000 12:30 PM
To: NT Developers Interest List
Subject: [ntdev] Re: How to debug a Windows Me test system

Hello Max, rick and Suyash,

Thank you all for your helpful information.

I used to use SoftICE to debug the drivers, and it is really a good tool.
But, now the driver I am debugging makes the system hang when I want to do
shut down or restart. Because all programs almost exit at that time, I can
not run the SoftICE. What I am thinking is to try to capture the whole
shut-down procedure through another PC. I wonder if it is possible to debug
the problem with WDEB386 or others.

Since I never use WDEB386 before, pls give me the detailed instruction on
how to set up the development and test system and how to debug the drivers
running in the test system.

Thanks again for your kindly help!

Regards,
Shunnian

On 11/15/00, “xxxxx@ontrack.com” wrote:

Goto http://www.microsoft.com/ddk/W2kDDK.htm

And download the Windows ME DDK with debugging support.

It has all of the necessary instructions to enable debugging with a remote
system.

Rick

-----Original Message-----
From: Maxim S. Shatskih [mailto:xxxxx@storagecraft.com]
Sent: Wednesday, November 15, 2000 2:34 PM
To: NT Developers Interest List
Subject: [ntdev] Re: How to debug a Windows Me test system

> (1) how to set up a connection between development system and test
>system;

For Win9x/Me, you can use either WDEB386 (free from the DDK) or SoftICE
(IIRC about $800 from NuMega).
WDEB386 is a DOS TSR which must be launched before the VMM is started. It
uses the null modem to connect to the host part. The host part can run any
terminal app - HyperTerminal is OK. WDEB386 is a command-line tool.
SoftICE is installed on a target machine only (it allows single-machine
debugging). It uses a hotkey to break the Windows execution (including the
interrupt handlers) and to pop up its “window”. It is a pseudographic UI
tool.
I personally prefer SI for Win9x debugging.

> (2) if I can use different OS in development system, such as Windows 98.

Yes. I used NT4 for this.
(my own opinion is that Win9x/Me is not suitable for a professional
desktop
at all - this OS is for secretary girls :slight_smile: )

Max

You are currently subscribed to ntdev as: xxxxx@ontrack.com
To unsubscribe send a blank email to $subst(‘Email.Unsub’)

You are currently subscribed to ntdev as: xxxxx@microsoft.com
To unsubscribe send a blank email to $subst(‘Email.Unsub’)

7

Hi Suyash,

Thank you for your information. However, I found the following paragragh in
Win2k DDK document:

Windows Debugger (WinDbg) is a powerful Windows®-based debugging tool. It
is capable of both user-mode and kernel-mode debugging on Windows NT® and
Windows 2000.
Note: On Windows 9x systems, WinDbg can only be used to debug user-mode
drivers and applications. This debugging must be done on two machines, with
the Windows 9x system as the target and WinDbg running on Windows NT or
Windows 2000 on the host machine.

Because I use WinME in my test system and Win98 in development system, I
don’t think that I can use WinDbg or Kdbg.

Good news!!! I have found the answers in WinMe DDK, which provides the
tools, dbginst.exe and debugger.exe. After carefully reading the document,
I have sucessfully set up my system and captured the useful messages when
the system hangs.

BTW, I also want to say thanks to Max and rick. You all make me go a short
way to solve my problem.

Best Regards,
Shunnian

On 11/15/00, “Suyash Sinha ” wrote:
> Shunnian,
>
> I understand the problem you have and you do require to have another machine
> to debug. You will find all the necessary information in windows2000 DDK
> under content heading “Debugger Documents”. The whole hardware and software
> config has been explained. You can either use Windbg (UI) or Kdbg (console)
> debugging tools. These will tell you exactly what is happening to your
> driver if you set proper breakpoints and dbgprints in the checked version of
> your driver.
>
> Docs are big and can’t be sent over the email;) No attachments, remember!
>
> Suyash Sinha
>
> -----Original Message-----
> From: xxxxx@asia.adaptec.com [mailto:xxxxx@asia.adaptec.com]
> Sent: Wednesday, November 15, 2000 12:30 PM
> To: NT Developers Interest List
> Subject: [ntdev] Re: How to debug a Windows Me test system
>
>
> Hello Max, rick and Suyash,
>
> Thank you all for your helpful information.
>
> I used to use SoftICE to debug the drivers, and it is really a good tool.
> But, now the driver I am debugging makes the system hang when I want to do
> shut down or restart. Because all programs almost exit at that time, I can
> not run the SoftICE. What I am thinking is to try to capture the whole
> shut-down procedure through another PC. I wonder if it is possible to debug
> the problem with WDEB386 or others.
>
> Since I never use WDEB386 before, pls give me the detailed instruction on
> how to set up the development and test system and how to debug the drivers
> running in the test system.
>
> Thanks again for your kindly help!
>
> Regards,
> Shunnian
>
> On 11/15/00, “xxxxx@ontrack.com” wrote:
> > Goto http://www.microsoft.com/ddk/W2kDDK.htm
> >
> > And download the Windows ME DDK with debugging support.
> >
> > It has all of the necessary instructions to enable debugging with a remote
> system.
> >
> > Rick
> >
> > -----Original Message-----
> > From: Maxim S. Shatskih [mailto:xxxxx@storagecraft.com]
> > Sent: Wednesday, November 15, 2000 2:34 PM
> > To: NT Developers Interest List
> > Subject: [ntdev] Re: How to debug a Windows Me test system
> >
> >
> > > (1) how to set up a connection between development system and test
> > >system;
> >
> > For Win9x/Me, you can use either WDEB386 (free from the DDK) or SoftICE
> > (IIRC about $800 from NuMega).
> > WDEB386 is a DOS TSR which must be launched before the VMM is started. It
> > uses the null modem to connect to the host part. The host part can run any
> > terminal app - HyperTerminal is OK. WDEB386 is a command-line tool.
> > SoftICE is installed on a target machine only (it allows single-machine
> > debugging). It uses a hotkey to break the Windows execution (including the
> > interrupt handlers) and to pop up its “window”. It is a pseudographic UI
> > tool.
> > I personally prefer SI for Win9x debugging.
> >
> > > (2) if I can use different OS in development system, such as Windows 98.
> >
> > Yes. I used NT4 for this.
> > (my own opinion is that Win9x/Me is not suitable for a professional
> desktop
> > at all - this OS is for secretary girls :slight_smile: )
> >
> > Max
> >
> >
> > —
> > You are currently subscribed to ntdev as: xxxxx@ontrack.com
> > To unsubscribe send a blank email to $subst(‘Email.Unsub’)
>
> —
> You are currently subscribed to ntdev as: xxxxx@microsoft.com
> To unsubscribe send a blank email to $subst(‘Email.Unsub’)

8

All is well that ends well;)

Suyash

-----Original Message-----
From: xxxxx@asia.adaptec.com [mailto:xxxxx@asia.adaptec.com]
Sent: Wednesday, November 15, 2000 10:00 PM
To: NT Developers Interest List
Subject: [ntdev] Re: How to debug a Windows Me test system

Hi Suyash,

Thank you for your information. However, I found the following paragragh in
Win2k DDK document:

Windows Debugger (WinDbg) is a powerful Windows(r)-based debugging tool. It
is capable of both user-mode and kernel-mode debugging on Windows NT(r) and
Windows 2000.
Note: On Windows 9x systems, WinDbg can only be used to debug user-mode
drivers and applications. This debugging must be done on two machines, with
the Windows 9x system as the target and WinDbg running on Windows NT or
Windows 2000 on the host machine.

Because I use WinME in my test system and Win98 in development system, I
don’t think that I can use WinDbg or Kdbg.

Good news!!! I have found the answers in WinMe DDK, which provides the
tools, dbginst.exe and debugger.exe. After carefully reading the document,
I have sucessfully set up my system and captured the useful messages when
the system hangs.

BTW, I also want to say thanks to Max and rick. You all make me go a short
way to solve my problem.

Best Regards,
Shunnian

On 11/15/00, “Suyash Sinha ” wrote:
> Shunnian,
>
> I understand the problem you have and you do require to have another
machine
> to debug. You will find all the necessary information in windows2000 DDK
> under content heading “Debugger Documents”. The whole hardware and
software
> config has been explained. You can either use Windbg (UI) or Kdbg
(console)
> debugging tools. These will tell you exactly what is happening to your
> driver if you set proper breakpoints and dbgprints in the checked version
of
> your driver.
>
> Docs are big and can’t be sent over the email;) No attachments, remember!
>
> Suyash Sinha
>
> -----Original Message-----
> From: xxxxx@asia.adaptec.com [mailto:xxxxx@asia.adaptec.com]
> Sent: Wednesday, November 15, 2000 12:30 PM
> To: NT Developers Interest List
> Subject: [ntdev] Re: How to debug a Windows Me test system
>
>
> Hello Max, rick and Suyash,
>
> Thank you all for your helpful information.
>
> I used to use SoftICE to debug the drivers, and it is really a good tool.
> But, now the driver I am debugging makes the system hang when I want to do
> shut down or restart. Because all programs almost exit at that time, I can
> not run the SoftICE. What I am thinking is to try to capture the whole
> shut-down procedure through another PC. I wonder if it is possible to
debug
> the problem with WDEB386 or others.
>
> Since I never use WDEB386 before, pls give me the detailed instruction on
> how to set up the development and test system and how to debug the
drivers
> running in the test system.
>
> Thanks again for your kindly help!
>
> Regards,
> Shunnian
>
> On 11/15/00, “xxxxx@ontrack.com” wrote:
> > Goto http://www.microsoft.com/ddk/W2kDDK.htm
> >
> > And download the Windows ME DDK with debugging support.
> >
> > It has all of the necessary instructions to enable debugging with a
remote
> system.
> >
> > Rick
> >
> > -----Original Message-----
> > From: Maxim S. Shatskih [mailto:xxxxx@storagecraft.com]
> > Sent: Wednesday, November 15, 2000 2:34 PM
> > To: NT Developers Interest List
> > Subject: [ntdev] Re: How to debug a Windows Me test system
> >
> >
> > > (1) how to set up a connection between development system and test
> > >system;
> >
> > For Win9x/Me, you can use either WDEB386 (free from the DDK) or SoftICE
> > (IIRC about $800 from NuMega).
> > WDEB386 is a DOS TSR which must be launched before the VMM is started.
It
> > uses the null modem to connect to the host part. The host part can run
any
> > terminal app - HyperTerminal is OK. WDEB386 is a command-line tool.
> > SoftICE is installed on a target machine only (it allows single-machine
> > debugging). It uses a hotkey to break the Windows execution (including
the
> > interrupt handlers) and to pop up its “window”. It is a pseudographic UI
> > tool.
> > I personally prefer SI for Win9x debugging.
> >
> > > (2) if I can use different OS in development system, such as Windows
98.
> >
> > Yes. I used NT4 for this.
> > (my own opinion is that Win9x/Me is not suitable for a professional
> desktop
> > at all - this OS is for secretary girls :slight_smile: )
> >
> > Max
> >
> >
> > —
> > You are currently subscribed to ntdev as: xxxxx@ontrack.com
> > To unsubscribe send a blank email to $subst(‘Email.Unsub’)
>
> —
> You are currently subscribed to ntdev as: xxxxx@microsoft.com
> To unsubscribe send a blank email to $subst(‘Email.Unsub’)

—
You are currently subscribed to ntdev as: xxxxx@microsoft.com
To unsubscribe send a blank email to $subst(‘Email.Unsub’)