Hello,
I am trying to write my first driver for Windows 2000. The driver does nothing at the moment. The DriverEntry-function returns 0 ("all ok") and that's it. I wrote an *.inf file but something seems to be wrong about it because Windows is unable to read the date.
[ external image ]
The date is in the same line as the version, but Windows has no problem reading the version. Does someone know what's wrong?
http://ontheserver.de/temp/2020-01-24/graphic.inf
http://ontheserver.de/temp/2020-01-24/graphic.sys
Thank you!
Gary
[solved] writing a driver: why does Windows not know the date
Moderator: Moderator Team
[solved] writing a driver: why does Windows not know the date
Last edited by Gary on Sat Jan 25, 2020 1:26 pm, edited 1 time in total.
Re: writing a driver: why does Windows not know the date
Try removing the space after the comma?
Re: writing a driver: why does Windows not know the date
Thank you for the response. The space was/is legal according to the syntax. I just checked it anyway but my test confirmed that removing the space makes no difference.
I checked the documentation and found that according to the documentation a driver needs to be digitally signed. If it is not signed then the date is replaced by 00/00/0000. In reality it seems as the date is simply not added to the registry. So I added 2 keys manually:
- DriverDate and
- DriverDateData
I just took the exact names for these keys and values from someone else's driver and from then on the device manager showed the date (from the driver I used as source). To fix this issue I will probably just add an instruction to the inf file to add the register keys (kind of manually adding what the driver installation procedure ignored).
The key DriverDateData seems to hold a Windows timestamp of the value in DriverDate.
I checked the documentation and found that according to the documentation a driver needs to be digitally signed. If it is not signed then the date is replaced by 00/00/0000. In reality it seems as the date is simply not added to the registry. So I added 2 keys manually:
- DriverDate and
- DriverDateData
I just took the exact names for these keys and values from someone else's driver and from then on the device manager showed the date (from the driver I used as source). To fix this issue I will probably just add an instruction to the inf file to add the register keys (kind of manually adding what the driver installation procedure ignored).
The key DriverDateData seems to hold a Windows timestamp of the value in DriverDate.
-
- Posts: 215
- Joined: Wed Feb 21, 2018 3:46 pm
- Location: Somewhere in France
Re: [solved] writing a driver: why does Windows not know the date
Try with a date before 2000 to be sure it's not a problem of the date (like the Year 2000 Problem).
Re: [solved] writing a driver: why does Windows not know the date
@shunesburg: Are you serious?
-
- Posts: 215
- Joined: Wed Feb 21, 2018 3:46 pm
- Location: Somewhere in France
-
- Posts: 43
- Joined: Tue May 26, 2020 5:30 pm
Re: [solved] writing a driver: why does Windows not know the date
What year 2000 problem? If I may ask.shunesburg wrote: ↑Mon Jan 27, 2020 2:41 pm Try with a date before 2000 to be sure it's not a problem of the date (like the Year 2000 Problem).
-
- Posts: 215
- Joined: Wed Feb 21, 2018 3:46 pm
- Location: Somewhere in France
Re: [solved] writing a driver: why does Windows not know the date
It's a joke because, before 2000 in the XXth century, there is a bug with the changing of date (1900 -> 2000).
-
- Posts: 43
- Joined: Tue May 26, 2020 5:30 pm
Re: [solved] writing a driver: why does Windows not know the date
The 32 bit version of the 2030 problem. (If I remember right.)
My name is MinecraftChest1.
I am a Windows and Linux user.
I have broken reactos once.
That's my resume.
I am a Windows and Linux user.
I have broken reactos once.
That's my resume.
Who is online
Users browsing this forum: No registered users and 14 guests