d a full OS - which suggests
to me that something more like a microkernel or an RTOS would better suit
your needs.
# Date: Wed, 19 Apr 2006 19:38:20 +0200
# From: Florian Xaver <[EMAIL PROTECTED]>
# To: freedos-user@lists.sourceforge.net
# Subject: Re: [Freedos-user] re: FreeDos a good choice f
Hi!
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 going to do what I need. Should I take this as a hint that I'm
look
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 goi
>> 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
> 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 stack.)
>
> 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 -
