Windows System Software -- Consulting, Training, Development -- Unique Expertise, Guaranteed Results
Before Posting...
Please check out the Community Guidelines in the Announcements and Administration Category.More Info on Driver Writing and Debugging
The free OSR Learning Library has more than 50 articles on a wide variety of topics about writing and debugging device drivers and Minifilters. From introductory level to advanced. All the articles have been recently reviewed and updated, and are written using the clear and definitive style you've come to expect from OSR over the years.
Check out The OSR Learning Library at: https://www.osr.com/osr-learning-library/
storport.sys source project
OSR_Community_User
Member Posts: 110,217
in NTDEV
I read somewhere that the source code for storport.sys, including the code for the windows 10 version, was available for driver developers to assist in writing new storage drivers. Finding that little nugget again feels as if I am looking for a needle in a field of haystacks. Can you help me locate that project please?
Howdy, Stranger!
| Upcoming OSR Seminars | ||
|---|---|---|
| OSR has suspended in-person seminars due to the Covid-19 outbreak. But, don't miss your training! Attend via the internet instead! | ||
| Internals & Software Drivers | 19-23 June 2023 | Live, Online |
| Writing WDF Drivers | 10-14 July 2023 | Live, Online |
| Kernel Debugging | 16-20 October 2023 | Live, Online |
| Developing Minifilters | 13-17 November 2023 | Live, Online |
Comments
Cheers,
Gabriel
www.kasardia.com
[1] https://github.com/Microsoft/Windows-driver-samples/tree/master/storage
On Mon, Jan 29, 2018 at 8:19 PM, [email protected]
wrote:
> I read somewhere that the source code for storport.sys, including the code
> for the windows 10 version, was available for driver developers to assist
> in writing new storage drivers. Finding that little nugget again feels as
> if I am looking for a needle in a field of haystacks. Can you help me
> locate that project please?
>
> ---
> NTDEV is sponsored by OSR
>
> Visit the list online at: showlists.cfm?list=ntdev>
>
> MONTHLY seminars on crash dump analysis, WDF, Windows internals and
> software drivers!
> Details at
>
> To unsubscribe, visit the List Server section of OSR Online at <
> http://www.osronline.com/page.cfm?name=ListServer>
>
--
Bercea. G.
Cheers,
Gabriel
In hindsight, I'm not sure there were any debugging problems I was able to solve with source code access that I could not have solved, with more effort and time, without source code access. Being very comfortable digging though assembler helps a lot, as does fast single stepping (1394 transport).
Not so long ago, I was working for a very large vendor of storage controller chips, which had a number of Windows kernel developers, and they did not have direct access to storport source code, although did have an employee who had good technical support contacts inside Microsoft.
The Microsoft policy on source code access has varied over the years. At one point all you needed was 10,000 Windows seats in your company, and you could get read access to the source code for debugging purposes. At the other end of the scale, many years ago, Microsoft gave a select few individual MVP kernel developers source access. I'm not sure what the official policy is today, but unless you work at a mega corporation that owns or sells a lot of copies of Windows (or you work at Microsoft, on the correct team), source access is likely not available.
Jan
-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf Of [email protected]
Sent: Monday, January 29, 2018 11:19 AM
To: Windows System Software Devs Interest List <[email protected]>
Subject: [ntdev] storport.sys source project
I read somewhere that the source code for storport.sys, including the code for the windows 10 version, was available for driver developers to assist in writing new storage drivers. Finding that little nugget again feels as if I am looking for a needle in a field of haystacks. Can you help me locate that project please?
---
NTDEV is sponsored by OSR
Visit the list online at: <http://www.osronline.com/showlists.cfm?list=ntdev>
MONTHLY seminars on crash dump analysis, WDF, Windows internals and software drivers!
Details at <http://www.osr.com/seminars>
To unsubscribe, visit the List Server section of OSR Online at <http://www.osronline.com/page.cfm?name=ListServer>
immensely valuable and saved many hours of debugging time on many problems.
You of course need to understand the source code organization, as indeed
otherwise blindly searching 80 million lines of code every time you needed
to figure something out would be horrible. Also note that windbg is happy
to point one at the source code for stackframes if you have the pdb files
and the source code.
Mark Roddy
On Wed, Jan 31, 2018 at 3:12 AM, [email protected] wrote:
> When I worked at one of the largest computer vendors a few years ago, a
> small number of us did have Windows source code access. You did almost have
> to sign your life away in the NDA. Having source access was occasionally
> moderately useful, but not as useful as one might think. Just finding the
> correct location in 80 million lines of code was often a major adventure.
> We also didn't get the source code in a form you could modify or build.
>
> In hindsight, I'm not sure there were any debugging problems I was able to
> solve with source code access that I could not have solved, with more
> effort and time, without source code access. Being very comfortable digging
> though assembler helps a lot, as does fast single stepping (1394 transport).
>
> Not so long ago, I was working for a very large vendor of storage
> controller chips, which had a number of Windows kernel developers, and they
> did not have direct access to storport source code, although did have an
> employee who had good technical support contacts inside Microsoft.
>
> The Microsoft policy on source code access has varied over the years. At
> one point all you needed was 10,000 Windows seats in your company, and you
> could get read access to the source code for debugging purposes. At the
> other end of the scale, many years ago, Microsoft gave a select few
> individual MVP kernel developers source access. I'm not sure what the
> official policy is today, but unless you work at a mega corporation that
> owns or sells a lot of copies of Windows (or you work at Microsoft, on the
> correct team), source access is likely not available.
>
> Jan
>
>
> -----Original Message-----
> From: [email protected] [mailto:[email protected]
> lists.osr.com] On Behalf Of [email protected]
> Sent: Monday, January 29, 2018 11:19 AM
> To: Windows System Software Devs Interest List
> Subject: [ntdev] storport.sys source project
>
> I read somewhere that the source code for storport.sys, including the code
> for the windows 10 version, was available for driver developers to assist
> in writing new storage drivers. Finding that little nugget again feels as
> if I am looking for a needle in a field of haystacks. Can you help me
> locate that project please?
>
> ---
> NTDEV is sponsored by OSR
>
> Visit the list online at: showlists.cfm?list=ntdev>
>
> MONTHLY seminars on crash dump analysis, WDF, Windows internals and
> software drivers!
> Details at
>
> To unsubscribe, visit the List Server section of OSR Online at <
> http://www.osronline.com/page.cfm?name=ListServer>
>
> ---
> NTDEV is sponsored by OSR
>
> Visit the list online at: showlists.cfm?list=ntdev>
>
> MONTHLY seminars on crash dump analysis, WDF, Windows internals and
> software drivers!
> Details at
>
> To unsubscribe, visit the List Server section of OSR Online at <
> http://www.osronline.com/page.cfm?name=ListServer>
>
Whereas, in Apple Platform, stepping thru the kernel to vendor specific code is fairly easy - though the native debugger is not as powerful as Windbg.
-Pro
> On Feb 4, 2018, at 10:57 AM, [email protected] wrote:
>
> Well my experience was just the opposite. Having source code access was immensely valuable and saved many hours of debugging time on many problems. You of course need to understand the source code organization, as indeed otherwise blindly searching 80 million lines of code every time you needed to figure something out would be horrible. Also note that windbg is happy to point one at the source code for stackframes if you have the pdb files and the source code.
>
>
>
> Mark Roddy
>
> On Wed, Jan 31, 2018 at 3:12 AM, [email protected] > wrote:
> When I worked at one of the largest computer vendors a few years ago, a small number of us did have Windows source code access. You did almost have to sign your life away in the NDA. Having source access was occasionally moderately useful, but not as useful as one might think. Just finding the correct location in 80 million lines of code was often a major adventure. We also didn't get the source code in a form you could modify or build.
>
> In hindsight, I'm not sure there were any debugging problems I was able to solve with source code access that I could not have solved, with more effort and time, without source code access. Being very comfortable digging though assembler helps a lot, as does fast single stepping (1394 transport).
>
> Not so long ago, I was working for a very large vendor of storage controller chips, which had a number of Windows kernel developers, and they did not have direct access to storport source code, although did have an employee who had good technical support contacts inside Microsoft.
>
> The Microsoft policy on source code access has varied over the years. At one point all you needed was 10,000 Windows seats in your company, and you could get read access to the source code for debugging purposes. At the other end of the scale, many years ago, Microsoft gave a select few individual MVP kernel developers source access. I'm not sure what the official policy is today, but unless you work at a mega corporation that owns or sells a lot of copies of Windows (or you work at Microsoft, on the correct team), source access is likely not available.
>
> Jan
>
>
> -----Original Message-----
> From: [email protected] [mailto:[email protected] ] On Behalf Of [email protected]
> Sent: Monday, January 29, 2018 11:19 AM
> To: Windows System Software Devs Interest List >
> Subject: [ntdev] storport.sys source project
>
> I read somewhere that the source code for storport.sys, including the code for the windows 10 version, was available for driver developers to assist in writing new storage drivers. Finding that little nugget again feels as if I am looking for a needle in a field of haystacks. Can you help me locate that project please?
>
> ---
> NTDEV is sponsored by OSR
>
> Visit the list online at: >
>
> MONTHLY seminars on crash dump analysis, WDF, Windows internals and software drivers!
> Details at >
>
> To unsubscribe, visit the List Server section of OSR Online at >
>
> ---
> NTDEV is sponsored by OSR
>
> Visit the list online at: >
>
> MONTHLY seminars on crash dump analysis, WDF, Windows internals and software drivers!
> Details at >
>
> To unsubscribe, visit the List Server section of OSR Online at >
>
> --- NTDEV is sponsored by OSR Visit the list online at: MONTHLY seminars on crash dump analysis, WDF, Windows internals and software drivers! Details at To unsubscribe, visit the List Server section of OSR Online at
Mr. Roddy wrote:
<quote>
Well my experience was just the opposite. Having source code access was
immensely valuable and saved many hours of debugging time on many problems.
</quote>
This.
I'll never forget the first day I had access to the Windows source code. The first task I set for myself was to discover why you had to both call IoMarkIrpPending AND return STATUS_PENDING from your dispatch entry point. I figured it'd take me a couple of hours, and this was something I *always* wanted to understand.
It took me two years to answer that question. And probably another two years to fully appreciate the consequences of that answer. Seriously.
The Windows source code is just like any really large and really complex code base: it's super easy to get lost looking for what you think is a simple answer to a simple question. The code is naturally full of acronyms, abbreviations, and technical details. It's not designed for learners. Not to mention, the overall source code base spans a large number of very different technical disciplines. You have to know *a lot* about how each piece of Windows works (what features are provided and how those features can be used) before you can understand how that piece is implemented.
The journey, to me at least, was totally worth it.
Peter
OSR
@OSRDrivers
Peter Viscarola
OSR
@OSRDrivers