Since about v0.9 I've been unable to get wine to reliably receive characters on the serial port. Sending is fine. The latest version I've tried is 1.1.23, and this always loses the first two characters of a line, then randomly loses some of the later ones. Is anyone else seeing the problem? It's an absolute show-stopper for me because the only Windows software I use needs serial coms at 9600 baud :( I've tried this on debian Etch, Lenny, & the current testing
On Wed, 2009-09-02 at 10:38 -0500, folderol wrote:> Since about v0.9 I've been unable to get wine to reliably receive > characters on the serial port. Sending is fine. The latest version > I've tried is 1.1.23, and this always loses the first two characters > of a line, then randomly loses some of the later ones. >I don't have any problems using serial ports with WINE. I only have one program that requires serial ports that I run with WINE - the EW Uploader, used to set parameters in an EW flight recorder and download IGC flight logs from it as ASCII files. IIRC it uses the Z-modem protocol for downloads. Details are in the AppDB: no winetricks were needed to get it working. It worked with WINE 1.0.1, 1.1.9 under Fedora 8 and is currently working with WINE 1.1.23 under Fedora 10. I'm using a NetMos Technology PCI 9845 Multi-I/O Controller, which provides 6 serial ports, to talk to it. Both motherboard ports (COM1 and COM2) are permanently connected to other devices. Martin
Unless I'm mistaken, z-modem is quite heavily error-checked, so losing some characters could probablyvbe absorbed without you noticing. The Application I'm using only checks the validity of entire strings, and doesn't retry - it just aborts. Yeah, I know. Crap :(
Ok. I've gone down to absolute basics. Simple 3-wire link between two computers with debian lenny (now upgraded to squeeze) on board. Using gtkterm on both of these with the usual, 9600 baud, 8 bit data, no parity, 1 stop bit, no flow control. Sending individual characters, or any group of characters either way shows no problems at all. Using 'Tera Term' under wine 1.1.26 (deb package), with exactly the same settings. Sending from Tera Term, to gtkterm works fine, no problems at all, but sending the other way results in always losing the first two characters of a line, and if it's more than about 8 characters also losing later ones, apparently randomly.
Oh dear [Embarassed] it seems that somewhere along the line Tera Term has developed a fault. When I try this with a different Windows terminal program everything is OK. I'll check out the original program again when I'm back at work. It may be that some intermediate version of wine had a problem, but the current one is OK - I do hope so!
Thanks for your comments guys. I've not had a lot to do with Kermit, and it had never registered with me that you could use it just as a terminal emulator. For some reason I had always thought of it as just(?) a complete file transfer package - ah well, you live and learn :) I've also now found the real cause of the original problem. The makers of the kit I was trying to link were cheapskates and instead of using a proper serial chip, they used a diode-resistor-capacitor trick to level shift 0-15V swings to +-7V (ish). However, there was a dry joint on the diode so it took qute a few cycles before it had built up the DC offset - hence the first few characters being missing. The fact that TeraTerm was exhibiting (apparently) similar behaviour totally threw me off the track :(