@fuckyduck: "hello all,
does a driver of a device that run on Win9x can easily be modified to be
used on WinCE.
Is it easy to switch an application (which does not require display) from
Win9x to WinCE?
What are the rules for moving a software from 9x to CE?
Are there web sites that are talking about that?
Many thanks by advance."
    @chrisNOSPAMPLEASE: "In order to do it you have to have the source code, and then recompile the 
driver in C++ based on the Windows CE Driver SDK documentation for the 
particular version of CE that you are using.
The drivers are in no way interoperable as in the case with 9x and NT where 
changes are more subtle.
Chris Tilley
Editor-in-Chief
___________________________________________________________________________
HPC:Factor 
<url>
HPC:Factor HPC Forums 
<url>
"Fab" <email_address> wrote in message 
news:416ea030$0$29510$<email_address>
<quote>"
    @fuckyduck: "ok I have the full source code (because I did it!) for Win9x. I only need to
change the target in the compiler, that's all?
"Chris Tilley - HPC:Factor" <email_address> schrieb im
Newsbeitrag news:416fe06a$0$11310$<email_address>
<quote>
where
___________________________________________________________________________
from"
    @chrisNOSPAMPLEASE: "In that case you have agood chance at making a port.
However there are some significant API differences as well as the obvious 
hardware ones. The resource assignment differs. You need to get into the 
driver development sections of the SDK for your target device.
Chris Tilley
Editor-in-Chief
___________________________________________________________________________
HPC:Factor 
<url>
HPC:Factor HPC Forums 
<url>
"Fab" <email_address> wrote in message 
news:416fe3b2$0$851$<email_address>
<quote>"
    @r_z_aret: "<quote>
What compiler and language are you using? 
If you are using VS.NET:
You probably can use the same compiler to target Windows CE devices,
depending on which version. I don't use any of these, and don't know
details.
If you are using any C or C++ compiler, other than VS.NET:
You will need to switch to eVC 3 or eVC 4, depending on how you write
your code and/or which platforms you want to target. Given that you
wrote your current program for 9x, you will almost certainly need to
deal with string conversions. Win 9x just barely supports UNICODE,
while Win CE only partly supports ANSI. I _strongly_ urge you to learn
more before you start converting; otherwise you will waste a lot of
your time. If you're using MFC, I _think_ that helps deal with some of
the details (I don't use it, so I'm not sure). I recommend reading
tchar.h (header file that comes with all Microsoft compilers). It is
not meant for human readers (I sure needed several attempts), but it
defines TCHAR and related macros, so understanding it will clarify
many mysteries.
If you are using VB, without VS.NET:
You may have some tough choices. Microsoft never supported VB as a
development platform for Windows CE. They provided eVB for older
platforms; it is essentially VB Script. Microsoft has no intention of
supporting eVB in the future. I don't use VB or eVB, so I don't know
how any of these handle UNICODE.
The following provides a good introduction to "platforms":
<url>
The following provides a decent introduction to UNICODE:
<url>
I just used google (<url> to
look up
windows ce porting code
and got 3830 hits. That would be a _lot_ to look through, but I think
several of the first few will be useful. And a little experimenting
with search strings should let you find very useful leads.
I just used google to look up
unicode
in this newsgroup (comp.os.ms-windows.ce) and got 170 hits. A quick
glance suggests you may need to work a bit to get useful info, but I
think the effort will be worthwhile.
-
To reply to me, remove the underscores (_) from my email address (and please indicate which newsgroup and message).
Robert E. Zaret, eMVP
PenFact, Inc.
500 Harrison Ave., Suite 3R
Boston, MA 02118
<url>"
    @r_z_aret: "Oops, I just noticed that the original post was about porting a
driver. I don't write drivers, so I'm not a reliable source. I _think_
you will need to use Platform Builder. Also, I just used google
(<url> to look up
driver windows ce porting
and got 2840 hits. I took a quick look and am pretty sure at least a
few will be helpful.
<quote>
-
To reply to me, remove the underscores (_) from my email address (and please indicate which newsgroup and message).
Robert E. Zaret, eMVP
PenFact, Inc.
500 Harrison Ave., Suite 3R
Boston, MA 02118
<url>"
    @chrisNOSPAMPLEASE: "You are correct. The full DDK and DDTK's are in Platform Builder for the 
specific required platform.
However you may be able to use the C tools from the VC6 tool kit.
Chris Tilley
Editor-in-Chief
___________________________________________________________________________
HPC:Factor 
<url>
HPC:Factor HPC Forums 
<url>
<email_address> wrote in message 
news:<email_address>
<quote>"
{'source': 'USENET', 'other_information': '{"reply_count": 6, "forum_name": "comp.os.ms-windows.ce.20140227.mbox"}', 'file': 'data/output/usenet-comp.os.parquet'}