kdfiles again and again

I really need to convince win7 to load the checked ndis.sys. Is there any hope that the ‘debug’ boot loader in win7 actually works with windbg and will load boot load drivers?

Did someone say that it would?

mm

One can only hope. What I was asking is ‘has anyone gotten this to work, or at least tried and failed?’

The last time this came up, Doron admitted that it was borked in vista but held out hope for win7.

Negative. I had just assumed that this is going to be broken indefinitely.

I’d love to be wrong.

mm

> I really need to convince win7 to load the checked ndis.sys

Have you tried just doing the, “change the ImagePath to
\system32\drivers\chk\foo.sys” trick? Usually works quite nicely.

-scott


Scott Noone
Consulting Associate
OSR Open Systems Resources, Inc.
http://www.osronline.com

wrote in message news:xxxxx@ntdev…
> I really need to convince win7 to load the checked ndis.sys. Is there any
> hope that the ‘debug’ boot loader in win7 actually works with windbg and
> will load boot load drivers?
>

>I really need to convince win7 to load the checked ndis.sys.

ImagePath registry rules


Maxim S. Shatskih
Windows DDK MVP
xxxxx@storagecraft.com
http://www.storagecraft.com

I’m guessing that neither of you have actually tried that with ndis on win7.

The answer is yes, I’ve tried it, and it bugchecks in NETIO.SYS. Ndis is a port driver and a kernel dll. I’m not convinced having an explicit load of ‘ndischk.sys’ while ndis.sys is hanging out in system32\drivers actually works. It is also possible that the checked ndis.sys requires checked netXXXX.sys components as well, which would be equally horrendous.

bcdedit /set bootdebug on

Now .kdfiles will work within the boot loader.


Jake Oshins
Hyper-V I/O Architect
Windows Kernel Group

This post implies no warranties and confers no rights.


wrote in message news:xxxxx@ntdev…
> I really need to convince win7 to load the checked ndis.sys. Is there any
> hope that the ‘debug’ boot loader in win7 actually works with windbg and
> will load boot load drivers?
>

Now that is good news.

Thanks, Jake.

mm

Thanks Jake.

Mark Roddy

On Thu, Feb 4, 2010 at 4:42 PM, Jake Oshins wrote:
> bcdedit /set bootdebug on
>
> Now .kdfiles will work within the boot loader.
>
> –
> Jake Oshins
> Hyper-V I/O Architect
> Windows Kernel Group
>
> This post implies no warranties and confers no rights.
>
> --------------------------------------------------------------
>
>
> wrote in message news:xxxxx@ntdev…
>>
>> I really need to convince win7 to load the checked ndis.sys. Is there any
>> hope that the ‘debug’ boot loader in win7 actually works with windbg and
>> will load boot load drivers?
>>
>
> —
> NTDEV is sponsored by OSR
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
>

How’d you guess that?

Then just replace ndis.sys itself and see if that works (or use .kdfiles
apparently, good to hear boot time replacement is fixed).

-scott


Scott Noone
Consulting Associate
OSR Open Systems Resources, Inc.
http://www.osronline.com

wrote in message news:xxxxx@ntdev…
> I’m guessing that neither of you have actually tried that with ndis on
> win7.
>
> The answer is yes, I’ve tried it, and it bugchecks in NETIO.SYS. Ndis is a
> port driver and a kernel dll. I’m not convinced having an explicit load of
> ‘ndischk.sys’ while ndis.sys is hanging out in system32\drivers actually
> works. It is also possible that the checked ndis.sys requires checked
> netXXXX.sys components as well, which would be equally horrendous.
>
>

I believe this will work for win7 (although I can’t triple check that I am not misremembering from here).

For boot start drivers, you’d need to enable bootdebug iirc.

The usual requirements re: matching the whole filename still apply.

  • S

-----Original Message-----
From: xxxxx@hollistech.com
Sent: Thursday, February 04, 2010 13:21
To: Windows System Software Devs Interest List
Subject: RE:[ntdev] kdfiles again and again

One can only hope. What I was asking is ‘has anyone gotten this to work, or at least tried and failed?’

The last time this came up, Doron admitted that it was borked in vista but held out hope for win7.


NTDEV is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer

Scott you cannot ‘just replace ndis.sys’ on win7. Well maybe you can. Again - have you tried this?

Yes, that works.

On Windows 7 you can take ownership of system files (some mojo on the
properties page). Then rename the ndis free-build driver (for later
restoration) and copy the ndis checked-build to the drivers folder. No “SFP”
on W7.

I don’t recall any need to have other checked components.

I like the ImagePath solution better.

Thomas F. Divine
http://www.pcausa.com


From:
Sent: Thursday, February 04, 2010 4:53 PM
To: “Windows System Software Devs Interest List”
Subject: RE:[ntdev] kdfiles again and again

> Scott you cannot ‘just replace ndis.sys’ on win7. Well maybe you can.
> Again - have you tried this?
>
>
> —
> NTDEV is sponsored by OSR
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer

I’ve done most wrappers, though not NDIS specifically. I suppose it could be
magically ju-jued and locked down, though the usual trick of taking
ownership and diddling the ACL allowed me to delete it without a problem.

-scott


Scott Noone
Consulting Associate
OSR Open Systems Resources, Inc.
http://www.osronline.com

wrote in message news:xxxxx@ntdev…
> Scott you cannot ‘just replace ndis.sys’ on win7. Well maybe you can.
> Again - have you tried this?
>
>

Well thanks Scott - that last bit actually worked. What a waste of an afternoon. Of course the whole point of this effort was to get ndiskd to work, but actually that doesn’t work either, even with the checked ndis and the public checked os ndis symbols. What a pile of frustratingly stupid barriers.

FYI if there is some trick to convincing win7 to start with bootdebug actually enabled such that windbg connects, I have no idea what that would be either. Not that it matters anymore.

Color Coded Frustration Level: ORANGE.

Sorry for any snidery. I’m pissed at tools and lashing out randomly.

bcdedit /set testsigning on
takeown /f ndis.sys
icacls ndis.sys /grant HOLLISTECH\markr:(F)
copy \someserver\someshare\somedirectory\ndis.sys
shutdown -r -t 0


Jake Oshins
Hyper-V I/O Architect
Windows Kernel Group

This post implies no warranties and confers no rights.


wrote in message news:xxxxx@ntdev…
> Scott you cannot ‘just replace ndis.sys’ on win7. Well maybe you can.
> Again - have you tried this?
>
>

Yes that works - but of course ndiskd doesn’t work outside of redmond. Yet another bork’d debugger extension.

Thanks for all the help, I’m back to grovelling through the disassembler looking for clues.

We are working on a fixed ndiskd. Does not help you today, but hopefully some time soon…

d

-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of xxxxx@hollistech.com
Sent: Thursday, February 04, 2010 3:51 PM
To: Windows System Software Devs Interest List
Subject: RE:[ntdev] kdfiles again and again

Yes that works - but of course ndiskd doesn’t work outside of redmond. Yet another bork’d debugger extension.

Thanks for all the help, I’m back to grovelling through the disassembler looking for clues.


NTDEV is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer

NDISKD is hopelessly broken and ‘they’ know about it. Another case of the
tools getting ‘wicked smaaatt’ but nobody realizing that the smarts rely on
symbols that are stripped from the public PDBs.

It has been that way for a long time now. Too bad, NDISKD is actually
useful (well, was actually useful).

Only orange, huh? I would count that as a good day.

Regards,
Dave Cattley

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of xxxxx@hollistech.com
Sent: Thursday, February 04, 2010 6:34 PM
To: Windows System Software Devs Interest List
Subject: RE:[ntdev] kdfiles again and again

Well thanks Scott - that last bit actually worked. What a waste of an
afternoon. Of course the whole point of this effort was to get ndiskd to
work, but actually that doesn’t work either, even with the checked ndis and
the public checked os ndis symbols. What a pile of frustratingly stupid
barriers.

FYI if there is some trick to convincing win7 to start with bootdebug
actually enabled such that windbg connects, I have no idea what that would
be either. Not that it matters anymore.

Color Coded Frustration Level: ORANGE.

Sorry for any snidery. I’m pissed at tools and lashing out randomly.


NTDEV is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer