Windows System Software -- Consulting, Training, Development -- Unique Expertise, Guaranteed Results

Home NTDEV

Before Posting...

Please check out the Community Guidelines in the Announcements and Administration Category.

More Info on Driver Writing and Debugging


The free OSR Learning Library has more than 50 articles on a wide variety of topics about writing and debugging device drivers and Minifilters. From introductory level to advanced. All the articles have been recently reviewed and updated, and are written using the clear and definitive style you've come to expect from OSR over the years.


Check out The OSR Learning Library at: https://www.osr.com/osr-learning-library/


Problem using Windbg in Windows 2000

OSR_Community_UserOSR_Community_User Member Posts: 110,217
Hi,

I have problems using the Windbg in Windows 2000 Professional version.
I want to debug a NDIS driver which i have written on Windows 2000.

I am using two systems (windows 2000 Build 2195) both connected using
serial cable. Both on COM1.

On the target system, i have added the string
/DEBUGPORT = COM1 /BAUDRATE = 19200

On the host system Windbg is running.

When i boot the target system in the debug mode, the host system with the
windbg is just waiting on the COM1 and does not even show any symbols
loading etc.

The symbol directory is maintained to be c:\winnt\symbols

Please let me know any mistakes i am doing or are there any new things
which i need to do for debugging using the Windbg in Windows 2000

Regards,
Santhosh

Comments

  • OSR_Community_UserOSR_Community_User Member Posts: 110,217
    Hello Santhosh,

    Seems to be that I have already encountered similar problem.

    > On the target system, I have added the string
    > /DEBUGPORT = COM1 /BAUDRATE = 19200

    I don't know exactly, but I don't use spaces before and after
    the equal character in this line. But this is now main reason.

    > On the host system Windbg is running.
    >
    > When I boot the target system in the debug mode, the host system with the
    > Windbg is just waiting on the COM1 and does not even show any symbols
    > loading etc.

    Here you should press Ctrl-Break and F5 (Go). This force system to
    continue booting and you will see all DbgPrint in your Command window.

    Another possible reason is wrong version of Windbg. Newer versions
    don't work correctly. :( Thus I use version 5.00.2127.1 from Win2K RC2
    DDK.

    I hope this help a little.

    Regards,
    Shura
    -----------------------------------------------------------------------
    Alexander Kobzhev Philips Research Laboratories Eindhoven
    Building: WL 1.3.20 Prof. Holstlaan 4
    Phone: +31 40 2742788 5656 AA Eindhoven
    Fax: +31 40 2744004 The Netherlands
Sign In or Register to comment.

Howdy, Stranger!

It looks like you're new here. Sign in or register to get started.

Upcoming OSR Seminars
OSR has suspended in-person seminars due to the Covid-19 outbreak. But, don't miss your training! Attend via the internet instead!
Kernel Debugging 13-17 May 2024 Live, Online
Developing Minifilters 1-5 Apr 2024 Live, Online
Internals & Software Drivers 11-15 Mar 2024 Live, Online
Writing WDF Drivers 20-24 May 2024 Live, Online