Re: SD: DHOS


[Prev][Next][Index][Thread]

Re: SD: DHOS




Well the comsys talks to the EIIP, which talks either directly to the 
link, or if requested to IR-P, TI-P or I2C-P, and that talks to the link


>From: "Kaus" <kaus@cybrzn.com>
>To: <shell-developers@lists.ticalc.org>
>Subject: Re: SD: DHOS
>Date: Fri, 14 Aug 1998 11:35:30 -0500
>Reply-To: shell-developers@lists.ticalc.org
>
>
>OK now i understand.  does the IR-P, TI-P and I2C-P all go both to the 
link
>and e2?
>Jonathan Kaus
>kaus@cybrzn.com
>
>-----Original Message-----
>From: Matt Butch <mjb25@hotmail.com>
>To: shell-developers@lists.ticalc.org 
<shell-developers@lists.ticalc.org>
>Date: Friday, August 14, 1998 11:02 AM
>Subject: Re: SD: DHOS
>
>
>>
>>
>>
>>>From: "Kaus" <kaus@cybrzn.com>
>>>To: <shell-developers@lists.ticalc.org>
>>>Subject: Re: SD: DHOS
>>>Date: Fri, 14 Aug 1998 10:32:31 -0500
>>>Reply-To: shell-developers@lists.ticalc.org
>>>
>>>
>>>I can do whatever is nesssary.
>>>
>>>Good block Diagram.  It has what i think is needed too.
>>>Question tho:
>>>    What is the ControlSys, and why does it connect to the comm
>>>systems and the kernal?
>>It is a module that enables the user to change stuff.  I'll take it 
out
>>and it will become part of Interface
>>>    Is the interface like In/Out to the screen/from keyboard, etc?  
If
>>so,
>>>why is it between the File Services and the Kernal?
>>Yes, it is the user interface.  the screen and keyboard stuff will be
>>handled by the kernal
>>
>>>
>>>Also, in order to use the other protocols, we need to use the e2.  We
>>wuld
>>>use the etra port on the e2 for these, since the e2 will be plugged 
in
>>most
>>>of the time.
>>>
>>>and shouldn't FileServices be connected to Communications Systems?
>>
>>yes I fixed it up
>>>
>>>Just some thoughts.
>>>Jonathan Kaus
>>>kaus@cybrzn.com
>>>
>>>
>>>-----Original Message-----
>>>From: Matt Butch <mjb25@hotmail.com>
>>>To: shell-developers@lists.ticalc.org
>><shell-developers@lists.ticalc.org>
>>>Date: Friday, August 14, 1998 8:03 AM
>>>Subject: Re: SD: DHOS
>>>
>>>
>>>>
>>>>Good, cause i'm not good at doing graphical stuff.
>>>>
>>>>Ok who wants to do what?  I'm willing to doing the communications
>>system
>>>>or the File Sevices.  We need a list of who wants to do what.
>>>>
>>>>Here is my ASCII block diagram:
>>>>             |-------------------|
>>>>          Kernal<->Interface<->File Sevices
>>>>             ^         ^              ^
>>>>             |         |   |----------|
>>>>             v         v   v
>>>>          Communicaions System<->EII Protocal<--|
>>>>                                    ^           |
>>>>                             |------|----|      |
>>>>                             |      |    |      |
>>>>                             v      v    v      |
>>>>                            I2CP   TIP  IRP     |
>>>>                             ^      ^    ^      v
>>>>                             |-------|---|---->Link
>>>>
>>>>>From: PXGray@aol.com
>>>>>Date: Thu, 13 Aug 1998 18:18:18 EDT
>>>>>To: shell-developers@lists.ticalc.org
>>>>>Subject: Re: SD: DHOS
>>>>>Reply-To: shell-developers@lists.ticalc.org
>>>>>
>>>>>
>>>>>In a message dated 8/13/98 10:47:20 AM US Eastern Standard Time,
>>>>>mjb25@hotmail.com writes:
>>>>>
>>>>><< OK who on this list is from the A85 list about DHOS??
>>>>>  >>
>>>>>
>>>>>I am.  I am interested in programming the OS interface, more
>>>>specifically, the
>>>>>graphical interface, if that is still to be included.
>>>>>
>>>>
>>>>
>>>>______________________________________________________
>>>>Get Your Private, Free Email at http://www.hotmail.com
>>>
>>>
>>
>>
>>______________________________________________________
>>Get Your Private, Free Email at http://www.hotmail.com
>
>


______________________________________________________
Get Your Private, Free Email at http://www.hotmail.com