>>>Detached Solutions takes no responsibility for any adverse effect that this software could cause to your machine or the data on it: backup important data before using Command Post. Command Post is protected by copyright laws and international copyright treaties, as well as other intellectual property laws and treaties. Command Post is licensed, not sold.

even if i pay $15 to get it licensed to me?... you'd think it should be 100% bug free if people are paying for it, and that you should take responsibility for lost data...

"100% bug-free" is nearly impossible, unless you have below 10 lines of code. There are all sorts of externalities that have to be considered: memory capacity, other apps installed, etc. $15 wouldn't be enough for 100% bug-free :-p

And something that is supposed to prevent crashes, is it Command Post's fault or the program's fault that it crashed? :-p

I don't think it's Command Post's fault if you're trying to make it crash :)

Correct. If the user is messing with the application in areas that are not meant to be messed up, then the application has a higher probability of crashing. The program, when correctly used, should be stable.

i know, but if i'm paying for something, i want to be able to blame the person i paid if it screws something up

Technically a program can't mess up. A program is an inactive bit of data without the user interacting with it. Therefore the user is the one that screws up, not the program.

that's beside the point. a program CAN do something that it was not intended to do. so unless you're telling me that it's impossible for a program to crash my calc, then you're not saying anything special. if i pay for a program then the maker of that program should take responsibility for any bugs that cause my calculator to crash. i'm not saying "if it's on my calc and my calc crashes then it's that program's fault".. i'm saying if it IS that program's fault, and i lose important data, and i paid for the program, then the maker should assume responsibility.

I'm just being as literal as possible here: a program won't do anything - inside or outside its specifications - unless the user starts it; so technically, the user causes all the errors.

so what's your point?

Barrett,
Every program i have ever used has had bugs. You can be sure that Command Post suffers from them as well. However, I think that it would be good to point out that Command Post has been tested heavily since september (over 5 months!) by myself and those who offered to be beta testers. during this time frame, very few features were added, and bugs that showed up were fixed.

I never leave people using my free programs high and dry if they have problems (often i fix the bug if there is one and send them an updated copy the next day); why should i make an exception for a program that I sell? One of the items in the Professional License IS support after all.

-Greg

i'm saying, IF i pay for it, AND it has a bug, AND that bug crashes my calculator, AND that crash causes me to lose valuable data, you should take responsibility in one way or another, either by apology (weak) or compensation by either recreating what they did, or being their slave for a while.

I'm not saying any of this will happen of course; i don't plan on buying it (or using it), and i don't program BASIC anymore and i don't use my calculator for valuable data.

i refuse to take any responsibility for something like that... just like any other company and/or individual will not take responsibility.
If you read the licenses with every piece of software you buy, they will essentially say that 'this product doesn't actually do anything even if you expect it to, and if it goofs up, it is your (the users) fault'

Microsoft and Cerulian Studios (makers of trillian), and the GNU GPL all say the same thing: No warranty. We take no responsibility for anything bad that happens.

Every company says that simply because they know that it is _impossible_ to remove every bug from a piece of software.

-Greg

This is amazing!!!!

The following Basic program exploits a bug in the ams:

prgm
local x
fill 0,x
endprgm

execute this and you will get an address error. I suspect this has to do with derefencing a handle that is null...

With kerno installed the error is caught and the program exits normally.

With command Post installed the error is caught. And now you get the standard dialog box that lets you go to the offending line of basic that caused the address error!

Congratulations Greg!

Yay! BASIC errors! Good for pranks :)

It's good that CP can detect this stuff. I use PreOS... will that also detect crashes? I think it has before. I might have to try that. Does it work on all AMS versions?

the crash protection works best with AMS 2.08 because TI fixed some of their bugs... for instance, in AMS versions less than 2.08, the home screen will say something like "error not found" instead of "Address Error" in the history. This doesn't affect the crash protection though... it is just an aesthetic thing that some people will probably eventually notice...

-Greg

Do you have a copy of AMS 2.08? Can you e-mail it to me at JudeCN@aol.com? Thanx, and great job with Command Center.

You can download it from www.CalcGames.org

Are you just trying to get publicity for your site? I do. :)

I heard that AMS 2.08 was buggy with the linkport. What else should I know about it? Oh wait... lord_nightrose wrote a big, long, descriptive summary of it... I should go refer to that. :)

Actually, the only linking problem AMS 2.08 had was a timing error when linked in TI-Connect.

Oh, and by the way:
http://www.geocities.com/augrad

you do know that ams 2.08 fixes a couple of bugs?

Which ones??

thanks, sam :)
The command post anti-crash mechanism works very nicely with the OS... i worked with it extensively and tried to work out allot of the bugs, or potential misuses that can arise. Plus CP has a huge advantage over ram based programs like KerNO and PreOS simply because the error handling code is contained in the FLASH memory instead of the RAM. I had a very difficult time making the crash protection work with TIFS (inline asm isn't fun) but i think it was worth the effort...

-Greg