Hi All,
Does anybody know how to setup target machine with WinDbg in Windows
Vista system (build 5231)? As usual, I tried to change “boot.ini” file to add
“/debug…”, however, it doesn’t work.
In this build, the boot loader would bring up two options during boot time. Besides the standard “Microsoft Windows”, there is another called “Legacy (pre-longhorn) Microsoft Windows Operating System”.
James
Boot.ini is now used for legacy OS’s. LH uses a new boot loader. To
change the options, you need to use bcdedit. You need to set the debug
settings and then turn debug on.
This should give you the possible parameters
Bcdedit -dbgsettings /?
IIRC, this is what I used to enable 1394 debuggin
Bcdedit -dbgsettings 1394 channel:6
After you create the settings, you need to enable debugging (yes, this
is a separate step)
bcdedit -debug on
hope that helps
d
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Zhou, James
Sent: Tuesday, October 25, 2005 6:30 PM
To: Windows System Software Devs Interest List
Subject: [ntdev] How to setup target machine with Windbg in Windows
Vista (5231) system?
Hi All,
Does anybody know how to setup target machine with WinDbg in Windows
Vista system (build 5231)? As usual, I tried to change “boot.ini” file
to add
“/debug…”, however, it doesn’t work.
In this build, the boot loader would bring up two options during boot
time. Besides the standard “Microsoft Windows”, there is another called
“Legacy (pre-longhorn) Microsoft Windows Operating System”.
James
Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256
You are currently subscribed to ntdev as: unknown lmsubst tag argument:
‘’
To unsubscribe send a blank email to xxxxx@lists.osr.com
Thanks. I’ll try out.
James
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com]On Behalf Of Doron Holan
Sent: Wednesday, October 26, 2005 12:48 PM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] How to setup target machine with Windbg in Windows
Vista (5231) system?
Boot.ini is now used for legacy OS’s. LH uses a new boot loader. To
change the options, you need to use bcdedit. You need to set the debug
settings and then turn debug on.
This should give you the possible parameters
Bcdedit -dbgsettings /?
IIRC, this is what I used to enable 1394 debuggin
Bcdedit -dbgsettings 1394 channel:6
After you create the settings, you need to enable debugging (yes, this
is a separate step)
bcdedit -debug on
hope that helps
d
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Zhou, James
Sent: Tuesday, October 25, 2005 6:30 PM
To: Windows System Software Devs Interest List
Subject: [ntdev] How to setup target machine with Windbg in Windows
Vista (5231) system?
Hi All,
Does anybody know how to setup target machine with WinDbg in Windows
Vista system (build 5231)? As usual, I tried to change “boot.ini” file
to add
“/debug…”, however, it doesn’t work.
In this build, the boot loader would bring up two options during boot
time. Besides the standard “Microsoft Windows”, there is another called
“Legacy (pre-longhorn) Microsoft Windows Operating System”.
James
Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256
You are currently subscribed to ntdev as: unknown lmsubst tag argument:
‘’
To unsubscribe send a blank email to xxxxx@lists.osr.com
Questions? First check the Kernel Driver FAQ at http://www.osronline.com/article.cfm?id=256
You are currently subscribed to ntdev as: unknown lmsubst tag argument: ‘’
To unsubscribe send a blank email to xxxxx@lists.osr.com
Doron Holan wrote:
Boot.ini is now used for legacy OS’s.
I find it extremely difficult to accept the use of the word “legacy” to
mean “every product that we are currently manufacturing and shipping”.
The only place where Windows Server 2003 could be considered “legacy” is
within Redmond, Washington. Surely it would be more accurate to say
“boot.ini is being eliminated in Vista”.
LH uses a new boot loader. To change the options, you need to use bcdedit.
This is a perfect example of a Microsoft disease: changing something
that did not need changing. What on earth was wrong with the simple,
flexible, human readable boot.ini?
You need to set the debug
settings and then turn debug on.This should give you the possible parameters
Bcdedit -dbgsettings /?IIRC, this is what I used to enable 1394 debuggin
Bcdedit -dbgsettings 1394 channel:6
That assumes that I am running in an environment where I am able to run
“bcdedit”. There have been many cases where I ran my handy-dandy
emergency bootable Linux CD, mounted an NTFS volume, and edited boot.ini
with vi to recover from some horrible situation. You have now made that
impossible, for no good, technical reason.
–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.
This is a beta product and as such I can’t really talk about it. I was
reticent to give the information about bcdedit out in a public forum in
the first place, but I wanted him to be unblocked.
Legacy - it’s just a word ;). You are assigning a value to it outside
of the boot loader functionality. Just take it as any OS which uses the
old boot loader (ntldr)
Why it was changed - there are many reasons why it changed. They are
actually quite reasonable and have thought behind them. This is not
change for the sake of change. This is change based on the evolution of
the OS, evolution of the bios and feedback from industry. I can’t give
exact details, I don’t work on the team and I don’t know what their
messaging is. You can revert to the older loader as well.
d
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Tim Roberts
Sent: Wednesday, October 26, 2005 10:10 AM
To: Windows System Software Devs Interest List
Subject: Re: [ntdev] How to setup target machine with Windbg in Windows
Vista (5231) system?
Doron Holan wrote:
Boot.ini is now used for legacy OS’s.
I find it extremely difficult to accept the use of the word “legacy” to
mean “every product that we are currently manufacturing and shipping”.
The only place where Windows Server 2003 could be considered “legacy” is
within Redmond, Washington. Surely it would be more accurate to say
“boot.ini is being eliminated in Vista”.
LH uses a new boot loader. To change the options, you need to use
bcdedit.
This is a perfect example of a Microsoft disease: changing something
that did not need changing. What on earth was wrong with the simple,
flexible, human readable boot.ini?
You need to set the debug
settings and then turn debug on.This should give you the possible parameters
Bcdedit -dbgsettings /?IIRC, this is what I used to enable 1394 debuggin
Bcdedit -dbgsettings 1394 channel:6
That assumes that I am running in an environment where I am able to run
“bcdedit”. There have been many cases where I ran my handy-dandy
emergency bootable Linux CD, mounted an NTFS volume, and edited boot.ini
with vi to recover from some horrible situation. You have now made that
impossible, for no good, technical reason.
–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.
Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256
You are currently subscribed to ntdev as: xxxxx@microsoft.com
To unsubscribe send a blank email to xxxxx@lists.osr.com
For testing purposes, the following will suite:
Maxim Shatskih, Windows DDK MVP
StorageCraft Corporation
xxxxx@storagecraft.com
http://www.storagecraft.com
----- Original Message -----
From: “Tim Roberts”
To: “Windows System Software Devs Interest List”
Sent: Wednesday, October 26, 2005 9:10 PM
Subject: Re: [ntdev] How to setup target machine with Windbg in Windows Vista
(5231) system?
> Doron Holan wrote:
>
> >Boot.ini is now used for legacy OS’s.
> >
>
> I find it extremely difficult to accept the use of the word “legacy” to
> mean “every product that we are currently manufacturing and shipping”.
> The only place where Windows Server 2003 could be considered “legacy” is
> within Redmond, Washington. Surely it would be more accurate to say
> “boot.ini is being eliminated in Vista”.
>
> >LH uses a new boot loader. To change the options, you need to use bcdedit.
> >
>
> This is a perfect example of a Microsoft disease: changing something
> that did not need changing. What on earth was wrong with the simple,
> flexible, human readable boot.ini?
>
> >You need to set the debug
> >settings and then turn debug on.
> >
> >This should give you the possible parameters
> >Bcdedit -dbgsettings /?
> >
> >IIRC, this is what I used to enable 1394 debuggin
> >Bcdedit -dbgsettings 1394 channel:6
> >
> >
>
> That assumes that I am running in an environment where I am able to run
> “bcdedit”. There have been many cases where I ran my handy-dandy
> emergency bootable Linux CD, mounted an NTFS volume, and edited boot.ini
> with vi to recover from some horrible situation. You have now made that
> impossible, for no good, technical reason.
>
> –
> Tim Roberts, xxxxx@probo.com
> Providenza & Boekelheide, Inc.
>
>
> —
> Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256
>
> You are currently subscribed to ntdev as: xxxxx@storagecraft.com
> To unsubscribe send a blank email to xxxxx@lists.osr.com
Guys, I have a side question on this line.
I have an Athlon 64-bit AMD machine, specifically, an HP Media
Center PC, with an external HP hard drive on an USB channel.
I tried to install Longhorn on that drive, well, the text-based
setup went on flawlessly, but the install bluescreened after the
first reboot. I believe the reason is that it’s not finding the
HP drive as a boot device. Looks like I need an USB drive for my
disk, but I couldn’t find it at the HP web site. Do any of you
have any experience with this, or do anyone know where to go to
find that kind of USB driver ?
Tks in advance,
Alberto.
----- Original Message -----
From: “Tim Roberts”
To: “Windows System Software Devs Interest List”
Sent: Wednesday, October 26, 2005 1:10 PM
Subject: Re: [ntdev] How to setup target machine with Windbg in
Windows Vista (5231) system?
> Doron Holan wrote:
>
>>Boot.ini is now used for legacy OS’s.
>>
>
> I find it extremely difficult to accept the use of the word
> “legacy” to mean “every product that we are currently
> manufacturing and shipping”. The only place where Windows
> Server 2003 could be considered “legacy” is within Redmond,
> Washington. Surely it would be more accurate to say “boot.ini
> is being eliminated in Vista”.
>
>>LH uses a new boot loader. To change the options, you need to
>>use bcdedit.
>>
>
> This is a perfect example of a Microsoft disease: changing
> something that did not need changing. What on earth was wrong
> with the simple, flexible, human readable boot.ini?
>
>>You need to set the debug
>>settings and then turn debug on.
>>
>>This should give you the possible parameters
>>Bcdedit -dbgsettings /?
>>
>>IIRC, this is what I used to enable 1394 debuggin
>>Bcdedit -dbgsettings 1394 channel:6
>>
>
> That assumes that I am running in an environment where I am
> able to run “bcdedit”. There have been many cases where I ran
> my handy-dandy emergency bootable Linux CD, mounted an NTFS
> volume, and edited boot.ini with vi to recover from some
> horrible situation. You have now made that impossible, for no
> good, technical reason.
>
> –
> Tim Roberts, xxxxx@probo.com
> Providenza & Boekelheide, Inc.
>
>
> —
> Questions? First check the Kernel Driver FAQ at
> http://www.osronline.com/article.cfm?id=256
>
> You are currently subscribed to ntdev as: xxxxx@ieee.org
> To unsubscribe send a blank email to
> xxxxx@lists.osr.com
IMO I would not want to use a usb disk as the boot device b/c the usb
core is not bullet proof in terms of making forward progress when there
is low memory; I also don’t know if you can hibernate using a usb disk.
Again, this is just my opinion and not the official msft stance.
d
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Alberto Moreira
Sent: Thursday, October 27, 2005 8:01 PM
To: Windows System Software Devs Interest List
Subject: Re: [ntdev] How to setup target machine with Windbg in Windows
Vista (5231) system?
Guys, I have a side question on this line.
I have an Athlon 64-bit AMD machine, specifically, an HP Media
Center PC, with an external HP hard drive on an USB channel.
I tried to install Longhorn on that drive, well, the text-based
setup went on flawlessly, but the install bluescreened after the
first reboot. I believe the reason is that it’s not finding the
HP drive as a boot device. Looks like I need an USB drive for my
disk, but I couldn’t find it at the HP web site. Do any of you
have any experience with this, or do anyone know where to go to
find that kind of USB driver ?
Tks in advance,
Alberto.
----- Original Message -----
From: “Tim Roberts”
To: “Windows System Software Devs Interest List”
Sent: Wednesday, October 26, 2005 1:10 PM
Subject: Re: [ntdev] How to setup target machine with Windbg in
Windows Vista (5231) system?
> Doron Holan wrote:
>
>>Boot.ini is now used for legacy OS’s.
>>
>
> I find it extremely difficult to accept the use of the word
> “legacy” to mean “every product that we are currently
> manufacturing and shipping”. The only place where Windows
> Server 2003 could be considered “legacy” is within Redmond,
> Washington. Surely it would be more accurate to say “boot.ini
> is being eliminated in Vista”.
>
>>LH uses a new boot loader. To change the options, you need to
>>use bcdedit.
>>
>
> This is a perfect example of a Microsoft disease: changing
> something that did not need changing. What on earth was wrong
> with the simple, flexible, human readable boot.ini?
>
>>You need to set the debug
>>settings and then turn debug on.
>>
>>This should give you the possible parameters
>>Bcdedit -dbgsettings /?
>>
>>IIRC, this is what I used to enable 1394 debuggin
>>Bcdedit -dbgsettings 1394 channel:6
>>
>
> That assumes that I am running in an environment where I am
> able to run “bcdedit”. There have been many cases where I ran
> my handy-dandy emergency bootable Linux CD, mounted an NTFS
> volume, and edited boot.ini with vi to recover from some
> horrible situation. You have now made that impossible, for no
> good, technical reason.
>
> –
> Tim Roberts, xxxxx@probo.com
> Providenza & Boekelheide, Inc.
>
>
> —
> Questions? First check the Kernel Driver FAQ at
> http://www.osronline.com/article.cfm?id=256
>
> You are currently subscribed to ntdev as: xxxxx@ieee.org
> To unsubscribe send a blank email to
> xxxxx@lists.osr.com
—
Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256
You are currently subscribed to ntdev as: xxxxx@microsoft.com
To unsubscribe send a blank email to xxxxx@lists.osr.com
Doron Holan wrote:
IMO I would not want to use a usb disk as the boot device b/c the usb
core is not bullet proof in terms of making forward progress when there
is low memory; …
How can memory be low at boot time? 
–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.
> How can memory be low at boot time?
How about some driver decided to allocate many megabytes of pool or common
memory. Just do a search on old messages in this list for something like
“how do I allocate a 1 gigabyte buffer for my hardware”.
> How can memory be low at boot time?
Having just fixed a bug in one of out proprietary boot-time drivers, where
it crashed the system because it didn’t check for failure on mapping a 400
byte user buffer into kernel space, I can state that it is in fact fairly
easy to run out of kernel addressible memory at boot time. All you need is
a big enough system.
Loren
I recall Spring 2003 was an interesting time. Windows Server 2003 despite
not yet being released was referred to as “downlevel” and provision of
features for Windows XP was referred to as “backport”. I think when you are
talking with the developers on the leading edge of products which take years
to deliver, it seems inevitable that these developers will spend a lot of
time working on the “version after next”, and these sorts of situations will
arise.
“Tim Roberts” wrote in message news:xxxxx@ntdev…
> Doron Holan wrote:
>
>>Boot.ini is now used for legacy OS’s.
>>
>
> I find it extremely difficult to accept the use of the word “legacy” to
> mean “every product that we are currently manufacturing and shipping”.
> The only place where Windows Server 2003 could be considered “legacy” is
> within Redmond, Washington. Surely it would be more accurate to say
> “boot.ini is being eliminated in Vista”.
>
>>LH uses a new boot loader. To change the options, you need to use
>>bcdedit.
>>
>
> This is a perfect example of a Microsoft disease: changing something that
> did not need changing. What on earth was wrong with the simple, flexible,
> human readable boot.ini?
>
>>You need to set the debug
>>settings and then turn debug on.
>>
>>This should give you the possible parameters
>>Bcdedit -dbgsettings /?
>>
>>IIRC, this is what I used to enable 1394 debuggin
>>Bcdedit -dbgsettings 1394 channel:6
>>
>
> That assumes that I am running in an environment where I am able to run
> “bcdedit”. There have been many cases where I ran my handy-dandy
> emergency bootable Linux CD, mounted an NTFS volume, and edited boot.ini
> with vi to recover from some horrible situation. You have now made that
> impossible, for no good, technical reason.
>
> –
> Tim Roberts, xxxxx@probo.com
> Providenza & Boekelheide, Inc.
>
>
Lyndon J Clarke wrote:
I recall Spring 2003 was an interesting time. Windows Server 2003 despite
not yet being released was referred to as “downlevel” and provision of
features for Windows XP was referred to as “backport”. I think when you are
talking with the developers on the leading edge of products which take years
to deliver, it seems inevitable that these developers will spend a lot of
time working on the “version after next”, and these sorts of situations will
arise.
Yes, exactly, and I’m actually quite aware of this. It won’t stop me
from calling it out when I see it.
The sessions at the MVP Summit were a perfect example of this. My
clients are all demanding two or more years in the past (since that’s
where THEIR customers are), I’m working in today trying to do that, and
the developers at Microsoft are all living two years in the future.
It’s a startling disconnect.
–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.
I think everyone in this space has the same tale. I dont have so much
experience here perhaps but I think the developers at Microsoft are quite
aware of the situation and are not unresponsive. For example, the backport
of filter manager to Windows 2000, this was something that was not in the
pipeline in Spring 2003, there was a clear message from the ISV space, and
we have the backport. I do sympathise (and sometimes suffer) when the
disconnect leads to surprises. Perhaps the particular point in the OP does
fall into this class.
“Tim Roberts” wrote in message news:xxxxx@ntdev…
> Lyndon J Clarke wrote:
>
>>I recall Spring 2003 was an interesting time. Windows Server 2003 despite
>>not yet being released was referred to as “downlevel” and provision of
>>features for Windows XP was referred to as “backport”. I think when you
>>are talking with the developers on the leading edge of products which take
>>years to deliver, it seems inevitable that these developers will spend a
>>lot of time working on the “version after next”, and these sorts of
>>situations will arise.
>>
>
> Yes, exactly, and I’m actually quite aware of this. It won’t stop me from
> calling it out when I see it.
>
> The sessions at the MVP Summit were a perfect example of this. My clients
> are all demanding two or more years in the past (since that’s where THEIR
> customers are), I’m working in today trying to do that, and the developers
> at Microsoft are all living two years in the future. It’s a startling
> disconnect.
>
> –
> Tim Roberts, xxxxx@probo.com
> Providenza & Boekelheide, Inc.
>
>
Hi,
I need to debug the kernel mode driver in Vista. I am trying to
debug the driver by connecting two machines by null modem cable. I want
to know how to setup the port and baud rate for debugging.
I tried bcdedit -dbgsettings /?, but not getting any help message.
Abhiman.
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Doron Holan
Sent: Wednesday, October 26, 2005 10:18 AM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] How to setup target machine with Windbg in Windows
Vista (5231) system?
Boot.ini is now used for legacy OS’s. LH uses a new boot loader. To
change the options, you need to use bcdedit. You need to set the debug
settings and then turn debug on.
This should give you the possible parameters
Bcdedit -dbgsettings /?
IIRC, this is what I used to enable 1394 debuggin
Bcdedit -dbgsettings 1394 channel:6
After you create the settings, you need to enable debugging (yes, this
is a separate step) bcdedit -debug on
hope that helps
d
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Zhou, James
Sent: Tuesday, October 25, 2005 6:30 PM
To: Windows System Software Devs Interest List
Subject: [ntdev] How to setup target machine with Windbg in Windows
Vista (5231) system?
Hi All,
Does anybody know how to setup target machine with WinDbg in Windows
Vista system (build 5231)? As usual, I tried to change “boot.ini” file
to add “/debug…”, however, it doesn’t work.
In this build, the boot loader would bring up two options during boot
time. Besides the standard “Microsoft Windows”, there is another called
“Legacy (pre-longhorn) Microsoft Windows Operating System”.
James
Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256
You are currently subscribed to ntdev as: unknown lmsubst tag argument:
‘’ To unsubscribe send a blank email to xxxxx@lists.osr.com
Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256
You are currently subscribed to ntdev as: unknown lmsubst tag argument:
‘’ To unsubscribe send a blank email to xxxxx@lists.osr.com
Try “bcdedit -? Dbgsettings”.
You need to do two things:
1 - use bcdedit -dbgsettings serial debugport:N baudrate:M (replace N
and M as appropriate)
2 - run bcdedit -debug on
This will set the debugger settings (globally) and then enable debugging
for the current (booted) entry.
If you’re trying to do this from a safe build you’ll need to provide the
ID for the entry you want to enter the debugger. Bcdedit -? Debug
should tell you how to do that.
-p
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of
xxxxx@wipro.com
Sent: Wednesday, November 09, 2005 5:02 AM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] How to setup target machine with Windbg in Windows
Vista (5231) system?
Hi,
I need to debug the kernel mode driver in Vista. I am trying to
debug the driver by connecting two machines by null modem cable. I want
to know how to setup the port and baud rate for debugging.
I tried bcdedit -dbgsettings /?, but not getting any help message.
Abhiman.
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Doron Holan
Sent: Wednesday, October 26, 2005 10:18 AM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] How to setup target machine with Windbg in Windows
Vista (5231) system?
Boot.ini is now used for legacy OS’s. LH uses a new boot loader. To
change the options, you need to use bcdedit. You need to set the debug
settings and then turn debug on.
This should give you the possible parameters Bcdedit -dbgsettings /?
IIRC, this is what I used to enable 1394 debuggin Bcdedit -dbgsettings
1394 channel:6
After you create the settings, you need to enable debugging (yes, this
is a separate step) bcdedit -debug on
hope that helps
d
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Zhou, James
Sent: Tuesday, October 25, 2005 6:30 PM
To: Windows System Software Devs Interest List
Subject: [ntdev] How to setup target machine with Windbg in Windows
Vista (5231) system?
Hi All,
Does anybody know how to setup target machine with WinDbg in Windows
Vista system (build 5231)? As usual, I tried to change “boot.ini” file
to add “/debug…”, however, it doesn’t work.
In this build, the boot loader would bring up two options during boot
time. Besides the standard “Microsoft Windows”, there is another called
“Legacy (pre-longhorn) Microsoft Windows Operating System”.
James
Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256
You are currently subscribed to ntdev as: unknown lmsubst tag argument:
‘’ To unsubscribe send a blank email to xxxxx@lists.osr.com
Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256
You are currently subscribed to ntdev as: unknown lmsubst tag argument:
‘’ To unsubscribe send a blank email to xxxxx@lists.osr.com
Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256
You are currently subscribed to ntdev as: unknown lmsubst tag argument:
‘’
To unsubscribe send a blank email to xxxxx@lists.osr.com
Have you tryed with Hyperterminal…
Bits—9600
databit -8
pariti -none
stop-1
Flowcontrol–Non
|
Regards;
Neeraj Kumar Jha
98195-37916
|
|
|
From:
Reply-To: “Windows System Software Devs Interest List”
To: “Windows System Software Devs Interest List”
Subject: RE: [ntdev] How to setup target machine with Windbg in Windows Vista (5231) system?
Date: Wed, 9 Nov 2005 18:31:41 +0530
>Hi,
> I need to debug the kernel mode driver in Vista. I am trying to
>debug the driver by connecting two machines by null modem cable. I want
>to know how to setup the port and baud rate for debugging.
>I tried bcdedit -dbgsettings /?, but not getting any help message.
>
>Abhiman.
>
>-----Original Message-----
>From: xxxxx@lists.osr.com
>[mailto:xxxxx@lists.osr.com] On Behalf Of Doron Holan
>Sent: Wednesday,
October 26, 2005 10:18 AM
>To: Windows System Software Devs Interest List
>Subject: RE: [ntdev] How to setup target machine with Windbg in Windows
>Vista (5231) system?
>
>
>Boot.ini is now used for legacy OS’s. LH uses a new boot loader. To
>change the options, you need to use bcdedit. You need to set the debug
>settings and then turn debug on.
>
>This should give you the possible parameters
>Bcdedit -dbgsettings /?
>
>IIRC, this is what I used to enable 1394 debuggin
>Bcdedit -dbgsettings 1394 channel:6
>
>After you create the settings, you need to enable debugging (yes, this
>is a separate step) bcdedit -debug on
>
>hope that helps
>d
>
>
>-----Original Message-----
>From:
xxxxx@lists.osr.com
>[mailto:xxxxx@lists.osr.com] On Behalf Of Zhou, James
>Sent: Tuesday, October 25, 2005 6:30 PM
>To: Windows System Software Devs Interest List
>Subject: [ntdev] How to setup target machine with Windbg in Windows
>Vista (5231) system?
>
>Hi All,
>
>Does anybody know how to setup target machine with WinDbg in Windows
>Vista system (build 5231)? As usual, I tried to change “boot.ini” file
>to add “/debug…”, however, it doesn’t work.
>
>In this build, the boot loader would bring up two options during boot
>time. Besides the standard “Microsoft Windows”, there is another called
>“Legacy (pre-longhorn) Microsoft Windows Operating System”.
>
>James
>
>
>
>
>—
>Questions? First check the Kernel Driver FAQ
at
>http://www.osronline.com/article.cfm?id=256
>
>You are currently subscribed to ntdev as: unknown lmsubst tag argument:
>‘’ To unsubscribe send a blank email to xxxxx@lists.osr.com
>
>—
>Questions? First check the Kernel Driver FAQ at
>http://www.osronline.com/article.cfm?id=256
>
>You are currently subscribed to ntdev as: unknown lmsubst tag argument:
>‘’ To unsubscribe send a blank email to xxxxx@lists.osr.com
>
>
>—
>Questions? First check the Kernel Driver FAQ at http://www.osronline.com/article.cfm?id=256
>
>You are currently subscribed to ntdev as: unknown lmsubst tag argument: ‘’
>To unsubscribe send a blank email to xxxxx@lists.osr.com
Jha ji, is that you?? From B’lore Park Controls??
----- Original Message -----
From: neeraj jha
To: Windows System Software Devs Interest List
Sent: Friday, November 11, 2005 2:11 AM
Subject: RE: [ntdev] How to setup target machine with Windbg in Windows Vista (5231) system?
Have you tryed with Hyperterminal…
Bits—9600
databit -8
pariti -none
stop-1
Flowcontrol–Non
Regards;
Neeraj Kumar Jha
98195-37916
From:
Reply-To: “Windows System Software Devs Interest List”
To: “Windows System Software Devs Interest List”
Subject: RE: [ntdev] How to setup target machine with Windbg in Windows Vista (5231) system?
Date: Wed, 9 Nov 2005 18:31:41 +0530
>Hi,
> I need to debug the kernel mode driver in Vista. I am trying to
>debug the driver by connecting two machines by null modem cable. I want
>to know how to setup the port and baud rate for debugging.
>I tried bcdedit -dbgsettings /?, but not getting any help message.
>
>Abhiman.
>
>-----Original Message-----
>From: xxxxx@lists.osr.com
>[mailto:xxxxx@lists.osr.com] On Behalf Of Doron Holan
>Sent: Wednesday, October 26, 2005 10:18 AM
>To: Windows System Software Devs Interest List
>Subject: RE: [ntdev] How to setup target machine with Windbg in Windows
>Vista (5231) system?
>
>
>Boot.ini is now used for legacy OS’s. LH uses a new boot loader. To
>change the options, you need to use bcdedit. You need to set the debug
>settings and then turn debug on.
>
>This should give you the possible parameters
>Bcdedit -dbgsettings /?
>
>IIRC, this is what I used to enable 1394 debuggin
>Bcdedit -dbgsettings 1394 channel:6
>
>After you create the settings, you need to enable debugging (yes, this
>is a separate step) bcdedit -debug on
>
>hope that helps
>d
>
>
>-----Original Message-----
>From: xxxxx@lists.osr.com
>[mailto:xxxxx@lists.osr.com] On Behalf Of Zhou, James
>Sent: Tuesday, October 25, 2005 6:30 PM
>To: Windows System Software Devs Interest List
>Subject: [ntdev] How to setup target machine with Windbg in Windows
>Vista (5231) system?
>
>Hi All,
>
>Does anybody know how to setup target machine with WinDbg in Windows
>Vista system (build 5231)? As usual, I tried to change “boot.ini” file
>to add “/debug…”, however, it doesn’t work.
>
>In this build, the boot loader would bring up two options during boot
>time. Besides the standard “Microsoft Windows”, there is another called
>“Legacy (pre-longhorn) Microsoft Windows Operating System”.
>
>James
>
>
>
>
>—
>Questions? First check the Kernel Driver FAQ at
>http://www.osronline.com/article.cfm?id=256
>
>You are currently subscribed to ntdev as: unknown lmsubst tag argument:
>‘’ To unsubscribe send a blank email to xxxxx@lists.osr.com
>
>—
>Questions? First check the Kernel Driver FAQ at
>http://www.osronline.com/article.cfm?id=256
>
>You are currently subscribed to ntdev as: unknown lmsubst tag argument:
>‘’ To unsubscribe send a blank email to xxxxx@lists.osr.com
>
>
>—
>Questions? First check the Kernel Driver FAQ at http://www.osronline.com/article.cfm?id=256
>
>You are currently subscribed to ntdev as: unknown lmsubst tag argument: ‘’
>To unsubscribe send a blank email to xxxxx@lists.osr.com
—
Questions? First check the Kernel Driver FAQ at http://www.osronline.com/article.cfm?id=256
You are currently subscribed to ntdev as: xxxxx@calsoft.co.in
To unsubscribe send a blank email to xxxxx@lists.osr.com
Yes…
|
Regards;
Neeraj Kumar Jha
98195-37916
|
|
|
From: “Arif”
Reply-To: “Windows System Software Devs Interest List”
To: “Windows System Software Devs Interest List”
Subject: Re: [ntdev] How to setup target machine with Windbg in Windows Vista (5231) system?
Date: Fri, 11 Nov 2005 09:42:16 +0530
Jha ji, is that you?? From B’lore Park Controls??
----- Original Message -----
From: neeraj jha
Sent: Friday, November 11, 2005 2:11 AM
Subject: RE: [ntdev] How to setup target machine with Windbg in Windows Vista (5231) system?
Have you tryed with Hyperterminal…
Bits—9600
databit -8
pariti -none
stop-1
Flowcontrol–Non
Regards;
Neeraj Kumar Jha
From: <xxxxx@wipro.com>
Reply-To: "Windows System Software Devs Interest List" <xxxxx@lists.osr.com>
To: "Windows System Software Devs Interest List" <xxxxx@lists.osr.com>
Subject: RE: [ntdev] How to setup target machine with Windbg in Windows Vista (5231) system?
Date: Wed, 9 Nov 2005 18:31:41 +0530
>Hi,
> I need to debug the kernel mode driver in Vista. I am trying to
>debug the driver by connecting two machines by null modem cable. I want
>to know how to setup the port and baud rate for debugging.
>I tried bcdedit -dbgsettings /?, but not getting any help message.
>
>Abhiman.
>
>-----Original Message-----
>From:
xxxxx@lists.osr.com
>[mailto:xxxxx@lists.osr.com] On Behalf Of Doron Holan
>Sent: Wednesday, October 26, 2005 10:18 AM
>To: Windows System Software Devs Interest List
>Subject: RE: [ntdev] How to setup target machine with Windbg in Windows
>Vista (5231) system?
>
>
>Boot.ini is now used for legacy OS's. LH uses a new boot loader. To
>change the options, you need to use bcdedit. You need to set the debug
>settings and then turn debug on.
>
>This should give you the possible parameters
>Bcdedit -dbgsettings /?
>
>IIRC, this is what I used to enable 1394 debuggin
>Bcdedit -dbgsettings 1394 channel:6
>
>After you create the settings, you need to enable debugging (yes, this
>is a separate step) bcdedit -debug on
>
>hope that
helps
>d
>
>
>-----Original Message-----
>From: xxxxx@lists.osr.com
>[mailto:xxxxx@lists.osr.com] On Behalf Of Zhou, James
>Sent: Tuesday, October 25, 2005 6:30 PM
>To: Windows System Software Devs Interest List
>Subject: [ntdev] How to setup target machine with Windbg in Windows
>Vista (5231) system?
>
>Hi All,
>
>Does anybody know how to setup target machine with WinDbg in Windows
>Vista system (build 5231)? As usual, I tried to change "boot.ini" file
>to add "/debug...", however, it doesn't work.
>
>In this build, the boot loader would bring up two options during boot
>time. Besides the standard "Microsoft Windows", there is another called
>"Legacy (pre-longhorn) Microsoft Windows Operating
System".
>
>James
>
>
>
>
>---
>Questions? First check the Kernel Driver FAQ at
>http://www.osronline.com/article.cfm?id=256
>
>You are currently subscribed to ntdev as: unknown lmsubst tag argument:
>'' To unsubscribe send a blank email to xxxxx@lists.osr.com
>
>---
>Questions? First check the Kernel Driver FAQ at
>http://www.osronline.com/article.cfm?id=256
>
>You are currently subscribed to ntdev as: unknown lmsubst tag argument:
>'' To unsubscribe send a blank email to xxxxx@lists.osr.com
>
>
>---
>Questions? First check the Kernel Driver FAQ at http://www.osronline.com/article.cfm?id=256
>
>You are currently subscribed to ntdev as: unknown lmsubst tag argument: ''
>To unsubscribe send a blank email to
xxxxx@lists.osr.com
---
Questions? First check the Kernel Driver FAQ at http://www.osronline.com/article.cfm?id=256
You are currently subscribed to ntdev as: xxxxx@calsoft.co.in
To unsubscribe send a blank email to xxxxx@lists.osr.com
---
Questions? First check the Kernel Driver FAQ at http://www.osronline.com/article.cfm?id=256
You are currently subscribed to ntdev as: unknown lmsubst tag argument: ''
To unsubscribe send a blank email to xxxxx@lists.osr.com
Abhiman,
On Vista, the /dbgsettings parameter sets the port and baudrate for
debugging for all Vista boot entries. To enable debugging on a particular
boot entry, you need to use the /debug parameter.
You might not even need to change the default debug settings. The default
global debugging settings for Vista are as follows:
Debugger type: Serial
Debugger port number: 1
Debugger baudrate: 115200
If you need to change the global debug settings, use the following command:
bcdedit /dbgsettings serial baudrate:57600 dbgport:2
-or-
bcdedit /dbgsettings 1394 channel:23
Then, to enable debugging on a particular boot entry, use the following
command:
bcdedit /debug {ID}
where {ID} is the identifier of the boot entry.
To enable debugging on the boot entry that you used to boot the system most
recently, use the following command:
bcdedit /debug {current}
(Be sure to include the braces {} in the command. They are required.)
To find the identifier for each boot entries on your system, use the
following command:
bcdedit /enum osloader
All of this should be explained in detail in the Help docs for Vista RTM.
There will also be a special section of help in the WDK docs for topics of
interest to driver devs and testers.
June Blender (MSFT)
WDK (DDK) Tool Docs
xxxxx@microsoft.com
wrote in message news:xxxxx@ntdev…
Hi,
I need to debug the kernel mode driver in Vista. I am trying to
debug the driver by connecting two machines by null modem cable. I want
to know how to setup the port and baud rate for debugging.
I tried bcdedit -dbgsettings /?, but not getting any help message.
Abhiman.
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Doron Holan
Sent: Wednesday, October 26, 2005 10:18 AM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] How to setup target machine with Windbg in Windows
Vista (5231) system?
Boot.ini is now used for legacy OS’s. LH uses a new boot loader. To
change the options, you need to use bcdedit. You need to set the debug
settings and then turn debug on.
This should give you the possible parameters
Bcdedit -dbgsettings /?
IIRC, this is what I used to enable 1394 debuggin
Bcdedit -dbgsettings 1394 channel:6
After you create the settings, you need to enable debugging (yes, this
is a separate step) bcdedit -debug on
hope that helps
d
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Zhou, James
Sent: Tuesday, October 25, 2005 6:30 PM
To: Windows System Software Devs Interest List
Subject: [ntdev] How to setup target machine with Windbg in Windows
Vista (5231) system?
Hi All,
Does anybody know how to setup target machine with WinDbg in Windows
Vista system (build 5231)? As usual, I tried to change “boot.ini” file
to add “/debug…”, however, it doesn’t work.
In this build, the boot loader would bring up two options during boot
time. Besides the standard “Microsoft Windows”, there is another called
“Legacy (pre-longhorn) Microsoft Windows Operating System”.
James
—
Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256
You are currently subscribed to ntdev as: unknown lmsubst tag argument:
‘’ To unsubscribe send a blank email to xxxxx@lists.osr.com
—
Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256
You are currently subscribed to ntdev as: unknown lmsubst tag argument:
‘’ To unsubscribe send a blank email to xxxxx@lists.osr.com