Yeah, if you have the tools, that's the way to do it. Just cut off little chunks with a hacksaw, thread one end with a threading tool, then take it to a grinding wheel to make a nice point. If you don't have the tools, you can probably use the hacksaw to make threads and use a file to make the point, but it will just take a lot longer.

The only downside to this technique is that steel is not as heat conductive as copper, so your tip will take about twice as long to heat up, but considering this is only a change from 1 minute to 2 minutes, I think it's worth it.

You could post your disassembler, that would definitely be legal

Yeah, indeed it would be.


Have fun finding your own roms

zStart set my contrast level automatically to the max, and I can't figure out how to reduce the number ;_; help?

Sir, delete the appvar and try the new one. What happened was that the first one I uploaded, 1.2.010, killed the location of the appVar when you installed it on ram clear. So you appvar is garbage. Delete it and you should be fine.

Actually, there's one thing CalcUtil does that zStart doesn't: allow log() to be used with arbitrary bases. I know MathPrint OSes have a logbase() function, but 2.53 was sooo buggy for me last I tried it.

That's a good point, omnicalc does that, but I'll see if I can do it too, I don't think it's very hard. In fact, OS 2.53 and 2.55 overload the log( functions too. So log(8,2) on a brand new OS will return 3.

That didn't work, my archive is still gone oh well.

I'm sorry to hear that, I don't know what could have happened. DrDnar's Archutil would definitely be useful to you since I would guess your programs aren't even deleted in the real flash.

    Eeems, what settings did you change? That might help explain what happened, because it sounds to me like it crashed either when it was making the changes, or it made bad changes.
I just set my contrast, lcd delay, changed the program settings to work with certain stuff, installed the on ramclear part etc.

Yep, it was the run on ram clear, that's fixed now though.

I'll try to see if that one works

The new one should work, just make sure you delete the appVar.



I really have to thank you guys for putting up with this. There are just some glitches that through all of my testing, I just can't cause, that's why I need people like you to find the flaws.

Next step is to find the necessary tools to compile ASM code described in the above documentation, which are currently nowhere to be found

Don't count your chickens before they hatch . This is not a problem since we already have documentation on all of the opcodes and can make our own programs. The real problem is that these calculators don't execute from ram, they only execute from rom. Which means that even if we do manage to type a program into these calculators and find a glitch to jump to a random spot in the OS, we have no way to run these programs.

The OS is at address 0000h and goes to FFFFh. Ram starts at 00h and goes to FFh on 4 separate banks. As you can see, ram on rom are completely different.

The only hope is in a ram area called DRM, it is really hard to access, but is much bigger. Our only chance of perhaps getting asm running is if this area is mapped to C000h-FFFFh or similar, however, this is extremely unlikely and the emulator that goplat disassembled did not show anything even remotely like that.


However, if anyone is interested, I can send you a disassembly of whatever OS you want. (Well, of course I would never actually send it, that would be illegal  , confusing...)

It probably has to be the correct OS, but what really matters is that the % recieved gets over 0%, and then you pull the cable out.

Roughly a minute.

Eeems, most likely you just need to clear ram again while holding VARS. I'll try to figure out what happened to you.

zTrumpet, I'll add it back, I didn't realize anyone actually used it I couldn't see how it would be used, but debugging makes sense.

Edit:
    Eeems, what settings did you change? That might help explain what happened, because it sounds to me like it crashed either when it was making the changes, or it made bad changes.

Edit2:
    It looks like installing/uninstalling the mod destroys some ram, so no harm was done. I'll just figure out what it's killing.

Total reformat update!!

Here's a massive update on my part, even though on the surface it would appear not much has changed:

• Completely redid the appVar system, (I cut off around 50 bytes through compression)
• Removed Executing past $C000
  
• Removed specific font options
• Added an ONSCRPT so that the hardware changes will persist through battery pulls
• Label menu shows 3 character labels
• Ability to run programs from the home screen
  
• Ability to run basic programs
• Seamless Goto in case an archived basic program Errors
• New parser hook system
• Parser hooks no longer runs in basic programs (used to cause errors)
• Font editor now exports appVars
• Running asm programs now handles the error handler correctly through hacking
• No longer store data on the extra ram page, now I use the very first Vat spot

Changing my appVar system meant a lot of changes, since it is used in almost every feature of the app. That's why so many little things were changed. It was also a good time to get rid of some of the unnecessary stuff.

Running programs from the home screen works exactly like you would expect it to. Check off the option under Run Programs and then just type prgmNAME on the homescreen and whether it is basic/asm archived/unarchived, it will run. It also allows you to put Asm( in front of it, even if it's a basic program Any basic programmers out there will also be happy to see that running stuff from the archive feels exactly like running stuff from ram. If an error pops up, just press goto and it will open an archived editing session. If you're not really paying attention, you would never even notice.

My parser hook system is pretty cool, it only enables itself when necessary, and it chains to omnicalc if omnicalc is enabled. It only runs if it is being called from the homescreen though, because the way I handle my parser hook, it wouldn't work right in basic programs. (Now if kerm would fix his chaining, we could have: DCS>zStart>Omnicalc>Symbolic, but we'll just have to wait on kerm )

I also stopped storing information on the extra ram page because I just didn't like doing that. I store stuff like where the font is located and where omnicalc is located because if I had to find them every time, your calculator would be noticeable slower. Now, I put it in the very first VAT spot. My hooks will always move it to the first spot and fix it's values, so feel free to try to mess with it in calcsys, you'll have best results if have the font hook turned on. Another interesting note is that it uses it's name for storage, that's why it looks so weird. And like all the other features in my app, the VAT entry only exists if there is a hook that needs it.


I'm trying to gear up for a ticalc.org release, so if you find any bugs, tell me. Since I changed all 21 of my source files, there are bound to still be a few errors here and there that I missed in my 16 hour debugging spree. I'd also like to know if the appVar conversion process is working nicely. You won't know that anything has changed, but the first time you run the new version, it actually does some serious work to the appVar.

Anyways, I think I've finally absorbed calcutil, so stop telling me about compatibility errors

Edit:
   It helps to attach the program.

Edit2:
   Fixed Eeems's little problem, and put C000 back.