Please pardon me for stating the obvious, but it appears that you don’t
understand what the meaning of environment is, in this context. In order to
produce a driver for Win98, you need to build it in the Win98 environment.
That is produce by the Win98 DDK. This can be done on Win98, ME, NT4, or
2K, as long as the compiler and DDK are there. The same holds true for
building a W2K driver, you build it in the W2K environment, which is created
by the W2K DDK, which works on any OS. It makes no difference what OS you
do the build on, just what DDK you use.
Phil
* Philip D. Barila | (503) 264-8386
* Intel Corp. | Not speaking for Intel
-----Original Message-----
From: Zhou, James [mailto:xxxxx@asia.adaptec.com]
Sent: Wednesday, September 27, 2000 2:51 AM
To: NT Developers Interest List
Subject: [ntdev] RE: How to load source code in Windbg kernel
Thank you, Raja.
But Win2k DDK suggests to compile the code in Win2k environment. ???
James
-----Original Message-----
From: xxxxx@aol.com [mailto:xxxxx@aol.com]
Sent: Friday, September 22, 2000 3:55 PM
To: NT Developers Interest List
Subject: [ntdev] RE: How to load source code in Windbg kernel
Typical reason: You are using certain function that is not supported in
Windows 98 SE. Compile your code using Win98 DDK.
Raja
<< Another question on Win2k driver.
If I compile my 1394 driver in Win2k DDK on WIn2k system, then the driver
can be loaded in Win2k system. But If I compile the same driver in Win2k
DDK on WIn98SE, then the driver can not be loaded in WIn98SE system. Any
body got any idea?
>>
You are currently subscribed to ntdev as: xxxxx@asia.adaptec.com
To unsubscribe send a blank email to $subst(‘Email.Unsub’)
You are currently subscribed to ntdev as: xxxxx@intel.com
To unsubscribe send a blank email to $subst(‘Email.Unsub’)