Having spent the last two years buried deep inside dynamic data from bridges and C# programs to complete the analysis - it was a bit surprising to be asked about device drivers. (I am the world’s worst at anything like this). We want to connect to a device across Ethernet for human safety reasons, but the DD are in C#.
I could decompile the DLL’s used to manage the device, C# does not protect someone’s code, and then get it working again in Windows 7 with VS2012, just to make sure I could. (On my home computer). But the INF file uses the MSDN Coinstallers.
What do they do?
I still have the OSRUSBFX2 box on my desk and I play with it from time to time. I took me an hour to remember the other day all the steps to get it working on a new computer. I would still like to use it with this device - just for the joy of watching the lights change.
I gave Windows 8 a miss, could not stand the interface. But I just loaded Windows 10 preview on an old box, it really should be called Windows 7.2. it is freaking fast to install. I think they have a winner.
Regards
John
On Oct 18, 2014, at 12:11 PM, xxxxx@gmail.com wrote:
…
We want to connect to a device across Ethernet for human safety reasons, but the DD are in C#.
No, they aren?t. The DLL that wrap the driver might be in C#, but the drivers are not.
I could decompile the DLL’s used to manage the device, C# does not protect someone’s code, and then get it working again in Windows 7 with VS2012, just to make sure I could. (On my home computer). But the INF file uses the MSDN Coinstallers.
What do they do?
?MSDN Coinstallers?? Could you possibly mean KMDF? KMDF and UMDF are implements as frameworks in a DLL. If you write a KMDF or UMDF driver, you need to have the DLL. Since you can?t be guaranteed that the version you need is installed, you have to include the coinstallers. If your version is already present, then the coinstallers don?t do anything.
I gave Windows 8 a miss, could not stand the interface. But I just loaded Windows 10 preview on an old box, it really should be called Windows 7.2. it is freaking fast to install. I think they have a winner.
The Windows 10 interface is just Windows 8.1 with the ?start? menu added back in.
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.
The coinstallers install the wdf runtime
d
Bent from my phone
From: xxxxx@gmail.commailto:xxxxx
Sent: ?10/?18/?2014 12:12 PM
To: Windows System Software Devs Interest Listmailto:xxxxx
Subject: [ntdev] WDFCoinstaller
Having spent the last two years buried deep inside dynamic data from bridges and C# programs to complete the analysis - it was a bit surprising to be asked about device drivers. (I am the world’s worst at anything like this). We want to connect to a device across Ethernet for human safety reasons, but the DD are in C#.
I could decompile the DLL’s used to manage the device, C# does not protect someone’s code, and then get it working again in Windows 7 with VS2012, just to make sure I could. (On my home computer). But the INF file uses the MSDN Coinstallers.
What do they do?
I still have the OSRUSBFX2 box on my desk and I play with it from time to time. I took me an hour to remember the other day all the steps to get it working on a new computer. I would still like to use it with this device - just for the joy of watching the lights change.
I gave Windows 8 a miss, could not stand the interface. But I just loaded Windows 10 preview on an old box, it really should be called Windows 7.2. it is freaking fast to install. I think they have a winner.
Regards
John
—
NTDEV is sponsored by OSR
Visit the list at: http://www.osronline.com/showlists.cfm?list=ntdev
OSR is HIRING!! See http://www.osr.com/careers
For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars
To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer</mailto:xxxxx></mailto:xxxxx>