We had a major storm through here recently and we suffered damage to the house roof and ceilings. I just received the quote to repair. I’m hoping that a small fraction of the 80,000 odd people that download SDIO and/or Desktop Info every month won’t mind chipping in a few dollars to help out. Click on the big blue button at the bottom of the page to help us keep a roof over our heads, literally!
Guests have read-only access to our forums. If you wish to participate you will need to register. Be sure to activate your account from the email sent to you when you register.
On a Windows 10x64, the 10x86 driver is offered, although there is a 10x64 driver available. This didn't happen in older versions of SDIO; it started happening when SDIO added a breakdown by different Windows builds.
@patch Thanks for the report. Are you able to pin down exactly which build this started occurring?
I found version R818 – everything works fine with it. R823 already suggests incorrectly. I don't know where to find the others...
@patch Introduced in 823 when I introduced the win10 build numbers. Why it shows up for you is the third digit in the inf file section field:
ntamd64.10.0.1..17763
the old code is not expecting anything past "ntamd64.10.0"
@glenn It's good that the cause was found quickly, since such x.10.0.1.x sections are encountered quite often.
