[Bug 59129] New: Parallel Port Tester fails to detect the parallel port's base I/O address
http://bugs.winehq.org/show_bug.cgi?id=59129 Bug ID: 59129 Summary: Parallel Port Tester fails to detect the parallel port's base I/O address Product: Wine Version: 11.0-rc1 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: wmi&wbemprox Assignee: wine-bugs@list.winehq.org Reporter: alexhenrie24@gmail.com Distribution: --- Steps to reproduce: 1. Use a computer with a motherboard-attached or PCI-attached parallel port. USB-attached parallel ports do not have base I/O addresses and Parallel Port Tester ignores them. 2. Ensure that /dev/lp0 exists and works outside of Wine, for example by connecting the parallel port to a printer or to an LED tester, running `echo hello > /dev/lp0`, and seeing the word printed on the printer or seeing different LEDs light up on the tester. 3. (Optional) Figure out what the base address of the parallel port is by looking at DEVNAME in /sys/class/printer/lp0/device/ppdev/parport0/uevent, then reading the first number in /proc/sys/dev/parport/<DEVNAME>/base-addr. You will need to convert the value to hexadecimal and prepend "0x" if you want to manually enter it into Parallel Port Tester. 4. Run `wine ParallelPortTesterSetup-1.0.0.2.exe` 5. Run `wine 'C:\Program Files (x86)\Parallel Port Tester\ParallelPortTester.exe'` 6. Click the drop-down labeled "Port" in the lower-right corner of the window. When my desktop computer is booted into Windows and I click the drop-down in Parallel Port Tester, it offers "LPT3 (0xEFF8)" as an option. When the same computer is booted into Linux and I run Parallel Port Tester on Wine, the drop-down is empty. However, if I run it on Wine with https://gitlab.com/alexhenrie/ioperm and enter the parallel port's base address manually, the program correctly displays the states of the parallel port's pins and can manipulate them. That means that the main part of the program works, it's just failing to automatically detect the port. The author helpfully wrote up an explanation of what the program does to find parallel ports and their base addresses: https://www.downtowndougbrown.com/2014/11/detecting-parallel-ports-and-their... $ sha256sum ParallelPortTesterSetup-1.0.0.2.exe 9e9b399dd92ac48433af2061eb8491d1d68a6134eaeab2efcdcd36361e723d09 -- 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.
http://bugs.winehq.org/show_bug.cgi?id=59129 Alex Henrie <alexhenrie24@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |download URL| |https://www.downtowndougbro | |wn.com/wp-content/uploads/2 | |022/01/ParallelPortTesterSe | |tup-1.0.0.2.zip -- 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.
http://bugs.winehq.org/show_bug.cgi?id=59129 --- Comment #1 from Hans Leidekker <hans@meelstraat.net> ---
SelectQuery portsQuery = new SelectQuery("Win32_PnPEntity", "ClassGUID=\"{4D36E978-E325-11CE-BFC1-08002BE10318}\"");
This query should work once we have a (stub) parallel port driver that registers itself.
ObjectQuery resourceQuery = new ObjectQuery("ASSOCIATORS OF {Win32_PnPEntity.DeviceID=\"" + deviceID + "\"} WHERE ResultClass = Win32_PortResource");
This needs an implementation of Win32_PortResource and an associator class. -- 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.
http://bugs.winehq.org/show_bug.cgi?id=59129 Alex Henrie <alexhenrie24@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |hardware -- 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 (2)
-
WineHQ Bugzilla -
WineHQ Bugzilla