This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Messages - thepenguin77
Pages: 1 ... 63 64 [65] 66 67 ... 108
961
« on: April 16, 2011, 06:11:00 pm »
And to put it to rest: bcall address: - 0000h - 3FFFh -- Look at the currently running app
- 4000h - 7FFFh -- Look at page 1Bh/3Bh/7Bh
- 8000h - BFFFh -- Look at boot code
So depending whichever range the bcall falls into is where the OS will look. And the data is always stored the same: addrLow, addrHigh, page
962
« on: April 15, 2011, 05:21:18 pm »
Meh, oh well. I guess we'll never know. At least this has made me decide to start disassembling 2.53. And now I have that cool program that gets the extra ram page, (though I can't think of any uses).
963
« on: April 13, 2011, 06:21:11 pm »
No, I'll disable the specific hook you have changed. So instead of just changing the option, you are actually disabling the hook too.
If you don't touch any of the options, it will do exactly what it does now.
964
« on: April 13, 2011, 06:14:11 pm »
So it uninstalls the hooks when A) zStart was uninstalled via the app and B) the calc is shutting down?
No, sorry, that was worded terribly. Current: Hooks are never turned off (with a few exceptions) and ones that are in use are re enabled when the app quits New: If you change an option, that specific hook is disabled. So that when the app quits, it only re enables it if it should be enabled. I guess I could have the install zStart option disable all hooks, I don't think that would lead to too many problems.
965
« on: April 13, 2011, 06:07:44 pm »
I have noticed some bugs.
Alplha on = screen off if you have opened mirage. thus killing the safe ram clear. When you have log names on, then turn them off, they are still on. I did a safe ram clear and it fixed it (I assume a normal one would work too.)
and how was that ninja's???
I know mirage does that, I just figure people can press [ON][CLEAR], [ALPHA], [ON][R] because I do not want to make the safe ram clear just [ON][ x ]. I could see people accidentally deleting something important with that because it's too easy to press. You know what, I actually have a way to fix the fact that it doesn't disable stuff when you disable it. What I'll do is when you turn something off, I'll disable that hook. So that way if you were turning it off, it's off. But if you were turning it on, it will get enabled on quit.
966
« on: April 13, 2011, 06:01:59 pm »
Ralph, maybe it quit because you already have the file. Check for EXPAGE in your programs list.
Also, I didn't touch memory related stuff in 2.71.
967
« on: April 12, 2011, 10:50:11 pm »
That's some weird stuff. I doubt it's the OS causing you the problems, so I made a program to dump the extra ram page. Just run this program and post the EXPAGE.8xp it gives you.
Then, after you are sure you have the page saved, preferably on the computer. Try the clear option, this will clear the extra ram page, and the program will most likely crash on exit. But when the calc recovers, see if the problem is gone, if it is, the EXPAGE will tell us why.
For the program, make sure you have at least 16500 bytes free. Also, if it ever quits for no apparent reason, that means it had an error, with a little looking, you can probably figure out what the error was.
Edit: If it is the OS, we have some work. See if the self test passes the OS test. [MODE][ALPHA][ S ] and let the number 0 increment to 1.
968
« on: April 12, 2011, 09:38:10 pm »
I couldn't make it happen. But I doubt your OS is corrupted. Usually when the OS gets corrupted, you'll lose a whole 64KB, not have some specific glitch.
So would just typing in [1][ALPHA][F1][1][2] enter cause the glitch. Assuming you were in Classic?
969
« on: April 12, 2011, 09:13:32 pm »
To be honest, you won't start optimizing stuff until you know how many t-states and bytes each command is. And don't go memorize it because you need to learn it through experience. The optimizations really start to come when you start rearranging code and taking different approach to tasks. The little trick optimizations wont really save you much time except for in sections of code that get run like 10,000 times per second. Well optimized code is usually created, it's reformed from bad code. So, what am I saying. Don't worry yourself over little optimizations, fix them if you find them, but mostly for learning purposes. It's with persistent attempts to write good code that you will in fact write good code. Oh, and IX is slow
970
« on: April 12, 2011, 09:03:20 pm »
Just a question. Why are you doing in-line assembly in assembly? Why not just type out the bcall? It makes it easier for the non-xeda's to read
971
« on: April 12, 2011, 08:55:46 pm »
Sorry, about the checkmate thing. That was probably when I got rid of the that bad optimization I talked about, I must have messed that up because it used to work flawlessly. I'll get it fixed.
And the opening move database is definitely not happening. It is useless code with too many conditionals. What if the opponent responds in an unusual way? You have to make a new set, but what if they do another unusual move... This ends up with >1000 lines of code that will soon become obsolete.
972
« on: April 12, 2011, 08:46:15 pm »
Yep, I only took all of the molar masses to 2 decimal places. That's what AP chem and my chem 1 use, so I just went with it.
For the safe ram clear, you need to press alpha, then hold ON and press [ x ]. I don't want to make it something else because it is a ram clear after all, you wouldn't want to hit it by accident. Say you're trying to put it in molar mass mode and you accidently hit the wrong key X.X
(Clarification, I'm not in chem 1. lol)
973
« on: April 11, 2011, 07:18:07 pm »
Yes. It is basically resetting all the settings, ports, hooks, and ram on the calculator without deleting your programs.
974
« on: April 11, 2011, 07:14:58 pm »
Should have explained that.
Here is exactly what it does. It archives all programs (protected and unprotected) and keeps a list of what it archived. Then it crashes. When it turns back on, it goes through the list and unarchives everything it just archived.
This is basically for when things on your calculator just aren't making sense and you need to clear ram, but you don't feel like archiving everything.
975
« on: April 11, 2011, 06:58:36 pm »
Update: - ON + VARS = archive all programs
- ON + R = safe ram clear
- ON + COS = Asm(
- ON + CLEAR = Restore zStart (used to be ENTER)
Axe support is hopefully on the way. I plan to install Axe's hooks and compile programs with ON + ENTER. DCS support is also hopefully on the way. I should be able to install DCS's hooks and let it make it's appvars. Kerm's also working on the chain glitch. Of course, both of those require entry points in the apps, so hopefully the author's will add them for me. :D (The source is here mainly as a backup, but have fun looking at how I do file operations from hooks if you want) Edit: Sorry, the last screeny sucked, this one is way better.
Pages: 1 ... 63 64 [65] 66 67 ... 108
|