[Bug 54551] New: Installing device driver for ESI QuataFire 610 soundcard fails with "Co-installer registration was unsuccessful". See attached screen dump "Error_message.png".
https://bugs.winehq.org/show_bug.cgi?id=54551 Bug ID: 54551 Summary: Installing device driver for ESI QuataFire 610 soundcard fails with "Co-installer registration was unsuccessful". See attached screen dump "Error_message.png". Product: Wine Version: 8.2 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: critical Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: joehope52(a)gmail.com Distribution: --- Created attachment 74095 --> https://bugs.winehq.org/attachment.cgi?id=74095 Log files, screen dump and SW. Overview: The device driver for ESI QuataFire 610 soundcard and its installation program runs on WIN XP SP1. The driver has been running on a PC with WIN XP SP3 which has now broken down. The driver installation log from that computer is attached as "Windows_installation_log.txt". The soundcard interface is FireWire (IEEE 1394). Instead the driver has been tried installed using wine: Steps to reproduce: The ESI manual instructs to copy the entire driver SW folder from the CD to the HDD and install from there. The driver SW folder is attached. Can also be downloaded from "download.esi-audio.com" using Product group: "Firewire Audio Interfaces", Select product: "QuataFire 610", select OS: "Windows XP" and then selecting version 1.19. 1. Copy driver SW to disk. 2. Navigate to the QuataFire 610/PC/v.1.19 folder 3. Select the file Setup.exe and run with wine. 4. Follow the instructions (supply destination path). Now the program crashes with the message: "Co-intaller registration was unsuccessful. Please run Setup again." (And for completeness - running the setup again does not help). Expected behaviour: Normally, after point 4 above, the installation program would ask the user to connect the hardware (soundcard), and continuing would complete the driver installation. The installation log from the failing attempt is attached as "Wine_installation_log.txt" The installation has been tried on wine versions 7.x, 8.0, 8.1, 8.2 and devel, on Mint 21 and versions 7.x and 8.2 on Fedora 37. (I remember the 7.x version as 7.6, but not sure). -- 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.
https://bugs.winehq.org/show_bug.cgi?id=54551 Zeb Figura <z.figura12(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|critical |normal CC| |z.figura12(a)gmail.com Component|-unknown |setupapi --- Comment #1 from Zeb Figura <z.figura12(a)gmail.com> --- Please don't attach programs you don't have the right to distribute. What is your goal in installing this driver? Note that you won't be able to use it to simply drive the audio device; see <https://wiki.winehq.org/Hardware> for more information. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=54551 --- Comment #2 from Alexandre Julliard <julliard(a)winehq.org> --- The content of attachment 74095 has been deleted for the following reason: Please do not attach copyrighted binaries -- 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.
https://bugs.winehq.org/show_bug.cgi?id=54551 --- Comment #3 from Jørn <joehope52(a)gmail.com> --- (In reply to Zeb Figura from comment #1)
Please don't attach programs you don't have the right to distribute.
What is your goal in installing this driver? Note that you won't be able to use it to simply drive the audio device; see <https://wiki.winehq.org/Hardware> for more information.
My goal installing the soundcard driver is to make it possible for my audio SW to communicate with the soundcard (use its inputs and outputs). Would that not be possible by installing the driver. By the way having read the hardware link above, I do not understand everything on that page. One of theese are: When is a driver a kernel driver? -- 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.
https://bugs.winehq.org/show_bug.cgi?id=54551 --- Comment #4 from Zeb Figura <z.figura12(a)gmail.com> --- (In reply to Jørn from comment #3)
(In reply to Zeb Figura from comment #1)
Please don't attach programs you don't have the right to distribute.
What is your goal in installing this driver? Note that you won't be able to use it to simply drive the audio device; see <https://wiki.winehq.org/Hardware> for more information.
My goal installing the soundcard driver is to make it possible for my audio SW to communicate with the soundcard (use its inputs and outputs). Would that not be possible by installing the driver.
No, it won't be possible. It would take a lot of work to make it possible with Wine, and even then it won't be recognized by native applications. If you want to use that sound card on Linux, you'll need to write an audio driver for Linux.
By the way having read the hardware link above, I do not understand everything on that page. One of theese are: When is a driver a kernel driver?
Almost anything that's called a "driver" runs as a kernel driver. In some cases there are user-space APIs, though, that can be used instead. For Wine's purposes the difference doesn't usually matter. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=54551 --- Comment #5 from Jørn <joehope52(a)gmail.com> --- (In reply to Zeb Figura from comment #4)
(In reply to Jørn from comment #3)
(In reply to Zeb Figura from comment #1)
Please don't attach programs you don't have the right to distribute.
What is your goal in installing this driver? Note that you won't be able to use it to simply drive the audio device; see <https://wiki.winehq.org/Hardware> for more information.
My goal installing the soundcard driver is to make it possible for my audio SW to communicate with the soundcard (use its inputs and outputs). Would that not be possible by installing the driver.
No, it won't be possible. It would take a lot of work to make it possible with Wine, and even then it won't be recognized by native applications. If you want to use that sound card on Linux, you'll need to write an audio driver for Linux.
I understand this as any windows program relying on communication with an external unit, will not run under wine. I this case it makes no sense keeping this bug. Im I the one to withdraw/reject the bug and how. I am now in writing bugs.
By the way having read the hardware link above, I do not understand everything on that page. One of theese are: When is a driver a kernel driver?
Almost anything that's called a "driver" runs as a kernel driver. In some cases there are user-space APIs, though, that can be used instead. For Wine's purposes the difference doesn't usually matter.
-- 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.
https://bugs.winehq.org/show_bug.cgi?id=54551 --- Comment #6 from Jørn <joehope52(a)gmail.com> --- (In reply to Jørn from comment #5)
(In reply to Zeb Figura from comment #4)
(In reply to Jørn from comment #3)
(In reply to Zeb Figura from comment #1)
Please don't attach programs you don't have the right to distribute.
What is your goal in installing this driver? Note that you won't be able to use it to simply drive the audio device; see <https://wiki.winehq.org/Hardware> for more information.
My goal installing the soundcard driver is to make it possible for my audio SW to communicate with the soundcard (use its inputs and outputs). Would that not be possible by installing the driver.
No, it won't be possible. It would take a lot of work to make it possible with Wine, and even then it won't be recognized by native applications. If you want to use that sound card on Linux, you'll need to write an audio driver for Linux.
I understand this as any windows program relying on communication with an external unit, will not run under wine. I this case it makes no sense keeping this bug. Am I the one to withdraw/reject the bug and how. I am new in writing bugs.
By the way having read the hardware link above, I do not understand everything on that page. One of theese are: When is a driver a kernel driver?
Almost anything that's called a "driver" runs as a kernel driver. In some cases there are user-space APIs, though, that can be used instead. For Wine's purposes the difference doesn't usually matter.
-- 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.
https://bugs.winehq.org/show_bug.cgi?id=54551 Zeb Figura <z.figura12(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |WONTFIX --- Comment #7 from Zeb Figura <z.figura12(a)gmail.com> --- Resolving WONTFIX. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=54551 Gijs Vermeulen <gijsvrm(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED --- Comment #8 from Gijs Vermeulen <gijsvrm(a)gmail.com> --- Closing WONTFIX. -- 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.
participants (1)
-
WineHQ Bugzilla