Re: Windows CE 5.0 bug list

Concerning VMini problem. Do You have "Wired Local Area Network (802.3,
802.5)"
feature included in Your current OS design? Can't remember where it comes
from (sysgen, makefiles or just catalog file) but it is true. VMini will be
built
and included into image only when "Wired Local Area Network (802.3, 802.5)"
presents, i.e. SYSGEN_ETHERNET=1. Why they (MS) did this way
is not very clear...

"Soh Kok Hong" <khsoh@xxxxxxxx> wrote in message
news:%23DY0iKfZFHA.1412@xxxxxxxxxxxxxxxxxxxxxxx
> Hi all,
>
> Is there a bug list some where for Windows CE 5.0? I sure hope there is
> one because this OS really need a bug list so that developers do not
> have to rediscover the same bugs. Strangely, none of these bugs could
> be found in the wince newsgroups. So, I've decided to post a list of
> the few bugs (with fixes) in this newsgroup unless MS decides to stop me
> from doing so. I've not posted actual code on fixing the bugs as I am
> not too sure if it is legal to post MS copyrighted and licenced code here.
>
> I've just started working with Windows CE and am trying to get it up and
> running on a CEPC platform (using an old Pentium III PC). And I was
> stuck at some of these errors:
>
>
> 1. The eboot loader (the one that loads the image via the ethernet) does
> not work for PCI ethernet devices that use PCI Bus Master mode. This is
> a problem for RTL8139x, DP83815 and 3C90x devices. The only reason it
> may work on some platforms is if the cards had been plugged into
> "special" PCI slots that turn on the bus master capability by default or
> if you had forced your PC BIOS to enable it. It would be nice if
> Microsoft had fixed it in the InitKitlNIC function. This bug would
> explain why the CEPC bootloader had been stuck trying to send out DHCP
> Discover packets.
>
> 2. The PC had only one ethernet port - hence, the platform and the
> debugger had to share the port. Digging through the documentation
> revealed the need for vmini and vbridge to be linked in. vbridge is a
> library that was already linked in via the Platform Builder settings.
> vmini is a DLL that has to be loaded. However, I discovered that
> vmini.dll was not built because of an invalid vmini.def file (supplied
> by MS) that requested for a static library to be built but not a DLL
> (the module def file had TARGETTYPE=LIBRARY). I'm still working on this
> to get VMINI up and running so that I can confirm that the target device
> and share the ethernet port with the debugger.
>


.