Re: Windows 7 64 bit and IO.Ports.SerialPort

From:

"mattd1" <someone@microsoft.com>

Newsgroups:

microsoft.public.dotnet.framework

Date:

Thu, 11 Feb 2010 10:46:03 -0500

Message-ID:

<eVPjSFzqKHA.4220@TK2MSFTNGP05.phx.gbl>

I did try that, and it just gave me different errors. I may wind up using XP
mode to see if that can get around the problem. I thought I would be safe
using the built in serial port classes. Guess I was wrong.

Thanks for the reply though

Matt

"Family Tree Mike" <FamilyTreeMike@ThisOldHouse.com> wrote in message
news:e5mUe$yqKHA.4752@TK2MSFTNGP04.phx.gbl...

On 2/11/2010 9:49 AM, mattd1 wrote:

Hi all -

Is anyone using the IO.Ports.SerialPort object successfully under Windows
7
64 bit? My PC crashed and in the rebuild I moved to 64 bit Win7, and now
an
app I had running successfully for quite a while (probably a year) on 32
bit
Vista now does not work on Win7 64 bit. I get various random errors, like
stack overflows in mscorlib, uninitialized objects, all in mscorlib.
Twice
while debugging I stepped through some comm code, and it actually blue
screened Win7 with a page fault. I have other apps that do not use the
serial port, and they work fine on 64 bit, it seems the serial port
object
has some serious problems in 64 bit. Can anyone confirm this? Or tell me
what magic trick needs to be performed to get it to work right?

Thanks

Matt

I don't have particular knowledge about the SerialPort class. Whenever
this type of scenario would occur in other codes moved to 64 bits, I would
rebuild the application targeting 32 bits (x86) and try the application in
that mode. The "Any CPU" mode seems to provide a false sense of security
in some respects.

--
Mike