CE 6.0 Duplicate IP Address

Hi All

Our networked CE 6.0 based product can be configured to use static (v4) IP
addresses and so it is possible (likely) that IP address conflicts can and
will occur from time to time. Presently when this happens during testing CE
detects the situation and shows a default duplicate IP address error dialog.
Is it possible to catch this error (exception?) and handle the problem
ourselves in code rather than rely on the default CE behaviour? Our product
will eventually be configured to run in kiosk mode and will not have a
keyboard or mouse attached (app input comes from a serial port) therefore our
users will have no way to dismiss the default error dialog when it pops up.

Any ideas on how to handle this kind of situation would be gratefully
received.

Best Regards

Phil

Paul
Wed Mar 26 08:21:32 PDT 2008

I believe that you can customize NetUI and handle that without showing the
dialog. If you're going to be building a device that has no user I/O,
you'll have to customize NetUI yourself anyway to cover many such
situations. Remember that you don't want to customize it in-place in the
PUBLIC folder (\WINCE500\PUBLIC\COMMON\OAK\DRIVERS\NETUI), but clone it to
your platform folder and make suitable changes. There should be some
information on doing this in the archives, which you can search via
GoogleGroups.

Paul T.

"Phil" <pclaydon@stanleyworks.nospam.com> wrote in message
news:E926B4E8-9BD1-47F2-BB2C-85EAABA7DA67@microsoft.com...
> Hi All
>
> Our networked CE 6.0 based product can be configured to use static (v4) IP
> addresses and so it is possible (likely) that IP address conflicts can and
> will occur from time to time. Presently when this happens during testing
> CE
> detects the situation and shows a default duplicate IP address error
> dialog.
> Is it possible to catch this error (exception?) and handle the problem
> ourselves in code rather than rely on the default CE behaviour? Our
> product
> will eventually be configured to run in kiosk mode and will not have a
> keyboard or mouse attached (app input comes from a serial port) therefore
> our
> users will have no way to dismiss the default error dialog when it pops
> up.
>
> Any ideas on how to handle this kind of situation would be gratefully
> received.
>
> Best Regards
>
> Phil
>

pclaydon
Thu Mar 27 02:40:03 PDT 2008

Thanks for your help Paul. I will give it a try.

Phil



"Paul G. Tobey [eMVP]" wrote:

> I believe that you can customize NetUI and handle that without showing the
> dialog. If you're going to be building a device that has no user I/O,
> you'll have to customize NetUI yourself anyway to cover many such
> situations. Remember that you don't want to customize it in-place in the
> PUBLIC folder (\WINCE500\PUBLIC\COMMON\OAK\DRIVERS\NETUI), but clone it to
> your platform folder and make suitable changes. There should be some
> information on doing this in the archives, which you can search via
> GoogleGroups.
>
> Paul T.
>
> "Phil" <pclaydon@stanleyworks.nospam.com> wrote in message
> news:E926B4E8-9BD1-47F2-BB2C-85EAABA7DA67@microsoft.com...
> > Hi All
> >
> > Our networked CE 6.0 based product can be configured to use static (v4) IP
> > addresses and so it is possible (likely) that IP address conflicts can and
> > will occur from time to time. Presently when this happens during testing
> > CE
> > detects the situation and shows a default duplicate IP address error
> > dialog.
> > Is it possible to catch this error (exception?) and handle the problem
> > ourselves in code rather than rely on the default CE behaviour? Our
> > product
> > will eventually be configured to run in kiosk mode and will not have a
> > keyboard or mouse attached (app input comes from a serial port) therefore
> > our
> > users will have no way to dismiss the default error dialog when it pops
> > up.
> >
> > Any ideas on how to handle this kind of situation would be gratefully
> > received.
> >
> > Best Regards
> >
> > Phil
> >
>
>
>