16,016,022 members
Sign in
Sign in
Email
Password
Forgot your password?
Sign in with
home
articles
Browse Topics
>
Latest Articles
Top Articles
Posting/Update Guidelines
Article Help Forum
Submit an article or tip
Import GitHub Project
Import your Blog
quick answers
Q&A
Ask a Question
View Unanswered Questions
View All Questions
View C# questions
View C++ questions
View Javascript questions
View Visual Basic questions
View .NET questions
discussions
forums
CodeProject.AI Server
All Message Boards...
Application Lifecycle
>
Running a Business
Sales / Marketing
Collaboration / Beta Testing
Work Issues
Design and Architecture
Artificial Intelligence
ASP.NET
JavaScript
Internet of Things
C / C++ / MFC
>
ATL / WTL / STL
Managed C++/CLI
C#
Free Tools
Objective-C and Swift
Database
Hardware & Devices
>
System Admin
Hosting and Servers
Java
Linux Programming
Python
.NET (Core and Framework)
Android
iOS
Mobile
WPF
Visual Basic
Web Development
Site Bugs / Suggestions
Spam and Abuse Watch
features
features
Competitions
News
The Insider Newsletter
The Daily Build Newsletter
Newsletter archive
Surveys
CodeProject Stuff
community
lounge
Who's Who
Most Valuable Professionals
The Lounge
The CodeProject Blog
Where I Am: Member Photos
The Insider News
The Weird & The Wonderful
help
?
What is 'CodeProject'?
General FAQ
Ask a Question
Bugs and Suggestions
Article Help Forum
About Us
Search within:
Articles
Quick Answers
Messages
Comments by Member 11137231 (Top 3 by date)
Member 11137231
14-Feb-15 7:59am
View
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.
Member 11137231
11-Feb-15 8:50am
View
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.
Member 11137231
10-Feb-15 5:57am
View
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.