Doors CS 7 Bug Reports

thepenguin77 · New Member Joined: 09 Jun 2010 Posts: 79

Sorry if this has been mentioned recently since I have not kept up with the bug reports.

DCS chains to both the rawKey hook and the parser hook, and that impresses me. The first time you run DCS, if the specific hook is enabled within the appvar, DCS will copy the 4 bytes at the hook pointer address to the appvar and replace it with its own hook. However, the problem comes from the fact that the second time you run DCS, it will do the exact same thing. This means that it is effectively chaining to itself and no longer chaining to the original program.

The quick fix for this would be to check the page of the hook you are about to chain to before copying it to the appvar. If that page is one of DCS's pages, then DCS is already chaining to another app and the copy should be aborted. If it is not one of DCS's pages, then you'd back it up like usual.

As for a specific location, the code in question happens at $696E on the second page in DCS 7.2 beta 2.

KermMartian · Posted: 09 Nov 2011 07:44:01 pm Post subject:

Ah yes, I think I've noticed that before, been too busy to do anything about it, and just shrugged my shoulders on the issue. I'll see what I can do as far as making enough room in the app to fit in a few dozen bytes of solution; I've added a note to myself about it in my bug reports page:

http://dcs.cemetech.net/index.php?title=Doors_CS_7_Scratchwork
_________________

thepenguin77 · New Member Joined: 09 Jun 2010 Posts: 79

I know how you feel with making room to fix bugs. I have the same thing going on with my app zStart.

I should point out though that this bugfix would be the last piece to having full compatibility between these two apps though. Wink

KermMartian · Posted: 16 Nov 2011 01:12:43 pm Post subject:

Thanks, I appreciate the solidarity. Smile

I've had this tab open for a week; I haven't forgotten about it. Hopefully I can get to this in the next week or so, but I'd appreciate continued pokes if you get a chance.
_________________

Dapianokid · Posted: 24 Nov 2011 07:13:06 pm Post subject:

I got one! I was programming in AXE and it cleared my ram. Thanks to flash ROM, my DocEditing program, homework, games, music, and previously attempted AXE programs were all saved! However, I had the expected mere 29766 (give or take a few) bytes left in my flash ROM, yet everything was hidden from Doors and the memory menu. I deleted my appvars from DoorsCS7 and everything was fine.
_________________
What if we all got together and did something ridiculous?
Well?

Dapianokid · Posted: 24 Nov 2011 07:28:15 pm Post subject:

This was stupid of me... I don't suggest it either. I was messing around with functions of axe, which I found to be just loads of fun:) however, I wrote this and the problems will be named following it. Garret said to fill the arguments with a random number. He picked it... -.-

KermMartian · Posted: 26 Nov 2011 03:10:03 am Post subject:

I don't know why you still listen to this kid. He lies about being a programmer on a shell that came out over ten years ago, probably before he first used a computer, he tells you to do things that break your calculator, it sounds like he charges people to copy programs from ticalc.org to their calculators, which is quite unethical... Neutral

ROM FAIL means that you need to pull all five batteries and let your calculator relax for a bit. Put in three AAAs, hold CLEAR, insert the last AAA with CLEAR held down, and tap ON. This clears your RAM, but if you ran into a ROM FAIL, it likely your archive got corrupted from the self-test, since the self test clears your Flash/archive.
_________________

qazz42 · Vampire Killer Joined: 07 Apr 2010 Posts: 4177

KermMartian · Posted: 26 Nov 2011 09:53:08 am Post subject:

I sure do, that's who sprang to my mind first when Dapianokid said his friend said he made MirageOS. There are some very unethical people out there, sadly. Sad

Anyway, this is way off-topic. Dapiano: I don't believe either of the things you described are actual DCS bugs; would you agree?
_________________

Sorunome · Posted: 27 Nov 2011 12:15:20 pm Post subject:

Well, I'm using DCS 7.2b.
I incert the dcs shell via zStart.
zStart runs on Ramclear
I have OS 2.43
Oh, a ti 84+ (no se)
And here is what happened: I started Direct USB GCB transmission, opend gossamer, home page loaded, as soon as it was finished the screen of Doors showed up that only shows up if you enter for the first time the app.
I pressed there X and then the instructions for doors came, no curser appeared and calc froze.....
_________________

KermMartian · Posted: 27 Nov 2011 12:19:53 pm Post subject:

That sounds like some problem with zStart, not Doors CS. Why are you using zStart to start Doors CS, anyway? Doors CS can start itself at startup with one of its features.
_________________

Sorunome · Posted: 27 Nov 2011 12:27:42 pm Post subject:

No, I mean that in insert Doors as a shell with zstart, as zstart has aswell a lot of other features. Smile

_________________

KermMartian · Posted: 28 Nov 2011 01:56:01 am Post subject:

Dapianokid · Posted: 01 Dec 2011 03:43:42 pm Post subject:

Kerm, I unfortunately have a bug to report. I made a simple equation solver and my battery has been running low. The thing is, it had an archive error when I ran it thru doors, deleted it, and then created a program called dcsasmax. It ran my program when I tried to edit it, but it ran it like an asm virus in the I could not use interrupts and it began to overload my LCD settings. So, what is dcsasmax? and why did it delete itself when the calculator turned itself off? it didn't even clear my RAM. Help!
kay update... It is just an Archive error, the calc basically is running out of batteries and accesses values that it shouldn’t in order to do it in a less battery consuming way.
This is in no way garrett related:P
_________________
What if we all got together and did something ridiculous?
Well?

KermMartian · Posted: 02 Dec 2011 12:26:10 am Post subject:

The archive error was Doors CS trying to alert you that your battery was low and thus that it refused to deal with the archive. The dcsasmex file is a temporary program created by Doors CS's intelligent writeback and RunProg subsystems to save both time and wear-and-tear on your archive for archived programs that will not require writeback. I'm not sure what you mean about interrupts and LCD settings, though.
_________________

Dapianokid · Posted: 02 Dec 2011 12:42:23 pm Post subject:

Well that was very smart of you to write those incredible subsystems. Incredible. I find that Doors is just Godly and Allmighty.
_________________
What if we all got together and did something ridiculous?
Well?

KermMartian · Posted: 02 Dec 2011 12:45:51 pm Post subject:

Claros · Newbie Joined: 28 Mar 2011 Posts: 4

Hello !

With DCS7.2b2 I encounter 2 bugs on my 84+. The first is the battery indicator doesn't work. The message "Your battery is low" (or something like that) appears on my calc but the indicator on DCS7 is still full.

The second is when I broke a program during it execute, and I press to go to the line, the editor remove random chars/lines on the program. This bugs destroy many of my programs: the Lbl disappeared.

PS: sorry for my english. Laughing

Thanks !

qazz42 · Vampire Killer Joined: 07 Apr 2010 Posts: 4177

Well, the second one has never happened to me, but for the first one you should know that battery on a TI-83+ affects your screen brightness, so on a TI-83+ DCS can tell how much battery you have left with ease. A TI-84+, on the other hand, doesn't use such primitive methods to determining battery left, so DCS cannot display it properly
_________________

Aes_Sedia5 · Posted: 06 Dec 2011 03:35:47 pm Post subject:

One thing I noticed, When I run the Inequalz app, and quit DCS as it asks me too, Then I run DCS again (without disabling Inequalz, I though it would do that automatically) I get Odd bugs, like the screeen randomly wiping and freezing, and Sometimes I cant edit programs, I choosed Program->Edit-> Then the screen freezes for a second with the menu. You hit clear and it goes away. Same problem while using break and Goto. And this is on the Nspire as well, which is buggy to begin with.
_________________