One should rethink their design if a kernel-mode driver needs this
information. Otherwise, store a config/info block for each channel/handle
opened to the device on the open call.
Greg
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com]On Behalf Of Michal Vodicka
Sent: Wednesday, November 21, 2001 8:50 PM
To: NT Developers Interest List
Subject: [ntdev] Re: How to access environment variables from KernelMo
de??- ?
From: xxxxx@pdq.net[SMTP:xxxxx@pdq.net]
Reply To: xxxxx@lists.osr.com
Sent: Thursday, November 22, 2001 3:32 AM
To: xxxxx@lists.osr.com
Subject: [ntdev] Re: How to access environment variables from
KernelMode??- ?Environment variables are by their nature
a user-mode entity and a hold-over from older operating systems.
How would you want to store per-process environment in registry? No
hold-over but necessary vehicle. Note it isn’t per-application but
per-process environment. Usually, I have opened several console windows
every one with different environment (for DDK build, Platform SDK build, our
internal build and so on). Fortunately, ms developers use command line
utilities and understand the importance of environment variables 
Best regards,
Michal Vodicka
STMicroelectronics Design and Application s.r.o.
[michal.vodicka@st.com, http:://www.st.com]
You are currently subscribed to ntdev as: xxxxx@pdq.net
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com