I have been trying to throw away my dependence on Windoz since the early Pentium era, but there always seems to be some essential application that can't be replaced. Currently it is the programs that read my blood glucose meeter and an athletic trainer system. Both of them communicate through a serial port. I am currently working on getting the trainer going. It loads fine and has no trouble running until it tries to connect to the hardware. I get a program error saying that it cannot find the trainer. I seem to have the link that points wine to the serial port device, but the terminal screen fills with 'handle not found' errors when the connection is attempted. Surely, after all the work that has gone into wine, someone has gotten the serial ports to work. Larry -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.winehq.org/pipermail/wine-users/attachments/20070216/fa558a28/attachment.html
>>>>> "Larry" == Larry Lohkamp <loko@comcast.net> writes:Larry> I have been trying to throw away my dependence on Windoz since Larry> the early Pentium era, but there always seems to be some Larry> essential application that can't be replaced. Currently it is the Larry> programs that read my blood glucose meeter and an athletic Larry> trainer system. Both of them communicate through a serial port. I Larry> am currently working on getting the trainer going. It loads fine Larry> and has no trouble running until it tries to connect to the Larry> hardware. I get a program error saying that it cannot find the Larry> trainer. I seem to have the link that points wine to the serial Larry> port device, but the terminal screen fills with 'handle not Larry> found' errors when the connection is attempted. Surely, after all Larry> the work that has gone into wine, someone has gotten the serial Larry> ports to work. I suspect that your setup is wrong. Either the serial port has inappropriate permissions or the link in dosdevices is wrong. I suggest you should learn some basic wine debugging. Run with e.g. with WINEDEBUG=+relay, pipe the resulting output into a file and afterwards grep through the file to find the place where the application tries to open the serial port. Try to find out what goes wrong and fix your setup. Bye -- Uwe Bonnes bon@elektron.ikp.physik.tu-darmstadt.de Institut fuer Kernphysik Schlossgartenstrasse 9 64289 Darmstadt --------- Tel. 06151 162516 -------- Fax. 06151 164321 ----------
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Thank you all. The link does indeed belong to the dinosaur and the rules in /etc/rules.d/50-udev-default.rules appear to be the source of the link setup. I chose to add the user to the uucp group as the simplest and safest long term cure. Changing the rules should produce a similar result, but re-installs and upgrades would probably reset the rules. And that would put me in the "what the heck did I do to fix that" mode. Solutions are usually obvious, if we can just get out of the rut we dig for ourselves. Again, thank you for expanding my view. Larry -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFF2f5c0kc1Yep+Et4RAsJsAJ95CpO0s+sDgc2pbPX0r4/RhqJXkACeLsat Inuari/IZLyl3+a9DPNuBIk=NOgj -----END PGP SIGNATURE-----