On 12/5/06, Donald E Haselwood <dhaselwood@verizon.net> wrote:
> > -----Original Message-----
> > From: slug@nks.net [mailto:slug@nks.net] On Behalf Of Chuck Hast
> > Sent: Tuesday, December 05, 2006 10:51 AM
> > To: slug@nks.net
> > Subject: [SLUG] VB issue under wine
> >
> > Do any of you run VB stuff under Wine? I have two of these things I have to
> > run here in the office, and so far I have not had luck getting them going.
> >
> > I think that it is a serial port issue but I can not figure out what I need
> > to do in order to correct it, I did find one recommendation that a entry be
> > made to the system.reg file, which I did but it did not work.
> >
> > When I run both of them they start up just fine, but when I get to the
> > point where I select the serial port and then hit the next step button (on
> > one it is start on the other it is just a 'OK' button which you punch after
> > selecting or accepting the serial port parameter and port number selection.
> >
> > The error I get is 8005, I think that the issue is that MSCOMM32.OCX is
> > looking for a comm port and I need to have something in there to make it
> > think it is talking to a comm port which then does whatever conversion is
> > needed to talk to a tty.
> >
> > Does anyone have any info on this?
> >
> >
> > --
> > Chuck Hast -- KP4DJT --
>
> Chuck,
>
> The only info I have is that I haven't been able to run a VB program that uses
> com ports, either. The routine, 'hcload.exe', is used to load and setup a
> HC11 micro over the com port. It's a rather simple program.
>
> I tried installing the program using Crossover. The installation ends with
> "success," but when I execute the routine nothing happens. Since the routine
> checks the com port as soon as it starts I presume it has to do with the com
> port. I had no luck with wine, either.
>
> I presume you have the directory '~/.wine/dosdevices' links setup correctly
> for your com port, e.g. 'com1 -> /dev/ttyS0'.
>
Don,
I realized today that I was trying to select on the VB app the wrong comm
port, now I no longer get the 8005 error, but I do not get any data flowing
across the serial port.
I do not have this directory that I know of, I will look at it tomorrow at work
and see if such a directory and file was created.
I have two programs, one that just opens the comm port and watches for
a data string starting with a radio callsign, as soon as a string arrives
wtih the right callsign, it captures it and parses out the water level data.
Only thing is that it does not get any data from the comm port. I can run
minicom and see the data arrive at the serial port, so I know it is working.
I will have to look into the file you mention above. Thank you for the info.
-- Chuck Hast -- KP4DJT -- To paraphrase my flight instructor; "the only dumb question is the one you DID NOT ask resulting in my going out and having to identify your bits and pieces in the midst of torn and twisted metal." ----------------------------------------------------------------------- This list is provided as an unmoderated internet service by Networked Knowledge Systems (NKS). Views and opinions expressed in messages posted are those of the author and do not necessarily reflect the official policy or position of NKS or any of its employees.
This archive was generated by hypermail 2.1.3 : Fri Aug 01 2014 - 20:04:07 EDT