I have an application that loads in Wine and runs in test mode that does not require USB ports. I have poked about in lots of Linux and Wine documents and threads but I can't find a description of a procedure that explains the principle of getting a Wine application to see and use USB ports. Every time I think I am on to something it never relates to my installation like it talks about removing or adding lines to files that don't exist. I figure if I understood the principle I could figure out what to do on my system.
I thought I would upgrade my Suse to the latest one and start from there but that has made things worse Dolphin has crashed twice KInfo no longer shows the tty devices under its device list for starters so things are going from bad to worse. I tried going through the Wine instructions but it is too fragmented and complex. I am sure I am missing something really simple but not knowing the principle points to achieve to make the connection work in Wine is the handicap.
The USB port of my device was always showing up in old Suse as ttyUSB0 when I plugged it in but in the terminal when I listed serial ports it was not there even though it is in the dialout group. I added me as a user to the group successfully but the application still doesn't see the USB port and it scans all comm ports up to 256 I think. My guess is it is seeing the tty ones but not the ttyUSB. Tomorrow I am going to try the link command "ln -s /dev/ttyUSB0 com8" and see if it picks it up but I don't really know what is missing. Any help would be appreciated especially any explanation of the principles involved.

Welcome to LQ!

If your application doesn't require USB ports, why are you seeking to add a ttyUSB?

Please digest the last paragraph of my first post particularly the third line from the bottom.
Perhaps I didn't explain things sufficiently it is always a problem when one is buried in something. The software wants to use USB ports and scans to see if anything is attached but it can't see them so it comes up in test mode.

No.
Perhaps you should retype it when you're not "buried"?

Habitual is talking about this:If you don't need them, then what's your goal? Mistype, perhaps?

I assume you found the following information in the link below since you mentioned creating a symbolic link. Without the link the windows software will not recognize the serial port. As stated make sure your user has the needed permissions for the ttyUSB0.

https://www.winehq.org/docs/wineusr-...s-to-configure

If the "new" SuSE is not recognizing the USB adapter and not creating a ttyUSB0 device ID then your troubles lie with the operating system and not with wine at the moment.

I found this that explains the principles and I am trying to do it now.
http://g8ogj.org/files/Using%20USB%2...wwto%20ipb.pdf
If I understand it correctly it might be that the Wine program needs permission to access the ports as well as the user but I will see if it works. If not I shall check out the other links you have given.
Thanks