Osgeld wrote:
Thanks for the interest! keep in mind I was just having fun with my apple and yea there are a billion ways to do it better. yes beagle compiler is used along with a memory driver and fast hplot. I originally went with the compiler because I thought I was going to do most of the XPM image decoding on the apple, though after seeing transfer times while trying to not loose any characters in the buffer, in basic, it would not be practical in this implementation. I wanted to use shape tables, I spent a while messing with hi writer and font mechanic and I could not get either to play nice with beagle compiler, though this was still back when I was trying to shovel as much work as possible to the Apple and the compiler was required IMO
I suppose you discovered that there is no good way of listening constantly for data transmissions at 115kbps while doing anything else. It is necessary to have the sender (the PC) wait to send until data is requested by the Apple II. That way, all the data can be sent at once, and the end of transmission must be unambiguous, with no more data sent until the Apple next requests it. When the end of data is determined, the Apple II can then process the data before requesting more, without any compromises for quick response to a fast serial port. -michael NadaNet 3.1 for Apple II parallel computing! Home page: http://home.comcast.net/~mjmahon/ "The wastebasket is our most important design tool--and it's seriously underused."