Post by drdiesel on Aug 23, 2012 17:03:35 GMT -5
I haven't owned a windows machine in over 10 years, and won't, ever!
Anyhow, the AIM software can be made to run under wine, with a bit of effort. This is the first piece of hardware that used a serial port that offered any resistance, most just work (after you link the serial port), don't know why.
This assumes a serial to USB converter connected to the hardware and Fedora Linux. Note all commands are without the ' character.
1. Plug your USB to serial adapter into your Linux computer.
2. Type 'dmesg' into a console window, you'll see something like this:
[ 1541.102708] keyspan 2-1.2.5:1.0: Keyspan 1 port adapter converter detected
[ 1541.103450] usb 2-1.2.5: Keyspan 1 port adapter converter now attached to ttyUSB0
Notice it attached the USB adapter to ttyUSB0, which in Fedora in actually in /dev/
3. cd to your wine dosdevices directory as your normal user: 'cd ~/.wine/dosdevices'
4. Make a symbolic link to your USB serial adaptor using your location found above; 'ln -s /dev/ttyUSB0 com1'
5. As root: 'chmod -R 777 /dev/ttyUSB0'
6. Open your AIM config file (_AIM_config.cfg) with any normal text editor. Make the following changes:
2000 // Max delay in milliseconds for external hardware
0 // one means RS232=115K, 0 means RS232=57.6K, May have to use "0" for Bluetooth
Note, a delay of 2000ms is probably much longer than it needs, but works good.
7. If you had the AIM hardware box already powered up, unplug it, wait 5 sec and plug it back in.
8. Launch AIM under wine, might/should work.
If you previously had the AIM up and running on a different COMM port, set it to com1, close the AIM application and start back on step 7.
For some reason if you try at 115K baud first, it seems to lock up the AIM hardware, it won't respond again until you bounce power to it. It took me a while to get past this!
If there is any documentation on how to talk to the AIM hardware, perhaps I could write a suitable native Linux version?
Andy
73
Anyhow, the AIM software can be made to run under wine, with a bit of effort. This is the first piece of hardware that used a serial port that offered any resistance, most just work (after you link the serial port), don't know why.
This assumes a serial to USB converter connected to the hardware and Fedora Linux. Note all commands are without the ' character.
1. Plug your USB to serial adapter into your Linux computer.
2. Type 'dmesg' into a console window, you'll see something like this:
[ 1541.102708] keyspan 2-1.2.5:1.0: Keyspan 1 port adapter converter detected
[ 1541.103450] usb 2-1.2.5: Keyspan 1 port adapter converter now attached to ttyUSB0
Notice it attached the USB adapter to ttyUSB0, which in Fedora in actually in /dev/
3. cd to your wine dosdevices directory as your normal user: 'cd ~/.wine/dosdevices'
4. Make a symbolic link to your USB serial adaptor using your location found above; 'ln -s /dev/ttyUSB0 com1'
5. As root: 'chmod -R 777 /dev/ttyUSB0'
6. Open your AIM config file (_AIM_config.cfg) with any normal text editor. Make the following changes:
2000 // Max delay in milliseconds for external hardware
0 // one means RS232=115K, 0 means RS232=57.6K, May have to use "0" for Bluetooth
Note, a delay of 2000ms is probably much longer than it needs, but works good.
7. If you had the AIM hardware box already powered up, unplug it, wait 5 sec and plug it back in.
8. Launch AIM under wine, might/should work.
If you previously had the AIM up and running on a different COMM port, set it to com1, close the AIM application and start back on step 7.
For some reason if you try at 115K baud first, it seems to lock up the AIM hardware, it won't respond again until you bounce power to it. It took me a while to get past this!
If there is any documentation on how to talk to the AIM hardware, perhaps I could write a suitable native Linux version?
Andy
73