WikiTI - User contributions [en]

Talk:WikiTI Home

2006-10-19T16:24:09Z

TD-Linux: /* Not "hardware" specific documents */

= Discussion =
What do you think about this wiki?

== More! ==

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

Timendus

== I hope we can do that soon ==

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

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

== Categories ==

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

== Move them? ==

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

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

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

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

== Caching ==

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

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

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

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

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

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

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

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

== On Other Calculators ==

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

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

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

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

== Not "hardware" specific documents ==

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

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

== Required logon ==

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

== Wiki update ==

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

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

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

Teams:Revsoft

2006-10-19T16:03:03Z

TD-Linux:

{{stub}}
== Worthless Nothingness ==
Wowee, I made a page for Revsoft! I'm not even a staff member, oh well.

== Staff members that have actually looked here o.O ==
I'm not a staff member, yay! [[User:TD-Linux|TD-Linux]] 08:13, 19 October 2006 (PDT)

[[Category:Teams|Revsoft]]

Teams:Revsoft

2006-10-19T15:19:00Z

TD-Linux:

== Worthless Nothingness ==
Wowee, I made a page for Revsoft! I'm not even a staff member, oh well.

== Staff members that have actually looked here o.O ==
I'm not a staff member, yay! [[User:TD-Linux|TD-Linux]] 08:13, 19 October 2006 (PDT)

[[Category:Teams|Revsoft]]

Teams:Revsoft

2006-10-19T15:17:41Z

TD-Linux:

Teams:Revsoft

2006-10-19T15:13:57Z

TD-Linux:

83Plus:Software:usb8x/Supported Devices

2006-10-19T15:08:50Z

TD-Linux: /* Should Work */

Most USB devices that are self-powered, or draw 100mA or less current from the USB bus should be compatible with usb8x. Below is a list of device classes and specific devices that have been tested. Devices that require isochronous endpoints or have an integrated USB hub are not currently compatible.

== Internal Driver ==
These devices work and usb8x contains an internal driver to control them.
* HID Keyboard
* HID Mouse
* Mass Storage Device. Tested with:
** Sandisk Cruzer
** Lexar JumpDrive/Secure
** SMI Corp USB Disk
** 512 Mini Disk Genie
** PQI Intelligent Stick
* TI Silverlink
* Some gamepad controllers. Tested with:
** Logitech Precision Gamepad
** Logitech Dual Action Gamepad (only the buttons, the D-pad and joysticks don't work)
** [http://www.retrousb.com/nintendo.html RetroZone NES pad]
** [http://www.planetgamecube.com/hardArt.cfm?artid=2459 Skillz Gamecube to USB] (The company no longer seems to exist.)
* Vernier EasyTemp

== External Driver ==
These devices work and an external driver exists to control them.
* None

== Works, No Complete Driver ==
These devices have been tested to work with usb8x, but no complete driver currently exists.
* EMS HID Playstation 2 controller adapter
* HID Mouse/Keyboard Combo (I ([[User:84plusfreak|84plusfreak]]) am writing a driver for it.)

== Should Work ==
These devices have been tested to properly initialize with usb8x, but no drivers have been attempted.
* Canon i850 printer
* Canon SD400 digital camera
* Motorola SURFboard cable modem
* Motorola V220 (can act as USB Modem)
* TI-84 Plus (calc<->calc)
* Generic IrDA USB dongle (says it draws 440 mA, but it initializes fine anyway)

== Not Compatible ==
These devices are not compatible with usb8x.
* Ezonics webcam - isochronous endpoints
* Netgear WG111 802.11 adapter - draws too much current?
* SMC 802.11b adapter - draws too much current
* Taurus MBT-1203 bluetooth adapter - has integrated hub

83Plus:Software:usb8x/Supported Devices

2006-10-19T15:07:36Z

TD-Linux: /* Internal Driver */

Most USB devices that are self-powered, or draw 100mA or less current from the USB bus should be compatible with usb8x. Below is a list of device classes and specific devices that have been tested. Devices that require isochronous endpoints or have an integrated USB hub are not currently compatible.

== Internal Driver ==
These devices work and usb8x contains an internal driver to control them.
* HID Keyboard
* HID Mouse
* Mass Storage Device. Tested with:
** Sandisk Cruzer
** Lexar JumpDrive/Secure
** SMI Corp USB Disk
** 512 Mini Disk Genie
** PQI Intelligent Stick
* TI Silverlink
* Some gamepad controllers. Tested with:
** Logitech Precision Gamepad
** Logitech Dual Action Gamepad (only the buttons, the D-pad and joysticks don't work)
** [http://www.retrousb.com/nintendo.html RetroZone NES pad]
** [http://www.planetgamecube.com/hardArt.cfm?artid=2459 Skillz Gamecube to USB] (The company no longer seems to exist.)
* Vernier EasyTemp

== External Driver ==
These devices work and an external driver exists to control them.
* None

== Works, No Complete Driver ==
These devices have been tested to work with usb8x, but no complete driver currently exists.
* EMS HID Playstation 2 controller adapter
* HID Mouse/Keyboard Combo (I ([[User:84plusfreak|84plusfreak]]) am writing a driver for it.)

== Should Work ==
These devices have been tested to properly initialize with usb8x, but no drivers have been attempted.
* Canon i850 printer
* Canon SD400 digital camera
* Motorola SURFboard cable modem
* Motorola V220 (can act as USB Modem)
* TI-84 Plus (calc<->calc)
* Generic IrDA USB dongle

== Not Compatible ==
These devices are not compatible with usb8x.
* Ezonics webcam - isochronous endpoints
* Netgear WG111 802.11 adapter - draws too much current?
* SMC 802.11b adapter - draws too much current
* Taurus MBT-1203 bluetooth adapter - has integrated hub

83Plus:Software:usb8x/Supported Devices

2006-10-19T15:06:22Z

TD-Linux: /* Should Work */

Most USB devices that are self-powered, or draw 100mA or less current from the USB bus should be compatible with usb8x. Below is a list of device classes and specific devices that have been tested. Devices that require isochronous endpoints or have an integrated USB hub are not currently compatible.

== Internal Driver ==
These devices work and usb8x contains an internal driver to control them.
* HID Keyboard
* HID Mouse
* Mass Storage Device. Tested with:
** Sandisk Cruzer
** Lexar JumpDrive/Secure
** SMI Corp USB Disk
** 512 Mini Disk Genie
* TI Silverlink
* Some gamepad controllers. Tested with:
** Logitech Precision Gamepad
** [http://www.retrousb.com/nintendo.html RetroZone NES pad]
** [http://www.planetgamecube.com/hardArt.cfm?artid=2459 Skillz Gamecube to USB] (The company no longer seems to exist.)
* Vernier EasyTemp

== External Driver ==
These devices work and an external driver exists to control them.
* None

== Works, No Complete Driver ==
These devices have been tested to work with usb8x, but no complete driver currently exists.
* EMS HID Playstation 2 controller adapter
* HID Mouse/Keyboard Combo (I ([[User:84plusfreak|84plusfreak]]) am writing a driver for it.)

== Should Work ==
These devices have been tested to properly initialize with usb8x, but no drivers have been attempted.
* Canon i850 printer
* Canon SD400 digital camera
* Motorola SURFboard cable modem
* Motorola V220 (can act as USB Modem)
* TI-84 Plus (calc<->calc)
* Generic IrDA USB dongle

== Not Compatible ==
These devices are not compatible with usb8x.
* Ezonics webcam - isochronous endpoints
* Netgear WG111 802.11 adapter - draws too much current?
* SMC 802.11b adapter - draws too much current
* Taurus MBT-1203 bluetooth adapter - has integrated hub

Z80 Routines:Graphic:Fastcopy

2006-06-20T16:17:36Z

TD-Linux: /* Safe Copy */

[[Category:Z80 Routines:Graphic|fastcopy]][[Category:Z80 Routines|fastcopy]]
'''Warning:''' The routines presented below will fail on some calculators due to manufacturing defects. Before using any of the routines below, read the safe copy section below.

The '''Fastcopy''' routine is used to copy the content of the Graph Buffer to the screen. It concerns all TI-z80 calculators, except TI-85 and TI-86, that has a special RAM area directly mapped to the screen.

Fastcopy is widely used, because the rom call _GrBufCpy waits too long between each output to the LCD driver. Using Fastcopy instead of _GrBufCpy increases significantly the speed of a program if it refreshes often the display (such as a lot of games). Most shells have this routine as built-in (ION, MirageOS, Venus ...).

Here is Joe Wingbermuehle's version, which is the one used in ION.

<nowiki>
;-----> Copy the gbuf to the screen (fast)
;Input: nothing
;Output:graph buffer is copied to the screen
fastCopy:
di
ld a,$80
out ($10),a
ld hl,gbuf-12-(-(12*64)+1)
ld a,$20
ld c,a
inc hl
dec hl
fastCopyAgain:
ld b,64
inc c
ld de,-(12*64)+1
out ($10),a
add hl,de
ld de,10
fastCopyLoop:
add hl,de
inc hl
inc hl
inc de
ld a,(hl)
out ($11),a
dec de
djnz fastCopyLoop
ld a,c
cp $2B+1
jr nz,fastCopyAgain
ret
</nowiki>

==Remarks and Improvements==
* Some instructions in Joe Wingbermuehle's Fastcopy are only there for having enough delay between two outputs to the LCD driver. One can modify Fastcopy to change these useless instructions into instructions that will clear the Graph Buffer at the same time:
<nowiki>
;-----> Copy the gbuf to the screen and clear graph buffer (fast)
;Input: nothing
;Output:graph buffer is copied to the screen and subsequently cleared
fastCopy:
di
ld a,$80
out ($10),a
ld hl,gbuf-12-(-(12*64)+1)
ld a,$20
ld c,a
inc hl
dec hl
fastCopyAgain:
ld b,64
inc c
ld de,-(12*64)+1
out ($10),a
add hl,de
ld de,11
fastCopyLoop:
add hl,de
inc hl
inc de
ld a,(hl)
ld (hl),0 ; clears the graph buffer at the same time
out ($11),a
dec de
djnz fastCopyLoop
ld a,c
cp $2B+1
jr nz,fastCopyAgain
ret
</nowiki>

'''ld (hl),0''' takes 10 cycles, so we can do with one less '''inc hl''' (6 cycles) and thus load 11 into de instead of 10.

==Safe Copy==
Many calculators recently manufactured by TI contained a buggy LCD driver, which had different (or varying) delays required to interface with it. Using the fast copy routines above with the LCDs will cause the LCD to display garbled information. However, we can do some additional hardware work to solve this problem, by waiting until we know the LCD is ready to accept a command:

* Bit 1 of Port 2 tells us that the lcd can accept an instruction
* Bit 7 of Port 10 tells us that the lcd can accept an instruction

The TI-OS and other apps generally use port 2 but being that bit 7 is sign bit we can use that as faster method of waiting.

<nowiki>
;-----> Copy the gbuf to the screen, guaranteed
;Input: nothing
;Output:graph buffer is copied to the screen, no matter the speed settings
;
;in f,(c) is an unofficial instruction.
;It must be noted that you cannot specify any other register. Only f works.
;You may have to add it in order for the routine to work.

.addinstr IN F,(C) 70ED 2 NOP 1

SafeCopy:
di
ld c,$10
ld a,$80
setrow:
in f,(c)
jp m,setrow
out ($10),a
ld hl,PlotSScreen
ld de,12
ld a,$20
col:
in f,(c)
jp m,col
out ($10),a
push af
ld b,64
row:
ld a,(hl)
rowwait:
in f,(c)
jp m,rowwait
out ($11),a
add hl,de
djnz row
pop af
dec h
dec h
dec h
inc hl
inc a
cp $2c
jp nz,col
ret
</nowiki>