Yep, ALCDFIX fixed it Kerm
qazz42 wrote:
Well the calc is a TI-84+SE (Real thing, not the crappy nspire emulator). And the OS is 2.43
OK, thanks for that. And none of the other games and programs that you've been using and playing display this behavior?
Err, tell you the truth, the Gemini thing might have been caused by the lcd bug... Also, some graphical things that get randomly screwed up on the DCS desktop are fine now that I have used ALCDFIX.....
qazz42 wrote:
Err, tell you the truth, the Gemini thing might have been caused by the lcd bug... Also, some graphical things that get randomly screwed up on the DCS desktop are fine now that I have used ALCDFIX.....
You didn't mention that graphical things were getting screwed up on the DCS desktop. 
What's the boot code of your calculator, btw?
Edit: That's [mode][alpha][S], btw.
qazz42 wrote:
Yeah, I probably shout of..
Err, boot code? What is that?
The Boot Code, surprisingly enough, is the version number of the boot code that handles loading an OS when none is installed, launching the OS, etc. You can think of it as the BIOS of the calculator, if you like. I'm curious about the version because I know you just got a TI-84+SE a few days ago, so I'm thinking it might have a new hardware revision of some sort. Err, boot code? What is that?
JoeYoung wrote:
_player1537 wrote:
feature request: ALCDFIX built into DCS?
seems minor. why not just use ALCDFIX?
KermMartian wrote:
JoeYoung wrote:
_player1537 wrote:
feature request: ALCDFIX built into DCS?
seems minor. why not just use ALCDFIX?
it modifies the calculator somehow. even a complete reset won't undo it
Ah, then it actually modifies the OS. I'm not sure why Doors CS would be affected by that, though, since it never touches the OS for any LCD code.
from what I've heard, it modifies the lcd wait time port, I forget which one exactly it was but I remember it getting spoken of. I think it takes the value in that port and divides it by 4, and adds that to the clock cycles it takes to send a byte to the lcd, it should all be hardware for that, not OS related. But that's just what I think someone said about it...
_player1537 wrote:
from what I've heard, it modifies the lcd wait time port, I forget which one exactly it was but I remember it getting spoken of. I think it takes the value in that port and divides it by 4, and adds that to the clock cycles it takes to send a byte to the lcd, it should all be hardware for that, not OS related. But that's just what I think someone said about it...
Yeah, but that delay is generally implemented by the OS; you can't modify the display directly to know what its delay should be. 
_LCD_DELAY is the entry point, but unless the program is calling an OS LCD copy routine instead of DCS's IFastcopy, I wouldn't think that that routine would be used, and therefore that ALCDFIX wouldn't help. qazz42 wrote:
K, my boot code iiiisss
1.02
OK, that's the same as mine, so that's nothing new. I can't think why that would be happening; I'll have to try the game on my calc and see what happens. 1.02
I've been working on ProgPad, and realized some issues to be addressed with the AP routines...
1)Returning 0 - the AP routines aren't returning HL as 0 if you cancel. (wouldn't it be easier to return z with xor a and nz with or 1)
2)Filetype checking - the routines should allow built in filtering (with an on/off choice)
Here's the F double S OTD on my website
1)Returning 0 - the AP routines aren't returning HL as 0 if you cancel. (wouldn't it be easier to return z with xor a and nz with or 1)
2)Filetype checking - the routines should allow built in filtering (with an on/off choice)
Here's the F double S OTD on my website
Anakclusmos wrote:
I've been working on ProgPad, and realized some issues to be addressed with the AP routines...
1)Returning 0 - the AP routines aren't returning HL as 0 if you cancel. (wouldn't it be easier to return z with xor a and nz with or 1)
2)Filetype checking - the routines should allow built in filtering (with an on/off choice)
Here's the F double S OTD on my website
Duly noted, and added to the Scratchwork page. What's that a screenshot of, is that something I should be dealing with? 1)Returning 0 - the AP routines aren't returning HL as 0 if you cancel. (wouldn't it be easier to return z with xor a and nz with or 1)
2)Filetype checking - the routines should allow built in filtering (with an on/off choice)
Here's the F double S OTD on my website
Register to Join the Conversation
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
Advertisement