[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 05:39:50 CDT 2018 

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

Anastasius Focht <focht at gmx.net> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|Cetus3D-Software (3D        |Cetus3D-Software (3D
                   |printer) UP Studio 2.4.x    |printer) UP Studio 2.4.x
                   |driver installation fails   |driver installation fails
                   |due to missing              |due to missing
                   |'setupapi.dll.DriverStoreFi |'setupapi.dll.DriverStoreFi
                   |ndDriverPackageW' stub      |ndDriverPackageW' stub
                   |                            |(Microsoft Driver Install
                   |                            |Frameworks for Applications
                   |                            |- DIFxApp)

--- Comment #4 from Anastasius Focht <focht at gmx.net> ---
Hello pellwestphal,

--- quote ---
I think I could get things to work without a USB connection. But I
haven't quite understood your comment. 
--- quote ---

https://www.cetus3d.com/en/forums/topic/can-the-cetus3d-be-connected-to-a-printserver/

--- quote ---
The Cetus3D has WiFi and connects to your local network that way.

That said, their USB protocol is proprietary, so you're not likely to have luck
with that. There is a partial open source implementation:
github.com/UP3D-gcode/UP3D but that would only be a starting point.

If you want g-code support to use something like octoprint, you'll need to get
the tinyFab CPU which should plug into your Cetus3D's motherboard.
--- quote ---

If the full functionality is available via WiFi then you might get lucky here.

Native Linux (albeit limited) support from some reverse engineered protocols ->
UP3DTools (console apps):

https://www.stohn.de/3d/index.php/2016/03/10/up3dtools-little-how-to/

https://github.com/MaikStohn/UP3D

No idea if all the needed functionality is implemented there.

--- quote ---
Is there a way to get the installer running and have functioning program
(without USB support) ?
If you had a link... 
--- quote ---

I'm not the developer of this software and don't own any hardware to test with,
how should I know?
The outer installer seems to accept some command line arguments though:

--- snip ---
...
002e:Call KERNEL32.lstrcmpiW(0033f51c L"-?",0050f278 L"/i") ret=00451170
002e:Ret  KERNEL32.lstrcmpiW() retval=ffffffff ret=00451170
002e:Call KERNEL32.lstrcmpiW(0033f51c L"-?",0050f264 L"/package") ret=0045119a
002e:Ret  KERNEL32.lstrcmpiW() retval=ffffffff ret=0045119a
002e:Call KERNEL32.lstrcmpiW(0033f51c L"-?",0050f25c L"/a") ret=004511c1
002e:Ret  KERNEL32.lstrcmpiW() retval=ffffffff ret=004511c1
002e:Call KERNEL32.lstrcmpiW(0033f51c L"-?",0050f214 L"/n") ret=00451220
002e:Ret  KERNEL32.lstrcmpiW() retval=ffffffff ret=00451220
002e:Call KERNEL32.lstrcmpiW(0033f51c L"-?",0050f23c L"/t") ret=0045135c
002e:Ret  KERNEL32.lstrcmpiW() retval=ffffffff ret=0045135c
002e:Call KERNEL32.lstrcmpiW(0033f51c L"-?",0050f234 L"/x") ret=004513b5
002e:Ret  KERNEL32.lstrcmpiW() retval=ffffffff ret=004513b5
002e:Call KERNEL32.lstrcmpiW(0033f51c L"-?",0050f21c L"/uninstall")
ret=004513dc
002e:Ret  KERNEL32.lstrcmpiW() retval=ffffffff ret=004513dc
002e:Call KERNEL32.lstrcmpiW(0033f51c L"-?",0050f1f4 L"/quiet") ret=00451403
002e:Ret  KERNEL32.lstrcmpiW() retval=ffffffff ret=00451403
002e:Call KERNEL32.lstrcmpiW(0033f51c L"-?",0050f1e0 L"/passive") ret=0045142f
002e:Ret  KERNEL32.lstrcmpiW() retval=ffffffff ret=0045142f
002e:Call KERNEL32.lstrcmpiW(0033f51c L"-?",0050f1d0 L"/qn") ret=0045145b
002e:Ret  KERNEL32.lstrcmpiW() retval=ffffffff ret=0045145b
002e:Call KERNEL32.lstrcmpiW(0033f51c L"-?",0050f1d8 L"/q") ret=00451482
002e:Ret  KERNEL32.lstrcmpiW() retval=ffffffff ret=00451482
002e:Call KERNEL32.lstrcmpiW(0033f51c L"-?",0050f1c8 L"/qb") ret=004514a9
002e:Ret  KERNEL32.lstrcmpiW() retval=ffffffff ret=004514a9
002e:Call KERNEL32.lstrcmpiW(0033f51c L"-?",0050f1c0 L"/qr") ret=004514d8
002e:Ret  KERNEL32.lstrcmpiW() retval=ffffffff ret=004514d8
002e:Call KERNEL32.lstrcmpiW(0033f51c L"-?",0050f1b8 L"/qf") ret=00451507
002e:Ret  KERNEL32.lstrcmpiW() retval=ffffffff ret=00451507
002e:Call KERNEL32.lstrcmpiW(0033f51c L"-?",0050f1a0 L"/norestart")
ret=00451536
002e:Ret  KERNEL32.lstrcmpiW() retval=ffffffff ret=00451536
002e:Call KERNEL32.lstrcmpiW(0033f51c L"-?",0050f180 L"/promptrestart")
ret=00451562
002e:Ret  KERNEL32.lstrcmpiW() retval=ffffffff ret=00451562
002e:Call KERNEL32.lstrcmpiW(0033f51c L"-?",0050f164 L"/forcerestart")
ret=0045158e
002e:Ret  KERNEL32.lstrcmpiW() retval=ffffffff ret=0045158e
002e:Call KERNEL32.lstrcmpiW(0033f51c L"-?",0050f158 L"/log") ret=004515ba
002e:Ret  KERNEL32.lstrcmpiW() retval=ffffffff ret=004515ba
002e:Call KERNEL32.lstrcmpiW(0033f51c L"-?",0050f134 L"/uithread") ret=004518c7
002e:Ret  KERNEL32.lstrcmpiW() retval=ffffffff ret=004518c7
002e:Call KERNEL32.lstrcmpiW(0033f51c L"-?",0050f204 L"/no_ini") ret=004518f7
...
002e:Call user32.MessageBoxW(00000000,005f8b30 L"Invalid command
line",00000000,00000010) ret=00415697 
--- snip ---

These are standard MSI-compatible arguments but they don't allow to control the
installation of components.

Peeking into 'UP Studio x86.msi', 'Component' table via ORCA revealed some
possible workaround...

--- snip ---
WinusbFM.inf_1    {46523B0D-F690-48B5-8166-80E828889E5E}    WinuFM_Dir    256  
 VersionNT64    WinusbFM.inf
WinusbFM.inf_2    {09D60680-3164-4045-B99D-0978980A9E27}    Driver_Dir    0   
VersionNT >= 500    WinusbFM.inf_1
--- snip ---

Indeed, if one sets the Windows version of the 32-bit WINEPREFIX to 'Windows
2000' via 'winecfg', the installer will skip installation of the driver
component(s).
It will warn you about it at the end but let the installer succeed.
Afterwards WinVer should be set back to default 'Windows 7'.

NOTE: Any follow-up issues should not be discussed here.
Wine Bugzilla is for reporting bugs, not end-user discussions ("what do I need
to do to get my app to work" -> https://forum.winehq.org/).

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