Hi! Well, Wine reports (with +comm,+file) right after you activate the GPS add-on, that the program initializes the com ports... However, the parameters of the port never get set, I also suspect, that these 5 dlls responsible for the gps relaying don't get activated... Is there a way to "pre-load" them (if they are supposed to run as service, they should probably be loaded all the time, right? )? Anyway... Tomorrow I'll buy a non-MS software; hopefully they implemented the NMEA protocol within the same exe and only 10 k code, instead of M$ 1,5 MB/5 files.... If it's not working out, I'll be back here! ;) Richard <lawson_whitney@juno.com> wrote in message 20011209.120201.134660752.0.lawson_whitney@juno.com">news:20011209.120201.134660752.0.lawson_whitney@juno.com... > On Sun, 9 Dec 2001, Richard Scheffenegger wrote: > > Huh? Wine reports what you tell it (with --debugmsg) to report. > If you are saying --debugmsg +comm shows that, there might be hope. > try: > > wine --debugmsg +file,+comm blah.exe 2>&1 | tee logfile > > Basic serial IO works, though the app may get hardware flow control when > it doesn't want it (this is in the process of being fixed). > > If the stupid app expects to find the comm port with DUN, RAS, or TAPI > you are welcome to figure out what those are 'spoze to do and make up > patches to implement one or more of them. > > I helped a bloke in Australia get one of those GPS things working maybe > a year ago. Maybe it was 2. Probably not an NT version, though. > In fact I don't think it was a M$ software at all. > With micro$oft, newer is nastier. >
