Omnimaga
Calculator Community => Other Calculators => Topic started by: Sorunome on March 06, 2013, 07:50:19 pm
-
Hey, my TI 89 is not archiving my 32778 large file, it says could not archive: memory, but when i look at how much free flash rom I have it is 192750, which is a lot more than the file big is, so why can't it archive it?
EDIT: I'm having another issue: With this one asm prog it is giving me error mem even thought it used to work when I had less free ram than I have right now. Could it be that the os thinks that my memory is lower?
Should I reset all?
-
Reset all and check the OS and send the newest one (even if you already have it on the calc)
Trust me, it's probably the best solution
-
I am getting now sooner the error mem with flash D:
I just read that flash could wear out, is it wearing out on my 89 (i bought it used)/me hopes that not, i don't wanne restart playing links awakening :P
-
You need to do a factory reset, then... I believe that's how you reset flash page rewrites
-
How do you factory reset the calc?
-
The flash chip is unlikely to be worn out. The TI-89 AMS operating system is smarter than the TI-83+ EOS. It avoid unnecessary un/archiving. It's more likely to be a corruption issue, but I sadly can't really help you with fixing that. The TI-89 platform doesn't have (to my knowledge) a program like MicrOS that could be used to identify and fix the corrupted data.
-
What about just rebooting the calculator (2nd + LEFT + RIGHT + ON), after transferring all important data (since you cannot archive it), assuming the calculator's OS state is not corrupted enough for transfers not to work ?
Resetting all memory and transferring the OS anew might be a bit of a heavy-handed hammer for something that might well be solved by a reboot ;)
And indeed, the Flash chip is extremely unlikely to be worn out.
-
I think it takes like 200000-10000000 rewrites before wearing out, right?
-
A bit less than that, good Flash memory chips are often rated for ~100K erase cycles for a given sector.
For a general sector, even with 3 daily erase + rewrite cycles (very heavy usage), reaching 100K cycles takes 30000+ days, i.e. more than three quarters of a century.
The single garbage collection sector gets more erase + rewrite cycles than the others do, but even then, the calculator will break in all kinds of other ways before the Flash memory wears out :)
-
Indeed. I think the only way it could happen faster is if someone decided to waste his calc, replace batteries with a power adapter then let an archive sector rewriting program run non-stop until the flash (or something else in the calc) dies.
Or maybe defective flash? (Like what was suspected with Drummist's 83+)
-
Don't reset it. You might just have to garbage collect archive.
-
Garbage collection is supposed to occur automatically when needed.
-
You can still force a garbage collect on the 89 (I think it might require a 3rd party program, but I can't check if you can do it without 3rd party software...)
On an unrelated note: 500th post!!! (only 12 more until a nice round number...)
-
You can still force a garbage collect on the 89
Sure, by using the EM_GC() ROM_CALL, through an ASM program or Exec string. But that's very seldom necessary, as GC occurs when needed :)
-
I think that GC didn't occur when needed as I did the os thing before all of your other posts and that bug is now a lot sooner already (and yes, linking is still working)
I'll try 2nd+left+right+on next ;)
EDIT: that didn't fix it D:/me gets a program to manually garbage collect
EDIT2: Nope, the one i tried isn't fixing it D:
-
Did you ever get this resolved?
The main issue is that the TIOS cannot find 32Kb of contiguous archive memory. Garbage collection attempts to re-locate flash sectors. But... iirc, it cannot re-locate sectors that have been locked. Some programs will lock their files (handles) then forget to unlock them. Or if a program errors out too soon and the handle is left locked.
There is a handle viewing program on Ticalc. It will loop thru every entry in the VAT. I think it will display hidden and locked handles -- which is most likely what your symptom sounds like.
Edit:
HANDLE-Explorer v2.70 by Thomas Nussbaumer
http://www.ticalc.org/archives/files/fileinfo/168/16897.html
-
No, it is not resolved yet, garbage collection didn't work, i'll check out that program, thanks! :)
-
There's a somewhat newer version of TICT Handle Explorer (tthdex), which can identify more handles, in the TI-68k Developer utilities, but it's not maintained anymore, and it predates the advent of the 89T.
-
Would it possibly work with Ghostbuster and/or HW3Patch?
-
Nope, a number of tricks that it used to identify handles were broken by AMS 2.07 and later.
-
Ok, I am suspecting now that my ROM is corrupt in some way, because when rom-dumping my calc and put the rom in an emulator i get the same issues.
Is there any way to know for sure/fix that?
-
After a quick investigation (less than 10 minutes, writing this post took me longer), it turns out that David's guess above was fully correct:
The main issue is that the TIOS cannot find 32Kb of contiguous archive memory.
There's no memory corruption at all, your calculator is simply out of memory for storing the data which you want to store, which is made of large blocks, leaving a large unusable slack at the end of each 64 KB sector...
Even my tiosmod+amspatch, which shrinks AMS 2.08 & 2.09 for 89 in such a way that users get 64 KB more archive space, wouldn't make it possible for you to store everything you want to store. While it would give you room for one more large file, e.g. data file number 8, you'd still be missing data file number 9. Data file number 10 can definitely be stored in the same sector as the assembly programs.
At least four solutions, three easy and one hard:
* use a V200 (assuming it's supported by the assembly program) or a 89T, only those have enough Flash memory;
* use TIEmu to emulate a V200 or 89T;
* use PedroM, which is far smaller than AMS, and could just work for the purposes of the program you want to use - but of course, no TI-BASIC or FlashApps on PedroM.
* use tiosmod+amspatch to shrink your OS (that's easy, all the more some ready-made patches are provided), then turn your 512 KB of data into a contiguous FlashApp (the hardest part is making TIFS work; the TIFS Sierra toolchain doesn't depend on Microsoft's proprietary incompatible so-called Java, but someone needs to give you the procedure for building a FlashApp through the set of command-line tools) + modify the assembly program(s) (IIRC, the set is open source) in such a way that it reads / they read from the FlashApp instead of reading from scattered files. Right, that's no much fun.
If you can stand the loss of any language other than English, you should use tiosmod+amspatch anyway: it makes the OS faster (and for you, smaller).
-
Huh, I used to be able to put files 1-9 in rom, and only had to have 10 in ram.
So i guess i'll do tiosmod and amspatch...i guess they are on ticalc? :P
-
If you want to be able to put data files 0-9 in Flash memory, then use tiosmod+amspatch, transfer the patched AMS 2.09 (due to a different number of sectors for AMS, you should lose all of your archive contents), transfer data files 0-9 and archive them, transfer assembly programs and archive them. That way, only data file 10 will stay in RAM.
-
Ok, you rock officially, it is working now again just as it used to, thanks a lot! :D