Re: coredll CreateFile on serial port
From: Daniel Moth (dmoth74_at_hotmail.com)
Date: 02/22/05
- Next message: GraemeR: "Re: coredll CreateFile on serial port"
- Previous message: GraemeR: "Re: coredll CreateFile on serial port"
- In reply to: GraemeR: "Re: coredll CreateFile on serial port"
- Next in thread: GraemeR: "Re: coredll CreateFile on serial port"
- Reply: GraemeR: "Re: coredll CreateFile on serial port"
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 22 Feb 2005 23:06:30 -0000
> Before leaving the thread can yopu advise the reference you used to fin
> error code 183?
Launch eVC (if you don't have it, it is a free download)
Tools->Error Lookup
Cheers
Daniel
-- http://www.danielmoth.com/Blog/ "GraemeR" <graeme@wave_nospam.co.nz> wrote in message news:cvgdkb$ghg$1@lust.ihug.co.nz... > Thanks Daniel. > >> It sounds like some other application is keeping the port open (probably >> your CEWedge). The port can only be used by one process at a time. > I thought of this. I manually reset the iPAQ (reset button on bottom) > before running my test code. Painful and slow, but must be done. > >> If you ever get a valid handle you should call CloseHandle when you are >> done. > I close the port when I'm finished with it; or attempt to reopen it. I'm > using a flag value of -1 to indicate the port is closed (i.e. handle not > initialised) > >> Let me advise you again to use one of the opennetcf classes or at least >> look at the code to see how to call the native APIs. > Have been trying but am a little weak with C# (and VB .NET) code. > > Before leaving the thread can yopu advise the reference you used to fin > error code 183? > Cheers, Graeme. >
- Next message: GraemeR: "Re: coredll CreateFile on serial port"
- Previous message: GraemeR: "Re: coredll CreateFile on serial port"
- In reply to: GraemeR: "Re: coredll CreateFile on serial port"
- Next in thread: GraemeR: "Re: coredll CreateFile on serial port"
- Reply: GraemeR: "Re: coredll CreateFile on serial port"
- Messages sorted by: [ date ] [ thread ]