Re: Disable "Receive all incoming beams"

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

The setting doesn't take effect immediately, try broadcasting a
WM_SETTINGCHANGED message and see if that works. You can find examples of
broadcasting the message in the archives of this group:-
http://groups.google.co.uk/group/microsoft.public.dotnet.framework.compactframework?hl=en

Peter

--
Peter Foot
Windows Embedded MVP
http://www.inthehand.com | http://www.peterfoot.net |
http://www.opennetcf.org

<maderjc@xxxxxxxxx> wrote in message
news:1116864837.616538.64990@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
> Ok I am trying to enable and disable the "Receive all incoming
> beams" so that I can use the OpenNETCF port. I am able to update the
> registry to make sure that the "IsEnabled" key if 0 'false' when I
> open the port. And then return it back to it pervious state when I
> close the port.
>
> Below shows the registry entry I am looking at.
>
> subKey = Registry.LocalMachine.OpenSubKey(@"SOFTWARE\Microsoft\Obex",
> true);
>
> if (subKey != null && subKey.ValueCount > 0)
> {
> subKey.SetValue("IsEnabled", iBeamValue);
> }
> if (subKey != null)
> {
> subKey.Close();
> Registry.LocalMachine.Close();
> }
>
>
> But when I change the "IsEnabled" from 1 'true' to 0
> 'false' right before I open the port I receive an error that the
> port is busy (OpenNETCF.IO.Serial.CommPortException:CreateFile Failed:
> 55). I look at the registry with a RegEdit utility and it shows the
> value at 0 'false'.
>
> So where am I going wrong?
> Do I need to refresh the registry after I update the value? How would
> I do that?
> Am I looking at the wrong registry entry?
> Does OpenNETCF port not use the registry to see in the Beams are
> enabled?
>
> I am using a Dell Axim x50 running Window Mobile 2003.
>
> Thanks,
> Jason
>


.

Relevant Pages

  • Re: Serial Port Application
    ... Can the registry be viewed from a Windows CE image? ... drivers which are actually active. ... >> Although the serial com port I use is defined under. ... I have created a new serial test program ...
    (microsoft.public.windowsce.app.development)
  • Re: Cannot Remote Desktop to home PC after installing XP SP3
    ... Remote Desktop unless a registry tweak is made. ... Are you connecting from a client which runs rdp 6.x? ... machine or port). ...
    (microsoft.public.windows.terminal_services)
  • Re: start service with parameters on restart
    ... i've rebooted the server with the registry hack in place. ... "Pegasus (MVP)" wrote: ... the parameter is a port number, ...
    (microsoft.public.windows.server.general)
  • Re: How do I clean out unwanted virtual COM ports?
    ... If I have a parade of devices with unique serial numbers the registry grows and grows with clutter. ... The problem is even worse when the devices are USB to serial devices that are assigned the next available COM port as well. ... However if the device is re-tested it will want to run the found new hardware wizard and add to the registry. ... I know the devices are gone for good and I want to pass this gem of knowledge on to windows to remove clutter and free consumed resources. ...
    (microsoft.public.windowsxp.general)
  • Re: benötigte Ports für FE-BE-Kommunikation durch eine Firewall
    ... > Firewall hindurch gehen muss. ... One port for the Active Directory logon and directory replication interface ... This value is not set in the DSProxy or System ... To map the port in the registry: ...
    (microsoft.public.de.german.exchange2000.setup.installation)