I would recommend trying to contact the WATT-32 library for such
examples... and there is example code on the website, although I'm not
sure it's c++.
I wasn't clear. Code's the only thing I don't need. It's the build scripts
(.bat files, make files, whatever) and examples of how to use the
I'm on the edge of buying hardware for my embedded project. I've been
holding back because I'm nervous about actually assembling the software.
Writing the software is no problem - I have my C++ inline assembler
coded and pretty much ready to go. What I'm uncomfortable with is the
actual process
Honestly, what's the average age on this list? Eleven?
---
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere
dos=high,umb
device=himem.exe
stacks=0,0
stacks - those are for interrupts, right? I mske minimal use of interrupts
myself, but I don't know what the packet driver or waterloo TCP is going
to do. I do know that at least 6 interrupts can occur simultaneously (3
serial ports, ethernet traffic,
I'm getting closer to having my application ready to stick on a TS5500.
I'd like to compile it to use real mode, as that's probably simplest, and
it ought to fit easily in 640k. So my main concern is to push other stuff
into high memory, leaving low memory free for my code and data.
Where can I
I'd originally posted, asking if FreeDOS is right for my application.
Since I've joined the list, I've had one or two people suggest other
operating systems, and a bunch of people bickering of the ownership of
some wretched piece of software. No one has stepped up and suggested that
FreeDOS is
I'm looking for an OS to run on an embedded system (a 586 based PC104)
board. What I need is pretty simple:
1) Access to ethernet, TCP and UDP. (Waterloo should do it.)
2) The ability to hook interrupts.
3) I need to be able to handle serial ports via interrupts; potentially
more than 4 ports
Hi, did you already try Linux, with your software running
as root so that it can access all I/O ports directly?
Or maybe RTLinux to get better realtime performance?
My concerns with Linux:
1) It has to have some sort of processing in the background to handle
ethernet and serial ports - and
I tried compiling my code with Watcom. I got extremely strange behaviour
-
the compiler planted stack checking calls, and the stack checks were
*convinced* I needed vast amounts of stack space to proceed with even
the
first function call out of main(). (I make very little use of the
