Re: Tech question re: Windows CE

From: Jim March <jmarch_at_prodigy_dot_net>
Date: Thu Jun 22 2006 - 13:08:15 CDT

Joseph Lorenzo Hall wrote:

>On 6/21/06, Jim March <> wrote:
>>Does anybody know where to find a list of WinCE filenames?
>>I ask because we have the Wyle test reports for the latest Diebold TSx
>>listing all of the source code files Wyle reviewed.
>>If we then cross-ref that against a list of CE files, we'll have yet
>>more proof that Wyle never reviewed CE.
>>Any ideas? Or do we get a lawsuit started and get it in discovery from MS?
>Does this help?
>It lists the names of common WinCE modules... I can imagine the
>specific file names are not far off from that. Of course, someone with
>Platform Builder will have source code and should be able to find
>source code file names for WinCE with some inspection. best, Joe

Ah. Yeah, it's a start.

One thing that jumps out at me...the name of the kernal is dead standard
according to the link you just gave (nk.lib - "this module is required
always"). Which jives with a Microsoft chart on the subject, showing
the "OEM modified bits" in blue:

So if we pull up the Wyle 4.6.4 report:

...we damned well should see an "nk.something" source code file, as
that's an OEM-modified module and the name never changes.

Aaaaandddd...<digs through the Wyle report>...<digs some more, it's LONG>...


It ain't there.

Well that's it, folks, final proof these things aren't legal. Absolute
confirmation that custom code is in every TS/TSx without independent
review. Stick a fork in it, it's done, end of discussion.

OVC-discuss mailing list
= The content of this message, with the exception of any external
= quotations under fair use, are released to the Public Domain
Received on Fri Jun 30 23:17:10 2006

This archive was generated by hypermail 2.1.8 : Fri Jun 30 2006 - 23:17:12 CDT