Running chkinf against against my inf file has been most helpful - wish I’d don’t it earlier!
In an attempt to catch any other issues I ran inf2cat in verbose mode and got:
Warnings:
22.9.3: Missing hardware ID (cannot have just compatible ID) in line %usb\vid_05ff&pid_001a.devicedesc%=lectouch_inst,,u
sb\vid_05ff&pid_001a in section [lecroytouch.ntx86] of \lectouch.inf
22.9.3: Missing hardware ID (cannot have just compatible ID) in line %usb\vid_05ff&pid_002a.devicedesc%=lectouch_inst,,u
sb\vid_05ff&pid_002a in section [lecroytouch.ntx86] of \lectouch.inf
What do these warnings mean?
Thanks
David
To answer my own post I just realised that I had too many commas!
I think the lines in question should have read:
%USB\VID_05FF&PID_001A.DeviceDesc%=LecTouch_Inst, USB\VID_05FF&PID_001A
%USB\VID_05FF&PID_002A.DeviceDesc%=LecTouch_Inst, USB\VID_05FF&PID_002A
D
Chkinf has been superseded by a new tool, infverif, in recent WDKs. You should use the new tool to verify your INF.
I’m building this for Windows 7 as that is what is running on the oscilloscope. For that I am using WDK7.1 It seems a bit excessive to install a complete WDK I can’t otherwise use for running infverif (unless of course it really is that much better).
For that I am using WDK7.1
Nothing terribly wrong with that. OTOH, if it were ME, I’d be using VS 2019 and the Windows 11 WDK… and targeting Windows 7.
Better tools.
Peter
AFAICT The windows 10 and 11 WDKs won’t let you target Win 7
D.
Sure it will. That’s why I suggested it.
Peter