Similar to United-Ti, Omnimaga now has a board for discontinued projects.  If a major project, meaning a project with its own subforum, is no longer being worked on, it will be relocated to the board "Discontinued Projects."  All topics will be locked but 100% viewable.

Generally speaking, all projects in the folder will have source code available, for example the recent relocation of Seek and Destroy.  If another member wishes to continue the project, the project will be returned to its original location.

Note that if a project has been finished successfully and released, it will not be moved to Discontinued Projects.  For instance my ASM Tutorials have not been relocated.

Oh yeah, I forgot that I shortened BrandonW's routine for using on simply the Ti-83+ BE.  Hence it wasn't "universal"

Hey Hot_Dog, I was sorry to hear about your laptop getting stolen and the project getting disbanded. It was pretty impressive all the stuff that you accomplished though and the other stuff that you have done despite not releasing this is surely going to help the community. I cant wait to see what other "smaller, less important" projects you come up with, because they are gonna be great.

Edit: Ha ha yes I did mean Hot_Dog, sorry I was looking at something else when I was typing.

Thanks, Madskillz!  Yeah, even though these things happen, I certainly don't consider my time a waste considering that S.A.D. helped me learn enough to contribute everything else.

I'm fishing for 2 ships for a simpler game I MIGHT be working on.  I would prefer people who are familiar with the Ptaloid and Tosonian ships from S.A.D.:

http://ourl.ca/6284
http://ourl.ca/6282

Anyways, I'm looking for a Ptaloid version of the Reclauda and a Tosonian version of the Argo.  (I don't mean copy their sprites.  I mean the former should be anti-air, the other is anti-everything)  Just one sprite for each.  Sprites should be at most 15 x 15, at least 9 x 9.

Even if I don't choose the ships you submit, I will give you +1 respect for your submission, unless I can tell you are spamming just to win points.

Wow. I'm sad to see the death of this. BTW, why are there svn files in the folder as well? Do you have a repository somewhere?

Yeah, I have a repository.  The reason I didn't give a link is it has .rom files

Quote from: Hot_Dog on June 28, 2011, 08:05:05 pm

Quote from: thepenguin77 on June 28, 2011, 08:03:12 pm

Yeah, hot_dog, I don't think putting it in the boot code is a good idea, yet. We first need to know what kind of side effects this will have before we make it permanent. (Programs will no longer crash, they will freeze or go crazy.)

Hmmm, that makes sense.  It's for that reason that Crabcake relocks the C000-FFFF area upon shutdown

Wait, you mean you already implemented this? Because if that's the case, then you should save the previous values so that if a person has it permanently unlocked, crabcake won't relock it.

Edit:
    Also with this, you don't to shut down the hooks.

Don't the hooks have problems when a different page is swapped using port $05 on a 15 Mhz?  On the 15 Mhz calcs, RAM is never unlocked.

Whatever the case, I agree about saving the value in case someone permanently unlocked their flash

By the way guys, as a reminder, DO NOT ATTEMPT TO UNLOCK FLASH UNLESS YOU KNOW WHAT YOU ARE DOING.

Modifying the boot code is actually a good idea.  However, I don't see it eliminating Crabcake for three reasons:

1. Crabcake is completely portable
2. There are some people who really shouldn't be messing with their boot code (or who don't WANT to mess up their boot code), namely beginners
3. There's always a chance that TI could write a boot 1.02, after which a new patch might have to be written.

Quote from: Hot_Dog on June 28, 2011, 06:02:11 pm

Cool!  What are the original values?

Too bad this doesn't work on a Ti-83+ BE

It has its own method that's just as easy

Well, almost as easy...