Serial port not working with legacy programms on XP laptop..

G

Guest

Guest
Archived from groups: microsoft.public.windowsxp.hardware (More info?)

have a VB6 executable talking via serial port to an external instrument.
It works fine on a number of machines running ME and Windows95 on a old
IBM380D laptop , but fails on any newer IBM T40 running XP.
Any change to serial comm driver in XP?. How can I revert to a different
driver?
Ted.
 
Archived from groups: microsoft.public.windowsxp.hardware (More info?)

You can not! Windows Nt/2000 and XP does not allow you to access to
hardware directly, like Windows 9x/ME. You will need to change the VB6
program in order to ue the WDM driver model.

"Titi Trandafir" <ttrandafir@juvent.com> wrote in message
news:eVa36FqNEHA.3264@tk2msftngp13.phx.gbl...
> have a VB6 executable talking via serial port to an external instrument.
> It works fine on a number of machines running ME and Windows95 on a old
> IBM380D laptop , but fails on any newer IBM T40 running XP.
> Any change to serial comm driver in XP?. How can I revert to a different
> driver?
> Ted.
>
>
 
Archived from groups: microsoft.public.windowsxp.hardware (More info?)

"Titi Trandafir" <ttrandafir@juvent.com> wrote in message
news:eVa36FqNEHA.3264@tk2msftngp13.phx.gbl...
> have a VB6 executable talking via serial port to an external instrument.
> It works fine on a number of machines running ME and Windows95 on a old
> IBM380D laptop , but fails on any newer IBM T40 running XP.
> Any change to serial comm driver in XP?. How can I revert to a different
> driver?
> Ted.
>
>

What do you mean by *fails* ?
 
Archived from groups: microsoft.public.windowsxp.hardware (More info?)

If you are either using Windows API functions to communicate through
the serial port or if you are using the MSComm ActiveX control that
comes with Visual Basic 6, then your code should work just fine no
matter what OS version you are using.

What type of error are you seeing? Are you able to open the COM port
but are not able to send or receive data or does your code fail when
you try to open the port?

If the code fails when you try to open the port, then it may be
related to the following problem:

If the device that you have connected to your serial port sends data
continuously and you are running Windows NT/2K/XP, then the problem
may be that Windows thinks that the device is a serial mouse and is
installing the mouse driver for the COM port when you first boot up.

The following URL contains more inforamtion on how to fix this type of
problem.
http://www.taltech.com/support/troublsht/NTDetect.htm


If you are able to open the port and cannot send or receive data then
the problem may be hardware related. Check that the ribbon cable that
goes from the motherboard to the COM port on the back of the PC is
plugged in correctly. You might also try using the Hyperterminal
program that comes with Windows to open the port to see if you can
send and receive data from it. If you can communicate using
Hyperterminal, then the problem is in your code - perhaps you have the
wrong serial communications parameters.

If you cannot send or receive data with Hyperterminal, then you most
likely have some other hardware problem - a bad cable, etc.



On Mon, 10 May 2004 08:14:21 -0700, "Titi Trandafir"
<ttrandafir@juvent.com> wrote:

> have a VB6 executable talking via serial port to an external instrument.
>It works fine on a number of machines running ME and Windows95 on a old
>IBM380D laptop , but fails on any newer IBM T40 running XP.
>Any change to serial comm driver in XP?. How can I revert to a different
>driver?
>Ted.
>
 
Archived from groups: microsoft.public.windowsxp.hardware (More info?)

I am not using API functions , I am using MSComm control in VB6.
NOTE: The protocol to talk serially to my external instrument is very simple
, I am sending a character and expect back another char.
It works fine when I try to communicate from XP hyperterminal.

Ted.



"Thomas Lutz" <tom@taltech.com> wrote in message
news:5qov901skuk12mf78dl7omlpgqcr0bmesv@4ax.com...
> If you are either using Windows API functions to communicate through
> the serial port or if you are using the MSComm ActiveX control that
> comes with Visual Basic 6, then your code should work just fine no
> matter what OS version you are using.
>
> What type of error are you seeing? Are you able to open the COM port
> but are not able to send or receive data or does your code fail when
> you try to open the port?
>
> If the code fails when you try to open the port, then it may be
> related to the following problem:
>
> If the device that you have connected to your serial port sends data
> continuously and you are running Windows NT/2K/XP, then the problem
> may be that Windows thinks that the device is a serial mouse and is
> installing the mouse driver for the COM port when you first boot up.
>
> The following URL contains more inforamtion on how to fix this type of
> problem.
> http://www.taltech.com/support/troublsht/NTDetect.htm
>
>
> If you are able to open the port and cannot send or receive data then
> the problem may be hardware related. Check that the ribbon cable that
> goes from the motherboard to the COM port on the back of the PC is
> plugged in correctly. You might also try using the Hyperterminal
> program that comes with Windows to open the port to see if you can
> send and receive data from it. If you can communicate using
> Hyperterminal, then the problem is in your code - perhaps you have the
> wrong serial communications parameters.
>
> If you cannot send or receive data with Hyperterminal, then you most
> likely have some other hardware problem - a bad cable, etc.
>
>
>
> On Mon, 10 May 2004 08:14:21 -0700, "Titi Trandafir"
> <ttrandafir@juvent.com> wrote:
>
> > have a VB6 executable talking via serial port to an external instrument.
> >It works fine on a number of machines running ME and Windows95 on a old
> >IBM380D laptop , but fails on any newer IBM T40 running XP.
> >Any change to serial comm driver in XP?. How can I revert to a different
> >driver?
> >Ted.
> >
>