Re(2): TI-H: TI Network - TIN

To: ti-hardware@lists.ticalc.org
Subject: Re(2): TI-H: TI Network - TIN
From: Grant Stockly <gussie@alaska.net>
Date: Mon, 19 Oct 1998 19:09:26 -0800
Delivered-To: ti-hardware-outgoing@towerguard.unix.edu.sollentuna.se
In-Reply-To: <fc.000f62d1001238c23b9aca0073a9e8d7.1239af@pinecrest.edu>
Reply-To: ti-hardware@lists.ticalc.org


>listen, there is no mbus, per say. the mbus is just a protocall. the only
>rogram out there that uses the mbus routines is mchat. and the only calc
>that the routines are written for is the 85. ok, here's a list of all the
>stuff that you mentioned, and here's the stuff that most closely resembles
>it that could be developed for the mbus system:
>
>1) You - Multi-calc capability
>1) MBus - Someone just has to write the code for the other calcs. it will
>be the same problem with your new 'tin', except that you are starting from
>scratch and you are expecting to have someone write drivers for all the
>calcs, when all that actually needs to be done is for someone to get up
>off their z80-coding ass and port it

Don't be a Microsoft.  We only need one network standard.  :|

>2) You - File Server
>2) MBus - e(g). a program could be programmed using the mbus routines that
>would use grant's i2c expander.

I can have it done tomorow if I skip my history homework.  :)

>3) You - More Addresses
>3) MBus - listen, how the hell are you going to get more than 100+ calc
>geeks to plug into your hub?

No one in their right mind would net 100 calcs to a 3k backbone.  Btw,
shift registers get quite expensive after the 10th unit.  :)

>nearly all the work is done for the mbus system. its just that people have
>to work with it and write programs using the routines. starting with a
>completely new system would be stupid.

Exactly!  No Microsoft!

References:

Re(2): TI-H: TI Network - TIN

From: fuzz@pinecrest.edu (David Norelid)