checked or free build seems to make no difference in win2000 ddk

device driver

    Sponsored Links

    Next

  • 1. Default struct alignment
    Hi, I found in doc that default struct member alignment (/Zp compiler switch) is 8 bytes. Is it true also for x64 compilations ? Peter
  • 2. using vector
    I am using WDK to build a driver. i want to use vector from STL. i added USE_STL=1 STL_VER=60 in sources and #include <vector>. do i have to add anything else? or is there a other way to add this? In general, what do you have to do to use part of the stl-lib.
  • 3. Windows 7 Multi-touch driver capability discovery and reboot p
    Thanks for the tip, the reboot is due to PNP_VetoOutstandingOpen. Now I know what to look for. Any ideas on the multi-touch capability report inconsistency? G. "Doron Holan [MSFT]" wrote: > have you looked at the device setup logs to see why the reboot is asked for? > > -- > > This posting is provided "AS IS" with no warranties, and confers no rights. > >
  • 4. Windows 7 Multi-touch driver capability discovery and reboot probl
    Hi, I created a Windows 7 multi-touch HID driver based on WDK EloMT sample. The driver works ok but I have the following problems that I don't know how to fix them. 1. After my driver is installed (without reboot), sometimes the computer property shows "Touch Input Available with 2 Touch Points", sometimes it shows "No Pen or Touch Input is available for this display". 2. After my driver is installed, most of the time the system won't ask for reboot but sometimes it will. If anyone can point me the direction of how to solve these inconsistencies it will be highly appreciated. Thanks. G.

checked or free build seems to make no difference in win2000 ddk

Postby Cristian Secara » Fri, 07 Nov 2003 08:36:50 GMT

I am using the Win2000 DDK to build a keyboard driver filter (kbdxx.dll).

The driver compiles and works fine.
My only problem is that - compared to the original Windows keyboard
drivers - the result .dll is too long (~double, even if I mimic an existing
keyboard layout language). The driver appears to have some "garbage" at its
end.

I suspect that the driver is build in "checked" version. However, I don't
know how to make it "free". I tried with the setenv.bat to set either
checked or free version, but the compiled .dll seems to be the same.
How should I check the actual "checked" or "free" status of the compiler ?

Thank you.
Best wishes,
    Cristi



Re: checked or free build seems to make no difference in win2000 ddk

Postby Don Burn » Fri, 07 Nov 2003 09:57:52 GMT

Check the directory where you built it, if there was bldfre.log then it
should have been built with a free build, look at the file for the
compilation switches and see if optization was applied.

-- 
Don Burn (MVP, Windows DDK)
Windows 2k/XP/2k3 Filesystem and Driver Consulting
Remove StopSpam from the email to reply







existing
its



Re: checked or free build seems to make no difference in win2000 ddk

Postby Ramboi2 » Fri, 07 Nov 2003 16:35:43 GMT

To make a free build, you got to open a Free Build environment or type set
under your command line, you will see if you are under free or checked
environment.

Ramboi









Re: checked or free build seems to make no difference in win2000 ddk

Postby Cristian Secara » Sat, 08 Nov 2003 09:42:56 GMT

Don: there is no "bldfre.log" on my computer drive. In fact, the C:\NTDDK
does not contain any *.log file.

Ramboi: a SET command under a given command line prompt does not gives any
information about the build environment, or so it seems to me. Neither
before, nor after manually enter the setenv.bat [param] command.

Strange thing is, the Driver Writers Guide says that
"For Windows 2000, output files are placed underneath a subdirectory named
either \objfre or \objchk, depending on whether you are using the free build
or checked build environment."
However, on my computer the output file is placed only in a subdirectory
named \obj. Either my own driver, or any driver from the original \src
sample
directory.

Cristi









Re: checked or free build seems to make no difference in win2000 ddk

Postby David J. Craig » Sat, 08 Nov 2003 10:46:52 GMT

Provide the EXACT steps you used to install the DDK.  Then provide the steps
you used to invoke the CMD window where you typed 'build -ceZ'.  Have you
read the install and readme files in the DDK's root directory?





build



set



Re: checked or free build seems to make no difference in win2000 ddk

Postby Cristian Secara » Sat, 08 Nov 2003 11:24:05 GMT




No longer needed: I found the reason !

I'm not sure if I can say so, but it may be my fault: I was using a shell
navigator (File Commander, an Australian program) for the sole purpose to
easy navigate through various directories. The program has a feature to easy
hide the panels and lets the user enter any command line. It has also a
powerful command line history - it remembers even after reboot.

But the problem is - it erases the session SET variables. I don't know why.
So my problem was that the "build -cZ" was given with all build session
switches erased.
Now I used the Win2000's Command Prompt (from Start menu) and all is ok.

Thanks for all your help. The failure of checking Ramboi's suggestion to
check the SET environment has put my hair out and took me to the right
direction :)

Cristi



Re: checked or free build seems to make no difference in win2000 ddk

Postby Don Burn » Sat, 08 Nov 2003 12:01:52 GMT

Are you sure this is a Win2k DDK, this sounds like an NT DDK.  There should
be a log file
of some sort in your build directory.


-- 
Don Burn (MVP, Windows DDK)
Windows 2k/XP/2k3 Filesystem and Driver Consulting
Remove StopSpam from the email to reply





build



set



Re: checked or free build seems to make no difference in win2000 ddk

Postby Cristian Secara » Sat, 08 Nov 2003 12:29:35 GMT




Yes, I am sure it is the Windows 2000 DDK. It also includes the WinME device
driver environment.
It defaults to x:\NTDDK at the time of install. In fact, the default
makefile.def has few wrong path parameters (like it assumes the install
directory is NT) which I presume are mistakenly left out from the old NT
DDK.

Cristi



Similar Threads:

1.Differences between DDK build 3790.1830 and WDK build 6001.180

2.Differences between DDK build 3790.1830 and WDK build 6001.18000

3.Getting Free drivers makes a huge difference.

4.Checked build driver with free build OS....

Hi,

I know, to help debugging, its required to have the windows checked 
build and with checked build driver (driver under development). But what 
happens if checked build driver is loaded and used with free build os ? 
(XP SP2).

As far as I know, the checked build driver
1. Does not have optimization enabled
2. Lots of DbgPrint
3. The size of the binary is huge (because of symbols and etc).
3. The driver will be slow.

Are there anything more to add to the above list ? If I manage to remove 
all the prints and if the driver is meeting the performance criterion, 
is it advisable to deploy the checked build driver with free build OS ?

Regards
Esha

5.A bug check build don't appear but free build does

Dear all:

      My driver is an atapi driver. 
      Using HCT 12.1 , free build
      Selected System -> Mother Board
      After gathing all infomation ready to test
      then Stand by (S3)
      Click test buttom will reboot within 5 seconds.
      But when I use check build, there's no reboot.
      Senior Enginner told me it may be timing issue.

      The problem is I couldn't see any message using check build.
      What else I can do ?

6. Checked build vs. Free build

7. Differences between checked and free versions of a driver

8. PCI device behaves differently in checked and free build



Return to device driver

 

Who is online

Users browsing this forum: No registered users and 52 guest