For those of list 1-6 that the calculator comes with, you don't need the | symbol in front. That symbol is the token for a small L in source coder.
Haobo wrote:
For those of list 1-6 that the calculator comes with, you don't need the | symbol in front. That symbol is the token for a small L in source coder.
yeah, I fixed it, but 2: Goto should still have worked.
Homerun doesn't work with unsquished assembly programs
https://ivoah.net
My Calcs: TI-86, TI SR-56, TI-Nspire CX CAS, TI-83+ SE
TI-84+ SE, TI-85, TI-73 Explorer VS, TI-84+ CSE, TI-89 Titanium
My Calcs: TI-86, TI SR-56, TI-Nspire CX CAS, TI-83+ SE
TI-84+ SE, TI-85, TI-73 Explorer VS, TI-84+ CSE, TI-89 Titanium
DoorsCS clears plotSScreen/graphscreen before launching an assembly program. Example where this behavior is bad: Program uses the data on graphscreen as level.
https://ivoah.net
My Calcs: TI-86, TI SR-56, TI-Nspire CX CAS, TI-83+ SE
TI-84+ SE, TI-85, TI-73 Explorer VS, TI-84+ CSE, TI-89 Titanium
My Calcs: TI-86, TI SR-56, TI-Nspire CX CAS, TI-83+ SE
TI-84+ SE, TI-85, TI-73 Explorer VS, TI-84+ CSE, TI-89 Titanium
Back port the real() fixes and app support from DCS 8
[edit]
Also the DCS6 header incorrectly calculates offsets for the unarchive portion of the header if the icon string has its closing quote. This should probably be documented, since the sprite editor in source coder terminates its strings.
[edit]
Also the DCS6 header incorrectly calculates offsets for the unarchive portion of the header if the icon string has its closing quote. This should probably be documented, since the sprite editor in source coder terminates its strings.
I was talking with some users on SAX this morning in regard to a glitch when using a program with Celtic3/DCS library commands. The program would randomly quit when run with the libs disabled in DoorsCS but would work fine with the libs active and with the dependent feature turned on and off. Initially I believed the glitch was in my program, which led to my sharing the program here this morning.
However, I was just possessed with the idea of RAM clearing, so as to totally purge the DCS hook from memory and attempt to run the program with no DCS interference at all -- it worked fine. This leads me to the conclusion that the glitch is not actually in my code at all but is in DCS's hook. Somehow, when the libs hook is disabled, it is not handling ignoring the commands properly. So Kerm, I have a bug for you. When I get home, I'm going to test with Celtic3 and no DCS to see if the same issue arises. I have enclosed the program for use with reproducing/testing this bug.
http://www.mediafire.com/download/npqqmnl8g5b488s/POLYAIO3+TI-84+Plus+Silver+Edition.8xp
However, I was just possessed with the idea of RAM clearing, so as to totally purge the DCS hook from memory and attempt to run the program with no DCS interference at all -- it worked fine. This leads me to the conclusion that the glitch is not actually in my code at all but is in DCS's hook. Somehow, when the libs hook is disabled, it is not handling ignoring the commands properly. So Kerm, I have a bug for you. When I get home, I'm going to test with Celtic3 and no DCS to see if the same issue arises. I have enclosed the program for use with reproducing/testing this bug.
http://www.mediafire.com/download/npqqmnl8g5b488s/POLYAIO3+TI-84+Plus+Silver+Edition.8xp
Although I was lucky and almost no data was lost, some of the Doors CS 7.2 xLib routines once froze and another time crashed (RAM reset) my calculator.
I am not quite sure what is going on there, I and PT_ need to analyze the code further to find out ehat exactly crashes.
Anyways, our algorithm uses the DrawShape ("real(12,...)"), ScrollScreen ("real(4,...)") and RecallPic ("real(3,...)") commands.
With some certain input it either throws an error and if pressing 2:Goto exits to the homescreen or once it froze and another time just crashed.
No libraries/external programs are used other than Doors CS, and we use TI-Basic, so the problem must be with Doors CS or, very unlikely, TI-OS.
I am running Doors CS 7.2 on a TI-83+ (Not SE) with TI-OS 1.19 installed. Me and PT_ have similar issues.
If that helps, I have ~16500 byets of RAM and ~33500 bytes of Flash Memory free. My last Garbage Collect was relatively long ago.
I am not quite sure what is going on there, I and PT_ need to analyze the code further to find out ehat exactly crashes.
Anyways, our algorithm uses the DrawShape ("real(12,...)"), ScrollScreen ("real(4,...)") and RecallPic ("real(3,...)") commands.
With some certain input it either throws an error and if pressing 2:Goto exits to the homescreen or once it froze and another time just crashed.
No libraries/external programs are used other than Doors CS, and we use TI-Basic, so the problem must be with Doors CS or, very unlikely, TI-OS.
I am running Doors CS 7.2 on a TI-83+ (Not SE) with TI-OS 1.19 installed. Me and PT_ have similar issues.
If that helps, I have ~16500 byets of RAM and ~33500 bytes of Flash Memory free. My last Garbage Collect was relatively long ago.
Nik wrote:
Although I was lucky and almost no data was lost, some of the Doors CS 7.2 xLib routines once froze and another time crashed (RAM reset) my calculator.
I am not quite sure what is going on there, I and PT_ need to analyze the code further to find out ehat exactly crashes.
Anyways, our algorithm uses the DrawShape ("real(12,...)"), ScrollScreen ("real(4,...)") and RecallPic ("real(3,...)") commands.
With some certain input it either throws an error and if pressing 2:Goto exits to the homescreen or once it froze and another time just crashed.
No libraries/external programs are used other than Doors CS, and we use TI-Basic, so the problem must be with Doors CS or, very unlikely, TI-OS.
I am running Doors CS 7.2 on a TI-83+ (Not SE) with TI-OS 1.19 installed. Me and PT_ have similar issues.
If that helps, I have ~16500 byets of RAM and ~33500 bytes of Flash Memory free. My last Garbage Collect was relatively long ago.
I am not quite sure what is going on there, I and PT_ need to analyze the code further to find out ehat exactly crashes.
Anyways, our algorithm uses the DrawShape ("real(12,...)"), ScrollScreen ("real(4,...)") and RecallPic ("real(3,...)") commands.
With some certain input it either throws an error and if pressing 2:Goto exits to the homescreen or once it froze and another time just crashed.
No libraries/external programs are used other than Doors CS, and we use TI-Basic, so the problem must be with Doors CS or, very unlikely, TI-OS.
I am running Doors CS 7.2 on a TI-83+ (Not SE) with TI-OS 1.19 installed. Me and PT_ have similar issues.
If that helps, I have ~16500 byets of RAM and ~33500 bytes of Flash Memory free. My last Garbage Collect was relatively long ago.
Addition: you will get a Syntax Error if the left bound of a shape > 95, so
Code:
real(12,7,96,0,97,64,1
EDIT: it froze when the upper bound > 63, so
Code:
real(12,7,0,64,96,66,1
I have two that have to deal with libs and a misc one
1. I was using ErrorHandle det(25,function,string)
It launched the specified program and when I pressed ON, RAM cleared.
2. ChkStats
Code:
shouldn't return the string value of "2CubicReg 55"
on 2.55 MP on a TI-84 Plus
Doors CS 7.2
DCSB 5
3. Even if on hooks and homerun hooks and run at startup are all off, if you launch dcs, your OFFSCRPT var is overwritten.
1. I was using ErrorHandle det(25,function,string)
It launched the specified program and when I pressed ON, RAM cleared.
2. ChkStats
Code:
det(4,3)
shouldn't return the string value of "2CubicReg 55"
on 2.55 MP on a TI-84 Plus
Doors CS 7.2
DCSB 5
3. Even if on hooks and homerun hooks and run at startup are all off, if you launch dcs, your OFFSCRPT var is overwritten.
- Comments2010
- Advanced Newbie (Posts: 72)
- 11 Apr 2016 12:24:47 pm
- Last edited by Comments2010 on 15 Apr 2016 08:33:17 am; edited 5 times in total
New bug! I'm working on adding asm libraries supplied by Dcs into my SysTools v3.0 program, and parts are being erased, overwritten, corrupted, and even copying chunks from the beginning over random parts mid-line further down. Please help! I lost all of my program to Dcs aside from my header which is pasted over every line now
This happens only when breaking a program to access the dcs program editor and it happens regularly
Apps installed:
Calcsys
Doors CS 7
Omnicalc (no hooks)
Start-up Customization (no hooks)
This happens only when breaking a program to access the dcs program editor and it happens regularly
Apps installed:
Calcsys
Doors CS 7
Omnicalc (no hooks)
Start-up Customization (no hooks)
Bugs with the Home run hook
The output( trick to hide the Done message doesn't work
Turning off lowercase won't work if the home run hook is on and the TI-OS Lowercase setting is checked
The output( trick to hide the Done message doesn't work
Turning off lowercase won't work if the home run hook is on and the TI-OS Lowercase setting is checked
DJ_O wrote:
The Output() trick only works on OS 2.43 or older.
But it works on my TI-84 Plus on 2.55 MP without Doors CS hooks, but with hooks, it says Done
When using libraries in Doors CS 7 to get the calculator ID, the hardware version digit (3rd digit) and the first digit of the serial number (4th digit) is incorrect
Comments2010 wrote:
When using libraries in Doors CS 7 to get the calculator ID, the hardware version digit (3rd digit) and the first digit of the serial number (4th digit) is incorrect
Are you talking about Celtic III's ChkStats function? Doors CS directly calls the OS BCALL for this and creates a string from what it returns: Code:
fChkSerial:
bcall($807E)
bcall(_Op4toOp6) ;move needed data out of harm's way
ld hl,Op6
ld bc,5
jp fBinToString+6
- Comments2010
- Advanced Newbie (Posts: 72)
- 19 Apr 2016 09:25:50 am
- Last edited by Comments2010 on 19 Apr 2016 09:30:32 am; edited 1 time in total
KermMartian wrote:
Comments2010 wrote:
When using libraries in Doors CS 7 to get the calculator ID, the hardware version digit (3rd digit) and the first digit of the serial number (4th digit) is incorrect
Are you talking about Celtic III's ChkStats function? Doors CS directly calls the OS BCALL for this and creates a string from what it returns: Code:
fChkSerial:
bcall($807E)
bcall(_Op4toOp6) ;move needed data out of harm's way
ld hl,Op6
ld bc,5
jp fBinToString+6
Please ignore the following sentence: Yes I was, but where does the "CubicReg " come from?
Comments2010 wrote:
Yes I was, but where does the "CubicReg " come from?
Pardon? Your post didn't mention anything about the CubicReg token. KermMartian wrote:
Comments2010 wrote:
Yes I was, but where does the "CubicReg " come from?
Pardon? Your post didn't mention anything about the CubicReg token. Comments2010 wrote:
2. ChkStats
Code:
shouldn't return the string value of "2CubicReg 55"
on 2.55 MP on a TI-84 Plus
Doors CS 7.2
DCSB 5
Code:
det(4,3)
shouldn't return the string value of "2CubicReg 55"
on 2.55 MP on a TI-84 Plus
Doors CS 7.2
DCSB 5
I was thinking of this
I have 3 bugs to report.
1/3
[FATAL]
Effect: Unrecoverable error occurs (RAM clear)
Occurs: replicate by doing this:
Make a locked program in RAM with a DCS7 header and this code
Code:
Run it with DCS7.2 and let the program exit with a Return command. Now exit to TI-OS and run the same program and press [ON] during the for( loop. Immediately after it displays "ERR:BREAK 1:Quit", the LCD enters test mode, the error message is glitched all over the screen, lines flicker and after about 5 seconds of this, it powers off and resets.
2/3
[Minor]
Sometimes [ON] breaking a program and quiting with HomeRun enabled, when you return to the home screen, button presses do nothing except for [2nd][OFF], and [ENTER]. [ENTER] will (most that I've seen) type "0" and then this bug is over. [2nd][Quit] also ends the bug.
3/3
[Major]
Sometimes, after ungrouping programs, they still don't show up in Doors CS. I think it may be due to backing up folders and restoring them.
1/3
[FATAL]
Effect: Unrecoverable error occurs (RAM clear)
Occurs: replicate by doing this:
Make a locked program in RAM with a DCS7 header and this code
Code:
For(A,0,1024
getKey->B
If B:1024->A
If not(B:End
If B!=0 and B!=22 and......:Goto 0A
If B=22:Goto 2F
.........
If A>=1024:Goto 0A
Run it with DCS7.2 and let the program exit with a Return command. Now exit to TI-OS and run the same program and press [ON] during the for( loop. Immediately after it displays "ERR:BREAK 1:Quit", the LCD enters test mode, the error message is glitched all over the screen, lines flicker and after about 5 seconds of this, it powers off and resets.
2/3
[Minor]
Sometimes [ON] breaking a program and quiting with HomeRun enabled, when you return to the home screen, button presses do nothing except for [2nd][OFF], and [ENTER]. [ENTER] will (most that I've seen) type "0" and then this bug is over. [2nd][Quit] also ends the bug.
3/3
[Major]
Sometimes, after ungrouping programs, they still don't show up in Doors CS. I think it may be due to backing up folders and restoring them.
A weird bug that I have found. In one of my projects, copying a line from one program into another program will cause my calculator to crash. Other times, It will dump random stuff into the program that I am copying from, and upon saving the program after removing it, random stuff get drawn to the 2nd quarter of the screen from the left. when the random stuff gets to the bottom of the screen, the screen (as one would expect) freaks out for about five seconds, and resets the ram. Other times, my calculator will become unresponsive, forcing me to push the reset button on the back.
I found a bug having to do with using the "Stop" command in any program at any time in these circumstances:
xLib/celtic III/DCS libraries enabled AND Homerun enabled
OS 2.43
DCS7.3 running(Runer112 version)
When you run a BASIC program in the TI-stock prgm menu, the calculator will crash and ram clear once you hit "Stop" in any program.
This only applies with all the libraries above enabled, not an individual library.
This also does not occur when the BASIC program is run from the DCS7 menu.
xLib/celtic III/DCS libraries enabled AND Homerun enabled
OS 2.43
DCS7.3 running(Runer112 version)
When you run a BASIC program in the TI-stock prgm menu, the calculator will crash and ram clear once you hit "Stop" in any program.
This only applies with all the libraries above enabled, not an individual library.
This also does not occur when the BASIC program is run from the DCS7 menu.
Register to Join the Conversation
Have your own thoughts to add to this or any other topic? Want to ask a question, offer a suggestion, share your own programs and projects, upload a file to the file archives, get help with calculator and computer programming, or simply chat with like-minded coders and tech and calculator enthusiasts via the site-wide AJAX SAX widget? Registration for a free Cemetech account only takes a minute.
» Go to Registration page
» Go to Registration page
» Goto page Previous 1, 2, 3 ... , 38, 39, 40 Next
» View previous topic :: View next topic
» View previous topic :: View next topic
Page 39 of 40
» All times are UTC - 5 Hours
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