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 ... 11 12 [13] 14 15 ... 108
181
« on: November 11, 2012, 04:04:53 pm »
Are you sure that you used the version that goes with your OS ?
The program throws an error if you run it on the wrong calc. Is grouping and ungrouping faster?
Yes I have a possible bug report. Since installing this morning my calc has been behaving rather oddly. I've been working on an axe project and using edit-from-archive and ON-ZOOM zstart features a lot, and suddenly (after the program crashed I think) the source axe file was filled with random tokens. This happened multiple times and eventually the dev cycle looped into restore axe backup, compile, archive source, run, executable crashed, go look at axe source, it's corrupted, restore axe backup. I tried restoring the OS, it went through the whole "Receiving...Operating System" dialog and then changed to "Waiting...Please Install Operating System." I then resent the OS (again) and now it's behaving perfectly normally. I have to do some stuff now, but when I have time I'll reapply the patch and see if I can duplicate the behavior.
Which OS? I had to do this 5 times, so there's a chance I made a mistake in one of them.
182
« on: November 10, 2012, 10:28:39 pm »
Whenever I try converting my image, it says "Wrong Header Type!!". Can you help me convert them? I have 2 sizes (96x64 and 192x128)
I don't have time right now, but try saving them with a different program. I know gimp always works, and I would assume paint would work as well. (Also, those are both 192x128).
183
« on: November 10, 2012, 10:20:38 pm »
I think The Reign of Legends 2 fans will love this... 
That seems really cool. I might give it a try at one point. By the way you should really bundle your patches together or in packages (eg those together and your other patches in another package) and put them in Omni download section or add a link to them there. It would give them more visibility.
Does that speed up Garbage Collecting too?
That's going to be a mega .zip file  And yes, Garbage Collection should take around 2/3 the normal amount of time.
184
« on: November 10, 2012, 10:06:59 pm »
So I was in an OS-patching mood, and speeding up flash access was an idea I've had for about a year. After you apply this patch, reading data from flash (unarchiving) will take 1/3 as long as it normally would and writing data to flash (archiving) will take 2/3 as long as it normally would. These effects will take place across the entire OS (including basic and assembly programs). As always, I made a patch for OS's 1.19_BE, 1.19_SE, 2.43, 2.53, and 2.55 (yes, the 83+BE and 83+SE require different patches). I was lazy and didn't include any kind of progress bar, so, you'll just have to wait in fear. I feel bad for the 83+BE users though because they have to wait far longer than what is acceptable. Before: | After: |  |  |
As far as I can tell, this mod is stable. I currently have it installed on my calculator and the only thing I've noticed is that stuff basically unarchives instantly. I didn't include an option to unpatch your calculator this time since an unpatch isn't really feasible (one part of the patching involves a find/replace of a certain OS call), but that's ok, because if you are unhappy with this mod, you'll probably need an OS reinstall anyways Lastly, I'd like to mention that there are a few things this won't speed up. Most notably: Axe when it writes an app, OS modding programs, and receiving OS's. All of these tasks still use the old WriteFlash routine and there's nothing I can do to change that (besides mod the boot code (and I'm not going to)). Oh, and as far as compatibility is concerned. Both version of the universal flash unlock still work (that was annoying) and this patch fixes the 2.55 fraction glitch (in a different way). So, install and enjoy your faster calculator. Edit: I cannot forget Runer112 who optimized the new _flashToRam routine and cut off like 20 bytes. So he gets credit too. Edit2: This program takes a long time to run and gives no display of progress, give it a solid 3 minutes before you assume it crashed.
185
« on: November 10, 2012, 08:45:23 pm »
I can make this too, when thepenguin can give me the asm codes to use with Axe.
Same, I want those codes, please share 
Make me a list of what you want.
186
« on: November 10, 2012, 06:13:30 pm »
Indeed, it is a glitch caused by an old flash unlock method (that older versions of Axe use). I made a patch that will essentially immunize your calculator from this glitch. So run that program and the problem will go away.
187
« on: November 09, 2012, 11:20:54 pm »
Well, it's not that hard really if you use zStart. I made an option to run a program when you turn your calculator on. Make your own version of this screen and then set it to run when your calculator turns on. Honestly, I don't feel like making this. But, if you do indeed make a usable menu, I'll give you the Asm codes to open each of the different features (like graph menu, stat editor, etc). That way when you click on the icons, they actually go somewhere
188
« on: November 09, 2012, 10:04:08 pm »
Why would you want to do this? Everything on the 84+ can be reached within 1-2 keys.
I don't see what the benefit of adding this screen would be.
189
« on: November 09, 2012, 08:52:45 pm »
I'd noticed that the restriction was arbitrary, but I never considered hacking the OS to remove it. Your understanding of the EOS amazes me.
It wasn't really all that difficult to do since like you said, I knew it was arbitrary. The first step was to prevent ERR:OVERFLOW. For this, I did 1E99 + 9E99 and set a break point at _FPAdd. From there, I just stepped through the code and waited for an ERR:OVERFLOW to be thrown. After about 3 iterations of this, I finally stumbled upon _CkValidNum which clearly compared the exponent to +99 and -99. I just disabled that check  (Actually, I still check for E-128) The second step was to allow 3 digit exponents, but again, this was just a bit of "find the error." I set a breakpoint in the massive parser loop (endless "CP \ jr z" table) and watched as the errors unfolded for E127. I soon found a routine that used RLD to rotate the low nibble of the current byte being parsed into memory and I saw that on the third iteration, the memory location became invalid and a counter went to zero. My solution for this was just to do some code injection where I put a call to the end of the page and wrote my own routine to parse the number. All I had to do was watch for the overflow and add $A0 (BCD hack) if the new exponent was going to be in the correct 100-127 range and increase the counter by 1 to avoid the error. So I guess that's a bit complicated, but the idea is that if something throws an exception, it's not very hard to catch by stepping through the code.
190
« on: November 09, 2012, 01:41:52 pm »
Is there a real way to have +64K ARC mem ? By "real" I mean durable of course
No, all of those hacks are really unstable. There really isn't any way to expand the memory. (That's a lie, there is one, but it only works on OS's <2.55 and would require a complete rewrite of the garbage collector, but I've looked into that and it's pretty ugly.)
191
« on: November 08, 2012, 11:46:52 pm »
That doesn't sounds like more precision at all! That sounds like a larger range with the same amount of precision
Yeah, I totally realize that. But I don't know what else to call it.
192
« on: November 08, 2012, 11:29:26 pm »
Did you know that placing the maximum exponent at 10^99 was a completely arbitrary move by TI? In any case, I did, and I got rid of that limitation. With this OS patch, your calculator can handle exponents from E-127 to E127.  I'm going to guess that TI added this limitation to keep up with their older calculators which only had room for a two digit number. They also probably kept it at two digits because they used a nice little hack to parse the numbers after the E token. But, in any case, I took off the bounds checking so that large numbers don't throw an ERR:OVERFLOW and modified the number parser to allow 3 digit numbers. I made a patch for 1.19, 2.43, 2.53, and 2.55. The 2.55 is the ugliest of them all as I had to locate some code on page 00 (which could potentially mean compatibility issues with other patches), but they all work. If you understand how TI-floats work, you might be wondering why I didn't allow E-128, and the reason for this is that there's a certain routine which could underflow back to E127, and that would just cause weird issues that I don't want to deal with. So E-127 is the limit. I included the patcher with it's patch files if you want to see what is going on. Edit: And like always, there's an option to undo the patch.
193
« on: November 08, 2012, 02:32:37 pm »
ld hl, $E9E1 ;pop hl \ jp (hl)
ld (appBackUpScreen), hl
call appBackUpScreen
here:
This returns with HL = here.
Edit:
optimized a little
Edit2:
Here are two other options (with runer's help)
Fastest version:
di
call $000F
here:
dec sp
dec sp
pop hl
Smallest version: (destroys BC and DE)
di
rst 20h
here:
dec sp
dec sp
pop hl
194
« on: November 06, 2012, 05:39:35 pm »
Oops, forgot to include that. Yes
195
« on: November 06, 2012, 11:04:53 am »
I think SPASM is what I will use.
But is there any readme or something to learn how to use it?
If you also decide to go with this setup, this is what needs to go in your asm.bat file that you make on the first day. This is because spasm has a different command line syntax than tasm:
to be honest I don't really know what this code does and where to put it.
(I have only small experience with batch code)
Ok, to be honest, if you aren't very good with batch files, now is not the time to learn. All you need to do is to have a setup that works. The same goes for spasm. All you need is the ability to use it, you don't need to worry about how it works (yet). So, to help you out, take this .zip file, extract it, and copy it to C:\. That way you have C:\asm\ already set up. Then, as you go through the first day, you can just laugh at the instructions because you've already done them.
Pages: 1 ... 11 12 [13] 14 15 ... 108
|
Show Posts