Re: Serial Port Application
From: Dean Ramsier (ramsiernospam_at_nospam.com)
Date: 05/28/04
- Next message: David F: "Instrumentation widgets / gadgets for CE .Net 4.2"
- Previous message: John Flynn: "Re: Serial Port Application"
- In reply to: John Flynn: "Re: Serial Port Application"
- Messages sorted by: [ date ] [ thread ]
Date: Fri, 28 May 2004 08:09:49 -0400
You can use the RemoteRegistryEditor available in PB or CE, or use one of
the various CE registry editors that can be found on the internet.
-- Dean Ramsier - eMVP "John Flynn" <anonymous@discussions.microsoft.com> wrote in message news:8D8260B6-357B-497C-A664-81D9F32F1E40@microsoft.com... > Paul, > > How can I view the Drivers/Active list as I am using a locally booted image. Can the registry be viewed from a Windows CE image? > > Thanks, > J > > ----- Paul G. Tobey [eMVP] wrote: ----- > > Nor will you. Drivers/Active is the list, generated at run-time, of the > (surprise), drivers which are actually active. > > So, no, it would not be enough to compare static reg files... > > Paul T. > > "John Flynn" <anonymous@discussions.microsoft.com> wrote in message > news:B8473390-C105-491B-BE7B-9A2647F7A91A@microsoft.com... > > I do not see any mention of Drivers/Active in either platform.reg, > project.reg or common.reg. > >> Although the serial com port I use is defined under. > >> [HKEY_LOCAL_MACHINE\Drivers\BuiltIn\Serial] > >> Would it be enough to compare each reg file (i.e. platform.reg, > project.reg or common.reg) and find the differences. > >> Thanks, > > J > >> ----- Paul G. Tobey [eMVP] wrote: ----- > >> I'd look at the registry of a running device of each type and look at > > HKLM/Drivers/Active. At a guess, you might be seeing an ordering > problem > > with the port names. That is, on his system, maybe the USB part of > the > > registry is first, causing COM1 to be the USB port and COM2 (or > whatever), > > to be the serial port. If the reverse is true on your device, you > might not > > pick up on the fact that they are swapped (or numbered differently in > some > > other way, maybe because of a driver included in one build and not > the > > other). The Active keys should be identical, if the builds are > intended to > > be the same. > >> Paul T. > >> "John Flynn" <anonymous@discussions.microsoft.com> wrote in message > > news:530766B7-958C-4849-B7B8-DAF47D5A588C@microsoft.com... > >> Paul, > >>> Thanks for your reply - sorry for the delay in getting back to > you. > >>> I have not modified the registry at all and I always us a debug > build. > >>> A colleage has completely rebuilt both nk.bin and application > using his > > configuration and this fails with an "Error 55". > >>> I have re-built my configuration and all works well. I do note on > my built > > that the USB devices fail to work but serial devices work fine. > Whereas my > > colleage has USB work but not serial. I don't know if this is a > coinsidence > > or not. > >>> I am at a loss how to go about debugging this one, can anyone > suggest a > > strategy? > >>> Thanks, > >> J > >>> ----- Paul G. Tobey [eMVP] wrote: ----- > >>> Maybe the names of the available serial ports are different. > A > > simple > >> registry difference is all that would be required to cause > this. If > > one > >> image is a debug image, the port might be in use as the serial > debug > > port, > >> making the port unavailable to the API... > >>> Paul T. > >>> "John Flynn" <anonymous@discussions.microsoft.com> wrote in > message > >> news:964B8420-2FD1-48C8-BB5C-E9A8A73185DA@microsoft.com... > >>> I have a serial port test program that I am having trouble with. > >>>> I have a Windows CE image that boots fine. This is an image that > I > >>> created some time ago. I have created a new serial test program > > from > >>> within Platform Builder and then copied this executable onto the > > hard > >>> disk where the WinCE image is. When I try to run this serial test > >>> program I get an "Error 55" when I try to open the serial port. > >>>> I then copied the new nk.bin image to the hard disk (the one that > > was > >>> build at the same time as the serial test program) and this > >>> combination worked fine. > >>>> So I know the the serial test program works fine but not witht > the > > old > >>> WinCE inmage. > >>>> Does anyone know what his problem might be. There seems to be > some > >>> dependency but I don't know what it is. > >>>> Any help would be appreciated. > >>>> Thanks > >>> J > >>>
- Next message: David F: "Instrumentation widgets / gadgets for CE .Net 4.2"
- Previous message: John Flynn: "Re: Serial Port Application"
- In reply to: John Flynn: "Re: Serial Port Application"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
