Post updates on your projects here, or give other authors your feedback on their works in progress.

When posting about an upcoming program of yours, please include a link to any relevant information (screen shots, etc.) in the URL field.

To have an entry removed, please Contact Us.

I hope to make a MacOS shell, sort of, for the TI86. I will hopefully post more, a lot more, information later

As is said, I would be posting more information later. Here it is. "I NEED HELP!!!" Anyone who would like to help me, give me ideas, constructively riticize, "constructively " criticize,or maybe alpha and beta test (later, way way later). Email me at ti86macos@hotmail.com. Then once I have a "group", I will give out information and questions.
NO WINDOWS USERS. No linux, unix, or other non-mac Operating Systems. Perferably Mac OS 9 users, but any will be accepted.

I finally was able to complete an extremely basic and ugly looking little variable displayer. I was hoping that someone here who would like to help me will look at my source and help me optimize it. I will have the source and program uploaded on my website within the next 3 days. I will use about 80% of this code in my MacOS.

Why?!?

MacOS blows as it already is.. why make it suck even worse, and put it on a perfectly good calculator?

A MacOS shell would be great, as long as it's small!

What do you all think about a little device that holds between 1 and 2 megs of memory, and is about the same width and thickness of the 86, but only about an inch to an inch and a half long. It would immediately interfaces with the calculator with a nice graphical interface that tells the user what the calculator contains and what the device has on it, and you have the option of running whatever is on the device, copying the data from the device to the calc, or sending data from the calc to the device. What do you think about that?

For this, you could have a device that attaches to the link port and reads a SmartMedia or Compact Flash card. A powerful microcontroller such as one of the PIC18 series devices could drive the interface if you're willing to solder surface-mount ICs. Some of NEC's 32-bit microcontrollers could also be good. This way, you could read it on a PC with a commercial reader, if the drivers used a standard FAT16 file system.

I am currently developing an assembly monthly planner program. It is about 30% completed. It will allow the user to input data about a day of the month, and then it will either keep the info, delete the info, or move it to a different day, based on the options the user selects for that data. The user, of course, must set the current day, for the data to be updated. It will also allow for permanant days such as birthdays or christmas. Any comments or suggestions are welcome.

Does anyone actually read the misc section. If so please reply. My program is about 50% done. I have implement an alogrithm that will calculate January 2002-Decemember 2099. I am now working on saving the entered data.

yes, some people read it. if you need a beta tester to help you work out the bugs, i'm willing to help.

Sounds good, I still have a way to go before I get a decently running program together (right now it just displays the months and that's about it). The problem I'm running into now is trying to get the information on ram page 1 $8100 (where I store the data entered temporarily) into a string. I may have to try something other than a block copy. I haven't tried the program with any shells yet, but if they use any of the safe memory areas then it probably won't work to well ... guess I'll leave that the testers when I decent version together.

I have found the error!!! It took me days, literally days of tearing up my code to find the ram page block copy error. It doesn't lie in the block copy. It doesn't lie in adding the data. It is right here: call execPg3. This piece of junk some how messes up a lot of the ram page, so I am not going to use it. That sets me back to 30% completed... Oh well... Found out a lot of interesting things about ti's memory... Oh yeah I have pics of the program on my website (although the website really sucks), so check it out if you want to. The black part is a cursor that inverses the pixels in the box when you move it around.

Oh yeah ... how is your MacOS program coming along?

very slow, but getting there.

First version released. Not to much there. Check it out and tell me what you think. www.csupomona.edu/~beroybal/monthly.html

I implemented more features now...Haven't uploaded yet...have a few bugs to work out. IMPORTANT: if u send me something make sure to include TI (with caps) in the subject.

Website and program updated...

Second to probably last version released. I will wait approximately one week (for testing, comments, suggestions) before I try to upload the program to ticalc. A lot of features have been implemented. Hope you enjoy the program...

Oh yeah the website is
http://www.csupomona.edu/~beroybal

Have you had the chance to check it out JohnC.?

Fixed known bugs. Have, at least in theory, allowed shells to run this program successfully. If someone could run this program against the different shells that would be helpful.

Yeah, I have. Sorry, I haven't had time to reply, but its nice.

Thanks, I'm glad you like it. For anyone who reads this I have, well actually Pete, found a bug in the program... Well actually there might be a few... but only 2 that I know of. It does not work with A-shell, or at least the one time I tried it. Also, if you enter multiple spaces (more than one) it can do anything from write back to the shell your in, to freeze the calc. In the new version...probably won't be out for quite a while... I plan to implement error detection in the string I hold the data in... This will seriously help most of the bugs... (as a side note, I uploaded a little binary program I created to help myself understand the memory, I don't know when or even if it will be put on ticalc.org. In the program though you just enter any binary number (101011 or 111111111111111111111111111101) and it should spit out the decimal equivalent (although if the binary is to big it will give you something like 5.00293E11 which I don't think would be all that helpfull)