Discussion:
WinDBG, doesn't support kernel debugging?
(too old to reply)
Harry Potter
2004-09-26 21:06:55 UTC
Permalink
Hi guys,
I'm trying to debug the sample IM drivers Passthru from Microsoft
samples.... I assume this is a kernel mode driver and therefore trying to
use the kernel mode debugging of the windbg on same local machine... but I
get the following error... what am I doing wrong???? Please note that I'm
running on windows 2000....

Microsoft (R) Windows Debugger Version 6.3.0017.0
Copyright (c) Microsoft Corporation. All rights reserved.

The system does not support local kernel debugging.
Local kernel debugging requires Windows XP, Administrative
privileges, and is not supported by WOW64.
Debuggee initialization failed, HRESULT 0x80004001
"Not implemented"

doesn't this feature supported on win 2000 pro??? what should I do then???
I have the administrative privilege on my own pc.
thank you...
nospam@cristalink.com
2004-09-26 21:38:18 UTC
Permalink
You should use a second computer to debug a remote machine via a COM port or
1394 . The abilities of the local debugging are very limited anyway.
Post by Harry Potter
Hi guys,
I'm trying to debug the sample IM drivers Passthru from Microsoft
samples.... I assume this is a kernel mode driver and therefore trying to
use the kernel mode debugging of the windbg on same local machine... but I
get the following error... what am I doing wrong???? Please note that I'm
running on windows 2000....
Microsoft (R) Windows Debugger Version 6.3.0017.0
Copyright (c) Microsoft Corporation. All rights reserved.
The system does not support local kernel debugging.
Local kernel debugging requires Windows XP, Administrative
privileges, and is not supported by WOW64.
Debuggee initialization failed, HRESULT 0x80004001
"Not implemented"
doesn't this feature supported on win 2000 pro??? what should I do then???
I have the administrative privilege on my own pc.
thank you...
Pat [MSFT]
2004-09-27 05:00:52 UTC
Permalink
The error message is stating that WinXP is the minimum for doing 'live'
local kernel debugging, not that WinDBG can't do it. I doubt that 'live' is
what you want to do anyway since it is fairly limited (e.g. you can't set a
break point). You would get a much better learning experince debugging
across 2 machines (so you can set break points, follow program flow, etc.).


pat
Post by Harry Potter
Hi guys,
I'm trying to debug the sample IM drivers Passthru from Microsoft
samples.... I assume this is a kernel mode driver and therefore trying to
use the kernel mode debugging of the windbg on same local machine... but I
get the following error... what am I doing wrong???? Please note that I'm
running on windows 2000....
Microsoft (R) Windows Debugger Version 6.3.0017.0
Copyright (c) Microsoft Corporation. All rights reserved.
The system does not support local kernel debugging.
Local kernel debugging requires Windows XP, Administrative
privileges, and is not supported by WOW64.
Debuggee initialization failed, HRESULT 0x80004001
"Not implemented"
doesn't this feature supported on win 2000 pro??? what should I do then???
I have the administrative privilege on my own pc.
thank you...
Hans De Smaele
2004-09-27 09:35:09 UTC
Permalink
You can download from the SysInternals website (http://www.sysinternals.com)
a tool, called LiveKd. This tool allows you to do local debugging on a W2K
computer. However, note that you're actually working on a local dump at that
moment, but it's a good solution to learn debugging with.
As the others said already, you need 2 computers to do live kernel
debugging. See the outstanding WinDbg doc for more information on this.

H.
Post by Pat [MSFT]
The error message is stating that WinXP is the minimum for doing 'live'
local kernel debugging, not that WinDBG can't do it. I doubt that 'live' is
what you want to do anyway since it is fairly limited (e.g. you can't set a
break point). You would get a much better learning experince debugging
across 2 machines (so you can set break points, follow program flow, etc.).
pat
Post by Harry Potter
Hi guys,
I'm trying to debug the sample IM drivers Passthru from Microsoft
samples.... I assume this is a kernel mode driver and therefore trying to
use the kernel mode debugging of the windbg on same local machine... but I
get the following error... what am I doing wrong???? Please note that I'm
running on windows 2000....
Microsoft (R) Windows Debugger Version 6.3.0017.0
Copyright (c) Microsoft Corporation. All rights reserved.
The system does not support local kernel debugging.
Local kernel debugging requires Windows XP, Administrative
privileges, and is not supported by WOW64.
Debuggee initialization failed, HRESULT 0x80004001
"Not implemented"
doesn't this feature supported on win 2000 pro??? what should I do then???
I have the administrative privilege on my own pc.
thank you...
Harry Potter
2004-09-27 16:03:02 UTC
Permalink
thank you all for your feedbacks
Post by Hans De Smaele
You can download from the SysInternals website
(http://www.sysinternals.com)
Post by Hans De Smaele
a tool, called LiveKd. This tool allows you to do local debugging on a W2K
computer. However, note that you're actually working on a local dump at that
moment, but it's a good solution to learn debugging with.
As the others said already, you need 2 computers to do live kernel
debugging. See the outstanding WinDbg doc for more information on this.
H.
Post by Pat [MSFT]
The error message is stating that WinXP is the minimum for doing 'live'
local kernel debugging, not that WinDBG can't do it. I doubt that 'live' is
what you want to do anyway since it is fairly limited (e.g. you can't set a
break point). You would get a much better learning experince debugging
across 2 machines (so you can set break points, follow program flow, etc.).
pat
Post by Harry Potter
Hi guys,
I'm trying to debug the sample IM drivers Passthru from Microsoft
samples.... I assume this is a kernel mode driver and therefore trying to
use the kernel mode debugging of the windbg on same local machine... but I
get the following error... what am I doing wrong???? Please note that I'm
running on windows 2000....
Microsoft (R) Windows Debugger Version 6.3.0017.0
Copyright (c) Microsoft Corporation. All rights reserved.
The system does not support local kernel debugging.
Local kernel debugging requires Windows XP, Administrative
privileges, and is not supported by WOW64.
Debuggee initialization failed, HRESULT 0x80004001
"Not implemented"
doesn't this feature supported on win 2000 pro??? what should I do the
n???
Post by Hans De Smaele
Post by Pat [MSFT]
Post by Harry Potter
I have the administrative privilege on my own pc.
thank you...
Sivaller
2004-09-29 07:37:17 UTC
Permalink
Try program Dbgview in the site sysinternal
Post by Harry Potter
thank you all for your feedbacks
Post by Hans De Smaele
You can download from the SysInternals website
(http://www.sysinternals.com)
Post by Hans De Smaele
a tool, called LiveKd. This tool allows you to do local debugging on a W2K
computer. However, note that you're actually working on a local dump at
that
Post by Hans De Smaele
moment, but it's a good solution to learn debugging with.
As the others said already, you need 2 computers to do live kernel
debugging. See the outstanding WinDbg doc for more information on this.
H.
Post by Pat [MSFT]
The error message is stating that WinXP is the minimum for doing 'live'
local kernel debugging, not that WinDBG can't do it. I doubt that
'live' is
Post by Hans De Smaele
Post by Pat [MSFT]
what you want to do anyway since it is fairly limited (e.g. you can't
set a
Post by Hans De Smaele
Post by Pat [MSFT]
break point). You would get a much better learning experince debugging
across 2 machines (so you can set break points, follow program flow,
etc.).
Post by Hans De Smaele
Post by Pat [MSFT]
pat
Post by Harry Potter
Hi guys,
I'm trying to debug the sample IM drivers Passthru from Microsoft
samples.... I assume this is a kernel mode driver and therefore
trying
Post by Harry Potter
to
Post by Hans De Smaele
Post by Pat [MSFT]
Post by Harry Potter
use the kernel mode debugging of the windbg on same local machine...
but I
Post by Hans De Smaele
Post by Pat [MSFT]
Post by Harry Potter
get the following error... what am I doing wrong???? Please note
that
Post by Harry Potter
I'm
Post by Hans De Smaele
Post by Pat [MSFT]
Post by Harry Potter
running on windows 2000....
Microsoft (R) Windows Debugger Version 6.3.0017.0
Copyright (c) Microsoft Corporation. All rights reserved.
The system does not support local kernel debugging.
Local kernel debugging requires Windows XP, Administrative
privileges, and is not supported by WOW64.
Debuggee initialization failed, HRESULT 0x80004001
"Not implemented"
doesn't this feature supported on win 2000 pro??? what should I do the
n???
Post by Hans De Smaele
Post by Pat [MSFT]
Post by Harry Potter
I have the administrative privilege on my own pc.
thank you...
Harry Potter
2004-09-30 19:17:36 UTC
Permalink
OOOOK... I see...
thank you both.
Post by Sivaller
Try program Dbgview in the site sysinternal
Post by Harry Potter
thank you all for your feedbacks
Post by Hans De Smaele
You can download from the SysInternals website
(http://www.sysinternals.com)
Post by Hans De Smaele
a tool, called LiveKd. This tool allows you to do local debugging on a
W2K
Post by Harry Potter
Post by Hans De Smaele
computer. However, note that you're actually working on a local dump at
that
Post by Hans De Smaele
moment, but it's a good solution to learn debugging with.
As the others said already, you need 2 computers to do live kernel
debugging. See the outstanding WinDbg doc for more information on this.
H.
Post by Pat [MSFT]
The error message is stating that WinXP is the minimum for doing
'live'
Post by Harry Potter
Post by Hans De Smaele
Post by Pat [MSFT]
local kernel debugging, not that WinDBG can't do it. I doubt that
'live' is
Post by Hans De Smaele
Post by Pat [MSFT]
what you want to do anyway since it is fairly limited (e.g. you can't
set a
Post by Hans De Smaele
Post by Pat [MSFT]
break point). You would get a much better learning experince
debugging
Post by Harry Potter
Post by Hans De Smaele
Post by Pat [MSFT]
across 2 machines (so you can set break points, follow program flow,
etc.).
Post by Hans De Smaele
Post by Pat [MSFT]
pat
Post by Harry Potter
Hi guys,
I'm trying to debug the sample IM drivers Passthru from Microsoft
samples.... I assume this is a kernel mode driver and therefore
trying
Post by Harry Potter
to
Post by Hans De Smaele
Post by Pat [MSFT]
Post by Harry Potter
use the kernel mode debugging of the windbg on same local machine...
but I
Post by Hans De Smaele
Post by Pat [MSFT]
Post by Harry Potter
get the following error... what am I doing wrong???? Please note
that
Post by Harry Potter
I'm
Post by Hans De Smaele
Post by Pat [MSFT]
Post by Harry Potter
running on windows 2000....
Microsoft (R) Windows Debugger Version 6.3.0017.0
Copyright (c) Microsoft Corporation. All rights reserved.
The system does not support local kernel debugging.
Local kernel debugging requires Windows XP, Administrative
privileges, and is not supported by WOW64.
Debuggee initialization failed, HRESULT 0x80004001
"Not implemented"
doesn't this feature supported on win 2000 pro??? what should I do
the
Post by Harry Potter
n???
Post by Hans De Smaele
Post by Pat [MSFT]
Post by Harry Potter
I have the administrative privilege on my own pc.
thank you...
Vipin
2004-10-01 08:56:52 UTC
Permalink
what I don't understand is why microsoft can't come up with something like
softice? Softice is damn costly for developers to purchase.And once we are
done with the development at office or on a particular project for which we
have softice license, we can't use for any other purpose.I used to work on
project for which they had softice license,but once I moved out of the
project, I can't use softice. Why doesn't MS come with a free debugger of
the same style?
Post by Pat [MSFT]
The error message is stating that WinXP is the minimum for doing 'live'
local kernel debugging, not that WinDBG can't do it. I doubt that 'live' is
what you want to do anyway since it is fairly limited (e.g. you can't set a
break point). You would get a much better learning experince debugging
across 2 machines (so you can set break points, follow program flow, etc.).
pat
Post by Harry Potter
Hi guys,
I'm trying to debug the sample IM drivers Passthru from Microsoft
samples.... I assume this is a kernel mode driver and therefore trying to
use the kernel mode debugging of the windbg on same local machine... but I
get the following error... what am I doing wrong???? Please note that I'm
running on windows 2000....
Microsoft (R) Windows Debugger Version 6.3.0017.0
Copyright (c) Microsoft Corporation. All rights reserved.
The system does not support local kernel debugging.
Local kernel debugging requires Windows XP, Administrative
privileges, and is not supported by WOW64.
Debuggee initialization failed, HRESULT 0x80004001
"Not implemented"
doesn't this feature supported on win 2000 pro??? what should I do then???
I have the administrative privilege on my own pc.
thank you...
Gary G. Little
2004-10-01 13:08:35 UTC
Permalink
They have ... it's called WinDbg.
--
The personal opinion of
Gary G. Little
Post by Vipin
what I don't understand is why microsoft can't come up with something like
softice? Softice is damn costly for developers to purchase.And once we are
done with the development at office or on a particular project for which we
have softice license, we can't use for any other purpose.I used to work on
project for which they had softice license,but once I moved out of the
project, I can't use softice. Why doesn't MS come with a free debugger of
the same style?
Post by Pat [MSFT]
The error message is stating that WinXP is the minimum for doing 'live'
local kernel debugging, not that WinDBG can't do it. I doubt that
'live'
Post by Vipin
is
Post by Pat [MSFT]
what you want to do anyway since it is fairly limited (e.g. you can't
set
Post by Vipin
a
Post by Pat [MSFT]
break point). You would get a much better learning experince debugging
across 2 machines (so you can set break points, follow program flow,
etc.).
Post by Pat [MSFT]
pat
Post by Harry Potter
Hi guys,
I'm trying to debug the sample IM drivers Passthru from Microsoft
samples.... I assume this is a kernel mode driver and therefore trying
to
Post by Pat [MSFT]
Post by Harry Potter
use the kernel mode debugging of the windbg on same local machine...
but
Post by Vipin
I
Post by Pat [MSFT]
Post by Harry Potter
get the following error... what am I doing wrong???? Please note that
I'm
Post by Pat [MSFT]
Post by Harry Potter
running on windows 2000....
Microsoft (R) Windows Debugger Version 6.3.0017.0
Copyright (c) Microsoft Corporation. All rights reserved.
The system does not support local kernel debugging.
Local kernel debugging requires Windows XP, Administrative
privileges, and is not supported by WOW64.
Debuggee initialization failed, HRESULT 0x80004001
"Not implemented"
doesn't this feature supported on win 2000 pro??? what should I do
then???
Post by Pat [MSFT]
Post by Harry Potter
I have the administrative privilege on my own pc.
thank you...
Vipin
2004-10-02 16:42:22 UTC
Permalink
But with windbg you can do kernel debugging on the same machine. That's what
I meant
Post by Gary G. Little
They have ... it's called WinDbg.
--
The personal opinion of
Gary G. Little
Post by Vipin
what I don't understand is why microsoft can't come up with something like
softice? Softice is damn costly for developers to purchase.And once we are
done with the development at office or on a particular project for which
we
Post by Vipin
have softice license, we can't use for any other purpose.I used to work on
project for which they had softice license,but once I moved out of the
project, I can't use softice. Why doesn't MS come with a free debugger of
the same style?
Post by Pat [MSFT]
The error message is stating that WinXP is the minimum for doing 'live'
local kernel debugging, not that WinDBG can't do it. I doubt that
'live'
Post by Vipin
is
Post by Pat [MSFT]
what you want to do anyway since it is fairly limited (e.g. you can't
set
Post by Vipin
a
Post by Pat [MSFT]
break point). You would get a much better learning experince debugging
across 2 machines (so you can set break points, follow program flow,
etc.).
Post by Pat [MSFT]
pat
Post by Harry Potter
Hi guys,
I'm trying to debug the sample IM drivers Passthru from Microsoft
samples.... I assume this is a kernel mode driver and therefore trying
to
Post by Pat [MSFT]
Post by Harry Potter
use the kernel mode debugging of the windbg on same local machine...
but
Post by Vipin
I
Post by Pat [MSFT]
Post by Harry Potter
get the following error... what am I doing wrong???? Please note that
I'm
Post by Pat [MSFT]
Post by Harry Potter
running on windows 2000....
Microsoft (R) Windows Debugger Version 6.3.0017.0
Copyright (c) Microsoft Corporation. All rights reserved.
The system does not support local kernel debugging.
Local kernel debugging requires Windows XP, Administrative
privileges, and is not supported by WOW64.
Debuggee initialization failed, HRESULT 0x80004001
"Not implemented"
doesn't this feature supported on win 2000 pro??? what should I do
then???
Post by Pat [MSFT]
Post by Harry Potter
I have the administrative privilege on my own pc.
thank you...
Vipin
2004-10-02 16:56:10 UTC
Permalink
Gary,

I meant you can't do KM debugging on a single machine.
Post by Vipin
But with windbg you can do kernel debugging on the same machine. That's what
I meant
Post by Gary G. Little
They have ... it's called WinDbg.
--
The personal opinion of
Gary G. Little
Post by Vipin
what I don't understand is why microsoft can't come up with something
like
Post by Gary G. Little
Post by Vipin
softice? Softice is damn costly for developers to purchase.And once we
are
Post by Gary G. Little
Post by Vipin
done with the development at office or on a particular project for which
we
Post by Vipin
have softice license, we can't use for any other purpose.I used to
work
Post by Vipin
on
Post by Gary G. Little
Post by Vipin
project for which they had softice license,but once I moved out of the
project, I can't use softice. Why doesn't MS come with a free debugger
of
Post by Gary G. Little
Post by Vipin
the same style?
Post by Pat [MSFT]
The error message is stating that WinXP is the minimum for doing
'live'
Post by Gary G. Little
Post by Vipin
Post by Pat [MSFT]
local kernel debugging, not that WinDBG can't do it. I doubt that
'live'
Post by Vipin
is
Post by Pat [MSFT]
what you want to do anyway since it is fairly limited (e.g. you can't
set
Post by Vipin
a
Post by Pat [MSFT]
break point). You would get a much better learning experince
debugging
Post by Gary G. Little
Post by Vipin
Post by Pat [MSFT]
across 2 machines (so you can set break points, follow program flow,
etc.).
Post by Pat [MSFT]
pat
Post by Harry Potter
Hi guys,
I'm trying to debug the sample IM drivers Passthru from Microsoft
samples.... I assume this is a kernel mode driver and therefore
trying
Post by Gary G. Little
Post by Vipin
to
Post by Pat [MSFT]
Post by Harry Potter
use the kernel mode debugging of the windbg on same local machine...
but
Post by Vipin
I
Post by Pat [MSFT]
Post by Harry Potter
get the following error... what am I doing wrong???? Please note
that
Post by Gary G. Little
Post by Vipin
I'm
Post by Pat [MSFT]
Post by Harry Potter
running on windows 2000....
Microsoft (R) Windows Debugger Version 6.3.0017.0
Copyright (c) Microsoft Corporation. All rights reserved.
The system does not support local kernel debugging.
Local kernel debugging requires Windows XP, Administrative
privileges, and is not supported by WOW64.
Debuggee initialization failed, HRESULT 0x80004001
"Not implemented"
doesn't this feature supported on win 2000 pro??? what should I do
then???
Post by Pat [MSFT]
Post by Harry Potter
I have the administrative privilege on my own pc.
thank you...
Gary G. Little
2004-10-03 17:13:31 UTC
Permalink
Personally, I would not want to debug my drivers on the same machine I use
to develope them. I have always debugged using a target and host set up, and
find it a MUCH safer environment than a single environment. To many times
have I had a bad crash that hosed the targets OS leading to a complete
reformat and install. Not to mention that installing and uninstalling
drivers can proliferate trash throughout the registry, eventually leading to
a crash and possible format and install. I prefer debugging my drivers using
serial or 1394 to a target to protect my development environment. Also, my
target has an 80gig FAT32 disc that has several pre-canned OS environments
such as 2K, XP, and Server 2003 allowing me to refresh a corrupted boot disc
or switch to another environment quickly for testing. Those precanned
environments are vanilla with only the minimum drivers added for runtime.
This allows a relatively quick restore capability to allow testing an
install on a clean system.

For what I have to pay for softice, I can purchase a cheap dual processor
system for a target.
--
Gary G. Little
Post by Vipin
Gary,
I meant you can't do KM debugging on a single machine.
Post by Vipin
But with windbg you can do kernel debugging on the same machine. That's
what
Post by Vipin
I meant
Post by Gary G. Little
They have ... it's called WinDbg.
--
The personal opinion of
Gary G. Little
Post by Vipin
what I don't understand is why microsoft can't come up with something
like
Post by Gary G. Little
Post by Vipin
softice? Softice is damn costly for developers to purchase.And once we
are
Post by Gary G. Little
Post by Vipin
done with the development at office or on a particular project for
which
Post by Vipin
Post by Gary G. Little
we
Post by Vipin
have softice license, we can't use for any other purpose.I used to
work
Post by Vipin
on
Post by Gary G. Little
Post by Vipin
project for which they had softice license,but once I moved out of the
project, I can't use softice. Why doesn't MS come with a free debugger
of
Post by Gary G. Little
Post by Vipin
the same style?
Post by Pat [MSFT]
The error message is stating that WinXP is the minimum for doing
'live'
Post by Gary G. Little
Post by Vipin
Post by Pat [MSFT]
local kernel debugging, not that WinDBG can't do it. I doubt that
'live'
Post by Vipin
is
Post by Pat [MSFT]
what you want to do anyway since it is fairly limited (e.g. you
can't
Post by Vipin
Post by Gary G. Little
set
Post by Vipin
a
Post by Pat [MSFT]
break point). You would get a much better learning experince
debugging
Post by Gary G. Little
Post by Vipin
Post by Pat [MSFT]
across 2 machines (so you can set break points, follow program flow,
etc.).
Post by Pat [MSFT]
pat
Post by Harry Potter
Hi guys,
I'm trying to debug the sample IM drivers Passthru from Microsoft
samples.... I assume this is a kernel mode driver and therefore
trying
Post by Gary G. Little
Post by Vipin
to
Post by Pat [MSFT]
Post by Harry Potter
use the kernel mode debugging of the windbg on same local
machine...
Post by Vipin
Post by Gary G. Little
but
Post by Vipin
I
Post by Pat [MSFT]
Post by Harry Potter
get the following error... what am I doing wrong???? Please note
that
Post by Gary G. Little
Post by Vipin
I'm
Post by Pat [MSFT]
Post by Harry Potter
running on windows 2000....
Microsoft (R) Windows Debugger Version 6.3.0017.0
Copyright (c) Microsoft Corporation. All rights reserved.
The system does not support local kernel debugging.
Local kernel debugging requires Windows XP, Administrative
privileges, and is not supported by WOW64.
Debuggee initialization failed, HRESULT 0x80004001
"Not implemented"
doesn't this feature supported on win 2000 pro??? what should I do
then???
Post by Pat [MSFT]
Post by Harry Potter
I have the administrative privilege on my own pc.
thank you...
Arkady Frenkel
2004-10-02 16:44:19 UTC
Permalink
But that on XP machines only
Arkady
Post by Vipin
But with windbg you can do kernel debugging on the same machine. That's what
I meant
Post by Gary G. Little
They have ... it's called WinDbg.
--
The personal opinion of
Gary G. Little
Post by Vipin
what I don't understand is why microsoft can't come up with something
like
Post by Gary G. Little
Post by Vipin
softice? Softice is damn costly for developers to purchase.And once we
are
Post by Gary G. Little
Post by Vipin
done with the development at office or on a particular project for which
we
Post by Vipin
have softice license, we can't use for any other purpose.I used to
work
Post by Vipin
on
Post by Gary G. Little
Post by Vipin
project for which they had softice license,but once I moved out of the
project, I can't use softice. Why doesn't MS come with a free debugger
of
Post by Gary G. Little
Post by Vipin
the same style?
Post by Pat [MSFT]
The error message is stating that WinXP is the minimum for doing
'live'
Post by Gary G. Little
Post by Vipin
Post by Pat [MSFT]
local kernel debugging, not that WinDBG can't do it. I doubt that
'live'
Post by Vipin
is
Post by Pat [MSFT]
what you want to do anyway since it is fairly limited (e.g. you can't
set
Post by Vipin
a
Post by Pat [MSFT]
break point). You would get a much better learning experince
debugging
Post by Gary G. Little
Post by Vipin
Post by Pat [MSFT]
across 2 machines (so you can set break points, follow program flow,
etc.).
Post by Pat [MSFT]
pat
Post by Harry Potter
Hi guys,
I'm trying to debug the sample IM drivers Passthru from Microsoft
samples.... I assume this is a kernel mode driver and therefore
trying
Post by Gary G. Little
Post by Vipin
to
Post by Pat [MSFT]
Post by Harry Potter
use the kernel mode debugging of the windbg on same local machine...
but
Post by Vipin
I
Post by Pat [MSFT]
Post by Harry Potter
get the following error... what am I doing wrong???? Please note
that
Post by Gary G. Little
Post by Vipin
I'm
Post by Pat [MSFT]
Post by Harry Potter
running on windows 2000....
Microsoft (R) Windows Debugger Version 6.3.0017.0
Copyright (c) Microsoft Corporation. All rights reserved.
The system does not support local kernel debugging.
Local kernel debugging requires Windows XP, Administrative
privileges, and is not supported by WOW64.
Debuggee initialization failed, HRESULT 0x80004001
"Not implemented"
doesn't this feature supported on win 2000 pro??? what should I do
then???
Post by Pat [MSFT]
Post by Harry Potter
I have the administrative privilege on my own pc.
thank you...
Pavel A.
2004-10-02 01:22:30 UTC
Permalink
Post by Vipin
And once we are
done with the development at office or on a particular project for which we
have softice license, we can't use for any other purpose.I used to work on
project for which they had softice license,but once I moved out of the
project, I can't use softice.
Is Softice really licensed per project? Haven't heard of this.

--PA
Harry Potter
2004-10-02 01:56:26 UTC
Permalink
reading and working more with windbg... it does seems to be a powerful
tools... the problem though is its help file.... its help file is useful
when you know what you're looking for but if you just want to start with
it...aaaahhhh.... and you have to rely on internet search and asking for
help through news groups... as I've been doing...

cheers
Post by Pavel A.
Post by Vipin
And once we are
done with the development at office or on a particular project for which we
have softice license, we can't use for any other purpose.I used to work on
project for which they had softice license,but once I moved out of the
project, I can't use softice.
Is Softice really licensed per project? Haven't heard of this.
--PA
Pavel A.
2004-10-02 22:34:58 UTC
Permalink
Post by Harry Potter
reading and working more with windbg... it does seems to be a powerful
tools... the problem though is its help file.... its help file is useful
when you know what you're looking for but if you just want to start with
it...aaaahhhh.... and you have to rely on internet search and asking for
help through news groups... as I've been doing...
You're right. Some of Softice documentation comes in printed form,
including the getting started guide. Just look in your Softice box.

--PA
Maxim S. Shatskih
2004-10-02 07:27:51 UTC
Permalink
Post by Vipin
project, I can't use softice. Why doesn't MS come with a free debugger of
the same style?
The only advantage of SoftICE is being single-machine, and the second machine
is cheaper then SoftICE.
--
Maxim Shatskih, Windows DDK MVP
StorageCraft Corporation
***@storagecraft.com
http://www.storagecraft.com
Arkady Frenkel
2004-10-02 15:30:29 UTC
Permalink
That true , but being single-machine ( Visual-SoftIce is exactly the same as
WinDbg - two machines debugger with gui on the master machine ), it gives
great opportunity to debug in places where difficult to set two computers
( plane , train , bus ... :) )
Arkady
Post by Maxim S. Shatskih
Post by Vipin
project, I can't use softice. Why doesn't MS come with a free debugger of
the same style?
The only advantage of SoftICE is being single-machine, and the second machine
is cheaper then SoftICE.
--
Maxim Shatskih, Windows DDK MVP
StorageCraft Corporation
http://www.storagecraft.com
Jochen Kalmbach
2004-10-02 15:59:42 UTC
Permalink
Hi Arkady,
Post by Arkady Frenkel
That true , but being single-machine ( Visual-SoftIce is exactly the
same as WinDbg - two machines debugger with gui on the master machine
), it gives great opportunity to debug in places where difficult to
set two computers ( plane , train , bus ... :) )
Why not use VMWare or VirtualPC and WinDbg?
--
Greetings
Jochen

My blog about Win32 and .NET
http://blog.kalmbachnet.de/
Arkady Frenkel
2004-10-02 16:26:04 UTC
Permalink
That variant too , unless some cases , like debugging display drivers (
SoftIse use dos box style window with it's own fonts making such debugging
less problematic ) or debugging some latency problems
Arkady
Post by Jochen Kalmbach
Hi Arkady,
Post by Arkady Frenkel
That true , but being single-machine ( Visual-SoftIce is exactly the
same as WinDbg - two machines debugger with gui on the master machine
), it gives great opportunity to debug in places where difficult to
set two computers ( plane , train , bus ... :) )
Why not use VMWare or VirtualPC and WinDbg?
--
Greetings
Jochen
My blog about Win32 and .NET
http://blog.kalmbachnet.de/
Vipin
2004-10-02 16:54:42 UTC
Permalink
Also I beleive softice is good at debugging windows applications because it
basically freezes, I guess at the CPU level, so debugger application window
overlaps are not an issue.
Post by Arkady Frenkel
That variant too , unless some cases , like debugging display drivers (
SoftIse use dos box style window with it's own fonts making such debugging
less problematic ) or debugging some latency problems
Arkady
Post by Jochen Kalmbach
Hi Arkady,
Post by Arkady Frenkel
That true , but being single-machine ( Visual-SoftIce is exactly the
same as WinDbg - two machines debugger with gui on the master machine
), it gives great opportunity to debug in places where difficult to
set two computers ( plane , train , bus ... :) )
Why not use VMWare or VirtualPC and WinDbg?
--
Greetings
Jochen
My blog about Win32 and .NET
http://blog.kalmbachnet.de/
Arkady Frenkel
2004-10-02 17:26:32 UTC
Permalink
If you mean that with resized/moved SI debug window you can see app window
and in Studio debug that blocked , I agree with that
Arkady
Post by Vipin
Also I beleive softice is good at debugging windows applications because it
basically freezes, I guess at the CPU level, so debugger application window
overlaps are not an issue.
Post by Arkady Frenkel
That variant too , unless some cases , like debugging display drivers (
SoftIse use dos box style window with it's own fonts making such debugging
less problematic ) or debugging some latency problems
Arkady
Post by Jochen Kalmbach
Hi Arkady,
Post by Arkady Frenkel
That true , but being single-machine ( Visual-SoftIce is exactly the
same as WinDbg - two machines debugger with gui on the master machine
), it gives great opportunity to debug in places where difficult to
set two computers ( plane , train , bus ... :) )
Why not use VMWare or VirtualPC and WinDbg?
--
Greetings
Jochen
My blog about Win32 and .NET
http://blog.kalmbachnet.de/
Vipin
2004-10-04 07:10:05 UTC
Permalink
I meant since the blocking happens something down the OS level, window
overlaps with the debugger and hence the
window messages getting pumped into the window message queue as a result of
application window coming upfront the debugger
are not at all an issue with softice,but with vc++ or windbg, for usermode
debugging, I have to make the screen work at higher resolution
and ensure the app windows and the debugger don't overlap to get around this
awful problem.

Softice rules in the usermode world also but for the price.
Post by Arkady Frenkel
If you mean that with resized/moved SI debug window you can see app window
and in Studio debug that blocked , I agree with that
Arkady
Post by Vipin
Also I beleive softice is good at debugging windows applications because
it
Post by Vipin
basically freezes, I guess at the CPU level, so debugger application
window
Post by Vipin
overlaps are not an issue.
Post by Arkady Frenkel
That variant too , unless some cases , like debugging display drivers (
SoftIse use dos box style window with it's own fonts making such
debugging
Post by Vipin
Post by Arkady Frenkel
less problematic ) or debugging some latency problems
Arkady
Post by Jochen Kalmbach
Hi Arkady,
Post by Arkady Frenkel
That true , but being single-machine ( Visual-SoftIce is exactly the
same as WinDbg - two machines debugger with gui on the master
machine
Post by Vipin
Post by Arkady Frenkel
Post by Jochen Kalmbach
Post by Arkady Frenkel
), it gives great opportunity to debug in places where difficult to
set two computers ( plane , train , bus ... :) )
Why not use VMWare or VirtualPC and WinDbg?
--
Greetings
Jochen
My blog about Win32 and .NET
http://blog.kalmbachnet.de/
Arkady Frenkel
2004-10-06 17:03:49 UTC
Permalink
Now , I see what you mean , but that the same with all debuggers , you need
to set windows separately to see what happen in two simultaneously
Arkady
Post by Vipin
I meant since the blocking happens something down the OS level, window
overlaps with the debugger and hence the
window messages getting pumped into the window message queue as a result of
application window coming upfront the debugger
are not at all an issue with softice,but with vc++ or windbg, for usermode
debugging, I have to make the screen work at higher resolution
and ensure the app windows and the debugger don't overlap to get around this
awful problem.
Softice rules in the usermode world also but for the price.
Post by Arkady Frenkel
If you mean that with resized/moved SI debug window you can see app window
and in Studio debug that blocked , I agree with that
Arkady
Post by Vipin
Also I beleive softice is good at debugging windows applications because
it
Post by Vipin
basically freezes, I guess at the CPU level, so debugger application
window
Post by Vipin
overlaps are not an issue.
Post by Arkady Frenkel
That variant too , unless some cases , like debugging display
drivers
Post by Vipin
(
Post by Arkady Frenkel
Post by Vipin
Post by Arkady Frenkel
SoftIse use dos box style window with it's own fonts making such
debugging
Post by Vipin
Post by Arkady Frenkel
less problematic ) or debugging some latency problems
Arkady
Post by Jochen Kalmbach
Hi Arkady,
Post by Arkady Frenkel
That true , but being single-machine ( Visual-SoftIce is exactly
the
Post by Arkady Frenkel
Post by Vipin
Post by Arkady Frenkel
Post by Jochen Kalmbach
Post by Arkady Frenkel
same as WinDbg - two machines debugger with gui on the master
machine
Post by Vipin
Post by Arkady Frenkel
Post by Jochen Kalmbach
Post by Arkady Frenkel
), it gives great opportunity to debug in places where difficult
to
Post by Arkady Frenkel
Post by Vipin
Post by Arkady Frenkel
Post by Jochen Kalmbach
Post by Arkady Frenkel
set two computers ( plane , train , bus ... :) )
Why not use VMWare or VirtualPC and WinDbg?
--
Greetings
Jochen
My blog about Win32 and .NET
http://blog.kalmbachnet.de/
Guillaume
2004-10-02 16:25:37 UTC
Permalink
Post by Arkady Frenkel
That true , but being single-machine ( Visual-SoftIce is exactly the same as
WinDbg - two machines debugger with gui on the master machine ), it gives
great opportunity to debug in places where difficult to set two computers
( plane , train , bus ... :) )
You mean debugging computers that are part of a plane, train or bus, or
just doing your work on a laptop while traveling? In the latter case,
please remind us not to buy your products... ;-)
Arkady Frenkel
2004-10-02 16:42:15 UTC
Permalink
Guillaume , don't install any driver without WHQL signature and in this case
such debugging will be the problem of mine and MSFT :) , OTOH I bought LG
Flatron before few weeks and the driver have no WHQL cat at all
Arkady
Post by Guillaume
Post by Arkady Frenkel
That true , but being single-machine ( Visual-SoftIce is exactly the same as
WinDbg - two machines debugger with gui on the master machine ), it gives
great opportunity to debug in places where difficult to set two computers
( plane , train , bus ... :) )
You mean debugging computers that are part of a plane, train or bus, or
just doing your work on a laptop while traveling? In the latter case,
please remind us not to buy your products... ;-)
Arkady Frenkel
2004-10-02 15:22:48 UTC
Permalink
Softice license is per machine not per project for sure
Arkady
Post by Vipin
what I don't understand is why microsoft can't come up with something like
softice? Softice is damn costly for developers to purchase.And once we are
done with the development at office or on a particular project for which we
have softice license, we can't use for any other purpose.I used to work on
project for which they had softice license,but once I moved out of the
project, I can't use softice. Why doesn't MS come with a free debugger of
the same style?
Post by Pat [MSFT]
The error message is stating that WinXP is the minimum for doing 'live'
local kernel debugging, not that WinDBG can't do it. I doubt that
'live'
Post by Vipin
is
Post by Pat [MSFT]
what you want to do anyway since it is fairly limited (e.g. you can't
set
Post by Vipin
a
Post by Pat [MSFT]
break point). You would get a much better learning experince debugging
across 2 machines (so you can set break points, follow program flow,
etc.).
Post by Pat [MSFT]
pat
Post by Harry Potter
Hi guys,
I'm trying to debug the sample IM drivers Passthru from Microsoft
samples.... I assume this is a kernel mode driver and therefore trying
to
Post by Pat [MSFT]
Post by Harry Potter
use the kernel mode debugging of the windbg on same local machine...
but
Post by Vipin
I
Post by Pat [MSFT]
Post by Harry Potter
get the following error... what am I doing wrong???? Please note that
I'm
Post by Pat [MSFT]
Post by Harry Potter
running on windows 2000....
Microsoft (R) Windows Debugger Version 6.3.0017.0
Copyright (c) Microsoft Corporation. All rights reserved.
The system does not support local kernel debugging.
Local kernel debugging requires Windows XP, Administrative
privileges, and is not supported by WOW64.
Debuggee initialization failed, HRESULT 0x80004001
"Not implemented"
doesn't this feature supported on win 2000 pro??? what should I do
then???
Post by Pat [MSFT]
Post by Harry Potter
I have the administrative privilege on my own pc.
thank you...
Vipin
2004-10-02 16:52:39 UTC
Permalink
License is per machine, we were using it here when working on NT4 kernel
mode printer drivers. But once I got out of the project, I haven't ever seen
softice and my company says, we can't give you softice because its license
is per machine based and the bad thing is I haven't really got the chance to
work on KM stuff ever since when I get some idle time at work,because
naturally I can't ask for a 2nd machine my manager, when I don't have any KM
stuff related to company project. Had there been a live kernel debugging
tool from MS, I could have got across this issue. I don't know when I would
get the chance to do some kernel debugging unless I give lame excuses to my
manager saying I want to do some R&D and he isn't a fool also to take my
reasons seriously :) Is there some open source project on this front
anywhere? I think that is the last hope, or is it something difficult to
develop?
Post by Arkady Frenkel
Softice license is per machine not per project for sure
Arkady
Post by Vipin
what I don't understand is why microsoft can't come up with something like
softice? Softice is damn costly for developers to purchase.And once we are
done with the development at office or on a particular project for which
we
Post by Vipin
have softice license, we can't use for any other purpose.I used to work on
project for which they had softice license,but once I moved out of the
project, I can't use softice. Why doesn't MS come with a free debugger of
the same style?
Post by Pat [MSFT]
The error message is stating that WinXP is the minimum for doing 'live'
local kernel debugging, not that WinDBG can't do it. I doubt that
'live'
Post by Vipin
is
Post by Pat [MSFT]
what you want to do anyway since it is fairly limited (e.g. you can't
set
Post by Vipin
a
Post by Pat [MSFT]
break point). You would get a much better learning experince debugging
across 2 machines (so you can set break points, follow program flow,
etc.).
Post by Pat [MSFT]
pat
Post by Harry Potter
Hi guys,
I'm trying to debug the sample IM drivers Passthru from Microsoft
samples.... I assume this is a kernel mode driver and therefore trying
to
Post by Pat [MSFT]
Post by Harry Potter
use the kernel mode debugging of the windbg on same local machine...
but
Post by Vipin
I
Post by Pat [MSFT]
Post by Harry Potter
get the following error... what am I doing wrong???? Please note that
I'm
Post by Pat [MSFT]
Post by Harry Potter
running on windows 2000....
Microsoft (R) Windows Debugger Version 6.3.0017.0
Copyright (c) Microsoft Corporation. All rights reserved.
The system does not support local kernel debugging.
Local kernel debugging requires Windows XP, Administrative
privileges, and is not supported by WOW64.
Debuggee initialization failed, HRESULT 0x80004001
"Not implemented"
doesn't this feature supported on win 2000 pro??? what should I do
then???
Post by Pat [MSFT]
Post by Harry Potter
I have the administrative privilege on my own pc.
thank you...
Arkady Frenkel
2004-10-02 17:22:02 UTC
Permalink
Now I see SI installed on specific machine where you did the project.

Really almost one man ( Matt Pietrek( http://www.wheaty.net ) ) did modern
( I worked with SI yet in 1990 on dos variant but he joined Numega in 1993 )
, if you interested in that story
look at http://www.codeproject.com/interview/mattpietrek13sep2000.asp

When I talked about WinDbg and SoftIce with one of WinDbg guys, he said
that for them forbidden to build new OS , at the moment I didn't catch that
and ask if
hooking IDT that what he meant and he said - Exactly.
SoftIce change IDT and that WinDbg can't ( by specification ) do .
Arkady
Post by Vipin
License is per machine, we were using it here when working on NT4 kernel
mode printer drivers. But once I got out of the project, I haven't ever seen
softice and my company says, we can't give you softice because its license
is per machine based and the bad thing is I haven't really got the chance to
work on KM stuff ever since when I get some idle time at work,because
naturally I can't ask for a 2nd machine my manager, when I don't have any KM
stuff related to company project. Had there been a live kernel debugging
tool from MS, I could have got across this issue. I don't know when I would
get the chance to do some kernel debugging unless I give lame excuses to my
manager saying I want to do some R&D and he isn't a fool also to take my
reasons seriously :) Is there some open source project on this front
anywhere? I think that is the last hope, or is it something difficult to
develop?
Post by Arkady Frenkel
Softice license is per machine not per project for sure
Arkady
Post by Vipin
what I don't understand is why microsoft can't come up with something
like
Post by Arkady Frenkel
Post by Vipin
softice? Softice is damn costly for developers to purchase.And once we
are
Post by Arkady Frenkel
Post by Vipin
done with the development at office or on a particular project for which
we
Post by Vipin
have softice license, we can't use for any other purpose.I used to
work
Post by Vipin
on
Post by Arkady Frenkel
Post by Vipin
project for which they had softice license,but once I moved out of the
project, I can't use softice. Why doesn't MS come with a free debugger
of
Post by Arkady Frenkel
Post by Vipin
the same style?
Post by Pat [MSFT]
The error message is stating that WinXP is the minimum for doing
'live'
Post by Arkady Frenkel
Post by Vipin
Post by Pat [MSFT]
local kernel debugging, not that WinDBG can't do it. I doubt that
'live'
Post by Vipin
is
Post by Pat [MSFT]
what you want to do anyway since it is fairly limited (e.g. you can't
set
Post by Vipin
a
Post by Pat [MSFT]
break point). You would get a much better learning experince
debugging
Post by Arkady Frenkel
Post by Vipin
Post by Pat [MSFT]
across 2 machines (so you can set break points, follow program flow,
etc.).
Post by Pat [MSFT]
pat
Post by Harry Potter
Hi guys,
I'm trying to debug the sample IM drivers Passthru from Microsoft
samples.... I assume this is a kernel mode driver and therefore
trying
Post by Arkady Frenkel
Post by Vipin
to
Post by Pat [MSFT]
Post by Harry Potter
use the kernel mode debugging of the windbg on same local machine...
but
Post by Vipin
I
Post by Pat [MSFT]
Post by Harry Potter
get the following error... what am I doing wrong???? Please note
that
Post by Arkady Frenkel
Post by Vipin
I'm
Post by Pat [MSFT]
Post by Harry Potter
running on windows 2000....
Microsoft (R) Windows Debugger Version 6.3.0017.0
Copyright (c) Microsoft Corporation. All rights reserved.
The system does not support local kernel debugging.
Local kernel debugging requires Windows XP, Administrative
privileges, and is not supported by WOW64.
Debuggee initialization failed, HRESULT 0x80004001
"Not implemented"
doesn't this feature supported on win 2000 pro??? what should I do
then???
Post by Pat [MSFT]
Post by Harry Potter
I have the administrative privilege on my own pc.
thank you...
Vipin
2004-10-04 07:02:52 UTC
Permalink
Thanks, I had read the article you pointed 2 years back. Cool isn't, after
getting laid from borland, he went on to become one of the top developers
in windows. Hats off to his perservernace. looks like I got to piece
together a second PC at home if I am going to do anything on this.
Post by Arkady Frenkel
Now I see SI installed on specific machine where you did the project.
Really almost one man ( Matt Pietrek( http://www.wheaty.net ) ) did modern
( I worked with SI yet in 1990 on dos variant but he joined Numega in 1993 )
, if you interested in that story
look at http://www.codeproject.com/interview/mattpietrek13sep2000.asp
When I talked about WinDbg and SoftIce with one of WinDbg guys, he said
that for them forbidden to build new OS , at the moment I didn't catch that
and ask if
hooking IDT that what he meant and he said - Exactly.
SoftIce change IDT and that WinDbg can't ( by specification ) do .
Arkady
Post by Vipin
License is per machine, we were using it here when working on NT4 kernel
mode printer drivers. But once I got out of the project, I haven't ever
seen
Post by Vipin
softice and my company says, we can't give you softice because its
license
Post by Vipin
is per machine based and the bad thing is I haven't really got the
chance
Post by Arkady Frenkel
to
Post by Vipin
work on KM stuff ever since when I get some idle time at work,because
naturally I can't ask for a 2nd machine my manager, when I don't have
any
Post by Arkady Frenkel
KM
Post by Vipin
stuff related to company project. Had there been a live kernel debugging
tool from MS, I could have got across this issue. I don't know when I
would
Post by Vipin
get the chance to do some kernel debugging unless I give lame excuses to
my
Post by Vipin
manager saying I want to do some R&D and he isn't a fool also to take my
reasons seriously :) Is there some open source project on this front
anywhere? I think that is the last hope, or is it something difficult to
develop?
Post by Arkady Frenkel
Softice license is per machine not per project for sure
Arkady
Post by Vipin
what I don't understand is why microsoft can't come up with something
like
Post by Arkady Frenkel
Post by Vipin
softice? Softice is damn costly for developers to purchase.And once we
are
Post by Arkady Frenkel
Post by Vipin
done with the development at office or on a particular project for
which
Post by Vipin
Post by Arkady Frenkel
we
Post by Vipin
have softice license, we can't use for any other purpose.I used to
work
Post by Vipin
on
Post by Arkady Frenkel
Post by Vipin
project for which they had softice license,but once I moved out of the
project, I can't use softice. Why doesn't MS come with a free debugger
of
Post by Arkady Frenkel
Post by Vipin
the same style?
Post by Pat [MSFT]
The error message is stating that WinXP is the minimum for doing
'live'
Post by Arkady Frenkel
Post by Vipin
Post by Pat [MSFT]
local kernel debugging, not that WinDBG can't do it. I doubt that
'live'
Post by Vipin
is
Post by Pat [MSFT]
what you want to do anyway since it is fairly limited (e.g. you
can't
Post by Vipin
Post by Arkady Frenkel
set
Post by Vipin
a
Post by Pat [MSFT]
break point). You would get a much better learning experince
debugging
Post by Arkady Frenkel
Post by Vipin
Post by Pat [MSFT]
across 2 machines (so you can set break points, follow program flow,
etc.).
Post by Pat [MSFT]
pat
Post by Harry Potter
Hi guys,
I'm trying to debug the sample IM drivers Passthru from Microsoft
samples.... I assume this is a kernel mode driver and therefore
trying
Post by Arkady Frenkel
Post by Vipin
to
Post by Pat [MSFT]
Post by Harry Potter
use the kernel mode debugging of the windbg on same local
machine...
Post by Vipin
Post by Arkady Frenkel
but
Post by Vipin
I
Post by Pat [MSFT]
Post by Harry Potter
get the following error... what am I doing wrong???? Please note
that
Post by Arkady Frenkel
Post by Vipin
I'm
Post by Pat [MSFT]
Post by Harry Potter
running on windows 2000....
Microsoft (R) Windows Debugger Version 6.3.0017.0
Copyright (c) Microsoft Corporation. All rights reserved.
The system does not support local kernel debugging.
Local kernel debugging requires Windows XP, Administrative
privileges, and is not supported by WOW64.
Debuggee initialization failed, HRESULT 0x80004001
"Not implemented"
doesn't this feature supported on win 2000 pro??? what should I do
then???
Post by Pat [MSFT]
Post by Harry Potter
I have the administrative privilege on my own pc.
thank you...
Arkady Frenkel
2004-10-04 10:20:04 UTC
Permalink
Did you pay attention what he wrote about stolen code from MS , that almost
impossible without knowledge of OS internals and processor architecture(
Intel ) .
Arkady
Post by Vipin
Thanks, I had read the article you pointed 2 years back. Cool isn't, after
getting laid from borland, he went on to become one of the top developers
in windows. Hats off to his perservernace. looks like I got to piece
together a second PC at home if I am going to do anything on this.
Post by Arkady Frenkel
Now I see SI installed on specific machine where you did the project.
Really almost one man ( Matt Pietrek( http://www.wheaty.net ) ) did modern
( I worked with SI yet in 1990 on dos variant but he joined Numega in
1993 )
Post by Arkady Frenkel
, if you interested in that story
look at http://www.codeproject.com/interview/mattpietrek13sep2000.asp
When I talked about WinDbg and SoftIce with one of WinDbg guys, he said
that for them forbidden to build new OS , at the moment I didn't catch
that
Post by Arkady Frenkel
and ask if
hooking IDT that what he meant and he said - Exactly.
SoftIce change IDT and that WinDbg can't ( by specification ) do .
Arkady
Post by Vipin
License is per machine, we were using it here when working on NT4 kernel
mode printer drivers. But once I got out of the project, I haven't ever
seen
Post by Vipin
softice and my company says, we can't give you softice because its
license
Post by Vipin
is per machine based and the bad thing is I haven't really got the
chance
Post by Arkady Frenkel
to
Post by Vipin
work on KM stuff ever since when I get some idle time at work,because
naturally I can't ask for a 2nd machine my manager, when I don't have
any
Post by Arkady Frenkel
KM
Post by Vipin
stuff related to company project. Had there been a live kernel debugging
tool from MS, I could have got across this issue. I don't know when I
would
Post by Vipin
get the chance to do some kernel debugging unless I give lame excuses to
my
Post by Vipin
manager saying I want to do some R&D and he isn't a fool also to take
my
Post by Arkady Frenkel
Post by Vipin
reasons seriously :) Is there some open source project on this front
anywhere? I think that is the last hope, or is it something difficult to
develop?
Post by Arkady Frenkel
Softice license is per machine not per project for sure
Arkady
Post by Vipin
what I don't understand is why microsoft can't come up with
something
Post by Arkady Frenkel
Post by Vipin
like
Post by Arkady Frenkel
Post by Vipin
softice? Softice is damn costly for developers to purchase.And
once
Post by Vipin
we
Post by Arkady Frenkel
Post by Vipin
are
Post by Arkady Frenkel
Post by Vipin
done with the development at office or on a particular project for
which
Post by Vipin
Post by Arkady Frenkel
we
Post by Vipin
have softice license, we can't use for any other purpose.I used to
work
Post by Vipin
on
Post by Arkady Frenkel
Post by Vipin
project for which they had softice license,but once I moved out of
the
Post by Arkady Frenkel
Post by Vipin
Post by Arkady Frenkel
Post by Vipin
project, I can't use softice. Why doesn't MS come with a free
debugger
Post by Arkady Frenkel
Post by Vipin
of
Post by Arkady Frenkel
Post by Vipin
the same style?
Post by Pat [MSFT]
The error message is stating that WinXP is the minimum for doing
'live'
Post by Arkady Frenkel
Post by Vipin
Post by Pat [MSFT]
local kernel debugging, not that WinDBG can't do it. I doubt that
'live'
Post by Vipin
is
Post by Pat [MSFT]
what you want to do anyway since it is fairly limited (e.g. you
can't
Post by Vipin
Post by Arkady Frenkel
set
Post by Vipin
a
Post by Pat [MSFT]
break point). You would get a much better learning experince
debugging
Post by Arkady Frenkel
Post by Vipin
Post by Pat [MSFT]
across 2 machines (so you can set break points, follow program
flow,
Post by Arkady Frenkel
Post by Vipin
Post by Arkady Frenkel
Post by Vipin
etc.).
Post by Pat [MSFT]
pat
Post by Harry Potter
Hi guys,
I'm trying to debug the sample IM drivers Passthru from
Microsoft
Post by Arkady Frenkel
Post by Vipin
Post by Arkady Frenkel
Post by Vipin
Post by Pat [MSFT]
Post by Harry Potter
samples.... I assume this is a kernel mode driver and therefore
trying
Post by Arkady Frenkel
Post by Vipin
to
Post by Pat [MSFT]
Post by Harry Potter
use the kernel mode debugging of the windbg on same local
machine...
Post by Vipin
Post by Arkady Frenkel
but
Post by Vipin
I
Post by Pat [MSFT]
Post by Harry Potter
get the following error... what am I doing wrong???? Please note
that
Post by Arkady Frenkel
Post by Vipin
I'm
Post by Pat [MSFT]
Post by Harry Potter
running on windows 2000....
Microsoft (R) Windows Debugger Version 6.3.0017.0
Copyright (c) Microsoft Corporation. All rights reserved.
The system does not support local kernel debugging.
Local kernel debugging requires Windows XP, Administrative
privileges, and is not supported by WOW64.
Debuggee initialization failed, HRESULT 0x80004001
"Not implemented"
doesn't this feature supported on win 2000 pro??? what should
I
Post by Vipin
do
Post by Arkady Frenkel
Post by Vipin
Post by Arkady Frenkel
Post by Vipin
then???
Post by Pat [MSFT]
Post by Harry Potter
I have the administrative privilege on my own pc.
thank you...
Vipin
2004-10-04 10:42:17 UTC
Permalink
yeah, I did,you meant this right:-
"The team was basically Frank, the SoftIce for Windows guru, and myself. You
wouldn't believe how much of the code was stolen from the DOS products. "

Thanks
Vipin
Post by Arkady Frenkel
Did you pay attention what he wrote about stolen code from MS , that almost
impossible without knowledge of OS internals and processor architecture(
Intel ) .
Arkady
Post by Vipin
Thanks, I had read the article you pointed 2 years back. Cool isn't, after
getting laid from borland, he went on to become one of the top developers
in windows. Hats off to his perservernace. looks like I got to piece
together a second PC at home if I am going to do anything on this.
Post by Arkady Frenkel
Now I see SI installed on specific machine where you did the project.
Really almost one man ( Matt Pietrek( http://www.wheaty.net ) ) did
modern
Post by Vipin
Post by Arkady Frenkel
( I worked with SI yet in 1990 on dos variant but he joined Numega in
1993 )
Post by Arkady Frenkel
, if you interested in that story
look at http://www.codeproject.com/interview/mattpietrek13sep2000.asp
When I talked about WinDbg and SoftIce with one of WinDbg guys, he said
that for them forbidden to build new OS , at the moment I didn't catch
that
Post by Arkady Frenkel
and ask if
hooking IDT that what he meant and he said - Exactly.
SoftIce change IDT and that WinDbg can't ( by specification ) do .
Arkady
Post by Vipin
License is per machine, we were using it here when working on NT4
kernel
Post by Vipin
Post by Arkady Frenkel
Post by Vipin
mode printer drivers. But once I got out of the project, I haven't
ever
Post by Vipin
Post by Arkady Frenkel
seen
Post by Vipin
softice and my company says, we can't give you softice because its
license
Post by Vipin
is per machine based and the bad thing is I haven't really got the
chance
Post by Arkady Frenkel
to
Post by Vipin
work on KM stuff ever since when I get some idle time at
work,because
Post by Arkady Frenkel
Post by Vipin
Post by Arkady Frenkel
Post by Vipin
naturally I can't ask for a 2nd machine my manager, when I don't have
any
Post by Arkady Frenkel
KM
Post by Vipin
stuff related to company project. Had there been a live kernel
debugging
Post by Vipin
Post by Arkady Frenkel
Post by Vipin
tool from MS, I could have got across this issue. I don't know when I
would
Post by Vipin
get the chance to do some kernel debugging unless I give lame
excuses
Post by Arkady Frenkel
to
Post by Vipin
Post by Arkady Frenkel
my
Post by Vipin
manager saying I want to do some R&D and he isn't a fool also to take
my
Post by Arkady Frenkel
Post by Vipin
reasons seriously :) Is there some open source project on this front
anywhere? I think that is the last hope, or is it something
difficult
Post by Arkady Frenkel
to
Post by Vipin
Post by Arkady Frenkel
Post by Vipin
develop?
Post by Arkady Frenkel
Softice license is per machine not per project for sure
Arkady
Post by Vipin
what I don't understand is why microsoft can't come up with
something
Post by Arkady Frenkel
Post by Vipin
like
Post by Arkady Frenkel
Post by Vipin
softice? Softice is damn costly for developers to purchase.And
once
Post by Vipin
we
Post by Arkady Frenkel
Post by Vipin
are
Post by Arkady Frenkel
Post by Vipin
done with the development at office or on a particular project for
which
Post by Vipin
Post by Arkady Frenkel
we
Post by Vipin
have softice license, we can't use for any other purpose.I used to
work
Post by Vipin
on
Post by Arkady Frenkel
Post by Vipin
project for which they had softice license,but once I moved out of
the
Post by Arkady Frenkel
Post by Vipin
Post by Arkady Frenkel
Post by Vipin
project, I can't use softice. Why doesn't MS come with a free
debugger
Post by Arkady Frenkel
Post by Vipin
of
Post by Arkady Frenkel
Post by Vipin
the same style?
Post by Pat [MSFT]
The error message is stating that WinXP is the minimum for doing
'live'
Post by Arkady Frenkel
Post by Vipin
Post by Pat [MSFT]
local kernel debugging, not that WinDBG can't do it. I doubt
that
Post by Vipin
Post by Arkady Frenkel
Post by Vipin
Post by Arkady Frenkel
'live'
Post by Vipin
is
Post by Pat [MSFT]
what you want to do anyway since it is fairly limited (e.g. you
can't
Post by Vipin
Post by Arkady Frenkel
set
Post by Vipin
a
Post by Pat [MSFT]
break point). You would get a much better learning experince
debugging
Post by Arkady Frenkel
Post by Vipin
Post by Pat [MSFT]
across 2 machines (so you can set break points, follow program
flow,
Post by Arkady Frenkel
Post by Vipin
Post by Arkady Frenkel
Post by Vipin
etc.).
Post by Pat [MSFT]
pat
Post by Harry Potter
Hi guys,
I'm trying to debug the sample IM drivers Passthru from
Microsoft
Post by Arkady Frenkel
Post by Vipin
Post by Arkady Frenkel
Post by Vipin
Post by Pat [MSFT]
Post by Harry Potter
samples.... I assume this is a kernel mode driver and
therefore
Post by Vipin
Post by Arkady Frenkel
Post by Vipin
trying
Post by Arkady Frenkel
Post by Vipin
to
Post by Pat [MSFT]
Post by Harry Potter
use the kernel mode debugging of the windbg on same local
machine...
Post by Vipin
Post by Arkady Frenkel
but
Post by Vipin
I
Post by Pat [MSFT]
Post by Harry Potter
get the following error... what am I doing wrong???? Please
note
Post by Vipin
Post by Arkady Frenkel
Post by Vipin
that
Post by Arkady Frenkel
Post by Vipin
I'm
Post by Pat [MSFT]
Post by Harry Potter
running on windows 2000....
Microsoft (R) Windows Debugger Version 6.3.0017.0
Copyright (c) Microsoft Corporation. All rights reserved.
The system does not support local kernel debugging.
Local kernel debugging requires Windows XP, Administrative
privileges, and is not supported by WOW64.
Debuggee initialization failed, HRESULT 0x80004001
"Not implemented"
doesn't this feature supported on win 2000 pro??? what should
I
Post by Vipin
do
Post by Arkady Frenkel
Post by Vipin
Post by Arkady Frenkel
Post by Vipin
then???
Post by Pat [MSFT]
Post by Harry Potter
I have the administrative privilege on my own pc.
thank you...
Loading...