Serial port sniffing problem

[Christopher Harrington]

(copying list again, below edited for brevity)

On Tue, Nov 29, 2016 at 12:39 PM Bill Lionheart <billlionheart at gmail.com>
wrote:

> $ ls -Fl
> lrwxrwxrwx 1 bill bill 10 May 11  2014 c: -> ../drive_c/
> lrwxrwxrwx 1 bill bill 12 Jan  6  2016 com1 -> /dev/ttyUSB0
>
> $ id -a
> uid=1001(bill) gid=1001(bill)
> groups=1001(bill),20(dialout)


> $ ls -l /dev/ttyUSB0
> crw-rw---- 1 root dialout 188, 0 Nov 29 18:27 /dev/ttyUSB0
>
>
>
All of this definitely looks correct.

Here are a couple more suggestions:
1. Try creating a brand new wine prefix. Yours certainly has a beard on it
and there may be artifacts of older copies of Wine that could be impacting
your testing. Anyway, this essentially would look like moving ~/.wine to
somewhere else, installing your test application again, and re-creating
your com1 file in dosdevices/. You can always move your .wine directory
back if it has important stuff in it.
2. See if using a more current version of Wine improves anything. You say
you're on Wine 1.8; if you could be more specific (try running wine
--version) that might give someone a lightbulb.
3. Crossover from Codeweavers is appallingly affordable if you haven't
looked into that yet, and it comes with professional support.

Anyway, wine-devel is more for discussion of development of Wine itself,
not a support forum. What you're probably looking for is wine-users. I'm
not subscribed to wine-users, so I can't copy your email there, but you can
subscribe here: https://www.winehq.org/mailman/listinfo/wine-users

Good luck.



>
> On 29 November 2016 at 17:57, Christopher Harrington
> <ironiridis+winehq at gmail.com> wrote:
> > On Tue, Nov 29, 2016 at 1:22 AM Bill Lionheart <billlionheart at gmail.com>
> > wrote:
> >>
> >> Using Wine  version 1.8 on Ubuntu 14.04.5
> >> I'm trying to use a AVRT5 APRS amateur radio GPRS tracker which has a
> >> serial interface. The device is supplied with a Prolific USB serial
> >> converter which comes up as /dev/ttyUSB0 which
> >> I have sym linked to COM1
> >
> >
> > Can you please cd into your dosdevices folder and run this command?
> >
> > ls -Fl
> >
> > (that's an uppercase F and a lowercase L)
> >
> > Then we will also need to see permissions of the serial device, so run
> this:
> >
> > ls -l /dev/ttyUSB0
> >
> > That's a lowercase L again... and run this too:
> >
> > id -a
> >
> > With all this info we can rule out a couple problems, chief among them:
> > 1. Is the symlink named correctly and actually pointing to something that
> > exists
> > 2. Do you actually have permissions to access the serial port
> >
> > If you provide the output of all three of these commands, we should be
> able
> > to help.
> >
> > -Chris
> >
> >>
> >>
> >
>
>
>
> --
> Professor of Applied Mathematics
> University of Manchester
> http://www.maths.manchester.ac.uk/bl
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.winehq.org/pipermail/wine-devel/attachments/20161129/311db80b/attachment.html>