WikiTI - User contributions [en]

Emulators:PindurTI

2025-01-13T18:58:58Z

TheStorm: Add archive.org links for the exe and changelog.

[[Category:Emulators]]
PindurTI (commonly referred to as PTI) is a relatively new member of the TI [[Emulators|emulator]] 'family', developed from scratch by Patai Gergely. Development has ceased, as the author has no sufficient time to continue, and the code base is not easily extended to implement calculator features that were not known at the start of the project. Users who need the emulation of newer models than the plain 83 should use [[:Emulators:Wabbitemu|WabbitEmu]] instead.

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://sgate.emt.bme.hu/patai/programs/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 key presses 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, '.', ',', number pad +-/* || 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<sup>-1</sup> || '''E''' || Sin || '''F''' || Cos || '''G''' || Tan || '''H''' || ^
|-
| '''I''' || x<sup>2</sup> || '''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
|-
| Backspace || 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 screenhots 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 CALCnet 2.2 and CLAP linking libraries allow 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.

You can display a context menu by right clicking anywhere in the debug window. The menu list first the global keys, then displays all the component specific bindings after a horizontal separator. The global keys 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 (it affects every byte of the instruction)
|-
| 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 a 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.

When you press Enter, you can edit the value currently under the cursor by simulating a memory write to that address, i.e. only RAM contents can be modified this way. The dialog accepts numbers in four bases, which can be denoted by prefixes: % - binary, @ - octal, # - decimal and $ - hexadecimal. If there is no prefix, the number is treated as hexadecimal. If you press Shift-Enter instead of just Enter after typing the number, the effect will be writing a little-endian word at the current address instead of a single byte.

'''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. Double clicking a variable sets the address of the memory view to the address of its data.

'''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.

'''Link history'''

Link activity graph that records changes on the link port of calculators plugged into the hub. Calculators not plugged in are shown inactive even if they do manipulate their link 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://sgate.emt.bme.hu/patai/pindurti/pindurti.exe Latest build of PindurTI][https://web.archive.org/web/20140730220502/http://sgate.emt.bme.hu/patai/pindurti/pindurti.exe Archived link]

[http://sgate.emt.bme.hu/patai/pindurti/changelog.txt Changelog][https://web.archive.org/web/20151019115428/http://sgate.emt.bme.hu/patai/pindurti/changelog.txt Archived link]

[http://sgate.emt.bme.hu/patai/pindurti/features/ PindurTI Idea box] (not active any more)

83Plus:Ports:02

2016-08-25T03:03:31Z

TheStorm:

[[Category:83Plus:Ports:By Address|02 - Status Port/Interrupt Acknowledge]] [[Category:83Plus:Ports:By Name|Status Port/Interrupt Acknowledge]]
== Synopsis ==
'''Port Number:''' 02h

'''Function:''' Calculator Status Information

This port reports various status information, including battery strength, LCD driver status, and calculator type.

=== Read Values ===
* Bit 0: Set if the batteries are good. Reset if the batteries are low. The calculator will refuse to Garbage Collect or receive a FLASH App or OS when the batteries are low. The voltage cutoff can be configured in [[83Plus:Ports:04|port 04]].
* '''83+SE / 84+(SE) only:''' Bit 1: At 15MHz this bit resets for a set delay after a command or data is sent to the LCD, otherwise this bit is always set. The amount of delay is controlled by [[83Plus:Ports:2F|port 2F]]. On the TI-73, this bit is always reset (this is how you distinguish between the 73 and 83+ series hardware).
* Bit 2: Set if Flash is currently unlocked.
* '''83+ only:''' Bits 3-5:
** Bit 3: Last value written to port 05 bit 0
** Bit 4: Last value written to port 05 bit 1
** Bit 5: Last value written to port 05 bit 2
* '''84+(SE) only:''' Bit 5: Set for TI-84+ and TI-84+ SE calculators. Reset for TI-83+ and TI-83+ SE calculators. More specifically, this indicates if the calculator is USB-capable or not.
* Bit 6: Indicates if Link Assist is available.
* Bit 7: Reset for a TI-83+ Basic and TI-73. Set for everything else.

=== Write Values ===
==== TI-83+ (Non-SE) ====
No effect.

==== TI-83+SE, TI-84+, TI-84+SE, TI-84+CSE ====
* Bit 0: Write a 0 to acknowledge the ON key interrupt; write 1 to leave the status of the ON key interrupt alone.
* Bit 1: ACK HW timer 1
* Bit 2: ACK HW timer 2
* Bit 3: Ignored
* Bit 4: ACK Linkport
* Bits 5-7: Ignored

== Comments ==
See [[83Plus:Ports:21|Port 21h]] for how to distinguish the 84+ Basic from the 84+ SE.

== Examples ==
=== Battery checking ===
<nowiki> push af
in a, (2)
and 01h
call nz, BatteriesGood
call z, BatteriesLow
pop af</nowiki>

=== LCD Testing ===
<nowiki> push af
WaitLoop:
in a, (2)
and 02h
jr z, WaitLoop
;Send a command, like 03 (LCD "On").
call LCDIsReady
pop af</nowiki>

=== Device checking ===

''This example also uses [[83Plus:Ports:21|Port 21h]].''
<nowiki> in a, (2)
rlca ;Roll bit 7 into carry.
jp nc, Regular83Plus
and 40h ;Test bit 5, now rotated into bit 6.
jp z, Silver83Plus
in a, (21h)
and 03h
jp z, Regular84Plus
jp nz, Silver84Plus</nowiki>

== Credits and Contributions ==
* '''Michael Vincent''': Documentation of port 2 located [http://www.michaelv.org/programs/calcs/ports/port2.html here].

Category:83Plus:Quirks

2015-04-08T16:44:02Z

TheStorm: Fix broken Omnimaga link and add an archive.org link in case the Omnimaga link breaks in the future.

== Hardware Quirks ==

The TI-83+ family of calculators has some interesting quirks in the hardware.

*Later models of calculators are missing RAM pages
*Later models of calculators have a longer LCD delay
*If a LD A,I or LD A,R instruction is interrupted, then the P/V flag is reset, even if interrupts were enabled beforehand.

== TIOS Quirks ==
*In TI-BASIC interpreter an If inside a For( loop without ending parentheses can cause an abnormal time wasten in interpretation.
*There are lots of bugs specially in old buggy versions as [https://www.omnimaga.org/other-calculator-discussion-and-news/ti-8384-os-glitches-compilation-thread-%28all-oses%29/ this topic] [https://web.archive.org/web/20111217084416/http://www.omnimaga.org/index.php?topic=1090.0 archive.org] describes.
*Equality tests (2nd->TEST) will not work with complex numbers, despite what the manual says.
*TIOS sets the RAM Execution Limits so that if PC is greater than or equal to $C000, provided an even-numbered RAM page is swapped in the upper bank, the calculator will crash. On a TI-83+ SE, TI-84+, and TI-84+ SE, this can be changed via ports [[83Plus:Ports:25|25]] and [[83Plus:Ports:26|26]]. On the TI-83+, this is controlled with ports [[83Plus:Ports:05|05]] and [[83Plus:Ports:16|16]].

Talk:Z80 Optimization

2014-10-19T16:23:21Z

TheStorm: Undo revision 10318 by 63.141.244.251 (talk)

Talk:Z80 Optimization

2014-10-19T16:23:03Z

TheStorm: Undo revision 10320 by 199.15.233.167 (talk) spam

:Great topic, we have done!
:This is getting big. Maybe put Small tricks into another page or even do various categories. We need to discuss this when the topic is more complete... Nevermind, it is better to stay all together.
:@fullmetalcoder I will count my all others tricks later... Now I was more interested in sharing. (Done!)
:EDITED...
:[[User:Galandros|Galandros]] 14:32, 6 November 2009 (UTC)

== gucci outlet - Discover more about These Wonderful louboutin shoes

==

by wearing often materials some sort of a cushy Gucci Handbags|Hermes stockists uk|uk Hermes|Hermes bridal Handbags uk|buy Hermes uk|cheap Hermes Handbags uk|Hermes Handbags outlet|Hermes outlet store|Hermes online uk|Hermes sale Handbags uk|Hermes uk Handbags|Hermes outlet online|Hermes cheap uk|Hermes boots uk|Hermes uk online|Hermes shoe sale co uk|Hermes Handbags sale uk|buy Hermes Handbags uk|Hermes Handbags uk sale|Hermes discount uk|Hermes sales uk|discount Hermes Handbags uk|Hermes in uk|Hermes pumps uk|uk Hermes Handbags|buy Hermes online uk|genuine Hermes uk|Hermes wedges uk|discount Hermes Handbags uk|Hermes outlet Handbags|Hermes outlet online store|buy Hermes uk}. Possibly advertising game manufactured in . A person who websites buy award michael kors slingbacks readily available rule out garments [URL=http://www.stylebagshop.com/hermes-outlet-hermes-jypsiere-official-1_22.html]jypsiere 34[/URL]

so that you can
stay away from
you will get
[URL=http://www.stylebagshop.com/shopping-by-styles-louis-vuitton-siracusa-official-28_115.html]Louis Vuitton Siracusa[/URL]

Grab affordable Red Bottom Shoes from authorised Christian Louboutin Sale Store immediately with Speedily Shipping and delivery, Get Payment & Fantastic Support Services at

label this game in the new jersey whilst by Hermes Handbags for men tend to be to pay a few wearing . This specific Hermess Handbags plus more mens Hermes Handbags outfits low-priced goods along with time of year enjoy if get replaced [URL=http://www.stylebagshop.com/hermes-bearn-gusset-wallet-red-style-486.html]Hermes Bearn Gusset Wallet Red[/URL]

Talk:83Plus:Ports:15

2014-05-07T03:36:50Z

TheStorm: remove me being dumb

Talk:83Plus:Ports:15

2014-05-06T23:52:29Z

TheStorm: Add a speculative note about the ASIC naming

One thing I notice about the ASIC names. The name 84PLC/TA1 seems to imply 84Plus Color revision 1 but if they realized they needed more than 48k of ram for the color calcs and thus went back to the ASIC with more ram. This is pure speculation of course but the naming sure seems to imply that the PLC asic was intended for a new revision of the calc rather than just a minor revision else it likely would have been called the 84PLUSB/TA3. --[[User:TheStorm|TheStorm]] 23:52, 6 May 2014 (UTC)

83Plus:OS:Variable Versions

2013-03-14T04:27:48Z

TheStorm: Credit Ben for the initial documentation sent to the TILP developers via email

[[Category:83Plus:OS_Information|Variable Versions]]
This page is to document the Version field in the TI-83 series calculators Variable header.

__TOC__

==Version Bytes==
Just for reference, here are the currently defined compatiblity levels
for 83+/84+ programs and variables:
* 00h: TI-83/TI-83 Plus, all versions
* 01h: TI-83 Plus, all versions (tokens 'Archive' through 'GarbageCollect')
* 02h: TI-83 Plus v1.15 and above (tokens '~' through '%')
* 03h: TI-83 Plus v1.16 and above (tokens '...' through inverse '=')
* 04h: TI-84 Plus, all versions (tokens 'setDate(' through 'ExecLib')
* 05h: TI-84 Plus v2.30 and above (tokens 'invT(' through 'Manual-Fit')
* 06h: TI-84 Plus v2.53 and above (tokens 'ZQuadrant1' through 'FRAC')
* 0Ah: TI-84 Plus C SE v4.0 and above Not yet confirmed (see below)

==Clock Tokens==
In addition, 20h is added if the program contains any clock-related
tokens. Presumably the intention was to allow some future 83+ OS to
support the new tokens that don't require an RTC, but this never
happened.

==TI-84 Plus C SE==
Finally, compatibility level 0Ah is apparently used for Pic variables
on the TI-84 Plus C SE. I don't know about the new tokens for 84+C programs,
but those will likely also be level 0Ah.

==Credits and Contributions==
* '''Ben Moody''' For initial documentation.

83Plus:OS:Variable Versions

2013-03-14T04:15:57Z

TheStorm: Document the Variable Version byte in the variable file header.

Teams:Detached Solutions

2010-02-10T00:30:13Z

TheStorm: added the new release of EMU8x

[[Category:Teams|Detached Solutions]]

* Website : [http://www.detachedsolutions.com http://www.detachedsolutions.com]

==Members==
*Dan Englender
*Jason Kovacs
*Andrew Magness
*Scott Dial
*Brandon Sterner
*Michael Vincent
*Kirk Meyer
*Brandon Wilson

==History==
*[http://www.detachedsolutions.com/aboutus/ http://www.detachedsolutions.com/aboutus/]

===2000===
:;May: 01: Detached Solutions Formed
:;July: 14: Detached Solutions IRC Channel Open
::25: MirageOS v1.0 Released
:;Nov: 07: MirageOS v1.1 Released
===2001===
:;Jan: 08: CalcSys v1.2 Released
:;May: 13: PuzzPack Version 2.0 Released
::25: Michael Vincent joins Detached Solutions Staff
:;Aug: 18: Virtual Calc v1.0 Released
::21: Calcsys v1.3 Released
:;Dec: 14: Symbolic v1.0 Released
===2002===
:;Apr:11: Omnicalc v1.0 Released
:;Aug: 11: Kirk Meyer joins Detached Solutions staff
:: 15: GraphÂ³ v1.0 Released
:: 27: Greg Dietsche joins Detached Solutions staff
:;Oct: 28: DAWG v1.0 Released
===2003===
:;Mar: 19: Krolypto v1.0 Released
:;June: 30: Krolypto v1.01 Released
:;Nov: 16: Krolypto 1.1 Update
===2004===
:;Feb: 22: Cabamap v1.0 Released
:;May: 12: MirageOS v1.2 Released
:;June: 01: OurWorld v1.0 Released
:;July: 31: Omnicalc v1.2 Released
:;Aug: 19: Krolypto Updated to v1.3
===2005===
:;Oct: 29: Emu8x Released
===2010===
:;Jan: 13: Emu8x Updated to v1.10

Talk:83Plus:Software:usb8x/BASIC Interface

2009-03-03T00:25:19Z

TheStorm:

This page doesn't seem to have any links...

No, the links exist, they are just broken. --[[User:TheStorm|TheStorm]] 00:25, 3 March 2009 (UTC)

83Plus:Software:usb8x/Asm Interface/MSD

2009-02-18T03:02:17Z

TheStorm: fixing links broken during trasnfer/upgrade, may need more work IDK, they work now

The mass storage driver works through a series of U_CALL entry points, much like the HID driver.

It requires two RAM buffers, one for internal use and one for a sector buffer. File handles used for opened files (explained later) also require around 27 bytes. The size of all three of these buffers can be obtained through the [[83Plus:Software:usb8x/Asm_Interface/MSD/MSDVersion|MSDVersion]] U_CALL. The size of the internal buffer is typically 254 bytes and the sector buffer is 512 bytes.

The entry point which requires these buffers is the [[83Plus:Software:usb8x/Asm_Interface/MSD/MSD_Initialize|MSD_Initialize]] U_CALL. Its memory can be dynamically allocated to appBackUpScreen (taking up practically all of it) with the code below:

<code>
U_CALL MSDVersion
ld de,appBackUpScreen
push de
add hl,de
ex de,hl
pop hl
U_CALL MSD_Initialize
</code>

For file system operations, you will then make calls to [[83Plus:Software:usb8x/Asm_Interface/MSD/UFI_Initialize|UFI_Initialize]] and [[83Plus:Software:usb8x/Asm_Interface/MSD/FAT_Initialize|FAT_Initialize]]. All entry points will return with the carry flag set if there are problems, with more detailed information available via [[83Plus:Software:usb8x/Asm_Interface/MSD/GetErrorCode|GetErrorCode]].

No knowledge of the intimate details of FAT16 are required. However, the "starting cluster" of a directory is used in several routines. This is a 16-bit number uniquely indentifying a directory. It is beneficial to use this number rather than an extremely long ASCIIZ directory path which wastes memory. It is easily obtained with [[/FAT_getStartingCluster|FAT_getStartingCluster]] by passing an ASCIIZ directory path to it.

== Entry Points ==

If all three of the initializing U_CALLs succeed, the other following entry points can then be called.

{| border="1" cellpadding="2" cellspacing="0"
|-
| [[83Plus:Software:usb8x/Asm_Interface/MSD/MSDVersion|MSDVersion]] || Gets mass storage driver version and memory requirements
|-
| [[83Plus:Software:usb8x/Asm_Interface/MSD/MSD_Initialize|MSD_Initialize]] || Initializes mass storage driver
|-
| [[83Plus:Software:usb8x/Asm_Interface/MSD/UFI_Initialize|UFI_Initialize]] || Initializes connected mass storage device for sector read/write operations
|-
| [[83Plus:Software:usb8x/Asm_Interface/MSD/UFI_getCapacity|UFI_getCapacity]] || Gets capacity of entire drive and sets up bytes-per-sector
|-
| [[83Plus:Software:usb8x/Asm_Interface/MSD/UFI_Read|UFI_Read]] || Reads sector at (MSDLBA) address into sector buffer
|-
| [[83Plus:Software:usb8x/Asm_Interface/MSD/UFI_Write|UFI_Write]] || Writes memory in sector buffer to (MSDLBA) address
|-
| [[83Plus:Software:usb8x/Asm_Interface/MSD/msdDetect|msdDetect]] || Detects and loads 83P/8XP levels based on detection string and specified directory
|-
| [[83Plus:Software:usb8x/Asm_Interface/MSD/FAT_Initialize|FAT_Initialize]] || Initializes connected mass storage device for FAT16 file system operations
|-
| [[83Plus:Software:usb8x/Asm_Interface/MSD/DOS_openFile|DOS_openFile]] || Opens a file and populates file handle with important information
|-
| [[83Plus:Software:usb8x/Asm_Interface/MSD/DOS_fileSeek|DOS_fileSeek]] || Sets seek pointer for file handle to specified offset
|-
| [[83Plus:Software:usb8x/Asm_Interface/MSD/DOS_fileRead|DOS_fileRead]] || Read bytes from a file
|-
| [[83Plus:Software:usb8x/Asm_Interface/MSD/DOS_fileWrite|DOS_fileWrite]] || Write bytes to a file and grows it if necessary
|-
| [[83Plus:Software:usb8x/Asm_Interface/MSD/DOS_updateAttributes|DOS_updateAttributes]] || Update "last modified" date/time and other attributes
|-
| [[83Plus:Software:usb8x/Asm_Interface/MSD/DOS_createFile|DOS_createFile]] || Create new file in specified directory with size 0
|-
| [[83Plus:Software:usb8x/Asm_Interface/MSD/DOS_createDirectory|DOS_createDirectory]] || Create new subdirectory in specified directory
|-
| [[83Plus:Software:usb8x/Asm_Interface/MSD/DOS_renameFileEntry|DOS_renameFileEntry]] || Rename specified file or folder
|-
| [[83Plus:Software:usb8x/Asm_Interface/MSD/DOS_deleteFileEntry|DOS_deleteFileEntry]] || Delete file or folder (including contents)
|-
| [[83Plus:Software:usb8x/Asm_Interface/MSD/DOS_countFilesInDir|DOS_countFilesInDir]] || Get number of files/folders in specified directory
|-
| [[83Plus:Software:usb8x/Asm_Interface/MSD/DOS_getNextFile|DOS_getNextFile]] || Get first/next file in specified directory
|-
| [[83Plus:Software:usb8x/Asm_Interface/MSD/DOS_getFileSize|DOS_getFileSize]] || Get size of file
|-
| [[83Plus:Software:usb8x/Asm_Interface/MSD/DOS_getDirEntry|DOS_getDirEntry]] || Get directory entry for specified file/folder
|-
| [[83Plus:Software:usb8x/Asm_Interface/MSD/FAT_nameConvertTo11|FAT_nameConvertTo11]] || Convert name to 11-character format (ex. "<code>README TXT</code>")
|-
| [[83Plus:Software:usb8x/Asm_Interface/MSD/FAT_nameConvertFrom11|FAT_nameConvertFrom11]] || Convert name to ASCIIZ format (ex. "readme.txt")
|-
| [[83Plus:Software:usb8x/Asm_Interface/MSD/FAT_lookupPath|FAT_lookupPath]] || Find whether specified file/directory exists
|-
| [[83Plus:Software:usb8x/Asm_Interface/MSD/FAT_findFileInCluster|FAT_findFileInCluster]] || Get directory entry for a file in specified folder
|-
| [[83Plus:Software:usb8x/Asm_Interface/MSD/FAT_getStartingCluster|FAT_getStartingCluster]] || Get starting cluster of specified directory
|-
| [[83Plus:Software:usb8x/Asm_Interface/MSD/MSD_ImportVariable|MSD_ImportVariable]] || Imports 8x* file in specified directory as calculator variable in RAM/Flash
|-
| [[83Plus:Software:usb8x/Asm_Interface/MSD/MSD_ExportVariable|MSD_ExportVariable]] || Exports calculator variable in RAM/Flash as 8x* file in specified directory
|}

== Other File Systems ==

You can use the [[83Plus:Software:usb8x/Asm_Interface/MSD/MSD_Initialize|MSD_Initialize]], [[83Plus:Software:usb8x/Asm_Interface/MSD/UFI_getCapacity|UFI_getCapacity]], [[83Plus:Software:usb8x/Asm_Interface/MSD/UFI_Read|UFI_Read]], and [[83Plus:Software:usb8x/Asm_Interface/MSD/UFI_Write|UFI_Write]] entry points to create your own file system driver. For example, you could create a driver for ext2/3, FAT32, or any other file system imaginable.

The low-level parts of the mass storage driver work by reading and writing sectors to the drive based on the current LBA address. This is located in (MSDLBA) in the mass storage driver's memory. To create your own file system driver, you will need to implement all of the details specific to that file system.

The [[83Plus:Software:usb8x/Asm_Interface/MSD/MSD_Initialize|MSD_Initialize]] entry point is required for any communication with the drive. When this entry point succeeds, you would then call [[83Plus:Software:usb8x/Asm_Interface/MSD/UFI_getCapacity|UFI_getCapacity]] to set up (MSDBPS) in the driver memory. This is necessary for the [[83Plus:Software:usb8x/Asm_Interface/MSD/UFI_Read|UFI_Read]] and [[83Plus:Software:usb8x/Asm_Interface/MSD/UFI_Write|UFI_Write]] entry points to succeed.

Once both entry points succeed, you are free to read and write as much as you like. The boot sector is located at LBA address 0x00000000. Most file systems require that you read this first to find out what to do next. Check out the mass storage driver in the usb8x source for more information.

83Plus:Software:usb8x/Asm Interface/MSD

2009-02-18T02:59:07Z

TheStorm:

The mass storage driver works through a series of U_CALL entry points, much like the HID driver.

It requires two RAM buffers, one for internal use and one for a sector buffer. File handles used for opened files (explained later) also require around 27 bytes. The size of all three of these buffers can be obtained through the [[83Plus:Software:usb8x/Asm_Interface/MSD/MSDVersion|MSDVersion]] U_CALL. The size of the internal buffer is typically 254 bytes and the sector buffer is 512 bytes.

The entry point which requires these buffers is the [[83Plus:Software:usb8x/Asm_Interface/MSD/MSD_Initialize|MSD_Initialize]] U_CALL. Its memory can be dynamically allocated to appBackUpScreen (taking up practically all of it) with the code below:

<code>
U_CALL MSDVersion
ld de,appBackUpScreen
push de
add hl,de
ex de,hl
pop hl
U_CALL MSD_Initialize
</code>

For file system operations, you will then make calls to [[83Plus:Software:usb8x/Asm_Interface/MSD/UFI_Initialize|UFI_Initialize]] and [[83Plus:Software:usb8x/Asm_Interface/MSD/FAT_Initialize|FAT_Initialize]]. All entry points will return with the carry flag set if there are problems, with more detailed information available via [[83Plus:Software:usb8x/Asm_Interface/MSD/GetErrorCode|GetErrorCode]].

No knowledge of the intimate details of FAT16 are required. However, the "starting cluster" of a directory is used in several routines. This is a 16-bit number uniquely indentifying a directory. It is beneficial to use this number rather than an extremely long ASCIIZ directory path which wastes memory. It is easily obtained with [[/FAT_getStartingCluster|FAT_getStartingCluster]] by passing an ASCIIZ directory path to it.

== Entry Points ==

If all three of the initializing U_CALLs succeed, the other following entry points can then be called.

{| border="1" cellpadding="2" cellspacing="0"
|-
| [[/MSDVersion|MSDVersion]] || Gets mass storage driver version and memory requirements
|-
| [[/MSD_Initialize|MSD_Initialize]] || Initializes mass storage driver
|-
| [[/UFI_Initialize|UFI_Initialize]] || Initializes connected mass storage device for sector read/write operations
|-
| [[/UFI_getCapacity|UFI_getCapacity]] || Gets capacity of entire drive and sets up bytes-per-sector
|-
| [[/UFI_Read|UFI_Read]] || Reads sector at (MSDLBA) address into sector buffer
|-
| [[/UFI_Write|UFI_Write]] || Writes memory in sector buffer to (MSDLBA) address
|-
| [[/msdDetect|msdDetect]] || Detects and loads 83P/8XP levels based on detection string and specified directory
|-
| [[/FAT_Initialize|FAT_Initialize]] || Initializes connected mass storage device for FAT16 file system operations
|-
| [[/DOS_openFile|DOS_openFile]] || Opens a file and populates file handle with important information
|-
| [[/DOS_fileSeek|DOS_fileSeek]] || Sets seek pointer for file handle to specified offset
|-
| [[/DOS_fileRead|DOS_fileRead]] || Read bytes from a file
|-
| [[/DOS_fileWrite|DOS_fileWrite]] || Write bytes to a file and grows it if necessary
|-
| [[/DOS_updateAttributes|DOS_updateAttributes]] || Update "last modified" date/time and other attributes
|-
| [[/DOS_createFile|DOS_createFile]] || Create new file in specified directory with size 0
|-
| [[/DOS_createDirectory|DOS_createDirectory]] || Create new subdirectory in specified directory
|-
| [[/DOS_renameFileEntry|DOS_renameFileEntry]] || Rename specified file or folder
|-
| [[/DOS_deleteFileEntry|DOS_deleteFileEntry]] || Delete file or folder (including contents)
|-
| [[/DOS_countFilesInDir|DOS_countFilesInDir]] || Get number of files/folders in specified directory
|-
| [[/DOS_getNextFile|DOS_getNextFile]] || Get first/next file in specified directory
|-
| [[/DOS_getFileSize|DOS_getFileSize]] || Get size of file
|-
| [[/DOS_getDirEntry|DOS_getDirEntry]] || Get directory entry for specified file/folder
|-
| [[/FAT_nameConvertTo11|FAT_nameConvertTo11]] || Convert name to 11-character format (ex. "<code>README TXT</code>")
|-
| [[/FAT_nameConvertFrom11|FAT_nameConvertFrom11]] || Convert name to ASCIIZ format (ex. "readme.txt")
|-
| [[/FAT_lookupPath|FAT_lookupPath]] || Find whether specified file/directory exists
|-
| [[/FAT_findFileInCluster|FAT_findFileInCluster]] || Get directory entry for a file in specified folder
|-
| [[/FAT_getStartingCluster|FAT_getStartingCluster]] || Get starting cluster of specified directory
|-
| [[/MSD_ImportVariable|MSD_ImportVariable]] || Imports 8x* file in specified directory as calculator variable in RAM/Flash
|-
| [[/MSD_ExportVariable|MSD_ExportVariable]] || Exports calculator variable in RAM/Flash as 8x* file in specified directory
|}

== Other File Systems ==

You can use the [[/MSD_Initialize|MSD_Initialize]], [[/UFI_getCapacity|UFI_getCapacity]], [[/UFI_Read|UFI_Read]], and [[/UFI_Write|UFI_Write]] entry points to create your own file system driver. For example, you could create a driver for ext2/3, FAT32, or any other file system imaginable.

The low-level parts of the mass storage driver work by reading and writing sectors to the drive based on the current LBA address. This is located in (MSDLBA) in the mass storage driver's memory. To create your own file system driver, you will need to implement all of the details specific to that file system.

The [[/MSD_Initialize|MSD_Initialize]] entry point is required for any communication with the drive. When this entry point succeeds, you would then call [[/UFI_getCapacity|UFI_getCapacity]] to set up (MSDBPS) in the driver memory. This is necessary for the [[/UFI_Read|UFI_Read]] and [[/UFI_Write|UFI_Write]] entry points to succeed.

Once both entry points succeed, you are free to read and write as much as you like. The boot sector is located at LBA address 0x00000000. Most file systems require that you read this first to find out what to do next. Check out the mass storage driver in the usb8x source for more information.

83Plus:Software:usb8x/Asm Interface/MSD

2009-02-18T02:58:17Z

TheStorm:

The mass storage driver works through a series of U_CALL entry points, much like the HID driver.

It requires two RAM buffers, one for internal use and one for a sector buffer. File handles used for opened files (explained later) also require around 27 bytes. The size of all three of these buffers can be obtained through the [[../MSDVersion|MSDVersion]] U_CALL. The size of the internal buffer is typically 254 bytes and the sector buffer is 512 bytes.

The entry point which requires these buffers is the [[../MSD_Initialize|MSD_Initialize]] U_CALL. Its memory can be dynamically allocated to appBackUpScreen (taking up practically all of it) with the code below:

<code>
U_CALL MSDVersion
ld de,appBackUpScreen
push de
add hl,de
ex de,hl
pop hl
U_CALL MSD_Initialize
</code>

For file system operations, you will then make calls to [[/UFI_Initialize|UFI_Initialize]] and [[/FAT_Initialize|FAT_Initialize]]. All entry points will return with the carry flag set if there are problems, with more detailed information available via [[../GetErrorCode|GetErrorCode]].

No knowledge of the intimate details of FAT16 are required. However, the "starting cluster" of a directory is used in several routines. This is a 16-bit number uniquely indentifying a directory. It is beneficial to use this number rather than an extremely long ASCIIZ directory path which wastes memory. It is easily obtained with [[/FAT_getStartingCluster|FAT_getStartingCluster]] by passing an ASCIIZ directory path to it.

== Entry Points ==

If all three of the initializing U_CALLs succeed, the other following entry points can then be called.

{| border="1" cellpadding="2" cellspacing="0"
|-
| [[/MSDVersion|MSDVersion]] || Gets mass storage driver version and memory requirements
|-
| [[/MSD_Initialize|MSD_Initialize]] || Initializes mass storage driver
|-
| [[/UFI_Initialize|UFI_Initialize]] || Initializes connected mass storage device for sector read/write operations
|-
| [[/UFI_getCapacity|UFI_getCapacity]] || Gets capacity of entire drive and sets up bytes-per-sector
|-
| [[/UFI_Read|UFI_Read]] || Reads sector at (MSDLBA) address into sector buffer
|-
| [[/UFI_Write|UFI_Write]] || Writes memory in sector buffer to (MSDLBA) address
|-
| [[/msdDetect|msdDetect]] || Detects and loads 83P/8XP levels based on detection string and specified directory
|-
| [[/FAT_Initialize|FAT_Initialize]] || Initializes connected mass storage device for FAT16 file system operations
|-
| [[/DOS_openFile|DOS_openFile]] || Opens a file and populates file handle with important information
|-
| [[/DOS_fileSeek|DOS_fileSeek]] || Sets seek pointer for file handle to specified offset
|-
| [[/DOS_fileRead|DOS_fileRead]] || Read bytes from a file
|-
| [[/DOS_fileWrite|DOS_fileWrite]] || Write bytes to a file and grows it if necessary
|-
| [[/DOS_updateAttributes|DOS_updateAttributes]] || Update "last modified" date/time and other attributes
|-
| [[/DOS_createFile|DOS_createFile]] || Create new file in specified directory with size 0
|-
| [[/DOS_createDirectory|DOS_createDirectory]] || Create new subdirectory in specified directory
|-
| [[/DOS_renameFileEntry|DOS_renameFileEntry]] || Rename specified file or folder
|-
| [[/DOS_deleteFileEntry|DOS_deleteFileEntry]] || Delete file or folder (including contents)
|-
| [[/DOS_countFilesInDir|DOS_countFilesInDir]] || Get number of files/folders in specified directory
|-
| [[/DOS_getNextFile|DOS_getNextFile]] || Get first/next file in specified directory
|-
| [[/DOS_getFileSize|DOS_getFileSize]] || Get size of file
|-
| [[/DOS_getDirEntry|DOS_getDirEntry]] || Get directory entry for specified file/folder
|-
| [[/FAT_nameConvertTo11|FAT_nameConvertTo11]] || Convert name to 11-character format (ex. "<code>README TXT</code>")
|-
| [[/FAT_nameConvertFrom11|FAT_nameConvertFrom11]] || Convert name to ASCIIZ format (ex. "readme.txt")
|-
| [[/FAT_lookupPath|FAT_lookupPath]] || Find whether specified file/directory exists
|-
| [[/FAT_findFileInCluster|FAT_findFileInCluster]] || Get directory entry for a file in specified folder
|-
| [[/FAT_getStartingCluster|FAT_getStartingCluster]] || Get starting cluster of specified directory
|-
| [[/MSD_ImportVariable|MSD_ImportVariable]] || Imports 8x* file in specified directory as calculator variable in RAM/Flash
|-
| [[/MSD_ExportVariable|MSD_ExportVariable]] || Exports calculator variable in RAM/Flash as 8x* file in specified directory
|}

== Other File Systems ==

You can use the [[/MSD_Initialize|MSD_Initialize]], [[/UFI_getCapacity|UFI_getCapacity]], [[/UFI_Read|UFI_Read]], and [[/UFI_Write|UFI_Write]] entry points to create your own file system driver. For example, you could create a driver for ext2/3, FAT32, or any other file system imaginable.

The low-level parts of the mass storage driver work by reading and writing sectors to the drive based on the current LBA address. This is located in (MSDLBA) in the mass storage driver's memory. To create your own file system driver, you will need to implement all of the details specific to that file system.

The [[/MSD_Initialize|MSD_Initialize]] entry point is required for any communication with the drive. When this entry point succeeds, you would then call [[/UFI_getCapacity|UFI_getCapacity]] to set up (MSDBPS) in the driver memory. This is necessary for the [[/UFI_Read|UFI_Read]] and [[/UFI_Write|UFI_Write]] entry points to succeed.

Once both entry points succeed, you are free to read and write as much as you like. The boot sector is located at LBA address 0x00000000. Most file systems require that you read this first to find out what to do next. Check out the mass storage driver in the usb8x source for more information.

Category talk:83Plus:BCALLs:By Name

2009-02-18T02:42:58Z

TheStorm: typo

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)
:::::If you'd like to either upload them somewhere or email them to tideletedmywebpage@mail.denglend.net I'll upload the pdfs to the wiki. Thanks. --Dan
::::::The PDFs are now available [http://wikiti.denglend.net/stuff/unsupage here]. It would be better if they were added to the wiki itself, but it's better than nothing for now. --[[User:Dan Englender|Dan Englender]] 12:58, 20 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)

This page needs to be fixed to show the names rather than address on the bcalls.--[[User:TheStorm|TheStorm]] 02:42, 18 February 2009 (UTC)

Category talk:83Plus:BCALLs:By Name

2009-02-18T02:42:38Z

TheStorm:

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)
:::::If you'd like to either upload them somewhere or email them to tideletedmywebpage@mail.denglend.net I'll upload the pdfs to the wiki. Thanks. --Dan
::::::The PDFs are now available [http://wikiti.denglend.net/stuff/unsupage here]. It would be better if they were added to the wiki itself, but it's better than nothing for now. --[[User:Dan Englender|Dan Englender]] 12:58, 20 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)

This page needs t be fixed to show the names rather than address on the bcalls.--[[User:TheStorm|TheStorm]] 02:42, 18 February 2009 (UTC)

83Plus:Software:usb8x

2009-02-18T02:39:48Z

TheStorm:

usb8x is a free, open source 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.12'''.

----

===New Users===
* [http://sourceforge.net/project/showfiles.php?group_id=143628 Download]
* [[83Plus:Software:usb8x/Install|Installation Instructions]]
* [[83Plus:Software:usb8x/FAQ|Frequently Asked Questions]]
* [[83Plus:Software:usb8x/Supported_Devices|Supported Devices]]
* [[83Plus:Software:usb8x/Changelog|Version History]]

===Programmer Documentation===
* [[83Plus:Software:usb8x/Build|Build Instructions]]
* [[83Plus:Software:usb8x/Asm_Interface|Assembly language interface]]
* [[83Plus:Software:usb8x/BASIC_Interface|BASIC language interface]]
* [[83Plus:Software:usb8x/Sample_Code|Code Examples]]
* [[83Plus:Software:usb8x/Error_Codes|Error codes]]

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

Category:86:RAM

2009-01-31T03:52:42Z

TheStorm: New page: RAM Areas Please read our page on Contributing before editing these pages!

[[Category:86|RAM Areas]]

Please read our page on [[Contributing]] before editing these pages!

Category:86:RAM:By Address

2009-01-31T03:52:20Z

TheStorm: New page: RAM Areas by Address See also list of RAM areas by name. Please read our page on Contributing before editing these pages!

[[Category:86:RAM|RAM Areas by Address]]

See also [[:Category:86:RAM:By Name|list of RAM areas by name]].

Please read our page on [[Contributing]] before editing these pages!

Category:86:RAM:By Name

2009-01-31T03:51:59Z

TheStorm: New page: RAM Areas by Name See also list of RAM areas by address. Please read our page on Contributing before editing these pages!

[[Category:86:RAM|RAM Areas by Name]]

See also [[:Category:86:RAM:By Address|list of RAM areas by address]].

Please read our page on [[Contributing]] before editing these pages!

Category:86:Ports:By Name

2009-01-31T03:50:58Z

TheStorm: New page: Ports by Name See also list of ports by address/number. Please read our page on Contributing before editing these pages!

[[Category:86:Ports|Ports by Name]]

See also [[:Category:86:Ports:By Address|list of ports by address/number]].

Please read our page on [[Contributing]] before editing these pages!

Category:86:Ports

2009-01-31T03:50:28Z

TheStorm: New page: Ports Please read our page on Contributing before editing these pages!

[[Category:86|Ports]]

Please read our page on [[Contributing]] before editing these pages!

Category:86:Ports:By Address

2009-01-31T03:50:07Z

TheStorm: New page: Ports by Address/Number See also list of ports by name. Please read our page on Contributing before editing these pages!

[[Category:86:Ports|Ports by Address/Number]]

See also [[:Category:86:Ports:By Name|list of ports by name]].

Please read our page on [[Contributing]] before editing these pages!

Category:86:OS Information

2009-01-31T03:49:34Z

TheStorm: New page: OS Information This is the central location for generic documentation on the TI-86. Here you should cover things like the system monitor, using edit buffers, etc. Please r...

[[Category:86|OS Information]]
This is the central location for generic documentation on the TI-86. Here you should cover things like the system monitor, using edit buffers, etc.

Please read our page on [[Contributing]] before editing these pages!

Category:86:Flags:By Address

2009-01-31T03:48:27Z

TheStorm: New page: System Flags by Address/Offset See also list of system flags by name. Please read our page on Contributing before editing these pa...

[[Category:86:Flags|System Flags by Address/Offset]]
See also [[:Category:86:Flags:By Name|list of system flags by name]].

Please read our page on [[Contributing]] before editing these pages!

Category:86:Flags

2009-01-31T03:47:37Z

TheStorm: New page: System Flags Please read our page on Contributing before editing these pages!

[[Category:83|System Flags]]
Please read our page on [[Contributing]] before editing these pages!

Category:86:Flags:By Name

2009-01-31T03:47:14Z

TheStorm: New page: System Flags by Name See also list of system flags by address/offset. Please read our page on Contributing before editing these...

[[Category:86:Flags|System Flags by Name]]
See also [[:Category:86:Flags:By Address|list of system flags by address/offset]].

Please read our page on [[Contributing]] before editing these pages!

Category:86:ROMCalls:By Address

2009-01-31T03:46:10Z

TheStorm: New page: System Calls by Address This is a list of all 86 System Calls, sorted by address. See also list of system calls by name. Please...

[[Category:86:ROMCalls|System Calls by Address]]
This is a list of all 86 System Calls, sorted by address.

See also [[:Category:86:ROMCalls:By_Name|list of system calls by name]].

Please read our page on [[Contributing]] before editing these pages!

Category:86

2009-01-31T03:45:01Z

TheStorm: New page: TI-86 Documentation This Category contains documentation specific to the TI-86.

[[Category:Calculator Documentation|TI-86 Documentation]]

This Category contains documentation specific to the TI-86.

Category:86:ROMCalls

2009-01-31T03:44:10Z

TheStorm: New page: System Calls (ROMCalls) This is a list of documented and undocumented system calls on the TI-86. Please read our page on Contributing before editing these pages!

[[Category:86|System Calls (ROMCalls)]]
This is a list of documented and undocumented system calls on the TI-86.

Please read our page on [[Contributing]] before editing these pages!

Category:86:ROMCalls:By Name

2009-01-31T03:43:08Z

TheStorm: New page: System Calls by Name This is a list of all 86 System Calls, sorted by name. See also list of system calls by address. Please...

[[Category:86:ROMCalls|System Calls by Name]]
This is a list of all 86 System Calls, sorted by name.

See also [[:Category:86:ROMCalls:By_Address|list of system calls by address]].

Please read our page on [[Contributing]] before editing these pages!

Calculator Documentation

2009-01-31T03:42:15Z

TheStorm:

== TI-83 (Regular) ==

* [[:Category:83:ROMCalls:By_Name|ROMCalls (System Entrypoints)]]
* [[:Category:83:Flags:By_Name|Flags]]
* [[:Category:83:OS_Information|General OS Documentation]]
* [[:Category:83:Ports:By_Address|Ports]]
* [[:Category:83:RAM:By_Name|RAM Areas]]

== TI-83 Plus Family ==

* [[:Category:83Plus:BCALLs:By_Name|B_CALLs (System Entrypoints)]]
* [[:Category:83Plus:Flags:By_Name|Flags]]
* [[:Category:83Plus:OS_Information|General OS Documentation]]
* [[:Category:83Plus:Hooks:By_Name|Hooks]]
* [[:Category:83Plus:Ports:By_Address|Ports]]
* [[:Category:83Plus:RAM:By_Name|RAM Areas]]
* [[:Category:83Plus:Software|Software Documentation]]
* [[:Category:83Plus:Basic|TI-83+ Basic]]

== TI-86 ==

* [[:Category:86:ROMCalls:By_Name|ROMCalls (System Entrypoints)]]
* [[:Category:86:Flags:By_Name|Flags]]
* [[:Category:86:OS_Information|General OS Documentation]]
* [[:Category:86:Ports:By_Address|Ports]]
* [[:Category:86:RAM:By_Name|RAM Areas]]

== M68K Family ==

* [[:Category:68k:Ports:By_Address|Ports]]

== Z80 programming ==
* [[Meta-tutorial]]
* [[:Category:Z80_Routines|Z80 Routines]]
* [[Z80 Instruction Set]]
* [[Good programming practices]]
* [[Programming under Unix-like operating systems]]

== Software ==
* [[Notable programs]]
* [[:Category:Emulators|Emulators]]
* [[83Plus:OS:TIOS Alternatives|TIOS Alternatives]]
* [[Experiments]]

== Linking ==
* [[Link cables]]

== TI Community ==

* [[Beginners|Beginners' manual]]
* [[History of the TI Z80 community]]
* [[:Category:Teams|Programming Teams]]
* [[TI websites]]

== Contributing ==

Please read our page on [[Contributing]] before you start contributing to WikiTI.

83Plus:OS:Dialog context

2009-01-31T03:27:59Z

TheStorm:

[[Category:83Plus:OS_Information|Dialog context]]
This Documentation is for use with the [[:Category:83Plus:BCALLs:By_Name:Dialog|Dialog BCALLS]].

== General Info ==
To start this context, load a menu structure* to ramCode/[[83Plus:RAM:8000|appData]], BCALL [[83Plus:BCALLs:4C06|DialogInit]] and then BCALL [[83Plus:BCALLs:4C03|StartDialog]].
You choose whether the run indicator is displayed and whether contexts are allowed (appAllowContext,(iy+appFlags)).
It is imperative that (cxCurApp) be one of the allowed values (use 58h=kExtApps).

If kSolveRoot (SOLVE EDITOR), kStatEd (list editor), or kInfStat (inferential statistic editor) are pressed, the entire screen is redrawn and then the parser callback is called with A=1.

If [UP], [DOWN], or [ENTER] are pressed, any entered number is parsed*.

If [2nd]+[QUIT] is pressed, whatever has been entered will be parsed* (no errors thrown nor anything displayed) to OP1, the previous context vectors are restored, SP is restored from (spSave), and the run indicator is turned off.

== Parsing the number ==
ParseInp is called on the data entered, and OP1 is checked to make sure it is REAL (error thrown if not (and this may return to the edit)).
A=0 is passed to the parser callback. B (8006h) is the index into a prompt structure (probably bID = 3). It is expected to return a value in A. Return zero to display the current line (string and number).
It also copies the number in OP1 to the spot bNumIndex points to. If 0,(iy+2Eh) is set, the rest of the line is not erased (then NewLine).

== Menu structure ==
Load as many of these structures, one after the other (zero-terminated), to ramCode/[[83Plus:RAM:8000|appData]] in the order you want it displayed.
Store the length-indexed strings in RAM as well (right after this structure, in ramCode/[[83Plus:RAM:8000|appData]]).

bID can be from 1-6:
bID = 1: display string (cannot select).
bID = 2: display highlightable choices (as in the MODE context). A byte table at 8009h has to do with what is selected here.
bID = 3: display prompt string and number.
bID = 4: display highlightable string.
bID = 5: display menu number (ex. "1:") and prompt string.
bID = 6: hidden, skip displaying this entry.

=== Prompt structure when bID = 1 ===
DB bID ;
DB bNumChoices ;probably always 1
DB bUnknown ;
DW wStringOffset ;offset from start of ramCode

=== Prompt structure when bID = 2 ===
DB bID ;
DB bNumChoices ;
DB bUnknown ;I think this is the number of rows to skip for next item, or something
DW wStringOffset ;offset from start of ramCode /
DB bColumn ;column to display string (this is probably ignored) \ There are bNumChoices of these.

=== Prompt structure when bID = 3 ===
DB bID ;
DB bNumChoices ;probably always 1
DB bNumIndex ;
DW wStringOffset ;offset from start of ramCode

=== Prompt structure when bID = 4 ===
DB bID ;
DB bNumChoices ;probably always 1
DB bUnknown ;
DW wStringOffset ;offset from start of ramCode

=== Prompt structure when bID = 5 ===
DB bID ;
DB bNumEntries ;probably always 1
DB bMenuItemNum ;1 for "1:", 2 for "2:", etc.
DW wStringOffset ;offset from start of ramCode

=== Prompt structure when bID = 6 ===
DB bID ;
DB bNumChoices ;
DB bUnknown ;
DW wStringOffset ;offset from start of ramCode < There are bNumChoices of these.

8038h: bNumIndex above is an offset into a list of floating-point numbers:
DB 00h,80h,00h,00h,00h,00h,00h,00h,00h
== Examples ==
=== Example Code ===
hookBackup equ appBackUpScreen
.db 0BBh,6Dh
ld hl,rawKeyHookPtr
ld de,hookBackup
ld bc,4
ldir
ld a,(flags+34h)
ld (de),a
ld a,(cxCurApp)
push af
ld a,58h
ld (cxCurApp),a
ld hl,structStart
ld de,ramCode
ld bc,structEnd-structStart
ldir
ld hl,dialogCallback
in a,(6)
bcall(_DialogInit)
bcall(_runIndicOff)
bcall(_StartDialog)
bcall(_cursorOff)
bcall(_clrLCDFull)
res appCurWord,(iy+appFlags)
bcall(_ClrTxtShd)
ld hl,cmdShadow
ld de,cmdShadow+1
ld (hl),' '
ld bc,127
ldir
pop af
ld (cxCurApp),a
ld hl,hookBackup
ld de,rawKeyHookPtr
ld bc,4
ldir
ld a,(hl)
ld (flags+34h),a
xor a
bcall(_GetDialogNumOP1)
ld hl,0
ld (penCol),hl
ld a,9
bcall(_DispOP1a)
dialogCallback:
xor a
ret
structStart:
;put your dialog data here
structEnd:
=== Example Table ===
structStart:
.db 1
.db 1
.db 1
.dw sOptions-structStart
.db 5
.db 1
.db 1
.dw sItem1-structStart
.db 5
.db 1
.db 2
.dw sItem2-structStart
.db 2
.db 3
.db 1
.dw sSelect-structStart
.dw sOpt1-structStart
.dw sOpt2-structStart
.db 3
.db 1
.db 0
.dw sNum-structStart
.db 4
.db 1
.db 1
.dw sDone-structStart
.db 0
sOptions:
.db 7,"OPTIONS"
sItem1: .db 5,"Item1"
sItem2: .db 5,"Item2"
sSelect:
.db 6,"Opts: "
sOpt1: .db 4,"Opt1"
sOpt2: .db 4,"Opt2"
sNum: .db 4,"Num="
sDone: .db 4,"Done"
structEnd:

== Credits ==
* Thanks to BrandonW for finding out all this info on the dialog BCALLs and for the example code, though apparently Detached Solutions knew it all along.

83Plus:OS:Dialog context

2009-01-31T03:27:47Z

TheStorm:

[[Category:83Plus:OS_Information|Dialog context]]
This Documentation is for use with the [[:Category:83Plus:BCALLs:By_Name:Dialog|Dialog BCALLS]].

== General Info ==
To start this context, load a menu structure* to ramCode/[[83Plus:RAM:8000|appData]], BCALL [[83Plus:BCALLs:4C06|DialogInit]] and then BCALL [[83Plus:BCALLs:4C03|StartDialog]].
You choose whether the run indicator is displayed and whether contexts are allowed (appAllowContext,(iy+appFlags)).
It is imperative that (cxCurApp) be one of the allowed value s (use 58h=kExtApps).

If kSolveRoot (SOLVE EDITOR), kStatEd (list editor), or kInfStat (inferential statistic editor) are pressed, the entire screen is redrawn and then the parser callback is called with A=1.

If [UP], [DOWN], or [ENTER] are pressed, any entered number is parsed*.

If [2nd]+[QUIT] is pressed, whatever has been entered will be parsed* (no errors thrown nor anything displayed) to OP1, the previous context vectors are restored, SP is restored from (spSave), and the run indicator is turned off.

== Parsing the number ==
ParseInp is called on the data entered, and OP1 is checked to make sure it is REAL (error thrown if not (and this may return to the edit)).
A=0 is passed to the parser callback. B (8006h) is the index into a prompt structure (probably bID = 3). It is expected to return a value in A. Return zero to display the current line (string and number).
It also copies the number in OP1 to the spot bNumIndex points to. If 0,(iy+2Eh) is set, the rest of the line is not erased (then NewLine).

== Menu structure ==
Load as many of these structures, one after the other (zero-terminated), to ramCode/[[83Plus:RAM:8000|appData]] in the order you want it displayed.
Store the length-indexed strings in RAM as well (right after this structure, in ramCode/[[83Plus:RAM:8000|appData]]).

bID can be from 1-6:
bID = 1: display string (cannot select).
bID = 2: display highlightable choices (as in the MODE context). A byte table at 8009h has to do with what is selected here.
bID = 3: display prompt string and number.
bID = 4: display highlightable string.
bID = 5: display menu number (ex. "1:") and prompt string.
bID = 6: hidden, skip displaying this entry.

=== Prompt structure when bID = 1 ===
DB bID ;
DB bNumChoices ;probably always 1
DB bUnknown ;
DW wStringOffset ;offset from start of ramCode

=== Prompt structure when bID = 2 ===
DB bID ;
DB bNumChoices ;
DB bUnknown ;I think this is the number of rows to skip for next item, or something
DW wStringOffset ;offset from start of ramCode /
DB bColumn ;column to display string (this is probably ignored) \ There are bNumChoices of these.

=== Prompt structure when bID = 3 ===
DB bID ;
DB bNumChoices ;probably always 1
DB bNumIndex ;
DW wStringOffset ;offset from start of ramCode

=== Prompt structure when bID = 4 ===
DB bID ;
DB bNumChoices ;probably always 1
DB bUnknown ;
DW wStringOffset ;offset from start of ramCode

=== Prompt structure when bID = 5 ===
DB bID ;
DB bNumEntries ;probably always 1
DB bMenuItemNum ;1 for "1:", 2 for "2:", etc.
DW wStringOffset ;offset from start of ramCode

=== Prompt structure when bID = 6 ===
DB bID ;
DB bNumChoices ;
DB bUnknown ;
DW wStringOffset ;offset from start of ramCode < There are bNumChoices of these.

8038h: bNumIndex above is an offset into a list of floating-point numbers:
DB 00h,80h,00h,00h,00h,00h,00h,00h,00h
== Examples ==
=== Example Code ===
hookBackup equ appBackUpScreen
.db 0BBh,6Dh
ld hl,rawKeyHookPtr
ld de,hookBackup
ld bc,4
ldir
ld a,(flags+34h)
ld (de),a
ld a,(cxCurApp)
push af
ld a,58h
ld (cxCurApp),a
ld hl,structStart
ld de,ramCode
ld bc,structEnd-structStart
ldir
ld hl,dialogCallback
in a,(6)
bcall(_DialogInit)
bcall(_runIndicOff)
bcall(_StartDialog)
bcall(_cursorOff)
bcall(_clrLCDFull)
res appCurWord,(iy+appFlags)
bcall(_ClrTxtShd)
ld hl,cmdShadow
ld de,cmdShadow+1
ld (hl),' '
ld bc,127
ldir
pop af
ld (cxCurApp),a
ld hl,hookBackup
ld de,rawKeyHookPtr
ld bc,4
ldir
ld a,(hl)
ld (flags+34h),a
xor a
bcall(_GetDialogNumOP1)
ld hl,0
ld (penCol),hl
ld a,9
bcall(_DispOP1a)
dialogCallback:
xor a
ret
structStart:
;put your dialog data here
structEnd:
=== Example Table ===
structStart:
.db 1
.db 1
.db 1
.dw sOptions-structStart
.db 5
.db 1
.db 1
.dw sItem1-structStart
.db 5
.db 1
.db 2
.dw sItem2-structStart
.db 2
.db 3
.db 1
.dw sSelect-structStart
.dw sOpt1-structStart
.dw sOpt2-structStart
.db 3
.db 1
.db 0
.dw sNum-structStart
.db 4
.db 1
.db 1
.dw sDone-structStart
.db 0
sOptions:
.db 7,"OPTIONS"
sItem1: .db 5,"Item1"
sItem2: .db 5,"Item2"
sSelect:
.db 6,"Opts: "
sOpt1: .db 4,"Opt1"
sOpt2: .db 4,"Opt2"
sNum: .db 4,"Num="
sDone: .db 4,"Done"
structEnd:

== Credits ==
* Thanks to BrandonW for finding out all this info on the dialog BCALLs and for the example code, though apparently Detached Solutions knew it all along.

User:TheStorm

2008-04-17T22:20:01Z

TheStorm:

Yeah...um...hi

I just add stuff other people find namely brandonw.

User:TheStorm

2008-04-17T22:19:46Z

TheStorm:

Yeah...um...hi
I just add stuff other people find namely brandonw.

83Plus:BCALLs:4C1E

2008-04-17T22:18:08Z

TheStorm: Typo

[[Category:83Plus:BCALLs:By_Name:Dialog|DialogStartGetKey]] [[Category:83Plus:BCALLs:By_Name|DialogStartGetKey]] [[Category:83Plus:BCALLs:By_Address|4C1E - DialogStartGetKey]]
{{missinfo|destroys}}
== Synopsis ==
'''Official Name:''' DialogStartGetKey

'''BCALL Address:''' 4C1E

Waits for a dialog keypress and then acts on it.
=== Inputs ===
* HL: address of a table

=== Outputs ===
* This doesn't return until you press [2nd]+[QUIT]
=== Destroys ===
* ''unknown''

== Comments ==
* This doesn't return until you press [2nd]+[QUIT]. You pass the address of a table in HL...if you pass a bID=3 table, it just returns. And the dialog has presumably already been displayed. It doesn't use the table for anything other than this, which is odd.
* Use with the other [[:Category:83Plus:BCALLs:By_Name:Dialog|Dialog BCALLs.]]
* [[83Plus:OS:Dialog_context|Info on how to use the Dialog BCALLs]] .

83Plus:BCALLs:49F0

2008-04-16T22:41:42Z

TheStorm:

[[Category:83Plus:BCALLs:By Name|CheckSplitFlag]] [[Category:83Plus:BCALLs:By Name:Display|CheckSplitFlag]] [[Category:83Plus:BCALLs:By Address|49F0 - CheckSplitFlag]]

== Synopsis ==
'''Official Name:''' CheckSplitFlag

'''BCALL Address:''' 49F0

Checks if either horizontal or G-T split screen modes are active.

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

=== Outputs ===
Z = 1 if no split screen mode is active
= 0 if a split screen mode is active

=== Registers Destroyed ===
''none''

== Comments ==
grfSplitOverride, (IY + sGrFlags) = 1 to ignore split mode settings
This flag is set to make system routines draw to the full screen even when in
a split screen mode.

83Plus:BCALLs:4FA8

2008-04-16T22:37:15Z

TheStorm: Added bcall

[[Category:83Plus:BCALLs:By Name|Bit_VertSplit]] [[Category:83Plus:BCALLs:By Name:Display|Bit_VertSplit]] [[Category:83Plus:BCALLs:By Address|4FA8 - Bit_VertSplit]]

== Synopsis ==
'''Official Name:''' Bit_VertSplit

'''BCALL Address:''' 4FA8

Tests if the TIâˆ’83 Plus is set to G-T (graph-table) display mode.

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

=== Outputs ===
NZ = 1 if G-T mode is set

=== Registers Destroyed ===
''none''

== Comments ==
Applications may want to reset the 83+ to full screen mode if graphing
functionality is used. In G-T mode the screen is split vertically with 1/2 being
the graph screen and the other the table display.

83Plus:BCALLs:4549

2008-04-16T22:34:21Z

TheStorm:

[[Category:83Plus:BCALLs:By Name|ClrScrn]] [[Category:83Plus:BCALLs:By Name:Display|ClrScrn]] [[Category:83Plus:BCALLs:By Address|4549 - ClrScrn]]

== Synopsis ==
'''Official Name:''' ClrScrn

'''BCALL Address:''' 4549

Clears the display. If textShadow is in use clears it also.

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

=== Outputs ===
''None''

=== Registers Destroyed ===
* DE,HL

== Comments ==
appTextSave,(IY + appFlags) = 1 if the textShadow is to be cleared also
G-T and HORIZ split screen modes will affect how this routine maps the
coordinates specified. To avoid this turn off the split screen modes.
grfSplit, (IY + sGrFlags) = 1 if horizontal split mode set
vertSplit, (IY + sGrFlags) = 1 if graph-table split mode set
grfSplitOverride, (IY + sGrFlags) = 1 to ignore split modes

83Plus:BCALLs:4549

2008-04-16T22:33:13Z

TheStorm: added bcall

[[Category:83Plus:BCALLs:By Name|ClrScrn]] [[Category:83Plus:BCALLs:By Name:Display|ClrScrn]] [[Category:83Plus:BCALLs:By Address|4549 - ClrScrn]]

== Synopsis ==
'''Official Name:''' ClrScrnFull

'''BCALL Address:''' 4549

Clears the display. If textShadow is in use clears it also.

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

=== Outputs ===
''None''

=== Registers Destroyed ===
* DE,HL

== Comments ==
appTextSave,(IY + appFlags) = 1 if the textShadow is to be cleared also
G-T and HORIZ split screen modes will affect how this routine maps the
coordinates specified. To avoid this turn off the split screen modes.
grfSplit, (IY + sGrFlags) = 1 if horizontal split mode set
vertSplit, (IY + sGrFlags) = 1 if graph-table split mode set
grfSplitOverride, (IY + sGrFlags) = 1 to ignore split modes

83Plus:RAM:8000

2008-04-14T01:35:04Z

TheStorm:

[[Category:83Plus:RAM:By_Name|appData]] [[Category:83Plus:RAM:By_Address|8000 - appData]]
== Synopsis ==
'''Official Name:''' appData

'''Memory Address:''' 8000h

'''Length:''' 256 bytes.

This area of memory functions as scratch memory for the boot code.

== Comments ==
One popular use of this area is to store a public key for validation by [[83Plus:BCALLs:801B|RSAValidate]] or [[83Plus:BCALLs:80A2|Rabin]].

It is generally free for programs to use.

Sometimes referred to as rameCode.

83Plus:BCALLs:4C03

2008-04-14T01:33:16Z

TheStorm:

[[Category:83Plus:BCALLs:By_Name:Dialog|StartDialog]] [[Category:83Plus:BCALLs:By_Name|StartDialog]] [[Category:83Plus:BCALLs:By_Address|4C03 - StartDialog]]
== Synopsis ==
'''Official Name:''' StartDialog

'''BCALL Address:''' 4C03

Starts a dialog at [[83Plus:RAM:8000|appData]] created with [[83Plus:BCALLs:4C06|DialogInit]]

=== Inputs ===
* [[83Plus:RAM:8000|appData]]: menu structure.

=== Outputs ===
* Starts Dialog
=== Destroys ===
* ''unknown''

== Comments ==
* Use [[83Plus:BCALLs:4C06|DialogInit]] to set up,
* Use with the other [[:Category:83Plus:BCALLs:By_Name:Dialog|Dialog BCALLs.]]
* Stores zero to (8033h), resets key override, draws dialog, and it starts waiting for a keypress.
* [[83Plus:OS:Dialog_context|Info on how to use the Dialog BCALLs]] .

83Plus:OS:Dialog context

2008-04-14T01:28:27Z

TheStorm:

[[Category:83Plus:OS_Information|Dialog context]]
This Documentation is for use with the [[:Category:83Plus:BCALLs:By_Name:Dialog|Dialog BCALLS]]

== General Info ==
To start this context, load a menu structure* to ramCode/[[83Plus:RAM:8000|appData]], BCALL [[83Plus:BCALLs:4C06|DialogInit]] and then BCALL [[83Plus:BCALLs:4C03|StartDialog]].
You choose whether the run indicator is displayed and whether contexts are allowed (appAllowContext,(iy+appFlags)).
It is imperative that (cxCurApp) be one of the allowed values (use 58h=kExtApps).

If kSolveRoot (SOLVE EDITOR), kStatEd (list editor), or kInfStat (inferential statistic editor) are pressed, the entire screen is redrawn and then the parser callback is called with A=1.

If [UP], [DOWN], or [ENTER] are pressed, any entered number is parsed*.

If [2nd]+[QUIT] is pressed, whatever has been entered will be parsed* (no errors thrown nor anything displayed) to OP1, the previous context vectors are restored, SP is restored from (spSave), and the run indicator is turned off.

== Parsing the number ==
ParseInp is called on the data entered, and OP1 is checked to make sure it is REAL (error thrown if not (and this may return to the edit)).
A=0 is passed to the parser callback. B (8006h) is the index into a prompt structure (probably bID = 3). It is expected to return a value in A. Return zero to display the current line (string and number).
It also copies the number in OP1 to the spot bNumIndex points to. If 0,(iy+2Eh) is set, the rest of the line is not erased (then NewLine).

== Menu structure ==
Load as many of these structures, one after the other (zero-terminated), to ramCode/[[83Plus:RAM:8000|appData]] in the order you want it displayed.
Store the length-indexed strings in RAM as well (right after this structure, in ramCode/[[83Plus:RAM:8000|appData]]).

bID can be from 1-6:
bID = 1: display string (cannot select).
bID = 2: display highlightable choices (as in the MODE context). A byte table at 8009h has to do with what is selected here.
bID = 3: display prompt string and number.
bID = 4: display highlightable string.
bID = 5: display menu number (ex. "1:") and prompt string.
bID = 6: hidden, skip displaying this entry.

=== Prompt structure when bID = 1 ===
DB bID ;
DB bNumChoices ;probably always 1
DB bUnknown ;
DW wStringOffset ;offset from start of ramCode

=== Prompt structure when bID = 2 ===
DB bID ;
DB bNumChoices ;
DB bUnknown ;I think this is the number of rows to skip for next item, or something
DW wStringOffset ;offset from start of ramCode /
DB bColumn ;column to display string (this is probably ignored) \ There are bNumChoices of these.

=== Prompt structure when bID = 3 ===
DB bID ;
DB bNumChoices ;probably always 1
DB bNumIndex ;
DW wStringOffset ;offset from start of ramCode

=== Prompt structure when bID = 4 ===
DB bID ;
DB bNumChoices ;probably always 1
DB bUnknown ;
DW wStringOffset ;offset from start of ramCode

=== Prompt structure when bID = 5 ===
DB bID ;
DB bNumEntries ;probably always 1
DB bMenuItemNum ;1 for "1:", 2 for "2:", etc.
DW wStringOffset ;offset from start of ramCode

=== Prompt structure when bID = 6 ===
DB bID ;
DB bNumChoices ;
DB bUnknown ;
DW wStringOffset ;offset from start of ramCode < There are bNumChoices of these.

8038h: bNumIndex above is an offset into a list of floating-point numbers:
DB 00h,80h,00h,00h,00h,00h,00h,00h,00h
== Examples ==
=== Example Code ===
hookBackup equ appBackUpScreen
.db 0BBh,6Dh
ld hl,rawKeyHookPtr
ld de,hookBackup
ld bc,4
ldir
ld a,(flags+34h)
ld (de),a
ld a,(cxCurApp)
push af
ld a,58h
ld (cxCurApp),a
ld hl,structStart
ld de,ramCode
ld bc,structEnd-structStart
ldir
ld hl,dialogCallback
in a,(6)
bcall(_DialogInit)
bcall(_runIndicOff)
bcall(_StartDialog)
bcall(_cursorOff)
bcall(_clrLCDFull)
res appCurWord,(iy+appFlags)
bcall(_ClrTxtShd)
ld hl,cmdShadow
ld de,cmdShadow+1
ld (hl),' '
ld bc,127
ldir
pop af
ld (cxCurApp),a
ld hl,hookBackup
ld de,rawKeyHookPtr
ld bc,4
ldir
ld a,(hl)
ld (flags+34h),a
xor a
bcall(_GetDialogNumOP1)
ld hl,0
ld (penCol),hl
ld a,9
bcall(_DispOP1a)
dialogCallback:
xor a
ret
structStart:
;put your dialog data here
structEnd:
=== Example Table ===
structStart:
.db 1
.db 1
.db 1
.dw sOptions-structStart
.db 5
.db 1
.db 1
.dw sItem1-structStart
.db 5
.db 1
.db 2
.dw sItem2-structStart
.db 2
.db 3
.db 1
.dw sSelect-structStart
.dw sOpt1-structStart
.dw sOpt2-structStart
.db 3
.db 1
.db 0
.dw sNum-structStart
.db 4
.db 1
.db 1
.dw sDone-structStart
.db 0
sOptions:
.db 7,"OPTIONS"
sItem1: .db 5,"Item1"
sItem2: .db 5,"Item2"
sSelect:
.db 6,"Opts: "
sOpt1: .db 4,"Opt1"
sOpt2: .db 4,"Opt2"
sNum: .db 4,"Num="
sDone: .db 4,"Done"
structEnd:

== Credits ==
* Thanks to BrandonW for finding out all this info on the dialog BCALLs and the for the example code, though apparently Detached solutions knew it all along.

83Plus:BCALLs:4C06

2008-04-13T02:56:58Z

TheStorm:

[[Category:83Plus:BCALLs:By_Name:Dialog|DialogInit]] [[Category:83Plus:BCALLs:By_Name|DialogInit]] [[Category:83Plus:BCALLs:By_Address|4C06 - DialogInit]]
== Synopsis ==
'''Official Name:''' DialogInit

'''BCALL Address:''' 4C06

Initializes the dialog context at [[83Plus:RAM:8000|appData]].

=== Inputs ===
* HL: is address of parser callback for any numbers entered.
* A: is page of parser callback for any numbers entered (must be non-zero).
* [[83Plus:RAM:8000|appData]]: menu structure.

=== Outputs ===
* Initializes the dialog context.
=== Destroys ===
* ''unknown''

== Comments ==
* Use [[83Plus:BCALLs:4C03|StartDialog]] to start Dialog
* Use with the other [[:Category:83Plus:BCALLs:By_Name:Dialog|Dialog BCALLs.]]
* [[83Plus:OS:Dialog_context|Info on how to use the Dialog BCALLs]] .
* [http://brandonw.net/calcstuff/ddemo.zip example program]

83Plus:OS:Dialog context

2008-04-13T02:55:48Z

TheStorm: /* Example Table */

[[Category:83Plus:OS_Information|Dialog context]]
This Documentation is for use with the [[:Category:83Plus:BCALLs:By_Name:Dialog|Dialog BCALLS]]

== General Info ==
To start this context, load a menu structure* to ramCode, BCALL DialogInit and then BCALL StartDialog.
You choose whether the run indicator is displayed and whether contexts are allowed (appAllowContext,(iy+appFlags)).
It is imperative that (cxCurApp) be one of the allowed values (use 58h=kExtApps).

If kSolveRoot (SOLVE EDITOR), kStatEd (list editor), or kInfStat (inferential statistic editor) are pressed, the entire screen is redrawn and then the parser callback is called with A=1.

If [UP], [DOWN], or [ENTER] are pressed, any entered number is parsed*.

If [2nd]+[QUIT] is pressed, whatever has been entered will be parsed* (no errors thrown nor anything displayed) to OP1, the previous context vectors are restored, SP is restored from (spSave), and the run indicator is turned off.

== Parsing the number ==
ParseInp is called on the data entered, and OP1 is checked to make sure it is REAL (error thrown if not (and this may return to the edit)).
A=0 is passed to the parser callback. B (8006h) is the index into a prompt structure (probably bID = 3). It is expected to return a value in A. Return zero to display the current line (string and number).
It also copies the number in OP1 to the spot bNumIndex points to. If 0,(iy+2Eh) is set, the rest of the line is not erased (then NewLine).

== Menu structure ==
Load as many of these structures, one after the other (zero-terminated), to ramCode in the order you want it displayed.
Store the length-indexed strings in RAM as well (right after this structure, in ramCode).

bID can be from 1-6:
bID = 1: display string (cannot select).
bID = 2: display highlightable choices (as in the MODE context). A byte table at 8009h has to do with what is selected here.
bID = 3: display prompt string and number.
bID = 4: display highlightable string.
bID = 5: display menu number (ex. "1:") and prompt string.
bID = 6: hidden, skip displaying this entry.

=== Prompt structure when bID = 1 ===
DB bID ;
DB bNumChoices ;probably always 1
DB bUnknown ;
DW wStringOffset ;offset from start of ramCode

=== Prompt structure when bID = 2 ===
DB bID ;
DB bNumChoices ;
DB bUnknown ;I think this is the number of rows to skip for next item, or something
DW wStringOffset ;offset from start of ramCode /
DB bColumn ;column to display string (this is probably ignored) \ There are bNumChoices of these.

=== Prompt structure when bID = 3 ===
DB bID ;
DB bNumChoices ;probably always 1
DB bNumIndex ;
DW wStringOffset ;offset from start of ramCode

=== Prompt structure when bID = 4 ===
DB bID ;
DB bNumChoices ;probably always 1
DB bUnknown ;
DW wStringOffset ;offset from start of ramCode

=== Prompt structure when bID = 5 ===
DB bID ;
DB bNumEntries ;probably always 1
DB bMenuItemNum ;1 for "1:", 2 for "2:", etc.
DW wStringOffset ;offset from start of ramCode

=== Prompt structure when bID = 6 ===
DB bID ;
DB bNumChoices ;
DB bUnknown ;
DW wStringOffset ;offset from start of ramCode < There are bNumChoices of these.

8038h: bNumIndex above is an offset into a list of floating-point numbers:
DB 00h,80h,00h,00h,00h,00h,00h,00h,00h
== Examples ==
=== Example Code ===
hookBackup equ appBackUpScreen
.db 0BBh,6Dh
ld hl,rawKeyHookPtr
ld de,hookBackup
ld bc,4
ldir
ld a,(flags+34h)
ld (de),a
ld a,(cxCurApp)
push af
ld a,58h
ld (cxCurApp),a
ld hl,structStart
ld de,ramCode
ld bc,structEnd-structStart
ldir
ld hl,dialogCallback
in a,(6)
bcall(_DialogInit)
bcall(_runIndicOff)
bcall(_StartDialog)
bcall(_cursorOff)
bcall(_clrLCDFull)
res appCurWord,(iy+appFlags)
bcall(_ClrTxtShd)
ld hl,cmdShadow
ld de,cmdShadow+1
ld (hl),' '
ld bc,127
ldir
pop af
ld (cxCurApp),a
ld hl,hookBackup
ld de,rawKeyHookPtr
ld bc,4
ldir
ld a,(hl)
ld (flags+34h),a
xor a
bcall(_GetDialogNumOP1)
ld hl,0
ld (penCol),hl
ld a,9
bcall(_DispOP1a)
dialogCallback:
xor a
ret
structStart:
;put your dialog data here
structEnd:
=== Example Table ===
structStart:
.db 1
.db 1
.db 1
.dw sOptions-structStart
.db 5
.db 1
.db 1
.dw sItem1-structStart
.db 5
.db 1
.db 2
.dw sItem2-structStart
.db 2
.db 3
.db 1
.dw sSelect-structStart
.dw sOpt1-structStart
.dw sOpt2-structStart
.db 3
.db 1
.db 0
.dw sNum-structStart
.db 4
.db 1
.db 1
.dw sDone-structStart
.db 0
sOptions:
.db 7,"OPTIONS"
sItem1: .db 5,"Item1"
sItem2: .db 5,"Item2"
sSelect:
.db 6,"Opts: "
sOpt1: .db 4,"Opt1"
sOpt2: .db 4,"Opt2"
sNum: .db 4,"Num="
sDone: .db 4,"Done"
structEnd:

== Credits ==
* Thanks to BrandonW for finding out all this info on the dialog BCALLs and the for the example code, though apparently Detached solutions knew it all along.

83Plus:OS:Dialog context

2008-04-13T02:54:21Z

TheStorm:

[[Category:83Plus:OS_Information|Dialog context]]
This Documentation is for use with the [[:Category:83Plus:BCALLs:By_Name:Dialog|Dialog BCALLS]]

== General Info ==
To start this context, load a menu structure* to ramCode, BCALL DialogInit and then BCALL StartDialog.
You choose whether the run indicator is displayed and whether contexts are allowed (appAllowContext,(iy+appFlags)).
It is imperative that (cxCurApp) be one of the allowed values (use 58h=kExtApps).

If kSolveRoot (SOLVE EDITOR), kStatEd (list editor), or kInfStat (inferential statistic editor) are pressed, the entire screen is redrawn and then the parser callback is called with A=1.

If [UP], [DOWN], or [ENTER] are pressed, any entered number is parsed*.

If [2nd]+[QUIT] is pressed, whatever has been entered will be parsed* (no errors thrown nor anything displayed) to OP1, the previous context vectors are restored, SP is restored from (spSave), and the run indicator is turned off.

== Parsing the number ==
ParseInp is called on the data entered, and OP1 is checked to make sure it is REAL (error thrown if not (and this may return to the edit)).
A=0 is passed to the parser callback. B (8006h) is the index into a prompt structure (probably bID = 3). It is expected to return a value in A. Return zero to display the current line (string and number).
It also copies the number in OP1 to the spot bNumIndex points to. If 0,(iy+2Eh) is set, the rest of the line is not erased (then NewLine).

== Menu structure ==
Load as many of these structures, one after the other (zero-terminated), to ramCode in the order you want it displayed.
Store the length-indexed strings in RAM as well (right after this structure, in ramCode).

bID can be from 1-6:
bID = 1: display string (cannot select).
bID = 2: display highlightable choices (as in the MODE context). A byte table at 8009h has to do with what is selected here.
bID = 3: display prompt string and number.
bID = 4: display highlightable string.
bID = 5: display menu number (ex. "1:") and prompt string.
bID = 6: hidden, skip displaying this entry.

=== Prompt structure when bID = 1 ===
DB bID ;
DB bNumChoices ;probably always 1
DB bUnknown ;
DW wStringOffset ;offset from start of ramCode

=== Prompt structure when bID = 2 ===
DB bID ;
DB bNumChoices ;
DB bUnknown ;I think this is the number of rows to skip for next item, or something
DW wStringOffset ;offset from start of ramCode /
DB bColumn ;column to display string (this is probably ignored) \ There are bNumChoices of these.

=== Prompt structure when bID = 3 ===
DB bID ;
DB bNumChoices ;probably always 1
DB bNumIndex ;
DW wStringOffset ;offset from start of ramCode

=== Prompt structure when bID = 4 ===
DB bID ;
DB bNumChoices ;probably always 1
DB bUnknown ;
DW wStringOffset ;offset from start of ramCode

=== Prompt structure when bID = 5 ===
DB bID ;
DB bNumEntries ;probably always 1
DB bMenuItemNum ;1 for "1:", 2 for "2:", etc.
DW wStringOffset ;offset from start of ramCode

=== Prompt structure when bID = 6 ===
DB bID ;
DB bNumChoices ;
DB bUnknown ;
DW wStringOffset ;offset from start of ramCode < There are bNumChoices of these.

8038h: bNumIndex above is an offset into a list of floating-point numbers:
DB 00h,80h,00h,00h,00h,00h,00h,00h,00h
== Examples ==
=== Example Code ===
hookBackup equ appBackUpScreen
.db 0BBh,6Dh
ld hl,rawKeyHookPtr
ld de,hookBackup
ld bc,4
ldir
ld a,(flags+34h)
ld (de),a
ld a,(cxCurApp)
push af
ld a,58h
ld (cxCurApp),a
ld hl,structStart
ld de,ramCode
ld bc,structEnd-structStart
ldir
ld hl,dialogCallback
in a,(6)
bcall(_DialogInit)
bcall(_runIndicOff)
bcall(_StartDialog)
bcall(_cursorOff)
bcall(_clrLCDFull)
res appCurWord,(iy+appFlags)
bcall(_ClrTxtShd)
ld hl,cmdShadow
ld de,cmdShadow+1
ld (hl),' '
ld bc,127
ldir
pop af
ld (cxCurApp),a
ld hl,hookBackup
ld de,rawKeyHookPtr
ld bc,4
ldir
ld a,(hl)
ld (flags+34h),a
xor a
bcall(_GetDialogNumOP1)
ld hl,0
ld (penCol),hl
ld a,9
bcall(_DispOP1a)
dialogCallback:
xor a
ret
structStart:
;put your dialog data here
structEnd:
=== Example Table ===
structStart:
.db 1
.db 1
.db 1
.dw sOptions-structStart

.db 5
.db 1
.db 1
.dw sItem1-structStart

.db 5
.db 1
.db 2
.dw sItem2-structStart

.db 2
.db 3
.db 1
.dw sSelect-structStart
.dw sOpt1-structStart
.dw sOpt2-structStart

.db 3
.db 1
.db 0
.dw sNum-structStart

.db 4
.db 1
.db 1
.dw sDone-structStart

.db 0
sOptions:
.db 7,"OPTIONS"
sItem1: .db 5,"Item1"
sItem2: .db 5,"Item2"
sSelect:
.db 6,"Opts: "
sOpt1: .db 4,"Opt1"
sOpt2: .db 4,"Opt2"
sNum: .db 4,"Num="
sDone: .db 4,"Done"
structEnd:

== Credits ==
* Thanks to BrandonW for finding out all this info on the dialog BCALLs and the for the example code, though apparently Detached solutions knew it all along.

83Plus:BCALLs:4FE1

2008-04-13T02:46:56Z

TheStorm:

[[Category:83Plus:BCALLs:By_Name:Dialog|ResDialogKeyOverride]] [[Category:83Plus:BCALLs:By_Name|ResDialogKeyOverride]] [[Category:83Plus:BCALLs:By_Address|4C18 - ResDialogKeyOverride]]
== Synopsis ==
'''Official Name:''' ResDialogKeyOverride

'''BCALL Address:''' 4C18

This is the key hook used by the dialog routines. It actually runs "add a,e." *sigh*

=== Inputs ===
* ''none''

=== Outputs ===
* ''none''

=== Destroys ===
* ''unknown''

== Comments ==
* Use with the other [[:Category:83Plus:BCALLs:By_Name:Dialog|Dialog BCALLs.]]
* [[83Plus:OS:Dialog_context|Info on how to use the Dialog BCALLs]] .

83Plus:BCALLs:4C18

2008-04-13T02:44:15Z

TheStorm:

[[Category:83Plus:BCALLs:By_Name:Dialog|ResDialogKeyOverride]] [[Category:83Plus:BCALLs:By_Name|ResDialogKeyOverride]] [[Category:83Plus:BCALLs:By_Address|4C18 - ResDialogKeyOverride]]
== Synopsis ==
'''Official Name:''' ResDialogKeyOverride

'''BCALL Address:''' 4C18

Disables the callback routine to handle keypresses.

=== Inputs ===
* ''none''

=== Outputs ===
* ''none''
=== Destroys ===
* ''unknown''

== Comments ==
* Use with the other [[:Category:83Plus:BCALLs:By_Name:Dialog|Dialog BCALLs.]]
* [[83Plus:OS:Dialog_context|Info on how to use the Dialog BCALLs]] .

83Plus:BCALLs:4CD

2008-04-13T02:40:39Z

TheStorm: