Re: CE virgin, looking for guidance in finding things

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

OK, then, I'm at a bit of a loss. Maybe CE isn't what I'm looking for,
but what is? I've been looking at OS offerings for about six months
now. Here's what I'm looking for:

1. Something that is available at a hobbyist's price range. I don't
mind spending 200-300$ on on an OS *and* tools, including a C++
compiler. $1000+ to open simply is not an option.

2. Something with predictable latency. I need to run 20 times a second
(more often might be better), without noticable jitter. I'm happy to do
this by spinning in a wait loop for the unused time, broken out by an
interrupt setting a flag - that's the DOS way. (I'd be happier if I
could idle the CPU for my unused time). I recognise that ethernet and
serial traffic automatically contributes to jitter, but at my level of
traffic it shouldn't contribute enough to matter. Mostly, I want an OS
that just handles my I/O and lets me run - not something that has
daemons in the background, demanding time. I don't need disk I/O (after
boot, anyway), I don't need video (might be nice for debugging, but can
live without it), I don't need web services. Just sockets, serial, and
access to in and out instructions so I can talk to other hardware.

3. Something that will handle TCP and UDP. I'm happy to call a "pump"
function to keep the TCP state machine moving, as part of my idle time.

4. Something that doesn't get into memory models, a la DOS. I don't
need much memory, but I'd like it to be flat, so I can grow the code
without getting into a fistfight with compilers. I especially don't
want to find out that I need X's library for TCP, but gosh, that only
compiles under Borland, but Y needs Watcom, and...

As far as I can tell; DOS violates (3&4), unix violates (2), and
everyone else violates (1). Any hobbyists out there way to show me the
better way?

.

Relevant Pages

  • Re: CE virgin, looking for guidance in finding things
    ... compiler. ... Something that will handle TCP and UDP. ... Something that doesn't get into memory models, a la DOS. ... As far as I can tell; DOS violates, unix violates, and ...
    (microsoft.public.windowsce.embedded.vc)
  • Re: CE virgin, looking for guidance in finding things
    ... DOS is not a great choice for you, since it has no sockets interface. ... Something that will handle TCP and UDP. ... As far as I can tell; DOS violates, unix violates, and ...
    (microsoft.public.windowsce.embedded.vc)
  • Re: Linux X demo
    ... when the source code obviously violates a required ... Yes, it's a warning, not an error message, but the standard makes no ... constraint invokes undefined behavior; the standard says so ... implementation's documentation makes a promise that the compiler fails ...
    (comp.lang.c)
  • Re: Bug/problem with lcc-win
    ... layer or through using a sufficiently old version of win32, ... which is a 16 bit DOS emulation mode (which does ... Who writes a Win32 compiler and is ... unfamiliar with the basic execution modes of Windows? ...
    (comp.lang.c)
  • Re: Dos programming
    ... version of DOS, a DOS compiler, a DOS graphics library)? ... stuff in their time that was little known outside the cult-like OS/2 ... a certain compiler (since all have strengths and weaknesses, ... figure out which assembler to use, ...
    (comp.os.msdos.djgpp)