-->
Memory Usage for the 89
-->
-->
Welcome,
Guest
. Please
login
or
register
.
Did you miss your
activation email
?
1 Hour
1 Day
1 Week
1 Month
Forever
Login with username, password and session length
-->
Home
About
Team
Rules
Stats
Status
Sitemap
Chat
Downloads
Forum
News
Our Projects
Major Community Projects
Recent Posts
Unread Posts
Replies
Tools
SourceCoder3
Other Things...
Omnimaga Radio
TI-83 Plus ASM File Unsquisher
Z80 Conversion Tools
IES TI File Editor
Free RAM areas
Comprehensive Getkeyr table
URL Shortener
Online Axe Tilemap Editor
Help
Contact Us
Change Request
Report Issue/Bug
Team
Articles
Members
View the memberlist
Search For Members
Buddies
Login
Register
Omnimaga
»
Forum
»
Calculator Community
»
Other Calc-Related Projects and Ideas
»
TI 68K
»
Memory Usage for the 89
« previous
next »
Print
Pages: [
1
]
Go Down
Author
Topic: Memory Usage for the 89 (Read 7789 times)
0 Members and 1 Guest are viewing this topic.
TC01
LV6
Super Member (Next: 500)
Posts: 344
Rating: +9/-0
Memory Usage for the 89
«
on:
July 08, 2011, 08:39:44 pm »
So, after suddenly finding myself
without a project
to work on the other day, I resolved to come up with some relatively simple calc utility I could actually code, and then code it.
And I came up with this: Memory Usage, a 68k C program which provides nicely formatted information about how much space is used up on the system.
The AMS's MEM dialog tells you how much space is being used for different variable types and how much is free. I, however, was interested in a folder-by-folder breakdown, among other things.
The attached images summarize the current features pretty well. First, when you run the program, there are three options: "general memory info", "flash app info", and "file/folder info". The general memory info first provides usage statistics about the RAM and the Flash: mostly what you can already get through the AMS's MEM menu. However, it also shows how much memory would be freed through Garbage Collect.
The files/folders mem screen shows a list of all folders and their sizes ordered by size. Selecting a folder opens up a sub menu displaying the number of unarchived bytes and the number of archived bytes. At this point, if you select "All", it shows you an ordered list of all files in that folder; selecting "Archived" or "Unarchived" displays only archived or unarchived programs in that folder, again sorted by size.
Currently, selecting a file does nothing, just exits.
The flash app screen, like the files and folders screen, shows an ordered list of folders by size. The name of an app might be cut off, but selecting the app will display the full name, the application ID (which is a handle to some info about the app in memory), and the size in a little popup window.
It should be compatible with the Titanium, though it cannot run on anything below AMS 1.x.
«
Last Edit: July 28, 2011, 03:29:02 pm by TC01
»
Logged
+1/-0 karm for this message
The userbars in my sig are links embedded links.
And in addition to calculator (and Python!) stuff, I mod Civilization 4 (frequently with Python).
TC01
LV6
Super Member (Next: 500)
Posts: 344
Rating: +9/-0
Re: Memory Usage for the 89
«
Reply #1 on:
July 13, 2011, 09:45:06 pm »
After a bit more debugging and coding, here's a real release of this program. I've fixed all the weirdness that was occurring on my 89 (and improved memory usage while I was at it).
Also, with debrouxl's assistance, I added a menu for displaying Flash applications. It works much the same as the folder\file system, but selecting a flash application brings up a little popup giving the full name (the name has to get cut off for size in some places), the application ID on your system, and the size.
Hopefully, even though the 68k community is dead, someone finds this potentially useful...
And yes, I know I just made a link to an attachment in the post right above this one, but I figured it might be lost in all the screenshots.
EDIT: removed v0.2
«
Last Edit: July 28, 2011, 03:34:15 pm by TC01
»
Logged
The userbars in my sig are links embedded links.
And in addition to calculator (and Python!) stuff, I mod Civilization 4 (frequently with Python).
Lionel Debroux
LV11
Super Veteran (Next: 3000)
Posts: 2135
Rating: +290/-45
Re: Memory Usage for the 89
«
Reply #2 on:
July 14, 2011, 08:47:23 am »
Nifty little utility indeed
Logged
Member of the
TI-Chess Team
.
Co-maintainer of
GCC4TI
(
GCC4TI online documentation
),
TILP
and
TIEmu
.
Co-admin of
TI-Planet
.
TC01
LV6
Super Member (Next: 500)
Posts: 344
Rating: +9/-0
Re: Memory Usage for the 89
«
Reply #3 on:
July 28, 2011, 03:32:38 pm »
I've released
version 0.3
.
As bugs were still happening on my 89, I went back and fixed them. (The fix entailed changing the way the program determined the size of files). The new way is more optimized, and bug free.
I also added an option to garbage collect to the main menu (because the 89 doesn't let you garbage collect manually), and then added information about whether a flash app is "marked for delete" to it's info page. (You currently can't delete flash apps from this interface, so it should always read "0").
Logged
The userbars in my sig are links embedded links.
And in addition to calculator (and Python!) stuff, I mod Civilization 4 (frequently with Python).
Jim Bauwens
Lua! Nspire! Linux!
Editor
LV10
31337 u53r (Next: 2000)
Posts: 1881
Rating: +206/-7
Linux!
Re: Memory Usage for the 89
«
Reply #4 on:
July 28, 2011, 03:48:13 pm »
Nice, should put this on one of my calcs when I have some time
Logged
TI-Nspire projects of me:
nCreator
|
PCspire
|
Klondike Lua
|
LogoMagic
|
EEPro for the TI-Nspire
|
Pegs
|
General math definitions
|
Mini vMac
|
CHIP-8 emulator
Print
Pages: [
1
]
Go Up
« previous
next »
Omnimaga
»
Forum
»
Calculator Community
»
Other Calc-Related Projects and Ideas
»
TI 68K
»
Memory Usage for the 89
\n\t\t\t\t\t\t\t\t\t
<' + '/div>\n\t\t\t\t\t\t\t\t\t
%body%<' + '/textarea>
\n\t\t\t\t\t\t\t\t\t\n\t\t\t\t\t\t\t\t\t
Max characters: 20000; characters remaining:
...<' + '/span><' + '/span>
\n\t\t\t\t\t\t\t\t\t\n\t\t\t\t\t\t\t\t\t
\n\t\t\t\t\t\t\t\t\t
\n\t\t\t\t\t\t\t\t\t
\n\t\t\t\t\t\t\t\t\t
\n\t\t\t\t\t\t\t\t\t\t
\n\t\t\t\t\t\t\t\t\t<' + '/div>\n\t\t\t\t\t\t\t\t<' + '/div>', sTemplateSubjectEdit: '
', sTemplateBodyNormal: '%body%', sTemplateSubjectNormal: '
%subject%<' + '/a>', sTemplateTopSubject: 'Topic: %subject% (Read 7789 times)', sErrorBorderStyle: '1px solid red' }); aJumpTo[aJumpTo.length] = new JumpTo({ sContainerId: "display_jump_to", sJumpToTemplate: "
Jump to:<" + "/label> %dropdown_list%", iCurBoardId: 195, iCurBoardChildLevel: 1, sCurBoardName: "TI 68K", sBoardChildLevelIndicator: "==", sBoardPrefix: "=> ", sCatSeparator: "-----------------------------", sCatPrefix: "", sGoButtonLabel: "go" }); aIconLists[aIconLists.length] = new IconList({ sBackReference: "aIconLists[" + aIconLists.length + "]", sIconIdPrefix: "msg_icon_", sScriptUrl: smf_scripturl, bShowModify: true, iBoardId: 195, iTopicId: 11993, sSessionId: "423f1c2cb88207ed0e17a4f952fd8609", sSessionVar: "d30df5562bd2", sLabelIconList: "Message Icon", sBoxBackground: "transparent", sBoxBackgroundHover: "#ffffff", iBoxBorderWidthHover: 1, sBoxBorderColorHover: "#adadad" , sContainerBackground: "#ffffff", sContainerBorder: "1px solid #adadad", sItemBorder: "1px solid #ffffff", sItemBorderHover: "1px dotted gray", sItemBackground: "transparent", sItemBackgroundHover: "#e0e0f0" }); } function tick2() { if (typeof(document.forms.quickModForm) != "undefined") { calcCharLeft2(); setTimeout("tick2()", 1000); } else setTimeout("tick2()", 800); } function message_onkeyup() { if (typeof(document.forms.quickModForm) != "undefined" && typeof(document.forms.quickModForm.message) != "undefined") { document.forms.quickModForm.message.onkeyup = function onkeyup(event) { storeCaret(this); calcCharLeft2(); }; } else setTimeout("message_onkeyup()", 800); } message_onkeyup(); function calcCharLeft2() { var maxLength = 20000; var oldEditor = "", currentEditor = document.forms.quickModForm.message.value; if (!document.getElementById("editorLeft2")) return; if (oldEditor != currentEditor) { oldEditor = currentEditor; if (currentEditor.replace(/\r/, "").length > maxLength) document.forms.quickModForm.message.value = currentEditor.replace(/\r/, "").substring(0, maxLength); currentEditor = document.forms.quickModForm.message.value.replace(/\r/, ""); } setInnerHTML(document.getElementById("editorLeft2"), maxLength - currentEditor.length); } // ]]>-->