Re: WINCE .NET 4.2/Accelent

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

From: Paul G. Tobey [eMVP] (ptobey_no_spam_at_instrument_no_spam.com)
Date: 06/10/04 

Date: Thu, 10 Jun 2004 14:48:12 -0700

I don't recall changing anything else. You might try commenting the
SYSINTR_NETWORK out of nkintr.h and recompiling your platform to see if
someone else is counting on that definition and needs to have oalintr.h
included there. You also have to watch the #include order to make sure
oalintr.h is always after nkintr.h.

Paul T.

"Rick" <Rick.Noriega@Sypris.com> wrote in message
news:rskhc0dm02cgjb1e38g5r0figueicu3i4h@4ax.com...
> I tried this and while it resolved the compiler warning, my ethernet
> connection was working no better. I recently did a side by side
> install of WinCE.NET 4.1 and 4.2. I have another PC with 4.2 alone.
> I am going to build there and see if that makes a difference.
>
> On Thu, 10 Jun 2004 08:59:27 -0700, "Paul G. Tobey [eMVP]"
> <ptobey_no_spam@instrument_no_spam.com> wrote:
>
> >I've done it. The reason you have a redefinition error for
SYSINTR_NETWORK
> >is that Microsoft now defines that in one of *their* header files. Of
> >course, Accelent also defines it. So, you have two choices: edit the MS
> >header file or take other actions to disable the MS version of the
#define,
> >or modify the Accelent source to remove *their* version of the #define
(and
> >correct whatever problems doing those things causes). I disabled the MS
> >define, as I liked the SYSINTR number I was using from Accelent. Here's
> >what I did in oalintr.h:
> >
> >// PGT: One of the QFEs added SYSINTR_NETWORK to nkintr.h. I want to use
> >// *our* value, not the one from nkintr.h, so I undefine it and redefine
it
> >// here.
> >#ifdef SYSINTR_NETWORK
> > #undef SYSINTR_NETWORK
> >#endif
> >
> >// Continue with the Accelent define of SYSINTR_NETWORK...
> >
> >Paul T.
> >
> >"Bruce Eitman (eMVP)" <beitmannospam@nospam.neo.rr.com> wrote in message
> >news:%23HYGajvTEHA.3476@tk2msftngp13.phx.gbl...
> >> Rick:
> >>
> >> The bad news is that I don't think that any other customers did this
work
> >> themselves. I believe that they purchased the upgrade or Schema from
> >> Accelent.
> >>
> >> You may want to contact SMSC to get the source code for that driver.
> >>
> >> --
> >> Bruce Eitman (eMVP)
> >> Senior Engineer
> >>
> >>
> >>
> >
>

Relevant Pages

  • Re: Counting milliseconds on PPC
    ... you can have a stopwatch functionality. ... >> the device actually counting milliseconds between power-off and ... >>> Paul T. ... The practical reason for needing to keep counting when the device is ...
    (microsoft.public.dotnet.framework.compactframework)
  • Re: Adding both .NET 2.0 and 3.5
    ... PB just can't deploy both to the same image and as Paul pointed out, there's no reason to ship both on a device anyway. ... Platform manager allows all versions to be added ... If you need to run .NET CF 3.5 applications, then add .NET CF 3.5 and live with it. ... It looks like that if I have only .NET 3.5 then I am able to execute both 2.0 and 3.5 programs in debug mode using VS2008. ...
    (microsoft.public.windowsce.platbuilder)
  • Re: PPC 2003 Thread
    ... this same executable runs just fine in PPC 2002 platform. ... >> might be helpful to put some debug messages in the thread so you can tell ... >> Paul T. ... >>> Hi Tobey, ...
    (microsoft.public.windowsce.embedded.vc)
  • Re: NETCF2 included but not built
    ... bought Platform Builder and call Microsoft. ... Paul G. Tobey wrote: ... the Platform builder 4.2 has .net compact framework 2.0 ... unpacked from the installation of that works fine in the target ...
    (microsoft.public.windowsce.embedded)
  • Re: NETCF2 included but not built
    ... bought Platform Builder and call Microsoft. ... Paul G. Tobey wrote: ... the Platform builder 4.2 has .net compact framework 2.0 ... unpacked from the installation of that works fine in the target ...
    (microsoft.public.windowsce.embedded)