WikiTI - User contributions [en]

Z80 Routines:Input:GetCSC

2017-08-20T20:44:36Z

Geekboy:

[[Category:Z80 Routines:Input|GetCSC]]
[[Category:Z80 Routines|GetCSC]]

This is a replacement for the GetCSC routine. Its returns are exactly the same. You need to have a variable called lastKey so keys won't repeat. Unless you want that. Feel free to add versions with fun stuff like controlled repeating.

<nowiki>;====== GetCSC clone ===========================================================
; This routine is a replacement for the GetCSC bcall. Its returns are the same.
; Inputs:
; - None
; Outputs:
; - A: Keycode
; Destroys:
; - AF, BC

; To do: Add debouncing

GetCloneSC:
; push bc ; uncomment for preserving bc
ld c, 0BFh
ld b, 7
getCSCloop:
ld a, c
out (1), a
nop
nop
nop
rrca
ld c, a
in a, (1)
cp 0ffh
jr nz, getCSCgotCSC
djnz getCSCloop
xor a
ld (lastKey), a
; pop bc
ret
getCSCgotCSC:
dec b
ld c, b
call getResetBit
ld a, b
sla c
sla c
sla c
add a, c
ld b, a ; This dance ensures that
ld a, (lastKey) ; the keycode is returned in A
ld c, a
ld a, b
cp c
ld (lastKey), a
jr nz, getCSCgoodCSC
xor a
getCSCgoodCSC:
; pop bc
ret

getResetBit:
cp $FF
ret z
ld b, 0
getResetBitLoop:
rrca
inc b
jr c, getResetBitLoop
ret</nowiki>

==== Alternative Version ====

This has debouncing?

<nowiki>;Getcsc replacement by James Montelongo
; Outputs:
; - A: Keycode
; Destroys:
; - AF
gsGetK:
gsGetCSC:
push hl
push de
push bc
ld e,$fe ;frist group
ld c,$01 ;key port
ld l,0 ;l holds key pressed
cscloop:
ld a,$ff ;For some reason emulator really wants it in the loop
out (1),a ;reset keyport
ld h,$fe
out (c),e ;set keygroup
ld b,8 ;loop, Delay needed when work with key driver
in a,(c) ;read key
cscbit:
inc l ;inc to get key pressed
rra ; if key pressed done
jp nc,donecsc
rlc h
djnz cscbit ;loop 8
rlc e ;next key group
jp m,cscloop ;if bit 7 set loop
ld l,0 ;if no key pressed 0
donecsc:
ld a,$ff
out (1),a
ld a,e
cpl
out (1),a
nop
nop
in a,(1)
inc a
jp z,nootherkeypressed
ld l,0
nootherkeypressed:
ld a,$ff
out (1),a
nop
ld a,e
out (1),a
nop
nop
in a,(1)
cp h
jr z,only1key
ld l,0
only1key:
ld a,l ;
or a
ld (gs_keymem),a
pop bc
pop de
pop hl
ret</nowiki>

Z80 Routines:Input:GetCSC

2017-08-20T19:13:05Z

Geekboy:

[[Category:Z80 Routines:Input|GetCSC]]
[[Category:Z80 Routines|GetCSC]]

This is a replacement for the GetCSC routine. Its returns are exactly the same. You need to have a variable called lastKey so keys won't repeat. Unless you want that. Feel free to add versions with fun stuff like controlled repeating.

<nowiki>;====== GetCSC clone ===========================================================
; This routine is a replacement for the GetCSC bcall. Its returns are the same.
; Inputs:
; - None
; Outputs:
; - A: Keycode
; Destroys:
; - AF, BC

; To do: Add debouncing

GetCloneSC:
; push bc ; uncomment for preserving bc
ld c, 0BFh
ld b, 7
getCSCloop:
ld a, c
out (1), a
nop
nop
nop
rrca
ld c, a
in a, (1)
cp 0ffh
jr nz, getCSCgotCSC
djnz getCSCloop
xor a
ld (lastKey), a
pop bc
ret
getCSCgotCSC:
dec b
ld c, b
call getResetBit
ld a, b
sla c
sla c
sla c
add a, c
ld b, a ; This dance ensures that
ld a, (lastKey) ; the keycode is returned in A
ld c, a
ld a, b
cp c
ld (lastKey), a
jr nz, getCSCgoodCSC
xor a
getCSCgoodCSC:
; pop bc
ret

getResetBit:
cp $FF
ret z
ld b, 0
getResetBitLoop:
rrca
inc b
jr c, getResetBitLoop
ret</nowiki>

==== Alternative Version ====

This has debouncing?

<nowiki>;Getcsc replacement by James Montelongo
; Outputs:
; - A: Keycode
; Destroys:
; - AF
gsGetK:
gsGetCSC:
push hl
push de
push bc
ld e,$fe ;frist group
ld c,$01 ;key port
ld l,0 ;l holds key pressed
cscloop:
ld a,$ff ;For some reason emulator really wants it in the loop
out (1),a ;reset keyport
ld h,$fe
out (c),e ;set keygroup
ld b,8 ;loop, Delay needed when work with key driver
in a,(c) ;read key
cscbit:
inc l ;inc to get key pressed
rra ; if key pressed done
jp nc,donecsc
rlc h
djnz cscbit ;loop 8
rlc e ;next key group
jp m,cscloop ;if bit 7 set loop
ld l,0 ;if no key pressed 0
donecsc:
ld a,$ff
out (1),a
ld a,e
cpl
out (1),a
nop
nop
in a,(1)
inc a
jp z,nootherkeypressed
ld l,0
nootherkeypressed:
ld a,$ff
out (1),a
nop
ld a,e
out (1),a
nop
nop
in a,(1)
cp h
jr z,only1key
ld l,0
only1key:
ld a,l ;
or a
ld (gs_keymem),a
pop bc
pop de
pop hl
ret</nowiki>

Axe

2015-01-01T21:32:02Z

Geekboy:

[[Category:83Plus:Software|Axe Parser]]

=== '''Axe Parser''' ===

It is a new programming language for the calculator. It is typed directly into a program just like BASIC and with a similar syntax. Unlike BASIC however, this is a compiled language, not an interpreted one. The program gets compiled into an assembly program. You can create Ion, MirageOS, DCS or Applications if you choose.

'''Advantages:'''
You basically get the simplicity of BASIC programming but with nearly the same size, speed, and compatibility of assembly programs. You won’t need “Shells” or “Libraries” to run the programs. They are just like any other assembly program.

'''Syntax:'''
It is similar to BASIC. First, it has an extremely loose syntax. You know how you can leave the end parenthesis off of BASIC commands and do multiple same-line DelVars? It’s like that on steroids (if you so choose). For instance: the store “->” can be used in expressions like A+B->C+1->D so now C holds A+B and D holds A+B+1.

'''Differences With BASIC:'''
A lot of commands will be re-defined. Most are usually unused anyway, but some are not. For instance, “DiagnosticOff” turns off the run indicator. But “sub()” now runs a subroutine since taking a set of characters from a string is as easy as copying part of the string to another portion in RAM.

'''Variables and Numbers:'''
All numbers and letters A-Z are 16-bit unsigned integers. Str, GDB and Pic define an arbitrary amount of data, which is stored inside program memory.

'''User Defined Variables:'''
Things like strings, lists, sprites, and floats will be defined by the user.

''Examples''

:ClrHome
:Disp "Hello World"
:Repeat getKey
:End

Axe's syntax is pretty much TI Basic's syntax, but its speed and capabilities are way ahead of Basic.

Axe was created and is developed by Quigibo/Kevin Horowitz.

Download link: [https://www.omnimaga.org/the-axe-parser-project/latest-updates-%28***do-not-post-here!***%29/ Download Here]

Category:84PCSE:BCALLs:By Name:Text

2014-08-03T01:38:19Z

Geekboy: Created page with 'Text'

[[Category:84PCSE:BCALLs:By Name|Text]]

84PCSE:BCALLs:4555

2014-08-03T01:36:55Z

Geekboy:

[[Category:84PCSE:BCALLs:By Name|VPutMap]] [[Category:84PCSE:BCALLs:By Address|44F8 - VPutMap]][[Category:84PCSE:BCALLs:By Name:Drawing|VPutMap]][[Category:84PCSE:BCALLs:By Name:Text|VPutMap]]
== Synopsis ==
'''Hypothesized Official Name:''' VPutMap

'''BCALL Address:''' 4555h

Displays a character at ([[84PCSE:RAM:8782|penCol]],[[84PCSE:RAM:8784|penRow]])

=== Inputs ===
* A = character to display
* ([[84PCSE:RAM:8782|penCol]]), ([[84PCSE:RAM:8784|penRow]]) = (X,Y) To display the character at
* [[84PCSE:Flags:14#Bit_4|penDrawColor]] = 1 to use penFGColor/penBGColor (0 to use black/white)
* ([[84PCSE:RAM:A038|penFGColor]]) = foreground color
* ([[84PCSE:RAM:A036|penBGColor]]) = background color
* [[84PCSE:Flags:32#Bit_7|penEraseBelow]] = 1 to erase a two-pixel border below the character
* [[84PCSE:Flags:32#Bit_2|penFontSelect]] = 1 for Large font 0 for Normal
* [[84PCSE:Flags:11#Bit_3|VerticalSplitBit]] = 1 Tells the routine you are in vertical split mode
=== Outputs ===
* Character displayed

=== Destroys ===
* Interrupts disabled

* [[84PCSE:RAM:8463|lFont_record]]
== Comments ==
* [[84PCSE:Flags:32#Bit_6|Unknown]] : Seems todo something similar to [[84PCSE:Flags:32#Bit_2|penFontSelect]] needs more research

84PCSE:BCALLs:4555

2014-08-03T01:34:17Z

Geekboy: Created page with 'VPutMap 44F8 - VPutMap == Synopsis == '''Hypothesized Official Name:''' VPutMap '''BCALL Address:''' 455…'

[[Category:84PCSE:BCALLs:By Name|VPutMap]] [[Category:84PCSE:BCALLs:By Address|44F8 - VPutMap]]
== Synopsis ==
'''Hypothesized Official Name:''' VPutMap

'''BCALL Address:''' 4555h

Displays a character at ([[84PCSE:RAM:8782|penCol]],[[84PCSE:RAM:8784|penRow]])

=== Inputs ===
* A = character to display
* ([[84PCSE:RAM:8782|penCol]]), ([[84PCSE:RAM:8784|penRow]]) = (X,Y) To display the character at
* [[84PCSE:Flags:14#Bit_4|penDrawColor]] = 1 to use penFGColor/penBGColor (0 to use black/white)
* ([[84PCSE:RAM:A038|penFGColor]]) = foreground color
* ([[84PCSE:RAM:A036|penBGColor]]) = background color
* [[84PCSE:Flags:32#Bit_7|penEraseBelow]] = 1 to erase a two-pixel border below the character
* [[84PCSE:Flags:32#Bit_2|penFontSelect]] = 1 for Large font 0 for Normal
* [[84PCSE:Flags:11#Bit_3|VerticalSplitBit]] = 1 Tells the routine you are in vertical split mode
=== Outputs ===
* Character displayed

=== Destroys ===
* Interrupts disabled

* [[84PCSE:RAM:8463|lFont_record]]
== Comments ==
* [[84PCSE:Flags:32#Bit_6|Unknown]] : Seems todo something similar to [[84PCSE:Flags:32#Bit_2|penFontSelect]] needs more research

Category:84PCSE:BCALLs

2014-08-03T01:02:00Z

Geekboy:

[[Category:84PCSE|System Calls (BCALLs)]]
This is a list of documented and undocumented system calls on the TI-84+CSE Edition Calculator.

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

Category:84PCSE:BCALLs

2014-08-03T01:00:55Z

Geekboy: Created page with 'System Calls (BCALLs) This is a list of documented and undocumented system calls on the TI-83+ family. Please read our page on Contributing before editin…'

[[Category:84PCSE|System Calls (BCALLs)]]
This is a list of documented and undocumented system calls on the TI-83+ family.

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

84PCSE:RAM:8797

2014-07-27T17:53:34Z

Geekboy: moved 84PCSE:RAM:8797 to 84PCSE:RAM:8798: URL and Ram address did not match. Obviously a typo

#REDIRECT [[84PCSE:RAM:8798]]

84PCSE:RAM:8798

2014-07-27T17:53:34Z

Geekboy: moved 84PCSE:RAM:8797 to 84PCSE:RAM:8798: URL and Ram address did not match. Obviously a typo

[[Category:84PCSE:RAM:By Address|8798 - saveSScreen]][[Category:84PCSE:RAM:By Name|saveSScreen]]
== Synopsis ==

'''Hypothesized Official Name:''' saveSScreen

'''Memory Address:''' 8798

'''Length:''' 768 bytes

This appears to be the same as the old [[83Plus:RAM:86EC|saveSScreen]]. It can generally be used for scrap RAM.

== Comments ==

saveSScreen used to be used for storing a bitmap image of the screen after powering-off. It is clearly not large enough to be used for that purpose now.

The OS never appears to touch this area. I suspect it's here at the behest of the Verilog and/or IQ Joe guys, in order to give them (and by extension, us) scrap RAM.

See also [[84PCSE:RAM:987C|plotSScreen]] for another 768 byte block of scrap RAM.

84PCSE:RAM:987C

2014-07-27T17:49:59Z

Geekboy: /* Synopsis */

[[Category:84PCSE:RAM:By Address|9340 - plotSScreen]][[Category:84PCSE:RAM:By Name|plotSScreen]]
== Synopsis ==

'''Hypothesized Official Name:''' plotSScreen

'''Memory Address:''' 987Ch

'''Length:''' 768 bytes

This appears to be the same as the old [[83Plus:RAM:9340|plotSScreen]]. It can generally be used for scrap RAM.

== Comments ==

plotSScreen used to be used for storing a bitmap image of the graph screen. It is clearly not large enough to be used for that purpose now.

The OS never appears to touch this area. I suspect it's here at the behest of the Verilog and/or IQ Joe guys, in order to give them (and by extension, us) scrap RAM.

See also [[84PCSE:RAM:8797|saveSScreen]] for another 768 byte block of scrap RAM.

83Plus:OS:Certificate/Headers:Fields:Application Headers

2013-06-13T04:05:06Z

Geekboy:

[[Category:83Plus:OS:Certificate/Headers:Fields_By_Number|Application Headers]] [[Category:83Plus:OS:Certificate/Headers:Fields:Application Headers|Application Headers]]

In the past, people liked to treat application headers as structs with fixed positions for everything. This is '''wrong.''' A valid application header must: Start with a master field ([[http://wikiti.brandonw.net/index.php?title=Category:83Plus:OS:Certificate/Headers:Fields:800|800]]), end with a final field ([[83Plus:OS:Certificate/Headers:Fields:807|807]]), contain a name field ([[83Plus:OS:Certificate/Headers:Fields:804|804]]), a key ID field ([[83Plus:OS:Certificate/Headers:Fields:801|801]]), a page count ([[83Plus:OS:Certificate/Headers:Fields:808|808]]), and a date stamp field ([[83Plus:OS:Certificate/Headers:Fields:032|032]]+[[83Plus:OS:Certificate/Headers:Fields:090|090]]) followed by a date stamp signature field ([[83Plus:OS:Certificate/Headers:Fields:020|020]]). Aside from the opening field being first, closing field being last, and dates stamp signature following the date stamp, those fields can be in '''any order.''' You may also specify a build ([[83Plus:OS:Certificate/Headers:Fields:803|803]]) and revision ([[83Plus:OS:Certificate/Headers:Fields:802|802]]) and disable the TI splash screen ([[83Plus:OS:Certificate/Headers:Fields:809|809]]). There's also support for some other stuff, but it is all optional.

In theory, it is legal to specify the master field as 800D xxxx if the application is less than 64 K in size. However, rabbitsign won't sign it.

The name field can be less than 8 bytes, so you do not have to pad app names out to 8 bytes. You can also specify an app name greater than 8 bytes, but the calculator will ignore everything past the 8th byte.

The date stamp signature never actually gets checked, so you can put garbage there. But it gets better! You can also just specify the date stamp signature as having zero length. You can also pull a similar stunt with the date stamp itself.

The final field is usually written as 807F00000000. That four byte length field is ignored, so you can just put 8070 instead.

People like to pad the application header until it is 128 bytes in size. That is not necessary. Execution starts after the app header.

<nowiki> ; Minimal application. This application is just 31 bytes! And takes up 16 K of archive space!
; Master Field
.db 80h, 0Fh, 0, 0, 0, 0
; Name
.db 80h, 43h, "nop"
; Disable TI splash screen.
.db 80h, 90h
; Pages
.db 80h, 81h, 1
; Signing Key ID
.db 80h, 12h, 1, 4 ; or 15 for the TI-84+CSE
; Date stamp. Apparently, the calculator doesn't mind if you put
; nothing in this.
.db 03h, 22h, 09h, 00h
; Date stamp signature. Since nothing ever checks this, there's no
; reason ever to update it. Or even have data in it.
.db 02h, 00
; Final field
.db 80h, 70h
b_call(_JForceCmdNoChar)
</nowiki>

83Plus:OS:Certificate/Headers:Fields:Application Headers

2013-06-13T03:12:37Z

Geekboy:

[[Category:83Plus:OS:Certificate/Headers:Fields_By_Number|Application Headers]] [[Category:83Plus:OS:Certificate/Headers:Fields:Application Headers|Application Headers]]

In the past, people liked to treat application headers as structs with fixed positions for everything. This is '''wrong.''' A valid application header must: Start with a master field ([[http://wikiti.brandonw.net/index.php?title=Category:83Plus:OS:Certificate/Headers:Fields:800|800]]), end with a final field ([[83Plus:OS:Certificate/Headers:Fields:807|807]]), contain a name field ([[83Plus:OS:Certificate/Headers:Fields:804|804]]), a key ID field ([[83Plus:OS:Certificate/Headers:Fields:801|801]]), a page count ([[83Plus:OS:Certificate/Headers:Fields:808|808]]), and a date stamp field ([[83Plus:OS:Certificate/Headers:Fields:032|032]]+[[83Plus:OS:Certificate/Headers:Fields:090|090]]) followed by a date stamp signature field ([[83Plus:OS:Certificate/Headers:Fields:020|020]]). Aside from the opening field being first, closing field being last, and dates stamp signature following the date stamp, those fields can be in '''any order.''' You may also specify a build ([[83Plus:OS:Certificate/Headers:Fields:803|803]]) and revision ([[83Plus:OS:Certificate/Headers:Fields:802|802]]) and disable the TI splash screen ([[83Plus:OS:Certificate/Headers:Fields:809|809]]). There's also support for some other stuff, but it is all optional.

In theory, it is legal to specify the master field as 800D xxxx if the application is less than 64 K in size. However, rabbitsign won't sign it.

The name field can be less than 8 bytes, so you do not have to pad app names out to 8 bytes. You can also specify an app name greater than 8 bytes, but the calculator will ignore everything past the 8th byte.

The date stamp signature never actually gets checked, so you can put garbage there. But it gets better! You can also just specify the date stamp signature as having zero length. You can also pull a similar stunt with the date stamp itself.

The final field is usually written as 807F00000000. That four byte length field is ignored, so you can just put 8070 instead.

People like to pad the application header until it is 128 bytes in size. That is not necessary. Execution starts after the app header.

<nowiki> ; Minimal application. This application is just 31 bytes! And takes up 16 K of archive space!
; Master Field
.db 80h, 0Fh, 0, 0, 0, 0
; Name
.db 80h, 48h, "nop"
; Disable TI splash screen.
.db 80h, 90h
; Pages
.db 80h, 81h, 1
; Signing Key ID
.db 80h, 12h, 1, 4 ; or 15 for the TI-84+CSE
; Date stamp. Apparently, the calculator doesn't mind if you put
; nothing in this.
.db 03h, 22h, 09h, 00h
; Date stamp signature. Since nothing ever checks this, there's no
; reason ever to update it. Or even have data in it.
.db 02h, 00
; Final field
.db 80h, 70h
b_call(_JForceCmdNoChar)
</nowiki>

83Plus:BCALLs:4E70

2013-02-23T06:42:17Z

Geekboy: /* Comments */

[[Category:83Plus:BCALLs:By Name|CreateVar]][[Category:83Plus:BCALLs:By Name:Variable|CreateVar]][[Category:83Plus:BCALLs:By Address|4E70 - CreateVar]]
== Synopsis ==
'''Official Name:''' CreateVar

'''BCALL Address:''' 4E70

Creates a variable of a specified type.

=== Inputs ===
* A: type of variable to create (05h for programs, 06h for protected programs, etc.)
* HL: length in bytes
* [[83Plus:RAM:8478|OP1]]+1 = name of variable

=== Outputs ===
* HL points to symbol table entry
* DE points to data section
* [[83Plus:RAM:8499|OP4]] contains the name as inputted in [[83Plus:RAM:8478|OP1]]

=== Registers Destroyed ===
* AF,BC,[[83Plus:RAM:8478|OP1]],[[83Plus:RAM:8483|OP2]]

== Comments ==
If the length of name is shorter than 8 characters it must be zero-terminated. If there isn't enough RAM a memory error will be generated. Contents of the program are random.<br /><br />
This Seems to leak memory when creating variables. ~ Geekboy1011

== Example ==
Create an unprotected program of size 10:

ld hl,progName-1
RST rMov9ToOP1
ld hl,10
ld a,05h
B_CALL CreateVar

progName: db "PROGNAME"

83Plus:BCALLs:42F1

2013-01-17T05:57:27Z

Geekboy:

[[Category:83Plus:BCALLs:By Name:Variable|ChkFindSym]] [[Category:83Plus:BCALLs:By Name|ChkFindSym]] [[Category:83Plus:BCALLs:By Address|42F1 - ChkFindSym]]
== Synopsis ==
'''Official Name:''' ChkFindSym

'''BCALL Address:''' 42F1

Recalls various pointers and information for a symbol in the VAT.

=== Inputs ===
* [[83Plus:RAM:8478|OP1]] = Name of variable (with proper initial defining byte, see example)

=== Outputs ===
* [[83Plus:RAM:8478|OP1]] = Name of variable
* HL = VAT pointer
* DE = Data location (if in archive, will be address when page is put into [[83Plus:Ports:06|bank A]])
* B = Flash Page, or 0 if in RAM
* C = Length of Variable Name
* A = the lower 5 bits is the type. Use the mask 1Fh.
* carry flag is set if the variable is not found in the VAT

=== Registers Destroyed ===
'All'

== Example ==
<nowiki>
ld hl,varname
B_CALL Mov9toOp1
B_CALL ChkFindSym
jr c,notfound ;carry flag is set if the VAT entry is not found
ex de,hl ;put data pointer into hl
xor a
cp b ;see if b is 0, and the program is in the ram
jr z,unarchived ;if so, jump to unarchived

;do something to get it into RAM

unarchived:

;do something once it is in RAM

varName:
.db AppVarObj, "APPVAR",0
</nowiki>

83Plus:Flags:3E

2013-01-12T06:21:13Z

Geekboy: /* Bit 0 */

[[Category:83Plus:Flags:By Address|3E]]
[[Category:83Plus:Flags:By Name|silentLinkFlags]]
== Synopsis ==
'''Flag Byte:''' 3Eh

'''Known Names:''' silentLinkFlags
== Bit Overview ==

=== Bit 0 ===
'''Official Name:''' silentLinkActive

Resetting disables Link Assist during the get key routines.
Naming is based off BrandonW's include file, needs some updating.

=== Bit 1 ===
{{Unknown-flag}}

=== Bit 2 ===
{{Unknown-flag}}

=== Bit 3 ===
{{Unknown-flag}}

=== Bit 4 ===
{{Unknown-flag}}

=== Bit 5 ===
{{Unknown-flag}}

=== Bit 6 ===
{{Unknown-flag}}

=== Bit 7 ===
{{Unknown-flag}}

== Credits and Contributions ==
* BrandonW for documenting it.
* Geekboy1011 for adding it to the wiki

83Plus:Flags:3E

2012-11-01T22:09:08Z

Geekboy:

[[Category:83Plus:Flags:By Address|3E]]
[[Category:83Plus:Flags:By Name|silentLinkFlags]]
== Synopsis ==
'''Flag Byte:''' 3Eh

'''Known Names:''' silentLinkFlags
== Bit Overview ==

=== Bit 0 ===
'''Official Name:''' silentLinkActive

Disables Link Assist during the get key routines.
Naming is based off BrandonW's include file, needs some updating.

=== Bit 1 ===
{{Unknown-flag}}

=== Bit 2 ===
{{Unknown-flag}}

=== Bit 3 ===
{{Unknown-flag}}

=== Bit 4 ===
{{Unknown-flag}}

=== Bit 5 ===
{{Unknown-flag}}

=== Bit 6 ===
{{Unknown-flag}}

=== Bit 7 ===
{{Unknown-flag}}

== Credits and Contributions ==
* BrandonW for documenting it.
* Geekboy1011 for adding it to the wiki

83Plus:Flags:3E

2012-11-01T22:08:43Z

Geekboy:

[[Category:83Plus:Flags:By Address|3E, 3e]]
[[Category:83Plus:Flags:By Name|silentLinkFlags]]
== Synopsis ==
'''Flag Byte:''' 3Eh

'''Known Names:''' silentLinkFlags
== Bit Overview ==

=== Bit 0 ===
'''Official Name:''' silentLinkActive

Disables Link Assist during the get key routines.
Naming is based off BrandonW's include file, needs some updating.

=== Bit 1 ===
{{Unknown-flag}}

=== Bit 2 ===
{{Unknown-flag}}

=== Bit 3 ===
{{Unknown-flag}}

=== Bit 4 ===
{{Unknown-flag}}

=== Bit 5 ===
{{Unknown-flag}}

=== Bit 6 ===
{{Unknown-flag}}

=== Bit 7 ===
{{Unknown-flag}}

== Credits and Contributions ==
* BrandonW for documenting it.
* Geekboy1011 for adding it to the wiki

83Plus:Flags:3E

2012-11-01T22:07:10Z

Geekboy: Created page with '3E silentLinkFlags == Synopsis == '''Flag Byte:''' 3Eh '''Known Names:''' silentLinkFlags == Bit Overvie…'

[[Category:83Plus:Flags:By Address|3E]]
[[Category:83Plus:Flags:By Name|silentLinkFlags]]

== Synopsis ==
'''Flag Byte:''' 3Eh

'''Known Names:''' silentLinkFlags
== Bit Overview ==

=== Bit 0 ===
'''Official Name:''' silentLinkActive

Disables Link Assist during the get key routines.
Naming is based off BrandonW's include file, needs some updating.

=== Bit 1 ===
{{Unknown-flag}}

=== Bit 2 ===
{{Unknown-flag}}

=== Bit 3 ===
{{Unknown-flag}}

=== Bit 4 ===
{{Unknown-flag}}

=== Bit 5 ===
{{Unknown-flag}}

=== Bit 6 ===
{{Unknown-flag}}

=== Bit 7 ===
{{Unknown-flag}}

== Credits and Contributions ==
* BrandonW for documenting it.
* Geekboy1011 for adding it to the wiki