Hi, Peter.  I use this systm I am on-line to, ONLY, as a pre-processor for
my mail, so I can't respond properly until I get your msg on omy off-line
reader.  :)  Just a small explanation.  :) 
 
However, I just couldn't wait to tell you how much I truly enjoyed your
msg.  High adventure for me - meeting someone like yourself.  
 
I think I asked you about jobs up your way because somewhere rattling
around in my brain was the small hope I just might be able to meet you and
that would be great. 
 
OOPS.  :)  It looks I am straying off topic here - a lot.  :)  Ok, I am
sorry, Mr. Moderator, but it is just this once, OK? 
 
Anyway, I will be getting back to you with my off-line reader.  Yes, Craig
did himself proud in his reply to me.  He has never disappointed me once
since he and I have gabbed on occassion.  In fact, he always surprises me
with his tremenodus knowledge on just about everything.  Sometimes I can't
help but wonder if he sleeps or if he is wired with a Power PC with an
infinite HD built in.  :) 
 
Anyway, back to something that might be technically relevent to OS/2. 
 
I followed up on Craigs info and contacted the company that produces
VxWorks.  I got a menu - right.  No human has called me back yet. 
 
Based on what Craig said tho, it sounds like VxWorks is a stand alone OS
and/or monitor - a Real-time one.  Further, and this is pur conjecture on
my part, it seems this prospective clients specs may be indicating that
OS/2 is used a s the development system where the Real-time system is built
(as in "Building" the Real-time apps for running under VxWorks)
and is targeted for some other PC or other micro or other mini o r
something.  Seems plausible based on my expereince in building embedded and
non-embedded Real-Time systems. 
 
Best I can do now is presume that VxWorks is stand alone multi-tasking
Real-Time system.  OS/2 and/or UNIX is used as the development system to
build apps that run under VxWorks and is used to test the apps (in
emulation) before being installed under VxWorks. 
 
Craig was clear about this and I will be asking what's up in this regard.
He may know since he worked on it for OS/2 V 1.x - I think that is what he
said. 
 
 
You are absolutely correct.  I am making a lot of assumptions - gulp :) - 
based on meager specs from the user thru a consulting firm.  Sheesh, 
when I say it that way, I almost want to puke. 
 
Anyway, things are moving fast right now and there seems to be tons of
software consulting assignments around and If this consulting firm doesn't
get on the ball and get me some answers I will dump them quciker than it
takes to drop an anvil from a one story building. 
 
I am not sure how but Craig seems to have gotten the idea that I do not
have a clue about what Real-Time systems are all about.  Heck, he may be
right, I have only been doing them, on and off, for about 20 years. 
 
I just haven't done them recently and I don't bother to keep up with any
new tools that are out there.  I don't consider myself specializing in
"Real-time systems.  I can't imagine why some people keep trying to
explain to me that Real-Time is a generic term blah, blah.  :)  I will have
to try to read my msg as others might and maybe I will find the answer to
that one.  :) 
 
It is OK, each person that has responded has sort of asserted their
expertise in Real-Time, as it were, by telling me they understand that at
least.  
 
I guess I wasn't communicating in any fully qualifed manner that I was
thinking about very, very, short response times meassured in micro or
milliseconds.  It was nice to be reminded this might be a big assumption.
They were right to remind me. 
 
I was just repeating the job specs, the vague job specs I was trying to
work with - and I see others were as exasperated as I was and am.  You
picked up on the fact that this sjunk was coming from the prospective
client.  Thanks for that.  :)  Talk to you later. 
 
Say hello on the Consulting echo and we will talk about jobs, OK? 
 
Regards, -= Lou =-  
 
--- PC-RAIN 1.00  (á1)