WikiTI - User contributions [en]

Programming under Unix-like operating systems

2008-08-12T20:14:44Z

Gambit: /* tpasm */ set pseudoop bug note

Here are the different tools at your disposal:

= General Overviews =

==Emulators==
* [http://lpg.ticalc.org/prj_tilem/ TilEm]
* VirtualTI through wine
* [[PindurTI]] through Wine
* [[PindurTI]] in non-interactive mode (with or without [http://kvince83.tengun.net/maxboard/viewtopic.php?t=2466 PTI frontend])

==Syntax highlighting==
Several editors have native or extensional support for editing Z80 assembly code with syntax highlighting:
* Kwrite and Kate can be made to syntax-highlight Z80 assembly with [http://www.ticalc.org/archives/files/fileinfo/391/39178.html the appropriate definition file]. The file must be placed in /usr/share/apps/katepart/syntax .
* SciTE and Emacs both have native modes for assembly code. For Emacs, one must make sure to turn on Font Lock mode as well.
* The [http://www.revsoft.org/phpBB2/viewforum.php?f=25 Z80 Assembly IDE] has simple syntax highlighting built-in.
* Users of Vim and WLA DX can use [http://sigma.unitedti.org/files/misc/z80.vim.bz2 this syntax file].

== Assembling ==

=== SPASM ===

'''Author''': Spencer Putt

'''Home Page''': [http://www.revsoft.org/phpBB2/viewforum.php?f=21 http://www.revsoft.org/phpBB2/viewforum.php?f=21]

SPASM is a portable Z80 assembler released under the GPL. Its distinguishing features are extremely fast assembly and powerful macro support. The output is only available in binary form, however with the use of [http://www.revsoft.org/phpBB2/viewforum.php?f=23 Wabbitsign], written by James Montelongo and Spencer Putt, it can easily be converted to any desired program type.

assembler foo.asm foo.bin
wabbit foo.bin foo.8xp

SPASM and Wabbitsign are included in [http://www.ticalc.org/archives/files/fileinfo/390/39009.html Z80 Assembly IDE 1.32] by burntfuse

=== tpasm ===

'''Author''': Todd Squires

'''Home page''': [http://www.sqrt.com/ http://www.sqrt.com/]

tpasm is a Free (GPL) assembler which supports the Z80 as well as the 6805, 6809, 68HC11, 6502, Sunplus, 8051, PIC, and AVR. It uses syntax very similar to ZMASM.

tpasm 1.2 does not support binary file output, but you can use ''objcopy'' (from the GNU binutils package) to convert its Intel Hex output into binary; e.g.

tpasm foo.asm -o intel foo.hex -l foo.lst
objcopy -I ihex foo.hex -O binary foo.bin

tpasm 1.4 has a bug where the set pseudo-opcode takes precedence over the Z80 set instruction. A quickfix is to disable the set pseudo-opcode by commenting line 86 of pseudo.c (.set is still available).

=== ASxxxx ===

'''Author''': Alan R. Baldwin

'''Home page''': [http://shop-pdp.kent.edu/ashtml/asxxxx.htm http://shop-pdp.kent.edu/ashtml/asxxxx.htm]

ASxxxx is a freeware assembler which supports the Z80 along with a large variety of other processors. It more closely resembles a modern PC assembler than a typical Z80 assembler, as it assembles each file into a relocatable object format which can then be linked with other files to produce the complete program. The linking is done by a separate program called ASlink (included with the package.)

To assemble and link a simple program you might do something like

asz80 -plogff foo.asm
aslink -u -b _CODE=0x9D95 -i foo.ihx foo.rel
objcopy -I ihex foo.ihx -O binary foo.bin

Note that the syntax is rather different from that of most Z80 assemblers. The important differences are
* Immediate values are marked with #.
* Indexed memory access is written as N(ix) rather than (ix+N).
* Constants are written differently: 0xAA, 0hAA, or $$AA for hexadecimal; 0o252, 0q252, or $&252 for octal; 0b10101010 or $%10101010 for binary.

For example,
ld hl,#str_hello
add a,3(ix)
xor #0x0f

There is also a modified version of ASxxxx distributed with the [http://sdcc.sf.net/ Small Device C Compiler]. This version is, if anything, more confusing to use due to the poorly-documented changes made by the SDCC team.

=== TASM ===

'''Author''': Thomas N. Anderson

'''Home page''': [http://home.comcast.net/~tasm/ http://home.comcast.net/~tasm/]

TASM is a shareware assembler which also supports a variety of processors.

There are several ways that you can use tasm under Linux:
* The TASM 3.1 for Linux shareware release is still in the wild. To use this you will need to enable "a.out" support in your kernel (it may be available as the module ''binfmt_aout''.) You will also need to obtain the ancient Linux libc version 4 (''not'' glibc) which can be found [http://ftp.linux.org.uk/pub/linux/libc/ here].
* You can use TASM 3.2 for Windows with [http://www.winehq.com Wine].
* You can pay the $40 and compile it yourself on the platform of your choice.

=== Brass ===
'''Author''': benryves

'''Home page''': [http://benryves.com/bin/brass/ http://benryves.com/bin/brass/]

Brass runs under Linux thanks to Mono.

=== Zasm ===
'''Author''': Steven Deprez

'''Home page''': [http://lpg.ticalc.org/prj_zasm/index.html http://lpg.ticalc.org/prj_zasm/index.html]

Zasm is an open source assembler that is almost fully compatible with Tasm and ZDS.

=== WLA DX ===
'''Author''': Ville Helin

'''Home page''': [http://www.villehelin.com/wla.html http://www.villehelin.com/wla.html]

WLA DX is another open-source (GNU GPL) cross-assembler with a primary focus on targeting video game consoles. It is a high-powered assembler with a wide variety of features such as, e.g. separate compilation, POSIX-like file I/O, and code sectioning. However it is cumbersome when assembling small projects, and semantics are unorthodox compared to other assemblers. (~ is the XOR operator, macro arguments are passed by value, etc.).

WLA DX has had an influence in the development of Brass.

=== Pasmo ===
'''Author''': Julián Albo

'''Home page''': [http://www.arrakis.es/~ninsesabe/pasmo/ http://www.arrakis.es/~ninsesabe/pasmo/]

Pasmo is another standalone Z80 cross-assembler with basic macro support, but without the ability to generate
relocatable object files. It is licensed under the GNU GPL, and exists as the package <tt>pasmo</tt> in the Debian pool.

=== z80asm ===
'''Author''': Bas Wijnen

'''Home page''': [http://savannah.nongnu.org/projects/z80asm/ http://savannah.nongnu.org/projects/z80asm/]

z80asm is a standalone Z80 cross-assembler similar in nature to Pasmo, in that it has macro support but cannot generate relocatable object files. It too is licensed under the GNU GPL (version 2 or later), and exists as the package <tt>z80asm</tt> in the Debian pool.

=== GNU as ===
'''Author''': the GNU binutils team

'''Home page''': [http://www.gnu.org/software/binutils/ http://www.gnu.org/software/binutils/]

Starting from version 2.17, the GNU assembler, part of the binutils package, is capable of cross-assembling Z80 code when configured for it at compile-time, such as with <tt>--target=z80-unknown-coff</tt>. binutils includes a powerful assembler and linker both, along with various utilities for handling object files, such as objcopy and objdump; for Z80, COFF is used for relocatable objects, with raw binary and Intel hex formats also supported. While this is probably one of the more powerful tools in the list for Z80 development, it also requires more work to start with, as the traditional way to get a cross-assembling binutils is to compile it oneself. Being a GNU package, binutils is naturally licensed under the GNU GPL (version 2 or later). Prepackaged binary versions of binutils are very common, but usually do not have cross-assembling capability.

==Sending programs to the calc==
* [http://www.ticalc.org/archives/files/fileinfo/374/37480.html TiLP-II] (requires [http://www.ticalc.org/archives/files/fileinfo/374/37479.html tilibs])
* [http://www.ticalc.org/archives/files/fileinfo/75/7588.html titranz] : commandline tool, only works for TI-83/TI-83+

= FreeBSD =
Much of the aforementioned software should compile independently without problem or with minor tweaking under FreeBSD, but it is best to utilize the ports collection whenever possible. Unfortunately, the current state of calculator-related software in the FreeBSD Ports Collection is lacking in variety.

* Development
{| width="75%" class="wikitable" style="margin: 1em auto 1em auto"
|- align="left"
!Port !! Current Version !! Location
|-
|tpasm || 1.2_1 || devel/tpasm
|-
|z80asm || 1.6_1 || devel/z80asm
|-
|z80-asm || 0.1_1 || devel/z80-asm
|-
|TI-GCC || 0.96.b8 || devel/tigcc
|-
|libtifiles2 || 1.0.1 || devel/libtifiles2
|}

* Communications
{| width="75%" class="wikitable" style="margin: 1em auto 1em auto"
|- align="left"
!Port !! Current Version !! Location
|-
|TiLP-II || 1.01 || comms/tilp2
|-
|libticables2 || 1.0.2 || comms/libticables2
|-
|libticalcs2 || 1.0.1 || comms/libticalcs2
|}

* Converters
{| width="75%" class="wikitable" style="margin: 1em auto 1em auto"
|- align="left"
!Port !! Current Version !! Location
|-
|libticonv || 1.0.0 || converters/libticonv
|}

* Emulation
{| width="75%" class="wikitable" style="margin: 1em auto 1em auto"
|- align="left"
!Port !! Current Version !! Location
|-
| TIEmu 2 || 2.08 || emulators/tiemu2
|}

= Mac OS X =
(Note that all of these assesments were made on a MacBook running 10.4.9 Intel. Mileage may vary on other versions and of course the Darwine stuff won't work on PPC.)

TiLP-II is known to compile and work properly with SilverLink and Direct USB cables with the 83+, 84+SE, and 89Ti, so there is no reason to believe it will not work with the other calculators. TI Connect X works well enough on Intel Macs even though it is not officially supported, however it seems to be more strict with the format of .8xk files than TiLP or TI Connect (Windows).

Brass works in Mono. Wabbitspasm compiles and works properly. ZDS works in Darwine.

TilEm compiles but seems to have some issues with multiple ROM versions. It is unclear to me if this is a problem with the build or TilEm itself. PindurTI is somewhat usable in Darwine: You must use the send.exe utility to send the ROM image, then it will emulate properly. However, it makes extensive use of the F-keys, including the ExposÃ© ones. Remapping the ExposÃ© keys is the only solution. TI FLASH Debugger runs in Darwine but the calculator windows are unskinned: You must either use the keyboard or click blindly in the window. The display output is fine, and other debugger windows appear to function properly. VirtualTI (2.5) should run OK after putting the ROM files somewhere Darwine knows about (I was lazy).

= Other Unixes =

This section is a stub. Please add it it.

Talk:83Plus:Basic:Routines:DecToFrac

2007-04-11T17:49:56Z

Gambit: one reason to keep

== Salute ==
@calc84maniac: Sweet routine. I salute your superior programming skills. I avoid using While loops, but your routine is definitely shorter and sweeter than mine. :-) --[[User:Saibot84|Saibot84]] 06:48, 11 April 2007 (PDT)

== Question ==
Anyone see any reason to keep my code here? --[[User:Saibot84|Saibot84]] 06:50, 11 April 2007 (PDT)
:Yes. Although it appears that mostly experts are on WikiTI, I suspect there are many passive users that browse this wiki. One possible reason to keep your code is for the beginners ("newbs") to learn from them. It might help for them to compare and contrast the differences in implementations. They can "step through" your (well commented) code and see how you drew your logic in writing DecToFrac. With that said, I'll have to find some time out of my day to do the above. :) [[User:Gambit|Gambit]] 10:49, 11 April 2007 (PDT)

83Plus:BCALLs:4F2A

2007-03-11T16:12:18Z

Gambit: Redirect

#REDIRECT [[83Plus:BCALLs:8033]]

Talk:WikiTI Home

2007-02-11T07:55:51Z

Gambit: Forgot to add signature (even if it is the wrong datestamp)

= Discussion =
What do you think about this wiki?

== More! ==

I think it needs information on more calculators than just the Ti-83+ series, and general assembly information (like a good cathegorized tutorial overview for instance) wouldn't hurt either, I think :)

Timendus

== I hope we can do that soon ==

Just, we don't want to waste time getting it all set up for that and have no one use it. If we see a lot of people milling around here, contributing, then by all means, we'll expand. But one thing we '''DON'T''' want to do is mirror 28 Days. We can link TO it, but we don't want it actually here.

--[[User:AndyJ|AndyJ]] 06:50, 27 Mar 2005 (PST)

== Categories ==

On many pages, there is now a sizable blank space at the top due to several lines of category links. What, if anything, should we do about this? [[User:FloppusMaximus|FloppusMaximus]] 19:06, 29 Mar 2005 (PST)

== Move them? ==

Move the Category links to the bottom should do it. :) That, or put them all on one line.

--[[User:AndyJ|AndyJ]] 19:07, 29 Mar 2005 (PST)

:Yeah, that sounds like a good idea. :) [[User:FloppusMaximus|FloppusMaximus]] 20:18, 29 Mar 2005 (PST)

:: I think I officially qualify as a robot now. You can tell I was getting tired towards the end, as I missed the minor-edit button a few times... sorry about that... [[User:FloppusMaximus|FloppusMaximus]] 21:28, 29 Mar 2005 (PST)
:: Actually, I was going to just mod the php code to fix this bug....keeping the category tags on the top might be a good idea actually. (JasonM)
:::That might still be a good idea. [[User:FloppusMaximus|FloppusMaximus]] 13:18, 3 Apr 2005 (PDT)

== Caching ==

Is it just me, or are there some serious caching problems here?
[[User:FloppusMaximus|FloppusMaximus]] 21:32, 1 Apr 2005 (PST)

: In particular? --[[User:Dan Englender|Dan Englender]] 21:42, 1 Apr 2005 (PST)

:: Ya, the wiki seems to have weird caching problems, especially since it appears the reload the page every time, even if it doesn't get changes. I don't know what's up. --[[User:AndyJ|AndyJ]] 22:35, 1 Apr 2005 (PST)

::: Considering the dynamic nature of a wiki (a page could be edited, at pretty much any time), I wouldn't mind not having it cached. (Though I would personally disable browser caching altogether if firefox would let me... :P ) --[[User:Aquanight|Aquanight]] 22:44, 1 Apr 2005 (PST)

:::: Er... I think I see what you mean... stuff is getting cached when it shouldn't be. (I could've sworn I told firefox to only use 0 KB (aka none) for cache and it's still caching ... argh.) --[[User:Aquanight|Aquanight]] 22:46, 1 Apr 2005 (PST)

::::: I've disabled caching myself as well. Perhaps we should just disable caching altogether? (JasonM)

::::::Caching has been disabled. (JasonM)

::: I found a "Disable Caching" option in Misc. Preferences, if that helps. [[User:Gambit|Gambit]] 00:28, 2 Apr 2005 (PST)

== On Other Calculators ==

Just a random idea I had -- a lot of the ROM calls, RAM addresses, and ports are very similar, if not identical, between the 83 and 83+, and more generally, between all of the Z80 calculators. For some of them -- [[83Plus:RAM:86D8]] and [[83:RAM:8253]], for instance -- it may be possible to combine the two into a single page, though I'm not sure that would be a good idea, given the potential for confusion. So here's what I propose instead:
* For simple things like penRow, we can just have two copies of the page, as there isn't very much to keep synchronized.
* For more detailed pages such as GetKey, have a brief description with a link -- "This routine waits for the user to press a key and returns it. It is equivalent to [[83Plus:BCALLs:4972|GetKey]] on the TI-83 Plus." -- on one page, and the more detailed description on the other. Not a redirect in this case; I'm talking about a distinct page, which would point out the different call points and RAM addresses; in the case of GetKey, for instance, the address of keyExtend is different and should be noted.
* In either case, on ''both'' pages, add a new section "On Other Calculators" near the bottom, with appropriate links. This section serves two purposes: First, it's simply useful information to have available, both for people trying to write cross-platform code, and for those of us who are interested in researching the OS. Secondly, it would serve as a reminder to editors that there are multiple pages that may need to be updated.
* It's also important to maintain the distinction between routines/variables/ports that are ''identical'' as opposed to those which merely have related functions. For example, the widely used GetK routine on the 83 isn't known -- to my knowledge -- on the 73, but GetCSC serves as an adequate substitute in many situations. This is something that belongs in "See Also," not in this section.
* Some templates might be in order here.

[[User:FloppusMaximus|FloppusMaximus]] 18:41, 24 May 2005 (PDT)

:It's not a bad idea. The only problem is that it makes a lot more work for people who just want to make a simple addition to the wiki. There's already a fairly high initial barrier (figuring out the templates and categories) to overcome for someone who wants to stroll along and add something to the wiki. For you and I it wouldn't be a big deal, but I'm worried it's going to dissuade a random person who floats by from adding ErrMemory to 83 Plus, because then 83 (and 86 or 73, if someone decides to start them) will have to be added/changed as well. --[[User:Dan Englender|Dan Englender]] 10:01, 25 May 2005 (PDT)
:It might also be cool to hack up the interlanguage features so we can have the nifty language link-box similar to what exists on wikipedia. --[[User:Dan Englender|Dan Englender]] 12:57, 27 March 2006 (PST)

== Wanted Pages ==
I decided it was too minor to post as news on the main page, but I modified the [[Special:wantedpages|Wanted Pages]] page so that the threshold is 1 link instead of 2 links. A *lot* more wanted pages show up now, though there is some junk in the list now too (like fake links from templates). I figure wanted pages are as good a place as any to start adding, so I'm going to try to make a dent in the list. Anyone who would like to help is welcome to do so :) --[[User:Dan Englender|Dan Englender]] 10:06, 25 May 2005 (PDT)

== Not "hardware" specific documents ==

I was so free to edit the artilce over Emulator(s). I also created an article regarding PindurTI.

As I already stated on the MaxCoderz board (http://joepnet.com/hosted/maxcoderz/phpBB2/viewtopic.php?t=1521), I think WikiTI has a lot of potential to collect information about the TI community aswell. Thinks like PindurTI, GrayScale and maybe even information about all the Zelda attempts. In my opinion, people can benefit from that information. --[[User:Kv83|Vincent Junemann]] 15:00, 21 February 2006 (CET)
:Hehe... Zelda attempts? We really do need a page for that ;) [[User:TD-Linux|TD-Linux]] 09:24, 19 October 2006 (PDT)

== Required logon ==

If the spam is being done by bots, perhaps instead of requiring a log-on, we can require either a log-on or a captcha? I realize there's additional coding involved, but we've had a fair number of useful contributions by non-logged in contributors, and it would be a shame to scare them off by prospects of account creation or the fact that we can track their activities, or what have you. --[[User:Dan Englender|Dan Englender]] 13:55, 23 Feb 2006 (PST)
:Agreed, if we can either find a mod for that or code one ourselves. Of course, maybe even a simple "check this box" thing would work if the bots are programmed just to hit mediawiki and not check for stuff... And if a botrunner ever finds it and fixes their bots, we can either just change it or go to a captcha... However, I think most of the legit anon edits were by people who have an account but just didn't notice they weren't logged in at the time. [[User:AndyJ|Andy Janata]] 18:40, 23 Feb 2006 (PST)

== Wiki update ==

Whats this undefined link I see on a lot of the pages?--[[User:Jim e|Jim e]] 06:07, 14 March 2006 (PST)
:Example? --[[User:Dan Englender|Dan Englender]] 06:12, 14 March 2006 (PST)

::This page has it right under the contents.--[[User:Jim e|Jim e]] 06:18, 14 March 2006 (PST)
:::I'm not seeing it. Screen grab? (Also, try clearing your browser's cache in case something's not playing nice between this and the old wiki) --[[User:Dan Englender|Dan Englender]] 06:21, 14 March 2006 (PST)

::::....It's gone now. I guess it was a fluke, but I did get an image before it disappeared, just to prove i'm not crazy. [http://www.txjim.com/undefined.jpg Pic]

== Motivation Idea ==

Here's an idea that might spark more interest in WikiTI...

Usually, this stuff occurs on the subconscious level, but what if it was brought out from these depths? We have this inquisitive.. knowledge.. accumulate thing... and so what if there was a page (or maybe a set of them) that had a list of questions about the unknowns of the TI-OS? This idea came from this quote:

<nowiki>In mathematics the art of asking questions is more valuable than solving problems. ~ Georg Cantor</nowiki>

All questions would be welcome (not sure about programming help oriented ones though), but maybe not all questions would be answerable, and maybe some questions would be better off not being answered. Other users will fill in the blanks and try to answer the question (because of generosity/competition/whatever). Concurrently, some users might think that some Q&A sections fit well together and then they will merge these into a wiki page. It might also be possible for someone to write a wiki page as an answer to a question!

The point of such a page as this is to 'encourage hacking' in its traditional sense, as it were. As a side effect, it ''might possibly'' help us all (new and old alike) with our hesitancy in editing a page. Furthermore, I think that this idea will only work if there is a continual asking of questions; otherwise, it will lag and eventually '''fail'''. Hence, the [[Wikipedia:WP:BB|Be Bold]] slogan of Wikipedia.

For example:
What are the specific differences between GarbageCollect-ing and "Defragmenting..."?

[[User:Brandonw|Brandonw]] and I talked about this on IRC:
<nowiki><BrandonW> It's a good idea, but I'm not so sure about it working on WikiTI.
<BrandonW> Maybe the question is elsewhere and the answer can be posted on WikiTI.
<BrandonW> The answer to every question can be a WikiTI link.
<BrandonW> That makes WikiTI bigger with more information and people get their questions answered.
<Gambit_> hmm, asked where? Is there a central location somewhere where these would be asked?
<Gambit_> WikiTI subforum in DS, perhaps?
<BrandonW> It could be hosted anywhere...someplace new.
<Gambit_> hm
<BrandonW> Perhaps.</nowiki>

Good or bad? Thoughts? --[[User:Gambit|Gambit]] 23:55, 10 February 2007 (PST)

Talk:WikiTI Home

2007-02-10T23:48:38Z

Gambit: Motivation Idea

83Plus:Software:usb8x/BASIC Interface/KBDGetKey

2007-02-07T22:37:31Z

Gambit: Very minor wiki markup conversion

== Synopsis ==
'''Name:''' KBDGetKey

'''Function Number:''' 11

'''Minimum usb8x version:''' 0.something

Gets keypress information from the USB KBD driver.

=== Inputs ===
''None''

=== Outputs ===
Each value in the list is the decimal value of the contents of the registers {A,B,C,D,E,H,L}.
* 1: Number of keys remaining in keyboard buffer
* 2: Raw key press modifiers
* 3: Raw key press keycode
* 4: Converted TIOS keyextend code
* 5: Converted TIOS _GetKey code (''not'' the same as the BASIC getkey codes. . . pester someone to add a conversion)
* 6: ''nonsense''
* 7: ''nonsense'' (mostly--whatever Dan left in H&L)

== Notes ==
It'd be nice to get a normal BASIC getKey-style return code. Perhaps the KBD driver wrapper could overwrite H (element 6, which is usually zero anyway) with that before returing.

'''Beware!''' Pressing scroll-, caps-, or num-lock may crash the program and possibly the driver! I don't know why exactly this happens, but ''does'' need to be fixed by somebody. My experience has been that it results in the program quitting for no apparent reason, and then, if you try running it again, a possible crash.

The raw key-press modifiers byte looks like this:
Bit 7 6 5 4 | 3 2 1 0
key Su Al Sh Cn | Su Al Sh Cn
side Right | left
Su=Super; Al=Alt; Sh=Shift; Cn=Control

Here's a loop to convert a byte into a list:
For(B,7,0,-1)
If X-B^2>0
Then
1→lMODS(B+1)
X-2^B→X
End
End
Then, to access bit 2 you would look at element 3 and so on. Note that if you Disp the list, it will show the bits in reverse order.

== See Also ==
* [[../KBDInit|KBDInit]] - Initialize the keyboard driver.

Category:Emulators

2006-09-03T03:27:24Z

Gambit: fixed categories

A software emulator allows computer programs to run on a platform (computer architecture and/or operating system) other than the one for which they were originally written. Unlike a simulation, which only attempts to reproduce a program's behavior, an emulation attempts to precisely model the state of the device being emulated.

[http://www.wikipedia.org Source: wikipedia]

==Advantages==
Why using an emulator instead of the ''real'' calculator? There are several reasons for this:
* When crashing, you can recover the emulator with the ease of one/two-clicks.
* Sending files is a matter of drag'n'droping the file.
* Test on different calcs.
* Access to powerfull debuging tools.
* Ability to take screenshots.

==TI Emulators==
There are four major emulator's available for the z80-series of calcs.
* [[Emulators:PindurTI|PindurTI]] (also known as PTI)
* [[Emulators:Virtual TI|Virtual TI]] (also known as VTI)
* [[Emulators:TilEm|TilEm]]
* TI Flash Debugger

[[Emulators:PindurTI|PindurTI]] is the latest addition to emulators and has the most accurate emulation of all emulators available. It is however only for Windows at the moment. Linux users can use [[Emulators:TilEm|TilEm]]. [[Emulators:Virtual TI|Virtual TI]] is the oldest and most used emulator at the moment. It has however a lot problems because of incorrect emulation.

Emulators:PindurTI

2006-09-03T03:23:58Z

Gambit: PindurTI moved to Emulators:PindurTI

PindurTI (commonly referred to as PTI) is the latest addition to the TI [[Emulators|emulator]] 'family', still in development by Patai Gergely. This page contains the up-to-date documentation.

==Features==
*Full support for 82 and 83. 83+ support isn't complete yet, but it's already the most accurate of all emulators.
*Raw virtual linking of any number of calculators.
*Built-in (animated) screenshotting ability.
*Debugger.
*Scripting for external tools (preliminary in the latest version), which is already used by [[LateNite]]

If you have ideas you want to incorporate in the tool, you can submit your ideas at the [http://www.hszk.bme.hu/~pg429/pindurti/features/ PindurTI idea box]. Repetitions and trivialities are frowned upon.

==Basics==
PindurTI requires no installation; it is a standalone executable you can put anywhere. It will only create a file called pti.conf in its working directory (which is by default the same as the one the executable is located in), so make sure this directory is not read-only for pindurti.exe.

At the moment of writing PindurTI has no real graphical user interface (GUI) yet, only the absolute minimum required to use all the features. Here are the steps to get going:

1. Start pindurti.exe. You will see any empty, fully cyan window. The four quarters of the window represent four slots where individual calculators can be run.

2. Drag-and-drop a ROM image to one of the quarters, preferably the top left. The quarter chosen will turn grey for the most part, and four icons will appear above the grey area.

3. Left click the grey part. This is the screen of the calculator, and the left click corresponds to the On key.

4. You can drag and drop other ROM images to the other slots. You can switch between the slots by right clicking them. (Left clicking also activates the slot, but it also causes the On key to be pressed.)

5. Files can be sent by dropping them to the appropriate slot. PTI uses silent linking, so the calculator must be on, somewhere in the TI-OS and ''not in receive mode'' in order for the transmission to succeed. You can also drop a group of files, they will be sent one after the other. Naturally, the file and the running ROM image must be for the same model, e.g. sending an 8xp file to a TI-82 won't work.

'''Pressing calculator keys'''

When interpreting keypresses for the calculators, PTI always acts as if the layout was English, so if you use an alternative layout (e.g. AZERTY or Cyrillic), 'Q' still refers to the button next to the Tab key and so on.

{| border="1" cellspacing="0" cellpadding="2"
! PC key !! Calculator key
|-
| left mouse button || On
|-
| A..Z || the button that yields the corresponding letter if alpha is on, see below
|-
| Space || 0
|-
| arrows, 0..9, Enter, '.', ',', numpad +-/* || the corresponding calculator key
|-
| [ || (
|-
| ] || )
|-
| F1 || Y=
|-
| F2 || Window
|-
| F3 || Zoom
|-
| F4 || Trace
|-
| F5 || Graph
|-
| Escape || Mode
|-
| Left Shift || 2nd
|-
| Left Control || Alpha
|-
| Right Shift || Clear
|-
| - || (-) (between the decimal point and Enter)
|-
| = || X,T,θ,''n''
|-
| Page Up || Matrx (82/83) or Apps (83+)
|-
| Page Down || Prgm
|-
| Insert || Vars
|-
| Delete || Del
|-
| Home || Math
|-
| End || Stat
|}

'''Mapping of letter keys'''

{| border="1" cellspacing="0" cellpadding="2"
| '''A''' || Math || '''B''' || Matrx || '''C''' || Prgm ||   ||   ||   ||  
|-
| '''D''' || x-1 || '''E''' || Sin || '''F''' || Cos || '''G''' || Tan || '''H''' || ^
|-
| '''I''' || x2 || '''J''' || , || '''K''' || ( || '''L''' || ) || '''M''' || Ã·
|-
| '''N''' || Log || '''O''' || 7 || '''P''' || 8 || '''Q''' || 9 || '''R''' || Ã—
|-
| '''S''' || Ln || '''T''' || 4 || '''U''' || 5 || '''V''' || 6 || '''W''' || -
|-
| '''X''' || Stoâ†’ || '''Y''' || 1 || '''Z''' || 2 ||   ||   ||   ||  
|}

==Other keys==

{| border="1" cellspacing="0" cellpadding="2"
! Key !! Effect
|-
| Tab || Start crude (9 fps) screenshot/Stop current screenshot
|-
| Alt || Start fine (25 fps) screenshot/Stop current screenshot
|-
| F9 || Reset calculator in active slot (simulates pulling batteries)
|-
| F10 || Open debugger
|-
| F11 || Enable/disable warp mode (fastest possible emulation) of active slot
|}

Note that only crude screenshots are displayed properly everywhere. Fine screenshots are only shown at full speed by Firefox.

==Additional functions==

The icons above each calculator screen can be used for the following purposes by left clicking, from left to right:

1. Pause/unpause

2. Enable/disable warp mode

3. Plug into a link hub; plug in two calculators to open a communication line between them. Connecting more than two calculators is not supported by the TI-OS. However, the CLAP linking library allows mass linking.

4. Toggle inclusion in screenshotting. If no slot is selected, always the active one will be captured. This feature can be used to allow capturing a slot even if we activate another in the meantime (e.g. to save an animated cutscene while using another calculator) or to record multiplayer games.

==Debugger==

The debug window is composed of separate modules, which show the state of the calculator from a certain aspect. Note that the components are tuned to the top left slot by default, and you have to change the slots manually in the layout editor if you want to examine a different slot.

Some keys are global in the debugger, i.e. they will always have the same effect regardless of the module selected. These keys are the following:

{| border="1" cellspacing="0" cellpadding="2"
! Key !! Effect
|-
| F7 || Execute one instruction (or skip to the next interrupt when halted)
|-
| F8 || Step over the next instruction; the same as F7, except that CALL, RST, DJNZ and repeat instructions (e.g. LDIR) are executed until either the program counter hits the subsequent instruction or 10000000 clock cycles elapse
|-
| F12 || Toggle the layout editor
|}

===Layout editor===

This feature is still under development. Most importantly, the modified layouts are not saved. The default layout is designed not to conceal anything if the window is maximised at a resolution of at least 1024x768. The keys are the following:

{| border="1" cellspacing="0" cellpadding="2"
! Key !! Effect
|-
| Insert || Add a component module after the selected one; the type of the component can be picked from a list
|-
| Delete || Delete the subtree starting from the currently selected node
|-
| 0..3 || Set the slot of every node in the subtree starting from the selection to the number pressed (0 - top left, 1 - top right, 2 - bottom left, 3 - bottom right)
|}

===Modules===

'''Disassembly'''

{| border="1" cellspacing="0" cellpadding="2"
! Key !! Effect
|-
| Up/down arrows, Page Up/Down || Navigate
|-
| F2 || Set/remove execution breakpoint at the cursor
|-
| G || Go to a specific address (enter in hexadecimal; press Escape instead of Enter to cancel)
|-
| P, S, B, D, H, X, Y || Go to the address pointed by PC, SP, BC, DE, HL, IX, IY, respectively
|-
| R || Run from cursor, i.e. set PC to the address of the instruction under the cursor
|}

Important: when a breakpoint is set, it affects all the slots at the same time for the time being!

'''Memory view'''

This is currently a read-only view of the 64K CPU address space. You can use the arrows and the page up/down keys to navigate. The G, P, S, B, D, H, X and Y keys have the same effect as on the disassembly pane.

'''Registers'''

The internal state of the Z80. Each value can be edited after left clicking; the values must be entered in hexadecimal. Editing can be concluded with Enter or by clicking elsewhere, and cancelled with Escape. Note that halt can have three values: 0 - normal operation, 1 - halt active, 2 - violating execution protection (if you attempt running any further, the calculator will be forced to reset).

'''Variables'''

A simple, read-only VAT viewer. It can be navigated using the up/down arrows, Page Up/Down and the mouse wheel as well.

'''LCD data'''

Graphical display of the contents of LCD memory. Note that all the 120 columns are shown here, even though all calculators emulated can only display 96. However, the memory is still there. The current X and Y addresses are shown by a bluish colour on the byte that will be accessed through the data port.

'''Key-value modules'''

The following modules are in this category: LCD physics, LCD software, Information, Time, Interrupts, Memory, Keyboard, Link. All of these display a list of characteristics. The right hand sides can be edited where the cursor turns into a hand. Editing can either mean a single click (e.g. interrupt frequencies or keyboard state) or bring up a text box for numeric values, where Escape can be used to cancel as usual.

==Scripting==

It is possible to run the emulator in a non-interactive mode through a pipe (communicating through stdio), just invoke the executable with the -p switch and redirect the input and the output. Do not try to run it with the keyboard on the input or a terminal on the output, because it will hang.

Each command sent must be on a separate line. All of them emit at least a line containing 'OK' as a response in case of success. Error conditions are signaled by outputs starting with 'Error:'.

The commands are the following:

*send-file <slot> <file> - send a file to the specified slot (the same as drag and drop); don't quote the filename, it's read from the first non-space after the slot number till the end of the line (the slot number must be between 0 and 15 or 0x0 and 0xf)

*activate-slot <slot> - select the current slot

*reset-calc - reset the calc in the current slot (you might need to run a few million cc's after this before pressing on)

*run <cycles> - run for the specified number of cycles (it should be a number between 1 and 2000000000); when debugging is enabled and execution stops on a breakpoint, there will be a line starting with 'Info:' output before the usual 'OK'

*step <n> - execute n instructions ignoring the breakpoints, n defaults to 1 when omitted; the firing of a possibly masked timer during a halt counts as one instruction

*draw-screen-bw - dump LCD memory â€” 96*64 bytes, 0 for white and 255 for black; the raw data is preceded by a line that always contains two characters: the first is '1' if the calculator is powered, '0' otherwise, and the second is '1' if the LCD is powered, '0' if it isn't (so the image should be displayed only if this line says '11')

*draw-screen-gs - dump greyscale screen (only updated 25 times per calculator second) â€” 96*64 bytes preceded by the same two-character line, same format but using the full range of values

*key-down <key> - press key (calc key, so the argument is a token like '2nd', 'mode' etc.)

*key-up <key> - release key

<key> must be one of the tokens below:

{| border="1" cellspacing="0" cellpadding="2"
|   || 7 || 6 || 5 || 4 || 3 || 2 || 1 || 0
|-
| 0 ||   ||   ||   ||   || up || right || left || down
|-
| 1 ||   || clear || ^ || / || * || - || + || enter
|-
| 2 ||   || vars || tan || ) || 9 || 6 || 3 || (-)
|-
| 3 || stat || prgm || cos || ( || 8 || 5 || 2 || .
|-
| 4 || x || matrx || sin || , || 7 || 4 || 1 || 0
|-
| 5 || alpha || math || x^-1 || x^2 || log || ln || sto ||  
|-
| 6 || del || mode || 2nd || y= || window || zoom || trace || graph
|}

The on key is called 'on', surprisingly. You can also write 'apps' instead of 'matrx'.

*dump-state <type> - obtain information about the internal state of the emulated hardware; <type> must be one of the following (without quotes): 'lcd physics', 'lcd software', 'model', 'time', 'interrupt', 'pager', 'keyboard', 'link', 'cpu', 'memory'. Except for the last two the format is the following after the initial 'OK': a line containing nothing but the number of subsequent lines, and a 'key: value' pair on each line. With 'cpu' it displays the registers with a 'reg=value' pair on each line, all in hex, while 'memory' is a dump of 65536 bytes as seen in the z80 address space with the current mapping mode

*{set|remove}-breakpoint <type> <args> - add/remove a breakpoint; the arguments depend on the type given; the only type currently supported is 'code' (again, no quotes). It has only one argument: a number specifying the address. It can be base 10, 16 or 8 differentiated by the usual C prefixes. (Actually, this applies to any numeric argument in any command.) For the removal you can also specify -1 here, which removes all code breakpoints.

There is currently no way to directly manipulate the state of the calculator.

==External Resources==
[http://www.hszk.bme.hu/~pg429/pindurti/pindurti.exe Latest build of PindurTI]

[http://users.hszk.bme.hu/~pg429/pindurti/changelog.txt Changelog]

[http://www.hszk.bme.hu/~pg429/pindurti/features/ PindurTI Idea box]
[[Category:Emulators]]

PindurTI

2006-09-03T03:23:58Z

Gambit: PindurTI moved to Emulators:PindurTI: Categorized under Emulators (I hope nobody minds)

#redirect [[Emulators:PindurTI]]

Emulators:PindurTI

2006-09-02T20:15:06Z

Gambit: fixed emulator catagory link

83Plus:Software:usb8x

2006-07-18T16:31:19Z

Gambit: minor typographical error -> language

usb8x is an application for the TI-84 Plus calculators. It combines a low level driver to support the calculator's USB port with a limited selection of device drivers. It is designed with two goals in mind: First, to allow programmers to create external applications/programs that use USB devices without any knowledge of the low-level workings of those devices or the USB port itself. Second, to allow programmers to create additional drivers for other USB hardware not currently supported natively in usb8x.

The current release version of usb8x is 0.09. Download it from its [http://sourceforge.net/projects/usb8x Sourceforge Page].

Additional Documentation:
* [[/Asm_Interface|Assembly language interface]]
* [[/BASIC_Interface|BASIC language interface]]
* [[/Sample_Code|Code Examples]]
* [[/Supported_Devices|Supported Devices]]
* [[/Changelog|Changelog]]
* [[/Error_Codes|Error codes]]

[[Category:83Plus:Software|usb8x]]

83Plus:Hooks:9B7C

2006-06-17T22:31:01Z

Gambit: event 23h

[[Category:83Plus:Hooks:By Address|9B7C - Cursor Hook]] [[Category:83Plus:Hooks:By Name|Cursor Hook]]
== Synopsis ==
'''Name:''' Cursor Hook

'''Hook Pointer Block Address:''' [[83Plus:RAM:9B7C|9B7C]]

'''Hook Enable BCALL:''' [[83Plus:BCALLs:4F60|4F60]]

'''Hook Disable BCALL:''' [[83Plus:BCALLs:4F69|4F69]]

'''Hook Call BCALL:''' [[83Plus:BCALLs:4F57|4F57]]

'''Hook Active Flag:''' [[83Plus:Flags:34#Bit_7|7, (iy + 34h)]]

This hook is called when the edit cursor (the flashing block cursor) is shown or hidden.

== Using the Hook ==
There are three events that are passed for various events, identified when A = 22h, 23h, or 24h. I'm not aware of any event where A < 22h.

* '''A = 22h:''' This is one of the two events that occur before the cursor will be displayed. Returning with the zero flag set will abort the display sequence, but returning with the zero flag reset will cause the sequence to continue. If you want to change the cursor, draw your own one here and return with the zero flag set.
* '''A = 23h:''' I (JasonM) have no clue why this event exists! It is called after event 22h, but before the actual drawing occurs. It's only called if you returned with the zero flag reset for event 22h (basically, if you said you want the cursor to flash.) If you return with zero set, it cancels the flash, otherwise it will draw it's usual cursor. It would appear that the TI-OS just wants to confirm your decision from the first event!
** If event 22h is returned with Z set (i.e. cancel normal cursor), then this event will trigger only if the [[83Plus:Flags:0C#Bit 3|cursor is showing]] and a key is pressed (the ability to check which key is inconclusive, although BC seems to be preserved from event 22h). Here would be a good time to erase an old custom cursor and draw the new one. Return with Z set in this case to cancel the normal action (Z reset will draw the normal large-font cursor).
* '''A = 24h:''' This event is called when the cursor block is about to be replaced with the character underneath it. Returning with the zero flag set will cause this operation to be canceled (the cursor block will be left on the screen.) The character underneath the cursor is passed in B (it's simply a copy of [[83Plus:RAM:844E|curUnder]]), and you should return the character in A. If you want to, you can return any character you like: this will make it appear that the cursor is above a character other than it actually is (note: this doesn't actually edit the text in the edit buffer.) The TI-OS tends to cause redraw errors if you return a character other than in B, so it's probably a good idea to to just return B (make sure you do an "or a" to clear the zero flag, or the cursor won't disappear.)

== Comments ==
Since it will be fired when the user enters most contexts (any context that starts in an edit buffer), it can serve as a useful hook if you want to fire in a particular context after the context is set up. It could also serve as a replacement for a custom interrupt under some situtations.

== Credits and Contributions ==
* '''Michael Vincent:''' Example of hook usage in [http://www.detachedsolutions.com/omnicalc Omnicalc]

Talk:83Plus:BCALLs:4F00

2006-06-13T20:37:04Z

Gambit:

After disassembling some code, does it sound reasonable if this routine is like RecAByteIO (which appears to be bport only) but with code that handles the SE link-assist? [[User:Gambit|Gambit]] 14:58, 10 June 2006 (PDT)
:That seems surprising considering that the entry point existed on pre-SE calculators, but I haven't tried disassembling it yet to check. --[[User:Dan Englender|Dan Englender]] 01:47, 11 June 2006 (PDT)
::Sorry about the Category mixup - I just changed the URL and didn't bother to look at the category bit.
::Assuming I got the keystrokes right, I saw the code reading from [[83Plus:Ports:09|port 09h]], and immediately assumed that the two were related somehow. Of course, I could be wrong, but I felt it was better to submit something than nothing :) ([[Wikipedia:WP:BB|Be bold]]!) [[User:Gambit|Gambit]] 13:37, 13 June 2006 (PDT)

Talk:83Plus:BCALLs:4F00

2006-06-10T21:58:16Z

Gambit: speculation

83Plus:BCALLs:4501

2006-05-04T17:49:31Z

Gambit: Minor formatting details (but improved example), otherwise good :)

== Synopsis ==
'''Official Name:''' PutMap

'''BCALL Address:''' 4501

Outputs a character in the large font at the current cursor location.

=== Inputs ===
* A = TI-ASCII code of character to display

=== Outputs ===
* character at coordinate ([[83Plus:RAM:844B|curRow]], [[83Plus:RAM:844C|curCol]])

=== Destroys ===
* none

== Comments ==
This B_CALL outputs the character stored in A at the current cursor location without changing the cursor. It uses the large font.

== Example ==
Shows É in the upper-left hand corner of the screen:
<nowiki>ld a, LcapEAcute
ld hl, $0000
ld (curRow),hl
B_CALL PutMap</nowiki>

[[Category:83Plus:BCALLs:By Name|PutMap]]
[[Category:83Plus:BCALLs:By Name:Text|PutMap]]
[[Category:83Plus:BCALLs:By Address|4501]]

83:RAM:8039

2006-03-11T23:12:39Z

Gambit: ...

[[Category:83:RAM:By_Address|8039 - OP Registers]] [[Category:83:RAM:By_Name|OP Registers]]
== Synopsis ==
'''Official Name:''' OP Registers

'''Memory Address:''' 8039h

'''Length:''' 66 bytes

In this RAM area the value of op1 to op6 is stored, each "register" getting 11 bytes.

'''OP Equates:'''
<nowiki>OP1 EQU 8039h
OP2 EQU 8044h
OP3 EQU 804Fh
OP4 EQU 805Ah
OP5 EQU 8065h
OP6 EQU 8070h</nowiki>

83:RAM:8E29

2006-03-11T23:12:27Z

Gambit: ...

[[Category:83:RAM:By_Address|8E29 - plotSScreen]] [[Category:83:RAM:By_Name|plotSScreen]]
== Synopsis ==
'''Official Name:''' plotSScreen

'''Memory Address:''' 8E29h

'''Length:''' 768 bytes.

This area of memory stores the contents of the graph screen.

83:RAM:8039

2006-03-02T01:41:21Z

Gambit: Revert - Ban these users too

83:RAM:8E29

2006-03-02T01:40:34Z

Gambit: Are the bots/humans getting smarter?

83:RAM:8E29

2006-02-23T11:21:19Z

Gambit: ...

83:RAM:8039

2006-02-23T11:21:05Z

Gambit: ...

83:RAM:8039

2006-02-22T03:02:09Z

Gambit: Revert...

83Plus:OS:TIOS Alternatives

2006-02-21T14:38:39Z

Gambit: Categorization

[[Category:83Plus:OS Information|TIOS Alternatives]]

{{wikify}}

Here is a list of possible alternatives to TIOS for the TI-83+/83+SE/84+/84+SE:

[http://michaelv.org/programs/calcs/ceptic.php CEPTIC by Michael Vincent]: CEPTIC is an acronym for Control and Execute Program for TI Calculators. ...This version is 83+ SE only, but it shouldn't be too hard to modify to run on the regular 83+ as well. Just remove the extra ports, and modify a few of the flash pages (7Dh...1Dh, et cetera). I'm just happy that I had the ability and knowledge to actually create a working (though non-practical at current) operating system. (Quoted from the linked site.)

[http://pongos.sourceforge.net/ PongOS by FloppusMaximus]: A free, if rather simple, operating system for the TI-83 Plus family of graphing calculators... (Quoted from the linked site.)

[http://brazucs.unitedti.org/vera/ Vera by UnitedTI]: What is Vera, you ask? Vera is the true calc lover's OS. It hasn't been coded yet, but the main idea behind it is that it consists of a very basic kernel that allows for file storage and some hardware control, on top of which other programs or plugins can be built. This approach has been nicked the Core Design Principle. It should make it possible for many people to work on one big project, without making it a huge mess.

If this will turn out to be true is to be found out, because not many z80 projects have been made by more than one person in the history of calculator programming. Vera will be designed for the Ti-83+ at first, and can perhaps later be ported to other "flashable" calculators. (Quoted from the linked site.)

[http://www.ticalc.org/archives/files/fileinfo/349/34973.html CSX by Sean McLaughlin]: CSX is a command line interpreter with an 89'ish layout. It can upload files from a PC (only TiLP has been tested), so it now potentially makes a great way to kill any number of minutes. (Quoted from the linked site.)

Nostalgy by XDG Kat-Productions: Nostalgy is an unofficial group project by certain members of XDG Kat-Productions. There is no working demo at the moment, but sources report that the project is not dead and that development is still slowly underway.

User talk:Saibot84

2006-02-21T14:37:32Z

Gambit:

Hi! Thanks for helping, been a while since I've seen you around anywhere. :) But I'd like to point out a couple things:

1) When you move a page, please go back to the page you moved (redirect=no) and click What Links Here. You need to go through and make sure there aren't any double redirects. MediaWiki only follows redirects once; if a redirect points to a redirect it'll leave you at a page with a link to the proper page. I'm pointing out the OS Alternatives sequence of pages in particular. All I did to fix it was go edit the root page to have an OS: in there as well.

2) Nostalgy is still "live"? News to me. :P Does this mean I should actually try to get the keypad routines working? :) Though I should actually be able to; I had to get a keypad working in AVR assembly in my assembly class last semester so I know pretty much exactly how to tackle it.

Nice to see you around again.

[[User:AndyJ|Andy Janata]] 22:53, 20 Feb 2006 (PST)

Thank you for welcoming me back. Yes, I was gone for a while, I was in a seminary in Germany, but I'm glad to say that there was a little progress with Nostalgy... I finished coding the font routines, some ION/RLE/VRLE compression/decompression routines, some string-displaying routines, and started playing around with trying to use the extra LCD RAM as temporary ram space. Of course, none of these have been tested yet, but at least there is a first draft of them, and knowing my coding abilities, they'll have to be debugged all over the place, but that's beside the point. Unfortunately, I believe I may be the only one with the most parts of the original source, as any uploads have been out-dated for a while. I have all these source parts, but they also need to be integrated into the project as a whole.

Sorry about the Wiki redirect stuff. I'm new to this whole Wiki-thing, it took me a while to figure out how to get it to do what i wanted it to... then i noticed the naming scheme in the Contributing page and tried to move it to the correct location.

BTW, why doesn't TIOS_Alternatives show up in Category:83Plus:OS Information?

[[User:Saibot84|Saibot84]] 06:06, 21 Feb 2006 (PST)

:Whoops, forgot the Category bit at the top. Welcome back. :) [[User:Gambit|Gambit]] 06:37, 21 Feb 2006 (PST)

Category talk:83Plus:BCALLs:By Name

2006-02-18T03:44:04Z

Gambit:

Why are there 180 items in this category and 183 items in the "by address" category?

:Hey, that's only 1.6 percent... not bad! Because the letter Z ([[83Plus:BCALLs:4A65]], [[83Plus:BCALLs:4A68]], [[83Plus:BCALLs:802A]]) does not exist. Administrators? Are we missing anything else? [[User:FloppusMaximus|FloppusMaximus]] 17:37, 7 Dec 2005 (PST)

::It only shows 200 ''items'' per page. This includes subcategories. Click the '''(next 200)''' link. [[User:AndyJ|Andy Janata]] 04:41, 8 Dec 2005 (PST)

:::That makes a lot of sense. Clearly, we have failed to comprehend what "There are X articles in this category" means.
:::Hmm... seems it stops ignoring case when you start moving about (compare [http://wikiti.denglend.net/index.php?title=Category:83Plus:BCALLs:By_Name], [http://wikiti.denglend.net/index.php?title=Category:83Plus:BCALLs:By_Name&until=ZeroToCertificate].) [[User:FloppusMaximus|FloppusMaximus]] 06:25, 8 Dec 2005 (PST)
:::: Ah. Well I changed the category limit to 400 because it was pissing me off --Dan
::::Probably because JMan only hacked the one part of the script. :) [[User:AndyJ|Andy Janata]] 04:46, 12 Dec 2005 (PST)

Is there a list of romcalls that are not officially listed in ti83plus.inc?--[[User:Jim e|Jim e]] 13:36, 13 Feb 2006 (PST)
:Not that I know of, but that wouldn't be a bad idea for another category (or two -- documented and undocumented. I would say by name only to keep category counts down)... [[User:AndyJ|Andy Janata]] 13:44, 13 Feb 2006 (PST)

::I don't see that we need more categories. What we've been doing -- distinguishing on the page itself between "Official" and "Unofficial" names -- should suffice for people who actually care about such things. It might be worth adding a template, perhaps, to say "This routine is documented in the {SDK guide | System Routines Documentation | Silver Edition Addendum | AppGuru | Dan's Undocumented Page}" with an appropriate link. (Speaking of which, [http://web.archive.org/web/*/http://education.ti.com/us/resources/developer/83/download/unsupported.html the last] seems to have been lost in the latest reorganization... Dan, could you put those PDFs back up somewhere?) But anyway, it's worth noting that the official documentation is often misleading and occasionally wrong, so "official" does not necessarily imply "better." [[User:FloppusMaximus|FloppusMaximus]] 14:34, 13 Feb 2006 (PST)
:::I actually don't have the docs in PDF format. I wrote them in .doc format, and TI converted them to PDF. Does anyone have the PDFs? I don't have acrobat, so converting them may be annoying. --Dan
::::I happened to find my wget-ed copy of the PDFs on TI's site ([[User:CalcKing|CalcKing]] might have a copy too) which I d/l after asking for your permission to 'copy them' to WikiTI (I began with [[83Plus:OS:Edit_Buffers]], but never finished the others -_-). How should I send them to you? [[User:Gambit|Gambit]] 19:44, 17 Feb 2006 (PST)

:There's a file I have called romcalls83.txt -- completely misnamed, as it primarily involves Flash, B_CALLs, and the 83+, and is an assembly include file, not plain text -- which has vaguely official-sounding names for a number of undocumented routines, and one-line descriptions for some of them. It runs up through OS 1.13, though it is missing a lot near the end. Its introduction states:
;i've compiled this list of romcalls from several different includes... sometimes trying to match up similarities between
;different calcs. this is what i came up with... there are still romcalls not listed here which are new to the 83+.
;i could not test each romcall individually so the ones i have not tried yet are commented out and due to the fact these
;equates are only my best guess. have fun!
:I honestly don't remember where or when I got it or who wrote it -- it certainly wasn't me, and Google doesn't know it. Perhaps it was on the old TCPA site? Anyway, if its author is still around and gives permission I'll be happy to distribute it, since it's useful information and seems to have vanished off the face of the earth.
:Apart from that... obviously you can see what B_CALL ''addresses'' aren't documented. As far as I know no official names beyond ti83plus.inc (and of course, ti83asm.inc, squish.inc, and ti86*.inc) have ever been published by TI, though some people seem to know more than they're telling... [[User:FloppusMaximus|FloppusMaximus]] 14:16, 13 Feb 2006 (PST)

::Yeah, I believe vortx (a.k.a. Brandon Sterner) compiled that list. In fact, it's hosted on the DS server - would it be OK if I posted a link to it? [[User:Gambit|Gambit]] 15:06, 13 Feb 2006 (PST)

Category talk:83Plus:BCALLs:By Name

2006-02-13T23:06:26Z

Gambit:

Why are there 180 items in this category and 183 items in the "by address" category?

:Hey, that's only 1.6 percent... not bad! Because the letter Z ([[83Plus:BCALLs:4A65]], [[83Plus:BCALLs:4A68]], [[83Plus:BCALLs:802A]]) does not exist. Administrators? Are we missing anything else? [[User:FloppusMaximus|FloppusMaximus]] 17:37, 7 Dec 2005 (PST)

::It only shows 200 ''items'' per page. This includes subcategories. Click the '''(next 200)''' link. [[User:AndyJ|Andy Janata]] 04:41, 8 Dec 2005 (PST)

:::That makes a lot of sense. Clearly, we have failed to comprehend what "There are X articles in this category" means.
:::Hmm... seems it stops ignoring case when you start moving about (compare [http://wikiti.denglend.net/index.php?title=Category:83Plus:BCALLs:By_Name], [http://wikiti.denglend.net/index.php?title=Category:83Plus:BCALLs:By_Name&until=ZeroToCertificate].) [[User:FloppusMaximus|FloppusMaximus]] 06:25, 8 Dec 2005 (PST)
:::: Ah. Well I changed the category limit to 400 because it was pissing me off --Dan
::::Probably because JMan only hacked the one part of the script. :) [[User:AndyJ|Andy Janata]] 04:46, 12 Dec 2005 (PST)

Is there a list of romcalls that are not officially listed in ti83plus.inc?--[[User:Jim e|Jim e]] 13:36, 13 Feb 2006 (PST)
:Not that I know of, but that wouldn't be a bad idea for another category (or two -- documented and undocumented. I would say by name only to keep category counts down)... [[User:AndyJ|Andy Janata]] 13:44, 13 Feb 2006 (PST)

::I don't see that we need more categories. What we've been doing -- distinguishing on the page itself between "Official" and "Unofficial" names -- should suffice for people who actually care about such things. It might be worth adding a template, perhaps, to say "This routine is documented in the {SDK guide | System Routines Documentation | Silver Edition Addendum | AppGuru | Dan's Undocumented Page}" with an appropriate link. (Speaking of which, [http://web.archive.org/web/*/http://education.ti.com/us/resources/developer/83/download/unsupported.html the last] seems to have been lost in the latest reorganization... Dan, could you put those PDFs back up somewhere?) But anyway, it's worth noting that the official documentation is often misleading and occasionally wrong, so "official" does not necessarily imply "better." [[User:FloppusMaximus|FloppusMaximus]] 14:34, 13 Feb 2006 (PST)

:There's a file I have called romcalls83.txt -- completely misnamed, as it primarily involves Flash, B_CALLs, and the 83+, and is an assembly include file, not plain text -- which has vaguely official-sounding names for a number of undocumented routines, and one-line descriptions for some of them. It runs up through OS 1.13, though it is missing a lot near the end. Its introduction states:
;i've compiled this list of romcalls from several different includes... sometimes trying to match up similarities between
;different calcs. this is what i came up with... there are still romcalls not listed here which are new to the 83+.
;i could not test each romcall individually so the ones i have not tried yet are commented out and due to the fact these
;equates are only my best guess. have fun!
:I honestly don't remember where or when I got it or who wrote it -- it certainly wasn't me, and Google doesn't know it. Perhaps it was on the old TCPA site? Anyway, if its author is still around and gives permission I'll be happy to distribute it, since it's useful information and seems to have vanished off the face of the earth.
:Apart from that... obviously you can see what B_CALL ''addresses'' aren't documented. As far as I know no official names beyond ti83plus.inc (and of course, ti83asm.inc, squish.inc, and ti86*.inc) have ever been published by TI, though some people seem to know more than they're telling... [[User:FloppusMaximus|FloppusMaximus]] 14:16, 13 Feb 2006 (PST)

::Yeah, I believe vortx (a.k.a. Brandon Sterner) compiled that list. In fact, it's hosted on the DS server - would it be OK if I posted a link to it? [[User:Gambit|Gambit]] 15:06, 13 Feb 2006 (PST)

Talk:83:RAM:8039

2006-02-13T19:27:18Z

Gambit: Added

Someone should put a list of where each individual OP starts on the page. I'm too lazy to add 11d to 8039h 5 times. ;) Also, should link in each of the OP's here via a redirect.

--[[User:AndyJ|AndyJ]] 12:07, 28 Mar 2005 (PST)

:Done. That wasn't too bad :) [[User:Gambit|Gambit]] 11:27, 13 Feb 2006 (PST)

83:RAM:8039

2006-02-13T19:24:17Z

Gambit: Added individual OP list

83:RAM:8070

2006-02-13T19:20:38Z

Gambit: OP6 Redirect

#REDIRECT [[83:RAM:8039]]

83:RAM:8065

2006-02-13T19:19:08Z

Gambit: OP5 Redirect

#REDIRECT [[83:RAM:8039]]

83:RAM:805A

2006-02-13T19:17:47Z

Gambit: OP4 Redirect

#REDIRECT [[83:RAM:8039]]

83:RAM:804F

2006-02-13T19:16:49Z

Gambit: OP3 Redirect

#REDIRECT [[83:RAM:8039]]

83:RAM:8044

2006-02-13T19:15:10Z

Gambit: Begin redirection!

#REDIRECT [[83:RAM:8039]]

83Plus:Basic:While

2005-12-09T23:11:20Z

Gambit: Removed preceding semicolons

[[Category:83Plus:Basic:Conditionals|While]]
== Synopsis ==
'''Token Size:''' 1 byte

'''Syntax:'''
:While ''condition''
:''command''
:End

The while command is used to execute a command or series of commands when a variable shares a given relationship with another variable or a value. A ''While'' command will continue to execute everything before the next ''End'' until the given condition is no longer met.

== Comments ==
Use of a Goto statement within an While statement will cause an increase in memory allocation, leading to program slowdowns and eventually a MEMORY error. For example, the following code will eventually cause an error:

<nowiki>
Lbl 0
While X=1
X+1->X
Disp X
Goto 0
End</nowiki>

If you must use a Goto within an While statement, it is possible to trick the 83+ into thinking the block ended by jumping to an otherwise unused label that uses an End statement followed by a jump to the proper label. For example, the above program could be rewritten like so:

<nowiki>0->X
Lbl 0
While X=1
X+1->X
Disp X
Goto 2
End
Return

Lbl 2
End
Goto 0</nowiki>

This would avoid the problem by causing the 83+ to terminate the While conditional prior to jumping.

== Examples ==
<nowiki>
While X =/= 105
Getkey -> G
End</nowiki>
Or, if you desire the use of other operators, such as And, Or, or Xor:
<nowiki>
While X=5 and Y=/=3
Input "",A
A+X->Y
End</nowiki>

83Plus:Basic:Graphics:DrawF

2005-12-09T23:10:31Z

Gambit: Removed preceding semicolons

[[Category:83Plus:Basic:Graphics|DrawF]]

== Synopsis ==
'''Token size:''' 1 byte

'''Syntax:''' DrawF ''function''

Draws the given function on the graph screen, regardless of how many Y= variables have been filled.

== Outputs: ==

Given function, as graphed on graph screen.

== Comments ==

*Draws any function specified.
*Input may use any variables used in Y= functions

== Examples ==
To draw the graph of Sin(X)
<nowiki>
ClrDraw
DrawF Sin(x)</nowiki>

To graph a function involving multiple user supplied variables:
<nowiki>
Prompt A,B,C
DrawF Alog(B)+C
Pause</nowiki>

== See also: ==

83Plus:Basic:While

2005-12-09T22:25:16Z

Gambit: nowiki formatting

[[Category:83Plus:Basic:Conditionals|While]]
== Synopsis ==
'''Token Size:''' 1 byte

'''Syntax:'''
:While ''condition''
:''command''
:End

The while command is used to execute a command or series of commands when a variable shares a given relationship with another variable or a value. A ''While'' command will continue to execute everything before the next ''End'' until the given condition is no longer met.

== Comments ==
Use of a Goto statement within an While statement will cause an increase in memory allocation, leading to program slowdowns and eventually a MEMORY error. For example, the following code will eventually cause an error:

<nowiki>
Lbl 0
While X=1
X+1->X
Disp X
Goto 0
End</nowiki>

If you must use a Goto within an While statement, it is possible to trick the 83+ into thinking the block ended by jumping to an otherwise unused label that uses an End statement followed by a jump to the proper label. For example, the above program could be rewritten like so:

<nowiki>0->X
Lbl 0
While X=1
X+1->X
Disp X
Goto 2
End
Return

Lbl 2
End
Goto 0</nowiki>

This would avoid the problem by causing the 83+ to terminate the While conditional prior to jumping.

== Examples ==
<nowiki>
:While X =/= 105
:Getkey -> G
:End</nowiki>
Or, if you desire the use of other operators, such as And, Or, or Xor:
<nowiki>
:While X=5 and Y=/=3
:Input "",A
:A+X->Y
:End</nowiki>

83Plus:Basic:Graphics:DrawF

2005-12-09T22:23:28Z

Gambit: nowiki formatting

[[Category:83Plus:Basic:Graphics|DrawF]]

== Synopsis ==
'''Token size:''' 1 byte

'''Syntax:''' DrawF ''function''

Draws the given function on the graph screen, regardless of how many Y= variables have been filled.

== Outputs: ==

Given function, as graphed on graph screen.

== Comments ==

*Draws any function specified.
*Input may use any variables used in Y= functions

== Examples ==
To draw the graph of Sin(X)
<nowiki>
:ClrDraw
:DrawF Sin(x)</nowiki>

To graph a function involving multiple user supplied variables:
<nowiki>
:Prompt A,B,C
:DrawF Alog(B)+C
:Pause</nowiki>

== See also: ==

83Plus:Hooks:9BC0

2005-10-28T04:16:26Z

Gambit: revert vandalism

[[Category:83Plus:Hooks:By Address|9BC0 - Menu Hook]] [[Category:83Plus:Hooks:By Name|Menu Hook]]
== Synopsis ==
'''Name:''' Menu Hook

'''Hook Pointer Block Address:''' [[83Plus:RAM:9BC0|9BC0]]

'''Hook Enable BCALL:''' [[83Plus:BCALLs:5083|5083]]

'''Hook Disable BCALL:''' [[83Plus:BCALLs:5086|5086]]

'''Hook Call BCALL:''' ''(Unknown)''

'''Hook Active Flag:''' [[83Plus:Flags:36#Bit_6|6, (iy + 36h)]]

The menu hook allows for modification of any of the system menus that are presented through the system monitor.

== Using the Hook ==
This hook, like most, is called for several events, each identified by A. In general, it appears that returning with the zero flag set will cause the OS to execute its normal behavior.

I've ordered the events in the order that they are called by the OS.

* '''A = 04h:''' This is the first event called. B contains the value of the menu about to be displayed. When this event is triggered, [[83Plus:RAM:85DE|MenuCurrent]] currently contains the ID referring to the menu that was previously displayed (if you went from one menu directly to another), or 0 if previously there was no menu displayed (you were seeing the context itself.)
* '''A = 00h:''' This is the second event, called after event 04h. This event allows you to provide your own menu table. B contains the menu ID. If you want to provide your own table, copy it to RAM, point HL to it, and return with the zero flag reset. It's called a second time, but with B being zero. The outputs appear to be the same, so handle it the same way.
* '''A = 02h:''' This event is called before the OS draws the menu header. C is the index of the header (zero based.) Returning with zero set will draw the header, returning with zero reset will cause it to not draw the header. It's also called after it's done drawing the headers, with C is the number of headers (basically, last index plus one). Return flag seems to be ignored.
* '''A = 01h:''' The OS is about to draw the text corresponding to a menu item. The number prefix has already been drawn. C contains the index of the item (zero indexed.) Returning with zero set will cause the OS to draw the string, returning with zero reset will cause it just to draw a blank line (but it does draw something!)
* '''A = 03h:''' The user selected an item from the menu that is about to cause a context switch. B contains the ID of the context the calculator might switch to. You can return with zero set to execute the app, or zero reset to cancel the execution. If you're switching to a flash app (B is cxextapps), then DE also points to the end of the name of the flash app in RAM. You can cancel the execution of a flash app (this could prove useful for a security app.)

83Plus:Basic:Graphics:DrawInv

2005-10-09T04:37:53Z

Gambit: No parentheses in arguments

DrawInv draws the function as if the Y and X values were switched. The following draws the inverse of y=x2:

<nowiki>DrawInv X^2</nowiki>

You should see a parabola starting at (0,0) moving off to the right.

Also you can use equations instead of strings. The following draws the inverse of the equation in Y1:
<nowiki>DrawInv Y1</nowiki>

You can access the equation variables by hitting [Vars], [Right] to Y-Vars, and finally to Functions.

83Plus:Basic:Graphics:DrawInv

2005-10-09T04:29:07Z

Gambit: All it needed was a few little tweaks :-)

DrawInv draws the function as if the Y and X values were switched. The following draws the inverse of y=x2:

<nowiki>DrawInv("X^2")</nowiki>

You should see a parabola starting at (0,0) moving off to the right.

Also you can use equations instead of strings. The following draws the inverse of the equation in Y1:
<nowiki>DrawInv(Y1)</nowiki>

You can access the equation variables by hitting [Vars], [Right] to Y-Vars, and finally to Functions.

83Plus:OS:ByROMPage

2005-09-13T18:39:47Z

Gambit: Got bored and added some information - the table might need work...

[[Category:83Plus:OS Information|ROM Page 1B]]

This page contains at the start a list of 3-byte vectors for ROM calls. This is then used by the B_CALL routine to determine what address on what page each ROM call resides. This is page 1B for the TI-83 Plus, 3B for the TI-84 Plus and 7B for the TI-83 Plus Silver Edition & the TI-84 Plus Silver Edition.

==Structure==

Each 3-byte vector contains an address and a page number. The address comes first, stored in little-endian format, followed by the page number.
{| border="1" cellspacing="0" cellpadding="2"
|+Example Vector Table
|-
! Address !! Common Name !! LSB Addr. Ptr. !! MSB Addr. Ptr. !! Page Number
|-
! 4000
| [[83Plus:BCALLs:4000|JErrorNo]] || C7 || 25 || 00
|-
! 4003
| [[83Plus:BCALLs:4003|FontHook]] || A3 || 77 || 7B
|-
! 4006
| [[83Plus:BCALLs:4006|LocalizeHook]] || 44 || 77 || 7B
|}
''Note: The preceding values were obtained from TI-OS v1.15. Values on other OSs are most likely to differ.''

In this manner, TI can change the address pointer and page of the actual routine on a different OS version (e.g. they needed to update a section of code) and the B_CALL routine would still point to the correct page and address.

==See Also==
* [[83Plus:OS:How BCALLs work|How BCALLs work]]

83Plus:OS:ByROMPage

2005-09-10T17:02:13Z

Gambit: Confirmed 83P, moved, and fixed category

[[Category:83Plus:OS Information|ROM Page 1B]]
{{stub}}

This page contains at the start a list of 3-byte vectors for ROM calls.

==Structure==

''to do''

Talk:83Plus:OS:Edit Buffers

2005-07-11T23:49:44Z

Gambit: Link to PDF

This information was from Dan Englender's [http://education.ti.com/downloads/pdf/us/editbuf.pdf editbuf.pdf] file findable at TI's [http://education.ti.com/us/resources/developer/83/download/unsupported.html Unsupported Documentation] page. [[User:Gambit|Gambit]] 16:49, 11 Jul 2005 (PDT)

83Plus:OS:Edit Buffers

2005-07-11T23:23:58Z

Gambit: "Wikified" Dan's PDF on TI's Unsupported Page

[[Category:83Plus:OS Information|Edit Buffers]]
== Introduction ==
The edit buffer is used to easily edit the contents of a variable on the calculator. Without the edit buffer, every time you needed to grow or shrink a variable, you would have to use InsertMem or DelMem, and then update the size bytes. For a variable that is constantly changing size, ie. one thatâ€™s currently having data inputted into it, this is a waste of time for both the CPU and the programmer. The edit buffer solves this problem.

When a variable is edited, all of available RAM is inserted into it. That way, all the other variables in RAM only have to be moved around twice (once when the edit buffer is opened, and once when itâ€™s closed), instead of every time a byte needs to be added or removed from the variable. However, this also means that while an edit buffer is open, the application canâ€™t allocate any other memory. This means no creating or resizing other programs, and no pushing to or popping from the floating point stack.

== Opening an Edit Buffer ==
This example assumes the type of variable youâ€™re opening in the edit buffer is a program. To edit a currently empty program, use the [[83Plus:BCALLs:4969|SetEmptyEditPtr]] entry point. If you need to edit a program that already has data in it, use some code like this:

<nowiki>SetupEditStuff:
ld hl,progname
rst rMov9ToOP1
B_CALL EditProg
set editOpen,(iy+editFlags) ;Editor is running
ld hl,(iMathPtr1)
inc hl
inc hl
ld (editTop),hl ;Top of edit session
push hl
ld hl,(iMathPtr2)
ld (editCursor),hl
push hl
ex de,hl
ld hl,(iMathPtr3)
B_CALL CpHLDE
jr nc,SetupEditProgSwapSkip
ex de,hl
SetupEditProgSwapSkip:
ld (editBtm),hl
ld (editTail),hl
pop hl
pop de
or a
sbc hl,de
ret z
ld c,l
ld b,h
ld hl,(editCursor)
dec hl
ld de,(editTail)
dec de
lddr
inc hl
ld (editCursor),hl
inc de
ld (editTail),de
ret</nowiki>

== Edit Buffer Variables ==
The edit buffer uses four memory variables to keep track of data in the edit buffer:

[[83Plus:RAM:96F4|editTop]]
:Holds a pointer to the beginning of the edit buffer. This will be directly after the size bytes for the variable. The value in editTop does not change during the course of the edit session.

[[83Plus:RAM:96F6|editCursor]]
:Holds a pointer to the equivilant location in the edit buffer for the on-screen cursor. The data between editTop and editCursor is all the data to the left of the cursor. The value in editCursor is variable and depends on how much data is to the left of the cursor.

[[83Plus:RAM:96F8|editTail]]
:Holds a pointer to the all the data thatâ€™s after the cursor. This data fills the area between editTail and editBtm. The area between editCursor and editTail is the free space for data to grow into.

[[83Plus:RAM:96FA|editBtm]]
:Holds a pointer to the end of the edit buffer. The value in editBtm is constant and doesnâ€™t change during the edit session.

== Navigating the Edit Buffer ==
Luckily, you donâ€™t have to modify the above variables manually; there are entry points provided to help navigate through the edit buffer.

[[83Plus:BCALLs:4936|BufClear]]
:Clears all the data in the edit buffer.

[[83Plus:BCALLs:4912|BufDelete]]
:Deletes the current token from the edit buffer.

[[83Plus:BCALLs:4909|BufInsert]]
:Inserts a token into the edit buffer, before the current character.

[[83Plus:BCALLs:4903|BufLeft]]
:Moves the edit pointers to the left.

[[83Plus:BCALLs:490F|BufReplace]]
:Replaces the current token in the edit buffer.

[[83Plus:BCALLs:4906|BufRight]]
:Moves the edit pointers to the right.

[[83Plus:BCALLs:4933|IsAtBtm]]
:Check if the cursor is at the bottom of the edit buffer.

[[83Plus:BCALLs:4930|IsAtTop]]
:Check if the cursor is at the top of the edit buffer.

== Closing an Edit Session ==
To close an edit session, use CloseEditEqu. You will probably want to close the edit session as soon as you are done with it, but in any case, it needs to be closed before the app returns to the OS. If you are using GetKey while the edit buffer is open, this means you will you will need to use Put Away notification to close the edit buffer before returning to the OS.

Help:Contents

2005-05-24T05:51:44Z

Gambit: Dan_E's question :)

For further information/syntax, please refer to [[wikipedia:Help:Contents|Wikipedia's Help System]].
== Frequently Asked Questions ==
=== Registering ===
; How do I register/login?
: In the upper-right hand corner of the screen, select [[Special:Userlogin|Create a user or login]].
; Do I need to provide my real name?
: No, it is a matter of personal preference/privacy to provide your real name.
; Can I change it later?
: Yes, once you login, you can change your password, real name, and e-mail address.

=== Getting Started ===
; Ok, I've logged in<nowiki>:</nowiki> how do I make a new page?
: Type the name in the Goto box on the left-hand side of the screen; see [[Contributing|Contributing Guidelines]] for the syntax. As an example, if you want to add documentation for RAM address FFFF on the 83+, type the following in the Goto box:
<nowiki>83Plus:RAM:FFFF</nowiki>
:Make sure you read the [[Contributing|Contributing Guidelines]]!!!
;Do I need to denote hexadecimal with a $ or h, like in Z80 assembly?
:No, it is assumed in WikiTI that all numbers/addresses are hexidecimal by default.
;What are templates?
:Templates, are, as the name says, templates. :-) They provide a default structure for the various pages. If all the WikiTI users follow these templates, it'll make all B_CALL pages look consistent, all ports the same format, etc. Thus, it is encouraged to use these (see [[ Contributing#Templates|Templates]] for a list of templates).
; How do I use a template?
* Select a template
* View the source and copy it (the ''View source'' tab is near the top of the screen (this is NOT the same as telling your browser you'd like to view the HTML source of the page; this shows you the wiki source))
* Paste the source into your new page (that you just Goto'ed)
* Edit the text to fit your type of documentation
; What's the category text at the top of the templates for?
: That is how WikiTI categorizes the various pages. Following the previous example, you should have these lines at the top of your new page:
<nowiki>[[Category:83Plus:RAM:By Address:FFFF - TheName]]
[Category:83Plus:RAM:By Name|TheName]</nowiki>
:If you are curious as to how a page works, don't forget to view the source of it :-)
;Can we only contribute undocumented information on the TI-OS?
:Absolutely not. You can contribute whatever you like, because in the end, we'd like WikiTi to become a complete reference. However, just make sure that you don't copy/paste other people's copyrighted documentation into the wiki unless you have permission to do so from the copyright holder.

=== Editing ===
; How do I make bold/italicized text?
: See [[wikipedia:Wikipedia:How_to_edit_a_page#Character_formatting|Character Formatting]].
; How do I make lists?
: See [[wikipedia:Wikipedia:How_to_edit_a_page#Sections.2C_paragraphs.2C_lists_and_lines|Lists and Lines]].
; Argh! The tab doesn't work!
: In Wikipedia, you use a colon : to indent a paragraph.
; How do I put text in that blue border?
: Use <nowiki> preceded with a space. The leading space tells the Wiki parser to display the text as a preformatted, fixed-width font, which is analogous to <pre> in HTML. So " <nowiki>Your text here</nowiki>" will show:
<nowiki>Your text here</nowiki>
; How do I make links?
: That depends on the kind of link you want to make. See [[wikipedia:Wikipedia:How_to_edit_a_page#Links_and_URLs|Links and URLs]] for a more in-depth discussion.
; Is there a way I can get it to wrap at the end of the window, and yet still have a line break when I put a line break in the text?
: Yes, there are two ways to do that:
:# Put two line breaks in to get one on the page; or
:# Manually use 

=== Browsing ===
;Why does my contribution not show up in the list?
:Most likely, you are viewing a cached version of WikiTI. Try clearing out your cache (browser-specific). Alternatively, you may wish to disable caching in your preferences. If you do have any issues that appear to be cache-related, please contact [[User:JasonM|JasonM]].

== Tips & Hints ==
* Use the Preview Button to view your changes before you Save.
* Mark minor changes as Minor Edits (see [[wikipedia:Wikipedia:How_to_edit_a_page#Minor_edits|Minor Edits]] as to what constitutes a Minor Edit).

As stated up above, please consult [[wikipedia:Help:Contents|Wikipedia's Help system]] for more information.

83Plus:BCALLs:45BE

2005-04-08T07:09:29Z

Gambit: Fixed Category:Util->Utility

[[Category:83Plus:BCALLs:By Name:Utility|CursorOff]] [[Category:83Plus:BCALLs:By Name|CursorOff]] [[Category:83Plus:BCALLs:By Address|45BE - CursorOff]]
== Synopsis ==
'''Official Name:''' CursorOff

'''BCALL Address:''' 45BE

Removes the cursor from the display and stops it from reappearing until [[83Plus:BCALLs:45C4|CursorOn]] is called.

=== Inputs ===
* none

=== Outputs ===
* curAble,(iy+curFlags) reset
* curOn,(iy+curFlags) reset
* [[83Plus:RAM:844A|curTime]]: 32h

=== Registers Destroyed ===
* All

== Comments ==

Help talk:Contents

2005-04-04T01:24:35Z

Gambit: Added headings

= Discussion =
What do you think?

== FAQ Started ==
Here is a little something that I wrote up. Hopefully, it'll answer many of a newbie's questions. If there are more, I guess you should ask in #WikiTI and hope that somebody answers and updates this FAQ. [[User:Gambit|Gambit]] 17:02, 3 Apr 2005 (PDT)

83Plus:BCALLs:4159

2005-04-04T01:20:39Z

Gambit:

[[Category:83Plus:BCALLs:By Name|Mov11B]]
[[Category:83Plus:BCALLs:By Name:Memory|Mov11B]]
[[Category:83Plus:BCALLs:By Address|4159 - Mov11B]]
== Synopsis ==
'''Official Name:''' Mov11B

'''BCALL Address:''' 4159

Copies an 11 byte memory block from source to destination.

=== Inputs ===
* HL: start of source block
* DE: start of destination block

=== Outputs ===
* 11 byte block starting at original HL copied to original DE

=== Destroys ===
* BC DE HL

== Comments ==
This B_CALL is similar to all the other MovXB ones out there. For some reason, TI didn't document this one.

== Example ==
Move 11 bytes from [[83Plus:RAM:8478|OP1]] to [[83Plus:RAM:9872|appBackUpScreen]]
<nowiki>ld hl,OP1
ld de,appBackUpScreen
B_CALL Mov11B</nowiki>

Help talk:Contents

2005-04-04T00:02:54Z

Gambit: FAQ Started

Here is a little something that I wrote up. Hopefully, it'll answer many of a newbie's questions. If there are more, I guess you should ask in #wikiti and hope that somebody answers and updates this FAQ. [[User:Gambit|Gambit]] 17:02, 3 Apr 2005 (PDT)

Help:Contents

2005-04-03T21:58:14Z

Gambit: Changed numbered lists to bulleted

For further information/syntax, please refer to [http://en.wikipedia.org/wiki/Help:Contents Wikipedia's Help system].

== FAQ ==
=== Registering ===
* '''How do I register/login?'''
** In the upper-right hand corner of the screen, select [[Special:Userlogin| Create a user or login]].
* '''Do I need to provide my real name?'''
** No, it is a matter of personal preference/privacy to provide your real name.
* '''Can I change it later?'''
** Yes, once you login, you can change your password, real name, and e-mail address.

=== Getting Started ===
* '''Ok, I've logged in: how do I make a new page?'''
** Type the name in the Goto box on the left-hand side of the screen; see [[Contributing| Contributing Guidelines]] for the syntax. As an example, if you want to add documentation for RAM address FFFF on the 83+, type the following in the Goto box:
<nowiki>83Plus:RAM:FFFF</nowiki>
* '''Do I need to denote hexadecimal with a $ or h, like in Z80 assembly?'''
** No, it is assumed in WikiTI that all numbers/addresses are hexidecimal by default.
* '''What are templates?'''
** Templates, are, as the name says, templates :) They provide a default structure for the various pages. If all the WikiTI users follow these templates, it'll make all B_CALL pages look consistent, all ports the same format, etc. Thus, it is encouraged to use these (see [[ Contributing#Templates| Templates]] for a list of templates).
* '''How do I use a template?'''
** Select a template
** View the source and copy it (the edit tab is near the top of the screen)
** Paste the source into your new page (that you just Goto'ed)
** Edit the text to fit your type of documentation
* '''What's the category text at the top of the templates for?'''
** That is how WikiTI categorizes the various pages. Following the previous example, you should have these lines at the top of your new page:
<nowiki>[Category:83Plus:RAM:By Address:FFFF - TheName]
[Category:83Plus:RAM:By Name|TheName]</nowiki>

If you are curious as to how a page works, don't forget to view the source of it :-)

=== Editing ===
* '''How do I make bold/italicized text?'''
** See [http://en.wikipedia.org/wiki/Wikipedia:How_to_edit_a_page#Character_formatting Character Formatting]
* '''How do I make lists?'''
** See [http://en.wikipedia.org/wiki/Wikipedia:How_to_edit_a_page#Sections.2C_paragraphs.2C_lists_and_lines Lists and Lines]
* '''Argh! The tab doesn't work!'''
** In Wikipedia, you use a colon : to indent a paragraph.
* '''How do I put text in that blue border?'''
** Use <nowiki> preceded with a space. The leading space tells the Wiki parser to display the text as a preformatted, fixed-width font, which is analogous to <pre> in HTML. So " <nowiki>Your text here</nowiki></nowiki>" will show:
<nowiki>Your text here</nowiki>
* '''How do I make links?'''
** That depends on the kind of link you want to make. See [http://en.wikipedia.org/wiki/Wikipedia:How_to_edit_a_page#Links_and_URLs Links and URLs] for a more in-depth discussion.

=== Recent Changes ===
None at this time

=== Browsing ===
* '''Why does my contribution not show up in the list?'''
** Most likely, you are viewing a cached version of WikiTI. Try clearing out your cache (browser-specific). Alternatively, you may wish to disable caching in your preferences.

=== Advanced ===
None at this time

== Tips && Hints ==
* Use the Preview Button to view your changes before you Save.
* Mark minor changes as Minor Edits (see [http://en.wikipedia.org/wiki/Wikipedia:How_to_edit_a_page#Minor_edits Minor Edits] as to what constitutes a Minor Edit).

As stated up above, please consult [http://en.wikipedia.org/wiki/Help:Contents Wikipedia's Help system] for more information.