Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.1 6/24/83; site ecn-pc.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!mhuxr!mhuxt!houxm!ihnp4!inuxc!pur-ee!ecn-pc!wdm
From: wdm@ecn-pc.UUCP (Tex)
Newsgroups: net.micro
Subject: Re: Intel 310s and 380s
Message-ID: <442@ecn-pc.UUCP>
Date: Fri, 13-Dec-85 11:39:12 EST
Article-I.D.: ecn-pc.442
Posted: Fri Dec 13 11:39:12 1985
Date-Received: Sat, 14-Dec-85 08:01:46 EST
References: <421@brl-tgr.ARPA> <564@cylixd.UUCP>
Reply-To: wdm@ecn-pc.UUCP (Tex)
Organization: Cybotech Product Development Lab
Lines: 59
Summary: 

In article <564@cylixd.UUCP> ron@cylixd.UUCP (Ronald Boyd) writes:
>In article <421@brl-tgr.ARPA> ABN.ISCAMS@usc-isid.arpa writes:
>
>>		! Intel also foists IRMX-86 on you (Everyone needs an
>>			archaric multi-user Operating System on a
>>			machine that one person uses?)
>iRMX is a single user, multi-tasking system and is
>sold as a *real-time* operating system. It is continuously being
>upgraded.iRMX is not intended as a development system, but that does not
>mean that it is not a good development environment. 

    "Intel's iRMX 86 Operating System is a real-time, multi-tasking,
    multiuser, multiprogramming operating system designed to support
    high performance, time-critical applications..."

    "In addition, the iRMX operating system provides OEMs with complete 
    development capabilities.  It has systems debuggers, crash analyzers, 
    screen editors, utilities, and an Interactive Configuration Utility (ICU) -
    everything the development engineer needs to design and configure 
    efficiently."

    Both of these quotations come from the Intel OEM Systems Handbook.

    I agree that it does not make for a good development system, but Intel
    apparently doesn't. 

>>		! Kermit is having a hard time here only because the
>As a test, we took the iRMX supplied system with Intel developed
>drivers, and pushed a serial line at 128Kbps with our monitor
>detecting no bit errors. I wonder what is wrong with your driver.

    I'm not sure it really involves the drivers, but I had an interesting
    problem with RMX.  I was designing what amounted to a real-time
    data storage and retrieval system for a robot.  Due to the
    nature of the robot software I had to respond to a query from the 
    robot in slightly lees than 20 ms.  In some modes of operation, the robot 
    would query the system every 20 ms.  Eventually, everything worked fine
    with one exception:  Opening a file on disk took about 100 ms.  This 
    alone caused me no problem.  The problem:  During that interval
    interrupts were disabled; I couldn't respond to my communication query.
    Intel's repsone was that I shouldn't be opening and closing files
    like that - opening and closing files is not a real-time operation.
    
    So, try doing a few things at once, including pushing a serial line
    to 128 kps.

>>	Intel 380's ! BIGGER Multi-User TURKEYS!! 
>>		! Intel hasn't managed to port MS-DOS to these yet!!!!
>The Intel customer base generally has no desire for MS-DOS and as I
>said it seems to port badly.

    You mean there are more people out there developing for non-IBM PC 
    systems than PC-type systems.  That would really surprise me.

>The above opinions do not represent anyone's but my own.

Ditto.