🚀 go-pugleaf

I have a question about Window's ability to truly multitask.

Windows is touted as a Multitasking OS for DOS computers.  What I
want to know is if anyone has had a good experience with this.  I
understand that Windows uses a non-preemptive scheme of giving 
tasks time to accomplish their jobs.

What I need to do is Real Time(tm) I/O.  Unfortunately the
customer has a big woody for Windows.  (Another victim of a 
ruthless marketing scheme.)  I am attempting to persuade
him that there are better things out there for his application.
If I am wrong in thinking that Windows will not be a wonderful
platform to develop under... well I guess you can tell me. ;)

As I see it, something else that provides true Multitasking and 
transparent networking (ie QNX) would be much better suited to
meet the requirements.

Has anyone attempted to network two PCs under windows. (make them
communicate RS232)?  ie... Send messages from a process on one
machine to a process on another machine?  How about Ethernet under 
Windows?  Or does Windows come in a network version with which
I can accomplish interprocess communication?  Should I RTFM?

How many processes can I launch under a session of windows without
causing my Compaq386/20e to slow to a crawl and then barf on itself?

My biggest problem is being able to prioritize I/O.  Right now
everyone waits his turn.  Sometimes waiting your turn is just not
the way I want to go.  Time slices seems to be a much better idea
to me... and I can implement priorities.

I want to hear some experiences on how Windows works as an embedded 
I/O controller with a maintenance interface to the world.  Or is
this a ridiculous use for Windows like I think it is?

Greg Kelley        gak@inel.gov  (internet?)
- I work for a perfectly safe and wonderfully compliant company.  For
  example, check out the disclaimer that they attach to my news 
  postings without even asking me!

========== long legal disclaimer follows, press n to skip ===========

Neither the United States Government or the Idaho National Engineering
Laboratory or any of their employees, makes any warranty, whatsoever,
implied, or assumes any legal liability or responsibility regarding any
information, disclosed, or represents that its use would not infringe
privately owned rights.  No specific reference constitutes or implies
endorsement, recommendation, or favoring by the United States
Government or the Idaho National Engineering Laboratory.  The views and
opinions expressed herein do not necessarily reflect those of the
United States Government or the Idaho National Engineering Laboratory,
and shall not be used for advertising or product endorsement purposes.