How do you find out the INF file that is being used when you plug in a device in WindowsWindows 7 driver...

What does an unprocessed RAW file look like?

Can we "borrow" our answers to populate our own websites?

Why did Luke use his left hand to shoot?

Does the US government have any planning in place to ensure there's no shortages of food, fuel, steel and other commodities?

Do authors have to be politically correct in article-writing?

Square Root Distance from Integers

Translation needed for 130 years old church document

Why does 0.-5 evaluate to -5?

Coworker asking me to not bring cakes due to self control issue. What should I do?

How to delete duplicate text from a file?

How do you get out of your own psychology to write characters?

Does diversity provide anything that meritocracy does not?

Which RAF squadrons and aircraft types took part in the bombing of Berlin on the 25th of August 1940?

How can I play a serial killer in a party of good PCs?

Why didn't Tom Riddle take the presence of Fawkes and the Sorting Hat as more of a threat?

How do you voice extended chords?

Best way to strengthen a wheel?

Why does magnet wire need to be insulated?

"Starve to death" Vs. "Starve to the point of death"

Does it take energy to move something in a circle?

Prioritising polygons in QGIS

How to politely refuse in-office gym instructor for steroids and protein

Book where a space ship journeys to the center of the galaxy to find all the stars had gone supernova

What is a good reason for every spaceship to carry a weapon on board?



How do you find out the INF file that is being used when you plug in a device in Windows


Windows 7 driver search woefully slowHow can I find out what chip is used in USB <-> Serial (RS232) converter from FTDI?How to completely remove all the driver files associated with a USB deviceHow to check inf manufacturerInstall Samsung Android Note 2 MTP INF driver for Win XP in to Win7 - Win10 is using the same exact driver?Debugging INF file to install in Win 10WinUsb driver doesn't installHow can I find out the USB Bandwidth usage of device in Windows 10Find corresponding .INF file for device driverHow do I get Windows 7 driver automatically installed?













1















How do you find out the INF file that is being used when you plug in a device
in windows .



We are plugging in a USB modem and it tries to install the MBB USB Drivers and then throws a error "INF written for Windows 95 or later, driver missing entry file" . Well i am installing the driver on windows XP which is later than windows 95 , so not sure what exactly is wrong .



i want to find out exactly which inf file windows is picking up and then maybe i can change the signature entry to $WindowsNT$ .



any thoughts here ..



while we are at the topic of device drivers . Could anyone please suggest a good book for windows device drivers . Something which is from ground up and covers a lot of basics .










share|improve this question














bumped to the homepage by Community 5 mins ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.






migrated from stackoverflow.com Jun 27 '11 at 5:17


This question came from our site for professional and enthusiast programmers.























    1















    How do you find out the INF file that is being used when you plug in a device
    in windows .



    We are plugging in a USB modem and it tries to install the MBB USB Drivers and then throws a error "INF written for Windows 95 or later, driver missing entry file" . Well i am installing the driver on windows XP which is later than windows 95 , so not sure what exactly is wrong .



    i want to find out exactly which inf file windows is picking up and then maybe i can change the signature entry to $WindowsNT$ .



    any thoughts here ..



    while we are at the topic of device drivers . Could anyone please suggest a good book for windows device drivers . Something which is from ground up and covers a lot of basics .










    share|improve this question














    bumped to the homepage by Community 5 mins ago


    This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.






    migrated from stackoverflow.com Jun 27 '11 at 5:17


    This question came from our site for professional and enthusiast programmers.





















      1












      1








      1








      How do you find out the INF file that is being used when you plug in a device
      in windows .



      We are plugging in a USB modem and it tries to install the MBB USB Drivers and then throws a error "INF written for Windows 95 or later, driver missing entry file" . Well i am installing the driver on windows XP which is later than windows 95 , so not sure what exactly is wrong .



      i want to find out exactly which inf file windows is picking up and then maybe i can change the signature entry to $WindowsNT$ .



      any thoughts here ..



      while we are at the topic of device drivers . Could anyone please suggest a good book for windows device drivers . Something which is from ground up and covers a lot of basics .










      share|improve this question














      How do you find out the INF file that is being used when you plug in a device
      in windows .



      We are plugging in a USB modem and it tries to install the MBB USB Drivers and then throws a error "INF written for Windows 95 or later, driver missing entry file" . Well i am installing the driver on windows XP which is later than windows 95 , so not sure what exactly is wrong .



      i want to find out exactly which inf file windows is picking up and then maybe i can change the signature entry to $WindowsNT$ .



      any thoughts here ..



      while we are at the topic of device drivers . Could anyone please suggest a good book for windows device drivers . Something which is from ground up and covers a lot of basics .







      windows drivers inf






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Jun 27 '11 at 3:53







      user66854












      bumped to the homepage by Community 5 mins ago


      This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.







      bumped to the homepage by Community 5 mins ago


      This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.






      migrated from stackoverflow.com Jun 27 '11 at 5:17


      This question came from our site for professional and enthusiast programmers.









      migrated from stackoverflow.com Jun 27 '11 at 5:17


      This question came from our site for professional and enthusiast programmers.
























          1 Answer
          1






          active

          oldest

          votes


















          0














          Just because you change the signature to Windows NT doesn't magically transform the driver into an NT driver. The driver model that is used by Windows NT is significantly different from Windows 9x, different enough to require that many devices use completely different drivers for the two operating systems.



          Granted, the error message is slightly confusing because XP is indeed "later" that Windows 95, but it is not a newer version of Windows 95. That would be either Windows 98 or Me. You need to find a driver that is written for Windows 2000 or XP, both based on the Windows NT code-base.



          But if the driver's INF file that you have now has the signature $Windows 95$, then you can be sure that it is not an NT driver, and it will not magically become one by changing that to $Windows NT$.





          As for general instruction on understanding and writing device drivers, check out the answers to these questions:




          • https://stackoverflow.com/questions/4288582/windows-nt-device-driver-development-book

          • https://stackoverflow.com/questions/3369160/best-book-for-learning-windows-device-driver-development


          But fair warning: the driver model changed again in Windows Vista. If you want to write drivers for devices that run on Windows Vista and 7, you'll need to make sure that you're learning about the updated model. If you still need the drivers to support legacy operating systems like Windows 2000/XP, then you'll need to stick with an older resource that talks about those operating systems.






          share|improve this answer


























          • Raymon Chen is lucky not to have said what you said, because he would then have been wrong. It is, after all, not DOS+Windows 95 issuing the error message about the INF file, but the newer operating system in question itself, which was known to come after DOS+Windows 95 from the get-go.

            – JdeBP
            Jun 27 '11 at 9:12











          • WDM drivers work on both Win 9x and Windows XP. Also some classes of drivers had incompatible changes in Vista, but not all of them.

            – John
            Jun 27 '11 at 21:24











          Your Answer








          StackExchange.ready(function() {
          var channelOptions = {
          tags: "".split(" "),
          id: "3"
          };
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function() {
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled) {
          StackExchange.using("snippets", function() {
          createEditor();
          });
          }
          else {
          createEditor();
          }
          });

          function createEditor() {
          StackExchange.prepareEditor({
          heartbeatType: 'answer',
          autoActivateHeartbeat: false,
          convertImagesToLinks: true,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: 10,
          bindNavPrevention: true,
          postfix: "",
          imageUploader: {
          brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
          contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
          allowUrls: true
          },
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          });


          }
          });














          draft saved

          draft discarded


















          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f302654%2fhow-do-you-find-out-the-inf-file-that-is-being-used-when-you-plug-in-a-device-in%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown
























          1 Answer
          1






          active

          oldest

          votes








          1 Answer
          1






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes









          0














          Just because you change the signature to Windows NT doesn't magically transform the driver into an NT driver. The driver model that is used by Windows NT is significantly different from Windows 9x, different enough to require that many devices use completely different drivers for the two operating systems.



          Granted, the error message is slightly confusing because XP is indeed "later" that Windows 95, but it is not a newer version of Windows 95. That would be either Windows 98 or Me. You need to find a driver that is written for Windows 2000 or XP, both based on the Windows NT code-base.



          But if the driver's INF file that you have now has the signature $Windows 95$, then you can be sure that it is not an NT driver, and it will not magically become one by changing that to $Windows NT$.





          As for general instruction on understanding and writing device drivers, check out the answers to these questions:




          • https://stackoverflow.com/questions/4288582/windows-nt-device-driver-development-book

          • https://stackoverflow.com/questions/3369160/best-book-for-learning-windows-device-driver-development


          But fair warning: the driver model changed again in Windows Vista. If you want to write drivers for devices that run on Windows Vista and 7, you'll need to make sure that you're learning about the updated model. If you still need the drivers to support legacy operating systems like Windows 2000/XP, then you'll need to stick with an older resource that talks about those operating systems.






          share|improve this answer


























          • Raymon Chen is lucky not to have said what you said, because he would then have been wrong. It is, after all, not DOS+Windows 95 issuing the error message about the INF file, but the newer operating system in question itself, which was known to come after DOS+Windows 95 from the get-go.

            – JdeBP
            Jun 27 '11 at 9:12











          • WDM drivers work on both Win 9x and Windows XP. Also some classes of drivers had incompatible changes in Vista, but not all of them.

            – John
            Jun 27 '11 at 21:24
















          0














          Just because you change the signature to Windows NT doesn't magically transform the driver into an NT driver. The driver model that is used by Windows NT is significantly different from Windows 9x, different enough to require that many devices use completely different drivers for the two operating systems.



          Granted, the error message is slightly confusing because XP is indeed "later" that Windows 95, but it is not a newer version of Windows 95. That would be either Windows 98 or Me. You need to find a driver that is written for Windows 2000 or XP, both based on the Windows NT code-base.



          But if the driver's INF file that you have now has the signature $Windows 95$, then you can be sure that it is not an NT driver, and it will not magically become one by changing that to $Windows NT$.





          As for general instruction on understanding and writing device drivers, check out the answers to these questions:




          • https://stackoverflow.com/questions/4288582/windows-nt-device-driver-development-book

          • https://stackoverflow.com/questions/3369160/best-book-for-learning-windows-device-driver-development


          But fair warning: the driver model changed again in Windows Vista. If you want to write drivers for devices that run on Windows Vista and 7, you'll need to make sure that you're learning about the updated model. If you still need the drivers to support legacy operating systems like Windows 2000/XP, then you'll need to stick with an older resource that talks about those operating systems.






          share|improve this answer


























          • Raymon Chen is lucky not to have said what you said, because he would then have been wrong. It is, after all, not DOS+Windows 95 issuing the error message about the INF file, but the newer operating system in question itself, which was known to come after DOS+Windows 95 from the get-go.

            – JdeBP
            Jun 27 '11 at 9:12











          • WDM drivers work on both Win 9x and Windows XP. Also some classes of drivers had incompatible changes in Vista, but not all of them.

            – John
            Jun 27 '11 at 21:24














          0












          0








          0







          Just because you change the signature to Windows NT doesn't magically transform the driver into an NT driver. The driver model that is used by Windows NT is significantly different from Windows 9x, different enough to require that many devices use completely different drivers for the two operating systems.



          Granted, the error message is slightly confusing because XP is indeed "later" that Windows 95, but it is not a newer version of Windows 95. That would be either Windows 98 or Me. You need to find a driver that is written for Windows 2000 or XP, both based on the Windows NT code-base.



          But if the driver's INF file that you have now has the signature $Windows 95$, then you can be sure that it is not an NT driver, and it will not magically become one by changing that to $Windows NT$.





          As for general instruction on understanding and writing device drivers, check out the answers to these questions:




          • https://stackoverflow.com/questions/4288582/windows-nt-device-driver-development-book

          • https://stackoverflow.com/questions/3369160/best-book-for-learning-windows-device-driver-development


          But fair warning: the driver model changed again in Windows Vista. If you want to write drivers for devices that run on Windows Vista and 7, you'll need to make sure that you're learning about the updated model. If you still need the drivers to support legacy operating systems like Windows 2000/XP, then you'll need to stick with an older resource that talks about those operating systems.






          share|improve this answer















          Just because you change the signature to Windows NT doesn't magically transform the driver into an NT driver. The driver model that is used by Windows NT is significantly different from Windows 9x, different enough to require that many devices use completely different drivers for the two operating systems.



          Granted, the error message is slightly confusing because XP is indeed "later" that Windows 95, but it is not a newer version of Windows 95. That would be either Windows 98 or Me. You need to find a driver that is written for Windows 2000 or XP, both based on the Windows NT code-base.



          But if the driver's INF file that you have now has the signature $Windows 95$, then you can be sure that it is not an NT driver, and it will not magically become one by changing that to $Windows NT$.





          As for general instruction on understanding and writing device drivers, check out the answers to these questions:




          • https://stackoverflow.com/questions/4288582/windows-nt-device-driver-development-book

          • https://stackoverflow.com/questions/3369160/best-book-for-learning-windows-device-driver-development


          But fair warning: the driver model changed again in Windows Vista. If you want to write drivers for devices that run on Windows Vista and 7, you'll need to make sure that you're learning about the updated model. If you still need the drivers to support legacy operating systems like Windows 2000/XP, then you'll need to stick with an older resource that talks about those operating systems.







          share|improve this answer














          share|improve this answer



          share|improve this answer








          edited May 23 '17 at 12:41









          Community

          1




          1










          answered Jun 27 '11 at 4:30









          Cody GrayCody Gray

          1,77711624




          1,77711624













          • Raymon Chen is lucky not to have said what you said, because he would then have been wrong. It is, after all, not DOS+Windows 95 issuing the error message about the INF file, but the newer operating system in question itself, which was known to come after DOS+Windows 95 from the get-go.

            – JdeBP
            Jun 27 '11 at 9:12











          • WDM drivers work on both Win 9x and Windows XP. Also some classes of drivers had incompatible changes in Vista, but not all of them.

            – John
            Jun 27 '11 at 21:24



















          • Raymon Chen is lucky not to have said what you said, because he would then have been wrong. It is, after all, not DOS+Windows 95 issuing the error message about the INF file, but the newer operating system in question itself, which was known to come after DOS+Windows 95 from the get-go.

            – JdeBP
            Jun 27 '11 at 9:12











          • WDM drivers work on both Win 9x and Windows XP. Also some classes of drivers had incompatible changes in Vista, but not all of them.

            – John
            Jun 27 '11 at 21:24

















          Raymon Chen is lucky not to have said what you said, because he would then have been wrong. It is, after all, not DOS+Windows 95 issuing the error message about the INF file, but the newer operating system in question itself, which was known to come after DOS+Windows 95 from the get-go.

          – JdeBP
          Jun 27 '11 at 9:12





          Raymon Chen is lucky not to have said what you said, because he would then have been wrong. It is, after all, not DOS+Windows 95 issuing the error message about the INF file, but the newer operating system in question itself, which was known to come after DOS+Windows 95 from the get-go.

          – JdeBP
          Jun 27 '11 at 9:12













          WDM drivers work on both Win 9x and Windows XP. Also some classes of drivers had incompatible changes in Vista, but not all of them.

          – John
          Jun 27 '11 at 21:24





          WDM drivers work on both Win 9x and Windows XP. Also some classes of drivers had incompatible changes in Vista, but not all of them.

          – John
          Jun 27 '11 at 21:24


















          draft saved

          draft discarded




















































          Thanks for contributing an answer to Super User!


          • Please be sure to answer the question. Provide details and share your research!

          But avoid



          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.


          To learn more, see our tips on writing great answers.




          draft saved


          draft discarded














          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f302654%2fhow-do-you-find-out-the-inf-file-that-is-being-used-when-you-plug-in-a-device-in%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown





















































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown

































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown







          Popular posts from this blog

          Why not use the yoke to control yaw, as well as pitch and roll? Announcing the arrival of...

          Couldn't open a raw socket. Error: Permission denied (13) (nmap)Is it possible to run networking commands...

          VNC viewer RFB protocol error: bad desktop size 0x0I Cannot Type the Key 'd' (lowercase) in VNC Viewer...