I’ve decided to jump into the world of driver development after having read this group
for about a year now. As I tend to learn best from jumping in head first and learning
through nessecity, i’ve decided to write my first kernel-mode code. I really want to
write a ramdisk driver for win2k+ that is dynamically loadable/unloadable via some
sort of method (not legacy hence 2k+ 
). I was basically wondering and asking input
on what would be the best way to go about designing this driver, like what would be the
best way to ‘store’ the data in memory? A section object? a disk file? a huge buffer from
ExAllocate… and friends? Don’t get me wrong, i dont want you guys to write it for me,
im just looking for some input on how to start about designing this thing first on paper
before i start coding so i can iron out design and potential implementation flaws before
i start having blue screens more often than the normal windows screens. so if anyone has
any tips/hints/advice/lessons learned regarding driver dev in general, or advice as to
a good implementation, feel free to let me know. I know it seems jumping writing a ramdisk
would be a rather large first step, but i hate learning slowly.
Asa
A ramdisk isn’t a terrible way to go. There is a good 2k+ ramdisk
sample provided by Microsoft, and I suggest you download and study
that. IIRC, there was a pre-PNP ramdisk sample somewhere as well,
which is also instructive.
Good luck.
-sd
Steve Dispensa
MVP - Windows DDK
www.kernelmustard.com
On Oct 20, 2004, at 10:57 PM, Asa Yeamans wrote:
I’ve decided to jump into the world of driver development after having
read this group
for about a year now. As I tend to learn best from jumping in head
first and learning
through nessecity, i’ve decided to write my first kernel-mode code. I
really want to
write a ramdisk driver for win2k+ that is dynamically
loadable/unloadable via some
sort of method (not legacy hence 2k+ ). I was basically wondering
and asking input
on what would be the best way to go about designing this driver, like
what would be the
best way to ‘store’ the data in memory? A section object? a disk file?
a huge buffer from
ExAllocate… and friends? Don’t get me wrong, i dont want you guys to
write it for me,
im just looking for some input on how to start about designing this
thing first on paper
before i start coding so i can iron out design and potential
implementation flaws before
i start having blue screens more often than the normal windows
screens. so if anyone has
any tips/hints/advice/lessons learned regarding driver dev in general,
or advice as to
a good implementation, feel free to let me know. I know it seems
jumping writing a ramdisk
would be a rather large first step, but i hate learning slowly.
Asa
Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256
You are currently subscribed to ntdev as: unknown lmsubst tag
argument: ‘’
To unsubscribe send a blank email to xxxxx@lists.osr.com