[Bug 45455] Cetus3D-Software (3D printer) UP Studio 2.4.x driver installation fails due to missing ' setupapi.dll.DriverStoreFindDriverPackageW' stub ( Microsoft Driver Install Frameworks for Applications - DIFxApp)

wine-bugs at winehq.org wine-bugs at winehq.org
Mon Jul 16 06:39:42 CDT 2018


https://bugs.winehq.org/show_bug.cgi?id=45455

--- Comment #5 from Anastasius Focht <focht at gmx.net> ---
Hello Austin,

--- quote ---
Do you know the prototype for this? I can't find a header or anything online.
--- quote ---

https://docs.microsoft.com/en-us/windows-hardware/drivers/install/driver-store

https://technet.microsoft.com/de-de/office/ff544837(v=vs.80).aspx

--- quote ---
Starting with Windows 7, the Windows Driver Kit (WDK) includes version 2.1 of
DIFxApp. For information about how to obtain the latest WDK, see How to Get the
WDK.
Note  Although version 2.1 of DIFxApp was available in earlier versions of the
WDK, use the version of DIFxApp in the Windows 7 WDK and later versions of the
WDK.

Starting with Microsoft Windows 2000, DIFxApp supports installing signed Plug
and Play (PnP) function drivers and signed class filter drivers. You need to
create only one installation package that will install driver packages. DIFxApp
can also be configured in legacy mode to install unsigned PnP function drivers
and unsigned class filter drivers. In legacy mode, DIFxApp will also install
driver packages that have missing files. 
--- snip ---

https://docs.microsoft.com/en-us/windows-hardware/drivers/install/difx-guidelines

--- quote ---
DIFx Guidelines

Starting in Windows 10 Version 1607 (Redstone 1), the Driver Install Frameworks
(DIFx) tools are no longer included in the WDK. Instead, we recommend providing
your driver as a standalone package that doesn't require an installer, ideally
through Windows Update. To add your driver to Windows Update, the first step is
to submit your driver package to the Sysdev Driver Portal.
--- quote ---

Windows Driver Kit Version 7.1.0 download:

https://www.microsoft.com/en-us/download/details.aspx?id=11800

Tidbit: The installation of WDK is also bugged, I already found a couple of
other issues.

Although the WDK contains 'setupapi.h' (and import lib) it doesn't contain
these prototypes. I suspect its exclusively used by Driver Install Frameworks
for Applications (DIFxApp) for "Driver Store" concept, hence not in public
headers.
Some of the parameters are probably related/same as other public setupapi:

https://docs.microsoft.com/en-us/windows/desktop/api/setupapi/nf-setupapi-setupgetinfdriverstorelocationa
(SetupGetInfDriverStoreLocationA/W)

Even if the parameter number can be figured out by trial/error (watching stack
imbalance after stdcall stub + adding more args as needed) I'm not sure if it's
worth to go further here. Microsoft Driver Store is a pointless concept for
Wine anyway.

Regards

-- 
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.



More information about the wine-bugs mailing list