Search found 606 matches
- Wed Jan 04, 2017 8:02 pm
- Forum: Calculator Hacking/Modding Discussions
- Topic: Addin manager: need to manipulate RAM & SMEM
- Replies: 11
- Views: 32213
Re: Addin manager: need to manipulate RAM & SMEM
It would be best to post the part of the source, which probably malfunctions.
- Wed Jan 04, 2017 7:34 am
- Forum: Calculator Hacking/Modding Discussions
- Topic: Addin manager: need to manipulate RAM & SMEM
- Replies: 11
- Views: 32213
Re: Addin manager: need to manipulate RAM & SMEM
For changing the addin icon, name, version and appname (name = displayed name in the system app, appname = beginning with an '@' and used for folders) I would have to write and read at the specific offset (for example: addin appname is at offset 0x20, so I would only modify the 8 bytes at 0x20, wit...
- Wed Jan 04, 2017 6:46 am
- Forum: Calculator Hacking/Modding Discussions
- Topic: Addin manager: need to manipulate RAM & SMEM
- Replies: 11
- Views: 32213
Re: Addin manager: need to manipulate RAM & SMEM
8 bytes. Also refer to http://casiopeia.net/forum/viewtopic.php?f=21&t=1774Zezombye wrote:Also, does the appname spans 8 or 9 bytes (including the '@', excluding the '\0')?
- Wed Jan 04, 2017 6:41 am
- Forum: Calculator Hacking/Modding Discussions
- Topic: Addin manager: need to manipulate RAM & SMEM
- Replies: 11
- Views: 32213
Re: Addin manager: need to manipulate RAM & SMEM
For shuffling addins, according to https://bible.planet-casio.com/simlo/chm/v20/fx_legacy_RAM.HTM the addin array is at 0x88006D9C. Theoretically all I would have to do is some memcpy. However, is the ram location the same with every OS? If not, is there a reliable way to know the location of the a...
- Sun Jan 01, 2017 6:07 pm
- Forum: Calculator Hacking/Modding Discussions
- Topic: MCS Files, g[12][mr] and on-calc
- Replies: 4
- Views: 10704
Re: MCS Files, g[12][mr] and on-calc
Next thing would be the enumeration of the MCS, the largest part of the main memory: // ********************* MCS ******************************** #define USE_TEXTVIEW_MCS 1 typedef struct { unsigned int adr1; unsigned int adr2; unsigned int adr3; unsigned int adr4; } TMCSHeader; typedef struct { un...
- Sun Jan 01, 2017 11:44 am
- Forum: Calculator Hacking/Modding Discussions
- Topic: MCS Files, g[12][mr] and on-calc
- Replies: 4
- Views: 10704
Re: MCS Files, g[12][mr] and on-calc
First thing would be the way to retrieve SETUP and ALPHA MEM from RAM. Setup_GetInfo is syscall 0x03DC. MCS_GetAlphaMem is syscall 0x0842. #define USE_TEXTVIEW 0 typedef struct { unsigned char Name1[13]; // will be set to "SETUP.g1m" on return unsigned char Name2[9]; // will be set to &quo...
- Sat Dec 31, 2016 6:05 pm
- Forum: Calculator Hacking/Modding Discussions
- Topic: MCS Files, g[12][mr] and on-calc
- Replies: 4
- Views: 10704
Re: MCS Files, g[12][mr] and on-calc
Most items which you can see with "MEMORY/F1:Main Memory" reside in the MCS. The MCS is a RAM-range starting at 88030000. Its directory starts at 88030100. The data-range starts at 88030A30, giving space for 0x93 internal main memory directory entries. Usually the MCS occupies about one 64...
- Sat Dec 31, 2016 2:54 pm
- Forum: Tutorials & Code Snippets
- Topic: Some hints concerning the G1S-type
- Replies: 14
- Views: 38914
Re: Some hints concerning the G1S-type
So that means FA-124 doesn't read the "deleted" special, and ignores the ID == 0 files and directories... right? Oo I do not know much about FA-124. I ceased using FA-124 shortly after I started the CASIO thing in 2008. Oh, and while I'm at it: is it possible to have less sectors, like: i...
- Sat Dec 31, 2016 11:07 am
- Forum: Casio fx-9860 SDK
- Topic: Some hints concerning the Appname
- Replies: 1
- Views: 5906
Some hints concerning the Appname
In the G1A-header at offset 0x20 resides a string which is used as MCS-working directory name. It must start with @. The following 7 characters usually correspond to the G1A-filename, which ain't necessarily so. This string (including the @) is returned by syscall 0x0462, if not changed by syscall 0...
- Fri Dec 30, 2016 10:54 pm
- Forum: Tutorials & Code Snippets
- Topic: Some hints concerning the G1S-type
- Replies: 14
- Views: 38914
Re: Some hints concerning the G1S-type
There are only deleted items (high nibble == 0) in Maths.g1s and Demonstrations.G1S. I usually test with real storage memories. This is more reliable. The fact, that the zero is the delete mark, is not random. The flash allows to change set bits to cleared bits by flashwriting a short value only. So...