Building a driver via winddk

Question

1.00/5 (1 vote)

See more:

Hello,
I'm new in windows driver development.
I modified parallel port driver for windows, I modified the parport file.
I used for building this driver WinDDK (3790.1830), I had a good file system (parport.sys). It work in windows x32 bits and in windows 7 x32 bits.

Without changing any thing in the code of new driver, I tried to build this driver for windows xp x64 and windows 7 x64, but I couldn't have a system file worked well in x64 environment.

For windows x64, I builded my new driver by using these command lines (in Dos)

setenv.bat [path] chk 64
build

I didn't have an error, but windows x64 didn't accept this driver.
I used the new version of WinDDK (7600.16385.1) to build this driver, but i had the same result, windows xp x64 or windows 7 x64 didn't accept this driver.

Someone could help me to build this driver for windows x64, via WINDDK?

Do I have to change something in my code to build this driver for win64?

I created the inf file for win32 and win64 via geninf.exe.

Is there a tool or a program as (geninf) to create an inf file for windows 64?

thank you for help.

Posted 9-Feb-15 4:35am

Member 11137231

Updated 9-Feb-15 4:43am

Add a Solution

Comments

[no name] 9-Feb-15 12:44pm

Some possible clues ...

http://forums.codeguru.com/showthread.php?330444-64-bit-driver-built-with-the-latest-DDK-wouldn-t-load

Member 11137231 10-Feb-15 5:57am

Thans for reply,
I read carefuly this link, but i don't understood what i must to change in the code or in the build file.

I didn't write my driver, I just modified the code of parallel port project in WINDDK (src/kernel/parport).

I copied the path (Parport) from Old version of WINDKK to WINDDK new version, and i tried to build it.

I built it with this option (chk ia64). i had the parport.sys file I didn't have any errors. but windows xp-x64 or 7-x64 don't load.

Anyone have a solution for build the driver for windows x64?

thank for help.

JJMatthews 11-Feb-15 8:09am

Just a guess here, but I had allot of problems when modifying the keyboard driver on Windows XP because of that Windows file protection stuff. Try renaming it, that would rule that out I believe.

Member 11137231 11-Feb-15 8:50am

if you guess rename the file system, i have renamed my driver or my file system by RGParport.sys. I modified the name of system file in sources file.
I didn't have any error in building. I used this parameter to build (setenv.bat [path] chk 64), but windows xp-64 and 7-64 couldn't load this driver. they said the driver does not compatible with 64 system.
I used windows 7 -64 as development environment. I build this driver for windows 32, and i used this parameter to build (setenv.bat [path] chk wxp). I had a very good result, it owrds well in windows xp-32 and 7-32. I built it via WinDDK old version. and now I try to build it for win64 in the old and new WinDDK.

thans very much for your help.

Mike Nordell 12-Feb-15 20:46pm

Have you signed the driver, or otherwise modified the registry on Win7-64 to allow loading unsigned drivers?

Member 11137231 14-Feb-15 7:59am

No, I'm new in driver development, and I don't know how can sign a driver or modify registries in windows for loading unsigned driver. But when I did my driver for windows 32 (XP and 7) I didn't sign this driver and I didn't modify any registry in windows. I used the geninf tool (in old version of WINDDK) to create the inf file. It's work correctly. I used too geninf tool for load the driver for windows 64 but I couldn't load it.
thanks very much for your help.

Mike Nordell 14-Mar-15 3:03am

In 32-bit Windows (Vista and earlier I believe) the signing is optional, while for 64-bit drivers since at least Win7 (but possibly Vista too) it's mandatory.

I could be wrong, but I do believe this is correct, meaning any 64-bit drivers for Win7 and later are REQUIRED to be signed (unless you tell the system at startup to allow unsigned drivers).

There are a quite a few Free Software drivers having been hit by this change, but solved it. See f.ex. imdisk.

++luck;

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

kommuric · Answer 1 · 2015-03-30T12:15:00

Best thing is to sign the drivers with test signature, at least. Please see the following link for documentation.

https://msdn.microsoft.com/en-us/library/windows/hardware/ff553480(v=vs.85).aspx[^]

Alternatively, on Windows 7, while booting, press F8. It should show options to enabled unsigned drivers. This should get you going without needing signed drivers, but remember that this is good for current session only.