Arlie,
Though this was not my thread, but I was reading it, and found it
interesting. Can you please tell me the command to transfer a file to
the debuggee.
On 8/17/05, Arlie Davis wrote:
> Are you using a kernel-mode debugger? The kernel debugger has a feature
> which will transfer your device driver from the development/debugger machine
> to the test machine over the debug cable, every time that driver starts.
> This way, you can simply delete the driver on the host machine (no file in
> system32/drivers at all), or leave a reliable “known-good” copy in that
> directory. Read up on the .kdfiles command; it’s a life-saver and a
> time-saver.
>
> Under normal conditions, you should never have to reinstall your system,
> even while debugging nasty driver bugs. Also, you do not say that happens
> when deleting the driver “does not work”, so we cannot help you diagnose
> that situation. Please provide more information.
>
> – arlie
>
>
>
> -----Original Message-----
> From: xxxxx@lists.osr.com
> [mailto:xxxxx@lists.osr.com] On Behalf Of xxxxx@uow.edu.au
> Sent: Tuesday, August 16, 2005 11:52 PM
> To: Kernel Debugging Interest List
> Subject: SPAM-LOW: [windbg] system restart
>
> after i make a mistake in my file system filter driver (eg access memory
> that not mine etc) i get the usual blue screen, so i go to the recovery
> console and delete the driver from system32/drivers and that will fix the
> problem 70% of the time but the other 30% of the time that will not work so
> i am forced to reinstall windows on my existing windows installation( just
> the system files are reinstalled, repair reinstall ) which is rather time
> consuming ~1h. is there a better way ?
>
> —
> You are currently subscribed to windbg as: xxxxx@stonestreetone.com To
> unsubscribe send a blank email to xxxxx@lists.osr.com
>
>
>
>
> —
> You are currently subscribed to windbg as: xxxxx@gmail.com
> To unsubscribe send a blank email to xxxxx@lists.osr.com
>
–
- Developer
Look in the debugger documentation under “.kdfiles” and you’ll see the
specific information about how to do this.
Regards,
Tony
Tony Mason
Consulting Partner
OSR Open Systems Resources, Inc.
http://www.osr.com
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Developer
Sent: Thursday, August 18, 2005 2:15 AM
To: Kernel Debugging Interest List
Subject: Re: SPAM-LOW: [windbg] system restart
Arlie,
Though this was not my thread, but I was reading it, and found it
interesting. Can you please tell me the command to transfer a file to
the debuggee.
On 8/17/05, Arlie Davis wrote:
> Are you using a kernel-mode debugger? The kernel debugger has a
feature
> which will transfer your device driver from the development/debugger
machine
> to the test machine over the debug cable, every time that driver
starts.
> This way, you can simply delete the driver on the host machine (no
file in
> system32/drivers at all), or leave a reliable “known-good” copy in
that
> directory. Read up on the .kdfiles command; it’s a life-saver and a
> time-saver.
>
> Under normal conditions, you should never have to reinstall your
system,
> even while debugging nasty driver bugs. Also, you do not say that
happens
> when deleting the driver “does not work”, so we cannot help you
diagnose
> that situation. Please provide more information.
>
> – arlie
>
>
>
> -----Original Message-----
> From: xxxxx@lists.osr.com
> [mailto:xxxxx@lists.osr.com] On Behalf Of
xxxxx@uow.edu.au
> Sent: Tuesday, August 16, 2005 11:52 PM
> To: Kernel Debugging Interest List
> Subject: SPAM-LOW: [windbg] system restart
>
> after i make a mistake in my file system filter driver (eg access
memory
> that not mine etc) i get the usual blue screen, so i go to the
recovery
> console and delete the driver from system32/drivers and that will fix
the
> problem 70% of the time but the other 30% of the time that will not
work so
> i am forced to reinstall windows on my existing windows installation(
just
> the system files are reinstalled, repair reinstall ) which is rather
time
> consuming ~1h. is there a better way ?
>
> —
> You are currently subscribed to windbg as: xxxxx@stonestreetone.com
To
> unsubscribe send a blank email to xxxxx@lists.osr.com
>
>
>
>
> —
> You are currently subscribed to windbg as: xxxxx@gmail.com
> To unsubscribe send a blank email to xxxxx@lists.osr.com
>
–
- Developer
—
You are currently subscribed to windbg as: unknown lmsubst tag argument:
‘’
To unsubscribe send a blank email to xxxxx@lists.osr.com
thanks tony, i got it.
On 8/18/05, Tony Mason wrote:
> Look in the debugger documentation under “.kdfiles” and you’ll see the
> specific information about how to do this.
>
> Regards,
>
> Tony
>
> Tony Mason
> Consulting Partner
> OSR Open Systems Resources, Inc.
> http://www.osr.com
>
>
> -----Original Message-----
> From: xxxxx@lists.osr.com
> [mailto:xxxxx@lists.osr.com] On Behalf Of Developer
> Sent: Thursday, August 18, 2005 2:15 AM
> To: Kernel Debugging Interest List
> Subject: Re: SPAM-LOW: [windbg] system restart
>
> Arlie,
>
> Though this was not my thread, but I was reading it, and found it
> interesting. Can you please tell me the command to transfer a file to
> the debuggee.
>
> On 8/17/05, Arlie Davis wrote:
> > Are you using a kernel-mode debugger? The kernel debugger has a
> feature
> > which will transfer your device driver from the development/debugger
> machine
> > to the test machine over the debug cable, every time that driver
> starts.
> > This way, you can simply delete the driver on the host machine (no
> file in
> > system32/drivers at all), or leave a reliable “known-good” copy in
> that
> > directory. Read up on the .kdfiles command; it’s a life-saver and a
> > time-saver.
> >
> > Under normal conditions, you should never have to reinstall your
> system,
> > even while debugging nasty driver bugs. Also, you do not say that
> happens
> > when deleting the driver “does not work”, so we cannot help you
> diagnose
> > that situation. Please provide more information.
> >
> > – arlie
> >
> >
> >
> > -----Original Message-----
> > From: xxxxx@lists.osr.com
> > [mailto:xxxxx@lists.osr.com] On Behalf Of
> xxxxx@uow.edu.au
> > Sent: Tuesday, August 16, 2005 11:52 PM
> > To: Kernel Debugging Interest List
> > Subject: SPAM-LOW: [windbg] system restart
> >
> > after i make a mistake in my file system filter driver (eg access
> memory
> > that not mine etc) i get the usual blue screen, so i go to the
> recovery
> > console and delete the driver from system32/drivers and that will fix
> the
> > problem 70% of the time but the other 30% of the time that will not
> work so
> > i am forced to reinstall windows on my existing windows installation(
> just
> > the system files are reinstalled, repair reinstall ) which is rather
> time
> > consuming ~1h. is there a better way ?
> >
> > —
> > You are currently subscribed to windbg as: xxxxx@stonestreetone.com
> To
> > unsubscribe send a blank email to xxxxx@lists.osr.com
> >
> >
> >
> >
> > —
> > You are currently subscribed to windbg as: xxxxx@gmail.com
> > To unsubscribe send a blank email to xxxxx@lists.osr.com
> >
>
>
> –
>
> - Developer
>
> —
> You are currently subscribed to windbg as: unknown lmsubst tag argument:
> ‘’
> To unsubscribe send a blank email to xxxxx@lists.osr.com
>
> —
> You are currently subscribed to windbg as: unknown lmsubst tag argument: ‘’
> To unsubscribe send a blank email to xxxxx@lists.osr.com
>
–
- Developer
.kdfiles
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Developer
Sent: Wednesday, August 17, 2005 11:15 PM
To: Kernel Debugging Interest List
Subject: Re: SPAM-LOW: [windbg] system restart
Arlie,
Though this was not my thread, but I was reading it, and found it
interesting. Can you please tell me the command to transfer a file to
the debuggee.
On 8/17/05, Arlie Davis wrote:
> Are you using a kernel-mode debugger? The kernel debugger has a
feature
> which will transfer your device driver from the development/debugger
machine
> to the test machine over the debug cable, every time that driver
starts.
> This way, you can simply delete the driver on the host machine (no
file in
> system32/drivers at all), or leave a reliable “known-good” copy in
that
> directory. Read up on the .kdfiles command; it’s a life-saver and a
> time-saver.
>
> Under normal conditions, you should never have to reinstall your
system,
> even while debugging nasty driver bugs. Also, you do not say that
happens
> when deleting the driver “does not work”, so we cannot help you
diagnose
> that situation. Please provide more information.
>
> – arlie
>
>
>
> -----Original Message-----
> From: xxxxx@lists.osr.com
> [mailto:xxxxx@lists.osr.com] On Behalf Of
xxxxx@uow.edu.au
> Sent: Tuesday, August 16, 2005 11:52 PM
> To: Kernel Debugging Interest List
> Subject: SPAM-LOW: [windbg] system restart
>
> after i make a mistake in my file system filter driver (eg access
memory
> that not mine etc) i get the usual blue screen, so i go to the
recovery
> console and delete the driver from system32/drivers and that will fix
the
> problem 70% of the time but the other 30% of the time that will not
work so
> i am forced to reinstall windows on my existing windows installation(
just
> the system files are reinstalled, repair reinstall ) which is rather
time
> consuming ~1h. is there a better way ?
>
> —
> You are currently subscribed to windbg as: xxxxx@stonestreetone.com
To
> unsubscribe send a blank email to xxxxx@lists.osr.com
>
>
>
>
> —
> You are currently subscribed to windbg as: xxxxx@gmail.com
> To unsubscribe send a blank email to xxxxx@lists.osr.com
>
–
- Developer
—
You are currently subscribed to windbg as: unknown lmsubst tag argument:
‘’
To unsubscribe send a blank email to xxxxx@lists.osr.com
But it doesn’t permanently transfer the files. It loads the driver from your
local store, depending on how you have established the mapping. Before you
run without the debugger and defiles you have to refresh the files on the
mule yourself via install or copy.
–
The personal opinion of
Gary G. Little
“Tony Mason” wrote in message news:xxxxx@windbg…
Look in the debugger documentation under “.kdfiles” and you’ll see the
specific information about how to do this.
Regards,
Tony
Tony Mason
Consulting Partner
OSR Open Systems Resources, Inc.
http://www.osr.com
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Developer
Sent: Thursday, August 18, 2005 2:15 AM
To: Kernel Debugging Interest List
Subject: Re: SPAM-LOW: [windbg] system restart
Arlie,
Though this was not my thread, but I was reading it, and found it
interesting. Can you please tell me the command to transfer a file to
the debuggee.
On 8/17/05, Arlie Davis wrote:
> Are you using a kernel-mode debugger? The kernel debugger has a
feature
> which will transfer your device driver from the development/debugger
machine
> to the test machine over the debug cable, every time that driver
starts.
> This way, you can simply delete the driver on the host machine (no
file in
> system32/drivers at all), or leave a reliable “known-good” copy in
that
> directory. Read up on the .kdfiles command; it’s a life-saver and a
> time-saver.
>
> Under normal conditions, you should never have to reinstall your
system,
> even while debugging nasty driver bugs. Also, you do not say that
happens
> when deleting the driver “does not work”, so we cannot help you
diagnose
> that situation. Please provide more information.
>
> – arlie
>
>
>
> -----Original Message-----
> From: xxxxx@lists.osr.com
> [mailto:xxxxx@lists.osr.com] On Behalf Of
xxxxx@uow.edu.au
> Sent: Tuesday, August 16, 2005 11:52 PM
> To: Kernel Debugging Interest List
> Subject: SPAM-LOW: [windbg] system restart
>
> after i make a mistake in my file system filter driver (eg access
memory
> that not mine etc) i get the usual blue screen, so i go to the
recovery
> console and delete the driver from system32/drivers and that will fix
the
> problem 70% of the time but the other 30% of the time that will not
work so
> i am forced to reinstall windows on my existing windows installation(
just
> the system files are reinstalled, repair reinstall ) which is rather
time
> consuming ~1h. is there a better way ?
>
> —
> You are currently subscribed to windbg as: xxxxx@stonestreetone.com
To
> unsubscribe send a blank email to xxxxx@lists.osr.com
>
>
>
>
> —
> You are currently subscribed to windbg as: xxxxx@gmail.com
> To unsubscribe send a blank email to xxxxx@lists.osr.com
>
–
- Developer
—
You are currently subscribed to windbg as: unknown lmsubst tag argument:
‘’
To unsubscribe send a blank email to xxxxx@lists.osr.com
Sometimes I hate the spell checker. “defiles” should have been “kdfiles”.
–
The personal opinion of
Gary G. Little
“Gary G. Little” wrote in message news:xxxxx@windbg…
> But it doesn’t permanently transfer the files. It loads the driver from
> your local store, depending on how you have established the mapping.
> Before you run without the debugger and defiles you have to refresh the
> files on the mule yourself via install or copy.
>
> –
> The personal opinion of
> Gary G. Little
>
> “Tony Mason” wrote in message news:xxxxx@windbg…
> Look in the debugger documentation under “.kdfiles” and you’ll see the
> specific information about how to do this.
>
> Regards,
>
> Tony
>
> Tony Mason
> Consulting Partner
> OSR Open Systems Resources, Inc.
> http://www.osr.com
>
>
> -----Original Message-----
> From: xxxxx@lists.osr.com
> [mailto:xxxxx@lists.osr.com] On Behalf Of Developer
> Sent: Thursday, August 18, 2005 2:15 AM
> To: Kernel Debugging Interest List
> Subject: Re: SPAM-LOW: [windbg] system restart
>
> Arlie,
>
> Though this was not my thread, but I was reading it, and found it
> interesting. Can you please tell me the command to transfer a file to
> the debuggee.
>
> On 8/17/05, Arlie Davis wrote:
>> Are you using a kernel-mode debugger? The kernel debugger has a
> feature
>> which will transfer your device driver from the development/debugger
> machine
>> to the test machine over the debug cable, every time that driver
> starts.
>> This way, you can simply delete the driver on the host machine (no
> file in
>> system32/drivers at all), or leave a reliable “known-good” copy in
> that
>> directory. Read up on the .kdfiles command; it’s a life-saver and a
>> time-saver.
>>
>> Under normal conditions, you should never have to reinstall your
> system,
>> even while debugging nasty driver bugs. Also, you do not say that
> happens
>> when deleting the driver “does not work”, so we cannot help you
> diagnose
>> that situation. Please provide more information.
>>
>> – arlie
>>
>>
>>
>> -----Original Message-----
>> From: xxxxx@lists.osr.com
>> [mailto:xxxxx@lists.osr.com] On Behalf Of
> xxxxx@uow.edu.au
>> Sent: Tuesday, August 16, 2005 11:52 PM
>> To: Kernel Debugging Interest List
>> Subject: SPAM-LOW: [windbg] system restart
>>
>> after i make a mistake in my file system filter driver (eg access
> memory
>> that not mine etc) i get the usual blue screen, so i go to the
> recovery
>> console and delete the driver from system32/drivers and that will fix
> the
>> problem 70% of the time but the other 30% of the time that will not
> work so
>> i am forced to reinstall windows on my existing windows installation(
> just
>> the system files are reinstalled, repair reinstall ) which is rather
> time
>> consuming ~1h. is there a better way ?
>>
>> —
>> You are currently subscribed to windbg as: xxxxx@stonestreetone.com
> To
>> unsubscribe send a blank email to xxxxx@lists.osr.com
>>
>>
>>
>>
>> —
>> You are currently subscribed to windbg as: xxxxx@gmail.com
>> To unsubscribe send a blank email to xxxxx@lists.osr.com
>>
>
>
> –
>
> - Developer
>
> —
> You are currently subscribed to windbg as: unknown lmsubst tag argument:
> ‘’
> To unsubscribe send a blank email to xxxxx@lists.osr.com
>
>
>