Wine + winebottler + azloader.exe + rs232 to usb adapter

anbes · Post by **anbes** » Mon Jun 07, 2010 8:27 am

Hello guys. I am new in mac world and in wine apps.
I have this singular situation:
I have a macbook with wine and winebottler installed.
I want to use this exe app: azloader.exe. Ok, wine is able to load it normally. But... the problem is, my macbook has not the RS-232 port. So I bought a RS-232 to USB adapter. I've installed the correct "drive" to use that. I've tried that in windows, and ok, the azloader was able to send data trhoutgh the "com 3 port" (that's where the driver rs232-usb is installed).
But my macbook couldn't. I believe that wine runs the azloader right, but it's not able to use thet rs232-usb mac's drive! I haven't installed the driver for windows with wine.
What to do? install the rs232-usb windows driver using wine?
what eles? install windows in bootcamp?
I've tried to "create" the azloader.app using winebottler, but it never ends the process.
What more can I do?
tks a lot

Martin Gregorie · Post by **Martin Gregorie** » Mon Jun 07, 2010 9:17 am

On Mon, 2010-06-07 at 08:27 -0500, anbes wrote:

So I bought a RS-232 to USB adapter. I've installed the correct
"drive" to use that. I've tried that in windows, and ok, the azloader
was able to send data trhoutgh the "com 3 port" (that's where the
driver rs232-usb is installed).

I run wine apps under Linux, so the following is probably directly
helpful, but may give you a clue. My Wine apps can use serial ports on
the motherboard and on a 6-port serial adapter card but have never been
able to see my pfranc USB-serial adapter. Other people have been able to
use USB-serial adapters, so maybe the chipset in the adapter is
important. On the other hand, all current Linuxes address serial ports
as /dev/ttyS[0-9] and USB adapters as /dev/ttyUSB[0-9], so its equally
possible that wine apps can't see USB devices because their names are
different.

Maybe OS X does something similar?

Martin

anbes · Post by **anbes** » Mon Jun 07, 2010 10:00 am

Humm, that's a point!
How can I change this "port name"?
Well, at leats I'll try use windows in bootcamp! I am tring to avoid windows!

John Drescher · Post by **John Drescher** » Mon Jun 07, 2010 10:18 am

Humm, that's a point!
How can I change this "port name"?
Well, at leats I'll try use windows in bootcamp! I am tring to avoid windows!

I thought you were supposed to make a link in dosdevices for the COM
port to the real device node on the *nix machine.

John

Martin Gregorie · Post by **Martin Gregorie** » Mon Jun 07, 2010 10:37 am

On Mon, 2010-06-07 at 11:08 -0400, John Drescher wrote:

Humm, that's a point!
How can I change this "port name"?
Well, at leats I'll try use windows in bootcamp! I am tring to avoid windows!

I thought you were supposed to make a link in dosdevices for the COM
port to the real device node on the *nix machine.

It's never been necessary on my system (Fedora 10) with /dev/ttyS*
devices and has never worked for my USB-serial adapter.

Martin

anbes · Post by **anbes** » Mon Jun 07, 2010 1:10 pm

Well, I think the only possibility is to install windows in my mac, isn't it?
I am not a programmer, so I don't have any idea how to "manipulate" these stuffs.
tks for all

Gert van den Berg · Post by **Gert van den Berg** » Mon Jun 07, 2010 1:28 pm

On Mon, Jun 7, 2010 at 20:10, anbes <[email protected]> wrote:

Well, I think the only possibility is to install windows in my mac, isn't it?
I am not a programmer, so I don't have any idea how to "manipulate" these stuffs.
tks for all

HAve a look at Virtualbox... (Its much nicer than dual booting...)

Someone who knows Mac OS better might still come up with a nicer solution...

doh123 · Post by **doh123** » Mon Jun 07, 2010 2:06 pm

all the devices are in /dev in OSX as well... I've never directly tried to access anything except the optical drive, which doesn't work in Wine on OSX... (yet). You should be able to try and directly access it just like in Linux.

Gert van den Berg · Post by **Gert van den Berg** » Mon Jun 07, 2010 2:27 pm

On Mon, Jun 7, 2010 at 21:06, doh123 <[email protected]> wrote:

all the devices are in /dev in OSX as well... I've never directly tried to access anything except the optical drive, which doesn't work in Wine on OSX... (yet). Â You should be able to try and directly access it just like in Linux.

If OS X detects the device correctly enough to load a driver... (which
may / may not be visible from System profiler)

The device names might also be different... (/dev/tty.something looks
common...) (try ls /dev/*tty* to try and find it...)

Thing like this might be needed: http://osx-pl2303.sourceforge.net/

Martin Gregorie · Post by **Martin Gregorie** » Mon Jun 07, 2010 2:51 pm

On Mon, 2010-06-07 at 21:26 +0200, Gert van den Berg wrote:

On Mon, Jun 7, 2010 at 21:06, doh123 <[email protected]> wrote:
all the devices are in /dev in OSX as well... I've never directly tried to access anything except the optical drive, which doesn't work in Wine on OSX... (yet). You should be able to try and directly access it just like in Linux.

If OS X detects the device correctly enough to load a driver... (which
may / may not be visible from System profiler)

The device names might also be different... (/dev/tty.something looks
common...) (try ls /dev/*tty* to try and find it...)

Thing like this might be needed: http://osx-pl2303.sourceforge.net/

Does OS X keep a static list of device files, as Linux used to do in
its pre UDEV days or do device files get built on the fly as they are
needed?

UDEV builds device files for things we think of as static (serial &
parallel ports, optical drives, etc) dynamically at boot time and
effectively destroys them when its shut down. This has implications for
access permissions: if you need non-standard access permissions you
can't just set them once: they must either be modified as the device
files are created (by changing the UDEV rules) or immediately after
booting the system (by putting chmod etc. commands
in /etc/rc.d/rc.local).

Martin

Gert van den Berg · Post by **Gert van den Berg** » Mon Jun 07, 2010 3:02 pm

On Mon, Jun 7, 2010 at 21:51, Martin Gregorie <[email protected]> wrote:

Does OS X keep a static list of device files, as Linux used to do in
its pre UDEV days or do device files get built on the fly as they are
needed?

Looks like automatically:
http://developer.apple.com/mac/library/ ... 7-BABGJBFJ

Charles Davis · Post by **Charles Davis** » Mon Jun 07, 2010 3:40 pm

On 6/7/10 1:06 PM, doh123 wrote:

all the devices are in /dev in OSX as well...

Right. In fact, there are TWO device files created for serial ports. The
names follow an irregular pattern (not like Linux, where it's a very
regular pattern): the one you want starts with "tty." followed by some
string describing the device providing the serial port. Make a symlink
from that device file to dosdevices/com1 in your Wine prefix (usually
it's ~/.wine, where '~' is your home folder).

By the way, you can't even see the .wine folder from the Finder, much
less make a symlink in it. You have to use the command line. Open
Terminal (in /Applications/Utilities) and type this in:

ln -s /dev/tty.<whatever> ~/.wine/dosdevices/com1

followed by Return. Replace '<whatever>' with whatever's after the
"tty." in the device file. Then try your program again; maybe this time
it will work.

Chip

James Mckenzie · Post by **James Mckenzie** » Mon Jun 07, 2010 4:06 pm

Gert van den Berg <[email protected]>

Sent: Jun 7, 2010 11:28 AM
To: [email protected]
Subject: Re: [Wine] Wine + winebottler + azloader.exe + rs232 to usb adapter

On Mon, Jun 7, 2010 at 20:10, anbes <[email protected]> wrote:
Well, I think the only possibility is to install windows in my mac, isn't it?
I am not a programmer, so I don't have any idea how to "manipulate" these stuffs.
tks for all

HAve a look at Virtualbox... (Its much nicer than dual booting...)

+1. However, you will need a fully licensed copy of Windows to complete the installation and it does take up space on your hard drive.

Someone who knows Mac OS better might still come up with a nicer solution...

I've seen Parallels, VirtualBox and VMWare Fusion. All are about the same, but VirtualBox is or should be free....

You might also want to take a look at the 'hack' USB patches as they may help your USB <-> serial product actually work.

James McKenzie

anbes · Post by **anbes** » Mon Jun 07, 2010 8:13 pm

But we do not must forguet, that I have to use wine anyway, `cause the "azloader.exe" is not avaliable in app format!
And I think that`s the manory cause of the problem, because this exe apps ins under wine, the drive solution must be too, ma ia wrong?

James McKenzie · Post by **James McKenzie** » Mon Jun 07, 2010 8:38 pm

Martin Gregorie wrote:

On Mon, 2010-06-07 at 21:26 +0200, Gert van den Berg wrote:

On Mon, Jun 7, 2010 at 21:06, doh123 <[email protected]> wrote:

all the devices are in /dev in OSX as well... I've never directly tried to access anything except the optical drive, which doesn't work in Wine on OSX... (yet). You should be able to try and directly access it just like in Linux.

If OS X detects the device correctly enough to load a driver... (which
may / may not be visible from System profiler)

The device names might also be different... (/dev/tty.something looks
common...) (try ls /dev/*tty* to try and find it...)

Thing like this might be needed: http://osx-pl2303.sourceforge.net/

Does OS X keep a static list of device files, as Linux used to do in
its pre UDEV days or do device files get built on the fly as they are
needed?

No, it is dynamic (sigh)

James McKenzie

Martin Gregorie · Post by **Martin Gregorie** » Tue Jun 08, 2010 4:38 am

On Mon, 2010-06-07 at 18:36 -0700, James McKenzie wrote:

Martin Gregorie wrote:
On Mon, 2010-06-07 at 21:26 +0200, Gert van den Berg wrote:

On Mon, Jun 7, 2010 at 21:06, doh123 <[email protected]> wrote:
If OS X detects the device correctly enough to load a driver... (which
may / may not be visible from System profiler)

The device names might also be different... (/dev/tty.something looks
common...) (try ls /dev/*tty* to try and find it...)

Thing like this might be needed: http://osx-pl2303.sourceforge.net/

Does OS X keep a static list of device files, as Linux used to do in
its pre UDEV days or do device files get built on the fly as they are
needed?

No, it is dynamic (sigh)

That's not necessarily a disaster. Can you change the instructions OS X
uses to add a device to its device list? If so, adding a HOWTO to the
Wine wiki or a pointer to one would be useful.

Martin