Register

Search found 604 matches

Return to advanced search

SimonLothar
Sat Jan 28, 2017 6:21 pm
 
Forum: Tutorials & Code Snippets
Topic: Some hints concerning the G1S-type
Replies: 14
Views: 23047

Re: Some hints concerning the G1S-type

- if I understood well, different types have different indexes (like, there is an enumeration for sectors, one for directories and one for files). Does that mean the dirref/dirnum should in fact be understood as the parent node, where the high two bytes are for the type (numeration to use and the n...
SimonLothar
Sat Jan 28, 2017 4:42 pm
 
Forum: Tutorials & Code Snippets
Topic: Some hints concerning the G1S-type
Replies: 14
Views: 23047

Re: Some hints concerning the G1S-type

PS: Btw, here is my current understanding of the SMEM/G1S. "The list has 0x800 entries, and occupies the two first sectors (or maybe * just one, but it looks like data storage starts at sector 3). Entries with * a type being 0xFFFF should not be read". As long as the first sector is not e...
SimonLothar
Thu Jan 26, 2017 6:38 am
 
Forum: Calculator Hacking/Modding Discussions
Topic: Serial communications
Replies: 19
Views: 32996

Re: Serial communications

I use SetupComm( Handle, $8000, 0 ); SetCommState( Handle, DCB ); with DCB (0x1C, 0x2580, 0x1011, 0, 0x4000, 0x1000, 8, 0, 2, 17, 19, 0, 0, 0, 0) or (0x1C, 0x2580, 0x1011, 0, 0x4000, 0x1000, 8, 0, 0, 17, 19, 0, 0, 0, 0) SetCommTimeOuts( Handle, CTO ); with CTO (0xFFFFFFFF, 0, 0, 0, 0) as preparing s...
SimonLothar
Sun Jan 22, 2017 10:03 pm
 
Forum: Calculator Hacking/Modding Discussions
Topic: Serial communications
Replies: 19
Views: 32996

Re: Serial communications

Hm, it seems that even with those settings, I can't communicate with the calculator. (it's writing ok, but it is not reading, so I assume what I wrote just disappeared) Do you have a serial monitor to verify, what you are sending arrives properly? A receiving add-in would do. Is there other setting...
SimonLothar
Sun Jan 22, 2017 3:17 pm
 
Forum: Calculator Hacking/Modding Discussions
Topic: Serial communications
Replies: 19
Views: 32996

Re: Serial communications

The OSes use no parity and two stop bits. I use one stop bit, when communicating, because the probability of line faults is very low. The "no parity"-setting is mandatory. After I sent the first check packet successfully with 9600 baud I switch over to 115 kBaud. The protocol with USB and ...
SimonLothar
Sat Jan 21, 2017 5:43 pm
 
Forum: Calculator Hacking/Modding Discussions
Topic: FONTCHARACTER Reference - compatibility, sets
Replies: 25
Views: 41683

Re: FONTCHARACTER Reference - compatibility, sets

Neither OS 1.05 nor OS 1.05AU has E7-opcodes.

Try

for (int minor = 0; minor <= 255; minor++) {

instead of

for (int minor = 0; minor < 255; minor++) {
SimonLothar
Sat Jan 21, 2017 7:56 am
 
Forum: Calculator Hacking/Modding Discussions
Topic: FONTCHARACTER Reference - compatibility, sets
Replies: 25
Views: 41683

Re: FONTCHARACTER Reference - compatibility, sets

cakeisalie5 wrote:EDIT: Using what I've manually decoded, I guessed the flags (first byte's high nibble) were:
- 0x04: appended newline
- 0x08: appended space
Fine. So that is unravelled, too.
SimonLothar
Fri Jan 20, 2017 10:43 pm
 
Forum: Calculator Hacking/Modding Discussions
Topic: FONTCHARACTER Reference - compatibility, sets
Replies: 25
Views: 41683

Re: FONTCHARACTER Reference - compatibility, sets

And if I understand well, the second dword is the flags of the entry. What I don't understand is that in your example, the size of the element is the high nibble of the first byte of the flags, where here, it looks like it is the lowest nibble. Also, the characters looks deformed: for 0x0E, it shou...
SimonLothar
Wed Jan 18, 2017 8:35 am
 
Forum: Calculator Hacking/Modding Discussions
Topic: FONTCHARACTER Reference - compatibility, sets
Replies: 25
Views: 41683

Re: FONTCHARACTER Reference - compatibility, sets

There seems to exist a systematic method to retrieve the opcode-table-pointers from a fx-9860 OS image (at least for OSes 1.02 to 2.09). Again this is a method written in a C-like language. // detect OpCode-tables // start with syscall 7fc // find the first "mov.l @(h'84,pc), rn&quo...
SimonLothar
Mon Jan 16, 2017 5:51 am
 
Forum: Calculator Hacking/Modding Discussions
Topic: FONTCHARACTER Reference - compatibility, sets
Replies: 25
Views: 41683

Re: FONTCHARACTER Reference - compatibility, sets

But they are located on the same table, right? The charater definitions, t. i. the glyph-tables are located in different tables compared to the opcode/string tables. I checked images between OS 1.02 and OS 2.09. The glyph tables have been extended at least since OS 2.00. The problem is, I would lik...
PreviousNext

Return to advanced search