Re: LZ: Teleconferece
[Prev][Next][Index][Thread]
>make this program that would alow people to chat
>adn then to page eachother with a small Beep.. well that will take up
>all 28 K or MORE!. to make this work you will need to write a NEW
Yeah, it would take most of the memory.
>trensfer protocol that will compensate for the additional people.
>because the TIProtocol that the calc uses now only makes room for 2
>calcs with not interferance. we need to build one that will compensate
>for interfearence, multiple people at once, and paging.. damn that will
>eb one HUGE program!
>and trying to transfer actual SOUND from one side
>to another and having it plaied on that side..
I didn't mean WAV files or anything, I was thinking along the lines of
musical tones that make up a short tune, like what has already been done on
the 85.
>NEVER! hehe that is
>almost funny to think of it. it would use 28k of mem in 1 sec. and the
>beep or "page" would be amazing in itself because you will need to make
>a daisy chain Y addapter that will have different addresses for the
>different things on it. it would require almost a seperate network card
>to addon to it. (which would eb incredably cool! cause you could trow on
>ROM to stor up data for latter use..) well I cant see the Page thing
>ever happening wiht the beep but you couls have the screen flash a few
>times when you are paged.. that wouldent bee that hard. about how much
>does ASM compress once it is written? cause you are going to use MORE
>then 28000 key strokes to make that program. (I think) well if you want
>ANY help or if you want a flow chart on how I plan to make the program
>to work Please E-mail me cause I have it all planned out! :) its very
>logical but I need to know how the TI prosses's data and how much it can
>handle in a burst. and what are the different specs for the com rutines
>for it? those are all things that are going to determin how this program
>will be wrote. ok well I am really pumped about this Idea! and if I
>couls program in ASM I would... but I still need to lean. >:( darn!
I am currently learning asm. But I've done nothing yet with link I/O. I
will work on it. I think that it is feasible. The best method would be to
have to sender calc transmit a packet which contains its own name and the
name of the calculator that it is going to. All calcs will receive the
message, but only the receiving calc would do anything. I don't think that
this would be difficult. It would require no new protocol. Everything
could be sent out using the normal protocol, except that it will be received
by all calcs, and ignored by all but the target. The beep would be
difficult because of the I/O port problem, but I have a way around that.
Why not put a speaker and a separate battery on the rtlink and set it up
somehow to trigger when something is received (problem with this is calcs
not being paged would also beep, any way around this?). Still looking for
input. It would definitely be a big challenge. The features that are most
important are the page (could be done with screen flashing instead), chat
features (calcs not chatting just ignore transmission), file xfer (send your
newest program out to several calcs at once?!). The only problem with using
the existing link protocol may be if the receiver sends something back to
the sender to say everything's ok. If it does, will that mess this plan up
since all the calc's would send an ok back at once. I'm going to take a
look at some info I have on the link protocol.
************************************************************
* Eric P. Anderson "Who is General *
* crusader@mo.net Failure and why *
* http://walden.mo.net/~crusader/ is he reading *
* Finger for PGP public key. drive C?" *
* Fprint:3E 3C 52 A2 C1 3F 61 B5 71 7F 10 F1 09 B4 D4 D7 *
* This is a public notice that all unsolicited and/or *
* commercial emailers will be charged an archival and *
* downloading fee of U.S. $500. Emailing me signifies *
* agreement to these terms. *
* "The price of freedom is eternal vigilance." -Jefferson *
************************************************************
References: