Author Topic: 42 ways to prevent a project from dying due to data losses  (Read 14708 times)

0 Members and 1 Guest are viewing this topic.

Offline Deep Toaster

  • So much to do, so much time, so little motivation
  • Administrator
  • LV13 Extreme Addict (Next: 9001)
  • *************
  • Posts: 8217
  • Rating: +758/-15
    • View Profile
    • ClrHome
Re: 42 ways to prevent a project from dying due to data losses
« Reply #45 on: September 12, 2010, 11:16:37 am »
Wasn't there a 1.3 being developed? Too bad it died :(

#57: Assembly games never reset your RAM unless they specifically have code for it. Don't worry about playing "unstable" games.
« Last Edit: September 12, 2010, 11:17:43 am by Deep Thought »




Offline DJ Omnimaga

  • Clacualters are teh gr33t
  • CoT Emeritus
  • LV15 Omnimagician (Next: --)
  • *
  • Posts: 55933
  • Rating: +3153/-232
  • CodeWalrus founder & retired Omnimaga founder
    • View Profile
    • DJ Omnimaga Music
Re: 42 ways to prevent a project from dying due to data losses
« Reply #46 on: September 12, 2010, 12:36:44 pm »
Yeah, I don't know what happened to it. I remember it started around late 2004. Ticalc.org made a fake news about its release in 2008, but it was a rickroll :P (the only ticalc.org fake news not posted on April 1st to initially show up with a blue border)
« Last Edit: September 12, 2010, 12:37:43 pm by DJ Omnimaga »

Offline Deep Toaster

  • So much to do, so much time, so little motivation
  • Administrator
  • LV13 Extreme Addict (Next: 9001)
  • *************
  • Posts: 8217
  • Rating: +758/-15
    • View Profile
    • ClrHome
Re: 42 ways to prevent a project from dying due to data losses
« Reply #47 on: December 03, 2010, 07:40:08 pm »
#58: You don't need to know ASM to program in hex on your calculator. They're totally different languages.
#59: If you ever forget the address of a ROM call, don't worry about looking it up. Just run this code
Code: (Hex, not ASM) [Select]
:AsmPrgm21000022EB9DCDEA9DEF0745EF2E45237CB52011C9EF0000C9
and wait for it to do whatever you want. Then the number that appears on your screen is the number you want.
[Probably obvious, but don't actually run that.]
#60: All Axe Parser does is convert the tokens of your source into ASM. So if you ever accidentally Axe, you can always compile programs by hand by running it through the file unsquisher and typing it into your calculator.
« Last Edit: December 03, 2010, 07:40:23 pm by Deep Thought »




Offline DJ Omnimaga

  • Clacualters are teh gr33t
  • CoT Emeritus
  • LV15 Omnimagician (Next: --)
  • *
  • Posts: 55933
  • Rating: +3153/-232
  • CodeWalrus founder & retired Omnimaga founder
    • View Profile
    • DJ Omnimaga Music
Re: 42 ways to prevent a project from dying due to data losses
« Reply #48 on: December 03, 2010, 07:57:24 pm »
What does :AsmPrgm21000022EB9DCDEA9DEF0745EF2E45237CB52011C9EF0000C9 actually do?

Offline Deep Toaster

  • So much to do, so much time, so little motivation
  • Administrator
  • LV13 Extreme Addict (Next: 9001)
  • *************
  • Posts: 8217
  • Rating: +758/-15
    • View Profile
    • ClrHome
Re: 42 ways to prevent a project from dying due to data losses
« Reply #49 on: December 03, 2010, 08:00:52 pm »
What does :AsmPrgm21000022EB9DCDEA9DEF0745EF2E45237CB52011C9EF0000C9 actually do?

It basically tries b_calling every address in memory as a routine ;D




Offline DJ Omnimaga

  • Clacualters are teh gr33t
  • CoT Emeritus
  • LV15 Omnimagician (Next: --)
  • *
  • Posts: 55933
  • Rating: +3153/-232
  • CodeWalrus founder & retired Omnimaga founder
    • View Profile
    • DJ Omnimaga Music
Re: 42 ways to prevent a project from dying due to data losses
« Reply #50 on: December 03, 2010, 11:06:55 pm »
I am confused, you mean it's like using every existing b_calls in a row?

Offline Deep Toaster

  • So much to do, so much time, so little motivation
  • Administrator
  • LV13 Extreme Addict (Next: 9001)
  • *************
  • Posts: 8217
  • Rating: +758/-15
    • View Profile
    • ClrHome
Re: 42 ways to prevent a project from dying due to data losses
« Reply #51 on: December 04, 2010, 11:41:48 am »
I am confused, you mean it's like using every existing b_calls in a row?

And the nonexistent ones. It basically runs b_call(0000)    b_call(0001)    b_call(0002)...

When it does what you want, the number on your screen is the number you want ;D




Offline jnesselr

  • King Graphmastur
  • LV11 Super Veteran (Next: 3000)
  • ***********
  • Posts: 2270
  • Rating: +81/-20
  • TAO == epic
    • View Profile
Re: 42 ways to prevent a project from dying due to data losses
« Reply #52 on: December 04, 2010, 12:43:59 pm »
I am confused, you mean it's like using every existing b_calls in a row?

And the nonexistent ones. It basically runs b_call(0000)    b_call(0001)    b_call(0002)...

When it does what you want, the number on your screen is the number you want ;D
In other words, for the non-existent ones like 0000, it takes the first two bytes as the address and the next one as the page. On my 2.43 calc, that would mean that it would call address 02DB on page E6 (Which, doesn't exist).  Also note that the bcall addresses have to be 3 bytes appart, so b_call(0001) would page address E602, page 80 (I think that on my calc, it only goes to page 7F).  So yeah, it's bad.

Offline DJ Omnimaga

  • Clacualters are teh gr33t
  • CoT Emeritus
  • LV15 Omnimagician (Next: --)
  • *
  • Posts: 55933
  • Rating: +3153/-232
  • CodeWalrus founder & retired Omnimaga founder
    • View Profile
    • DJ Omnimaga Music
Re: 42 ways to prevent a project from dying due to data losses
« Reply #53 on: December 04, 2010, 04:07:57 pm »
I see. So when calling a non-existent B_call it crashes, right?

Ashbad

  • Guest
Re: 42 ways to prevent a project from dying due to data losses
« Reply #54 on: December 04, 2010, 04:09:02 pm »
not always, but calling a random point in memory is never really good, you might hit a part that messes with the archive, and with no register input it could destroy your archive  :crazy:
« Last Edit: December 04, 2010, 04:09:28 pm by Ashbad »

Offline DJ Omnimaga

  • Clacualters are teh gr33t
  • CoT Emeritus
  • LV15 Omnimagician (Next: --)
  • *
  • Posts: 55933
  • Rating: +3153/-232
  • CodeWalrus founder & retired Omnimaga founder
    • View Profile
    • DJ Omnimaga Music
Re: 42 ways to prevent a project from dying due to data losses
« Reply #55 on: December 04, 2010, 08:24:09 pm »
Ah, right. I guess this is like when you store stuff directly to memory addresses in Axe. If you store at the wrong location it can be quite bad. X.x