How access com ports from DOS programs

[Luzius Auer]

I use som DOS programs which access com devices. Serial
communications are practically unusable while running these
programs in XP or XPhome (all of them work flawlessly under
*all* other windows versions):

GeoPoint
Geop3.exe V 3.53) by Geosystem SA
direct interface to digitizers (graphic tablets)

CommsLink for Psion LZ machines:
CL.exe server program for data exchange

Kermit
IBM-PC MS-DOS Kermit: 3.15 15 Sept 1997
Copyright (C) Trustees of Columbia University 1982, 1997

While GUI versions for Kermit and CommsLink are available,
there isnt' any for GeoPoint (programmed in Logitech Modula
3.4)!

What has changed in XP ?
Is there a workaround or a registry setting to change
or is the com support so poorly implemented in XP ?

[Mike Brannigan [MSFT]]

"Luzius Auer" > wrote in message
...
> I use som DOS programs which access com devices. Serial
> communications are practically unusable while running these
> programs in XP or XPhome (all of them work flawlessly under
> *all* other windows versions):
> <snip>
> What has changed in XP ?
> Is there a workaround or a registry setting to change
> or is the com support so poorly implemented in XP ?

What has changed is that the NT family of Windows (of which Windows XP is
the version 5.1 member) do not allow direct access to the hardware - unlike
the 16/32bit Windows products (3.1x/95/98/Me). This improves stability and
security of your PC and the OS. Applications must be written to access the
COM ports via the appropriate operating system calls.
The COM support for applications that follow this new model is perfect.
Your only solution is a change of software to one that works with Windows XP
or reverting to an older operating system where your software is supported.

--
Regards,

Mike
--
Mike Brannigan [Microsoft]

This posting is provided "AS IS" with no warranties, and confers no
rights

Please note I cannot respond to e-mailed questions.
Please use these newsgroups

"Luzius Auer" > wrote in message
...
> I use som DOS programs which access com devices. Serial
> communications are practically unusable while running these
> programs in XP or XPhome (all of them work flawlessly under
> *all* other windows versions):
>
> GeoPoint
> Geop3.exe V 3.53) by Geosystem SA
> direct interface to digitizers (graphic tablets)
>
> CommsLink for Psion LZ machines:
> CL.exe server program for data exchange
>
> Kermit
> IBM-PC MS-DOS Kermit: 3.15 15 Sept 1997
> Copyright (C) Trustees of Columbia University 1982, 1997
>
> While GUI versions for Kermit and CommsLink are available,
> there isnt' any for GeoPoint (programmed in Logitech Modula
> 3.4)!
>
> What has changed in XP ?
> Is there a workaround or a registry setting to change
> or is the com support so poorly implemented in XP ?
>

[Si Ballenger]

On Fri, 27 Jun 2003 13:35:18 +0100, "Mike Brannigan [MSFT]"
> wrote:

>"Luzius Auer" > wrote in message
...
>> I use som DOS programs which access com devices. Serial
>> communications are practically unusable while running these
>> programs in XP or XPhome (all of them work flawlessly under
>> *all* other windows versions):
>> <snip>
>> What has changed in XP ?
>> Is there a workaround or a registry setting to change
>> or is the com support so poorly implemented in XP ?
>
>What has changed is that the NT family of Windows (of which Windows XP is
>the version 5.1 member) do not allow direct access to the hardware - unlike
>the 16/32bit Windows products (3.1x/95/98/Me). This improves stability and
>security of your PC and the OS. Applications must be written to access the
>COM ports via the appropriate operating system calls.
>The COM support for applications that follow this new model is perfect.
>Your only solution is a change of software to one that works with Windows XP
>or reverting to an older operating system where your software is supported.

You are missing the big picture in that these programs still work
under NT and 2K, it is only in *XP* that the problems occurr.

[Mike Brannigan [MSFT]]

"Si Ballenger" > wrote in message
>
> You are missing the big picture in that these programs still work
> under NT and 2K, it is only in *XP* that the problems occurr.

If they worked under 2000 and NT x.x then they are performing actions or
calling APIs that have changed in the way they have been handled.
In which case the advice I provided still stands. Upgrade the apps or
revert to an earlier OS after you have tried the various compatibility modes
available to you under Windows XP.

--
Regards,

Mike
--
Mike Brannigan [Microsoft]

This posting is provided "AS IS" with no warranties, and confers no
rights

Please note I cannot respond to e-mailed questions.
Please use these newsgroups

"Si Ballenger" > wrote in message
...
> On Fri, 27 Jun 2003 13:35:18 +0100, "Mike Brannigan [MSFT]"
> > wrote:
>
> >"Luzius Auer" > wrote in message
> ...
> >> I use som DOS programs which access com devices. Serial
> >> communications are practically unusable while running these
> >> programs in XP or XPhome (all of them work flawlessly under
> >> *all* other windows versions):
> >> <snip>
> >> What has changed in XP ?
> >> Is there a workaround or a registry setting to change
> >> or is the com support so poorly implemented in XP ?
> >
> >What has changed is that the NT family of Windows (of which Windows XP is
> >the version 5.1 member) do not allow direct access to the hardware -
unlike
> >the 16/32bit Windows products (3.1x/95/98/Me). This improves stability
and
> >security of your PC and the OS. Applications must be written to access
the
> >COM ports via the appropriate operating system calls.
> >The COM support for applications that follow this new model is perfect.
> >Your only solution is a change of software to one that works with Windows
XP
> >or reverting to an older operating system where your software is
supported.
>
> You are missing the big picture in that these programs still work
> under NT and 2K, it is only in *XP* that the problems occurr.

[Si Ballenger]

On Sat, 28 Jun 2003 00:54:57 +0100, "Mike Brannigan [MSFT]"
> wrote:

>"Si Ballenger" > wrote in message
>>
>> You are missing the big picture in that these programs still work
>> under NT and 2K, it is only in *XP* that the problems occurr.
>
>If they worked under 2000 and NT x.x then they are performing actions or
>calling APIs that have changed in the way they have been handled.
>In which case the advice I provided still stands. Upgrade the apps or
>revert to an earlier OS after you have tried the various compatibility modes
>available to you under Windows XP.

Then it is an XP problem and not the "NT family" problem as
described below. An important difference.

>> >What has changed is that the NT family of Windows (of which Windows XP is
>> >the version 5.1 member) do not allow direct access to the hardware -
>unlike
>> >the 16/32bit Windows products (3.1x/95/98/Me). This improves stability

[Mike Brannigan [MSFT]]

OK, So the apps are not compatible with the Windows XP - where certain
steps were taken to improve stability and security.
I'm not sure what more you want me to say.
The application vendor will either have to release a patch or a new version
of their application that is compatible.
Windows XP is reaching the 2 year old mark later this year, it is not like
the app vendors have not had sufficient time to take the necessary steps to
make their application compatible.


--
Regards,

Mike
--
Mike Brannigan [Microsoft]

This posting is provided "AS IS" with no warranties, and confers no
rights

Please note I cannot respond to e-mailed questions.
Please use these newsgroups

"Si Ballenger" > wrote in message
...
> On Sat, 28 Jun 2003 00:54:57 +0100, "Mike Brannigan [MSFT]"
> > wrote:
>
> >"Si Ballenger" > wrote in message
> >>
> >> You are missing the big picture in that these programs still work
> >> under NT and 2K, it is only in *XP* that the problems occurr.
> >
> >If they worked under 2000 and NT x.x then they are performing actions or
> >calling APIs that have changed in the way they have been handled.
> >In which case the advice I provided still stands. Upgrade the apps or
> >revert to an earlier OS after you have tried the various compatibility
modes
> >available to you under Windows XP.
>
> Then it is an XP problem and not the "NT family" problem as
> described below. An important difference.
>
> >> >What has changed is that the NT family of Windows (of which Windows XP
is
> >> >the version 5.1 member) do not allow direct access to the hardware -
> >unlike
> >> >the 16/32bit Windows products (3.1x/95/98/Me). This improves
stability
>