Ask a questionAsk a question
 

QuestionSideshow driver 64 bit

  • Thursday, September 24, 2009 1:03 PMCsenteri Barna Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Hi

    I want to compile our drivers to be used on Vista 64 bit (for now).
    WDK used is 7600, tried build environment ia64 and amd64 too.
    The compilation is successfull on both but the 64 bit Vista doesn't recognises the drivers.

    Tried manual instalation (which works in x86) and the result is "the folder does not contain compatible software ... make sure it's designed to work with 64 bit ..."

    The inf file what I use has x86, ia64 and amd64 entries but I also tried the generic aproach from the NoDevice generic sideshow driver with NT$ARCH$
    The result is the same error.

    Do I have to do something else too, am I missing something?

    regards,
    Barna Csenteri

All Replies

  • Friday, September 25, 2009 7:54 AMCsenteri Barna Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    The device simulator 3.0 does not work on Vista 64 bit (crashes) so I could not check what is different there.
    B.
  • Friday, September 25, 2009 3:31 PMDan PolivyMSFT, ModeratorUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    The amd64 flavor is the one you want for client 64-bit OSes.  The WDK sample driver should work on 64-bit--are you compiling the INX into an INF file, and does it include the appropriate decorations on the DDInstall sections (http://msdn.microsoft.com/en-us/library/ms794553.aspx)?

    You should also review the setupapi.dev.log in \windows\inf for more details on what might be failing.

    Dan

  • Thursday, October 01, 2009 11:48 AMCsenteri Barna Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    Hi

    The inf was ok, I managed to install the driver at the end.
    But it doesn't starts - my error was related to 64 bit and unsigned drivers - unsigned drivers are not working on 64 bit.

    Even the user mode drivers like a sideshow one produces verify_file_signature error in setupapi.app.log - thought this "feature" is only for kernel mode drivers but no - they are valid for the user mode sideshow drivers too ...

    Which for me is a dead end for the moment - I can switch off the signature requirement for debugging purpose but until we are not signing that driver I cannot give it to any customer ...

    Thank You for your response and regards,
    Barna Csenteri

  • Friday, October 02, 2009 10:01 AMCsenteri Barna Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Also tried the famous "bcdedit -set loadoptions DDISABLE_INTEGRITY_CHECKS" which in earlier Vista releases disabled the signature check. Unfortunatelly from SP1 it does not works - the option is registered but the logfiles are showing a catalog file/signature error with or without this option ...

    I know that the reason of those signature checks were a lot's of 3rd party bad written crashing drivers but I do not see this problem with user mode drivers like Sideshow is ...

    Anyway, I know this is not Your problem but if You know any way to disable this signature checks for user mode drivers let me know (I know about the F8/start option but this one is really anoying since it have to be done on every boot)

    regards,
    Barna Csenteri

  • Wednesday, October 07, 2009 10:41 PMDan PolivyMSFT, ModeratorUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Barna,

    If you are able to get the driver installed, but not load, what is the error code showing in device manager?  Alternately, have you tried starting the driver while under a debugger? There are docs in MSDN explaining how to attach at driver start time.  It may just be a driver error instead of a signature error causing problems.  The check for signature on driver load only happens for kernel mode drivers.

    Dan