TIFAQ
Compiled By Dan H. Eicher
L.D.O.M. 05.20.98
Please send questions comments or concerns to [email protected]
This document is the work of many, who have given of their time
to help others learn about the TI-99/4A. If this document helps
you, won't you consider adding a section?
Thanks,
Dan
=======================================================================
Questions:
Abbreviations.
By Dan H. Eicher..............................................TIFAQ001
HOW CAN I LEARN TO PROGRAM IN ASSEMBLY LANGUAGE (A/L)?
By John Bull..................................................TIFAQ002
HOW CAN I RUN ASSEMBLY LANGUAGE PROGRAMS FROM EXTENDED BASIC?
By John Bull..................................................TIFAQ003
What are TOKENS?
By Jacques Groslouis..........................................TIFAQ004
What are they(tokens)?
By Jacques Groslouis..........................................TIFAQ005
How can I use Graphics for other machines on my TI?
By Deanna Sheridan............................................TIFAQ006
What is a TIFILES header?
By Steven A. Reynolds.........................................TIFAQ007
Technical Update by Jeff Brown
What is V9T9
By Steve A. Reynolds..........................................TIFAQ008
SubTopic: How do I get the TRANS program over to the TI
since the Forth program won't work?
SubTopic: Why don't the DOAD utilities like TIDIR or TICOPY work?
SubTopic: How do I use a file I downloaded on my IBM with V9T9?
SubTopic: V9T9 module images
What is the TI List Server
From the South West 99ers................................................TIFAQ009
What is a RAMDISK
By Bob Carmany................................................TIFAQ010
Is there a Forth compiler for the TI and Geneve?
By John Carver................................................TIFAQ011
Can I use 720 and 1.44 Meg floppies on my Geneve
By Ken........................................................TIFAQ012
How do I set up a system and what are my expansion options?
By Andy Frueh.................................................TIFAQ013
What is Funnelweb
By Andy Frueh.................................................TIFAQ014
Can I get on to the Internet with My TI-99/4a
By John Bull..................................................TIFAQ015
What is PC99
By Mike Wright for Cadd Electronics...........................TIFAQ016
Can I use my TI 99/4A on the internet?
By Lew King...................................................TIFAQ017
======================================================================
TIFAQ001
Abrreviations.
By Dan H. Eicher
<[email protected]>
AVPC - Advanced Video Display Processor, produced by Digit Systems
(Tom Spilane) - This PBOX card use an 9938.
c - Small C by Clint Pulley for the 99/4a.
E/A - Editor Assembler.
FDC - Floppy Disk Controller.
FWEB - Funnel Web.
GRAMULATOR - Graphics Ram Module produced by Cadd Electronics
allows the user to load/modify and run cartridges.
Unlike the GramKracker produced by Millers Graphics
with modifications, this unit could also run MBX
modules.
GRAM KRACKER - See Gramulator.
Grand Ram - A ramdisk produced by DataBiotics. Unique in that
it both battery backed up like a Horizon Ramdisk and
provided print spooler software (like the Myarc 512K)
card. It also included connectors on board to connect
to emulate the PBOX bus and cartridge port.
GROM - Graphic ROM
Rom Memory developed by TI that automatically increments.
HFDC - Myarc Hard Floppy Disk Controller.
MBP - Eight port analog to digital card with real time clock.
MBX - Milton Bradley Expansion Unit (yes the toy maker) allowed
the 99/4a to use voice directed games.
PBOX - Peripheral Expansion Box also known as PEB.
PC99 - A software package for MSDOS PC's (486-50 or faster) that
emulate a TI99/4A. This is commercial software and well
supported.
PGRAM - Like the GramKracker, but on a PBOX card.
PIO - Parrallel/Printer Port.
POP-CART - Cartridge produced by OPA that up to 512K of grom
code and any number of cartridges could be placed.
SOB - Son Of a Board. This board also plugs into the console,
in the GROM1 socket. It adds an enhanced menu upon power
up and fixes some video initialization problems that are
transparent, unless you are using a 9938 or 9958 video
controller chip in your system.
TIM - TI Image Maker. This is a an 80-column board produced by
OPA. It had a Yamaha 9958 chip and came bundled with the
SOB. It mounts inside the TI console in the TMS9918 socket.
V9t9 - A software package for MSDOS PC's (386-25 or faster) that
emulates a TI99/4A. This is freeware (produced by Ed.
Swartz) and no support from the author is available,
but the source code is.
XB - Extended Basic.
Return to table of contents.
======================================================================
TIFAQ002
HOW CAN I LEARN TO PROGRAM IN ASSEMBLY LANGUAGE (A/L)?
By John Bull
<[email protected]>
You will need -
Hardware: TI-99/4a with 32K Memory Expansion and at
least one floppy drive.
Software: The Editor/Assembler cartridge and the two
floppies that come with it. However, FunnelWeb
includes all of the essential software and is perhaps
more convenient.
Texts: The Editor/Assembler User's Manual. This is an
absolutely necessary reference but is not a beginner's guide
for learning to program.
Also, an Introduction to Assembly Language that guides you
through the process of writing A/L programs. One is by Ralph
Molesworth and there are several others, equally good.
You use the Editor program to write A/L SOURCE code, save it
to disk as a D/V80 file, and then use the Assembler program
to assemble it into A/L OBJECT code which is in machine
language. This is a D/F80 file, ready to run with the E/A
Loader or from Extended Basic if you wrote it for that.
There are four Modes for A/L programming and you choose the
one that suits your purpose. The Graphics mode is the
simplest, most generally useful mode and the one that is
at hand when you start. Bit-map and Multicolor mode is for
detailed screen graphics. Text mode is for text only, as
in word processing.
Writing A/L programs is laborious and not easy to learn but the
results are worth the effort. They are VERY fast and can do many
things that are not practical with other languages.
John Bull
[email protected]Return to table of contents.
======================================================================
TIFAQ003
HOW CAN I RUN ASSEMBLY LANGUAGE PROGRAMS FROM EXTENDED BASIC?
By John Bull.
<[email protected]>
To run from Extended Basic, an Assembly Language program must be
written for that purpose or modified. X/B cannot use files created by
the C (compressed) option of the Assembler. X/B does not handle DEF's
but the address of utilities must be EQUated. For instance, a
program written for the Editor/Assembler loaders might begin:
DEF START
REF STRASG,STRREF
For X/B this should be:
REF START
STRASG EQU >2010
STRREF EQU >2014
The list of EQUates for X/B is on pages 415 and 416 of the
Editor/Assembler Manual. Modifying an E/A program to run from
X/B is sometimes as simple as the above. Please note, the E/A
manual has a typo. Page 416 should read NUMREF EQU >200C
Two ways you can run an A/L program from X/B: One is to put at the
beginning of your X/B program:
10 CALL INIT
20 CALL LOAD("DSKn.FILENAME") where FILENAME is the file name of
the A/L program.
Now the program is in memory and can be run with CALL
LINK("START"), where START is the entry point as defined in
the program.
Another way, more work but often more convenient, is to
imbed the A/L program in your X/B program, where it will
stay, ready to run, whenever you load the X/B program. There
are two programs available to do the imbedding: Harry Wlhelm's
HML, High Memory Loader and Scott Kaplan's ALSAVE, which loads
into low memory. HML is easier to use but will not work with
very large X/B programs.
Whatever way you load the A/L program, it remains in memory
until you do CALL INIT, or BYE and so it is available in other
X/B programs that you RUN from the first one.
NOTE: Issueing a new from X/B will leave your A/L program in
memory.
John Bull
[email protected]Return to table of contents.
======================================================================
TIFAQ004
What are TOKENS?
By Jacques Groslouis
<[email protected]>
Tokens are used to aid in the parsing of Commands, Functions, and
Statements in BASIC programs. When run BASIC programs are usually
interpreted as opposed to being compiled. Upon running an interpreted
program the contents of each program line is translated to its required
functions as the program runs. On the other hand a compiled program is
first converted to an assembly language program, and then is run as an
A/L program. A compiled program will run faster than an interpreted
program.
A TI BASIC program is interpreted twice which explains why certain
functions in TI BASIC run slower than the same function on other
computers. This additional interpretation is required because of the
basic structure of the TI computer. Instead of using an operating
system which must be booted and requiring the loading of a BASIC
interpreter program, a TI has much of this already available when the TI
is turned on. These preloaded programs are included in the GROM modules
in the TI console. Additional GROM modules are also included in the
various cartridges which can be plugged into a TI console. The program
instructions contained in these GROM modules are written in Graphic
Programming Language (GPL) a special language written by Texas
Instruments. This is the second language which must be interpreted when
a TI BASIC or Extended Basic program is run.
A TI BASIC or XBASIC program consists of a series of numbered program
lines containing various Commands, Functions and/or Statements which in
GPL are abbreviated to one byte tokens. These abbreviations are listed
in TIFAQ005. For example the token for the PRINT command is represented
by character 156 (>9C) and the GOSUB command is represented by character
135 (>87). An example of a program line in usual LIST (DV80) format
compared to MERGE (DV163) format is as follows:
LIST format: 10 PRINT XYZ
MERGE format:
CHR$(0)&CHR$(10)&CHR$(156)&CHR$(200)&CHR$(3)&CHR$(88)&
CHR$(89)&CHR$(90)&CHR$(0)
These tokens have the following meanings:
CHR$(0)&CHR$(10) Represents line number in base 256 notation.
CHR$(156) Represents PRINT statement.
CHR$(200)&CHR$(3) Indicates that following characters are
unquoted string with a length of 3
characters.
CHR$(88)&CHR$(89)&CHR$(90) Represents the characters XYZ.
CHR$(0) Represents end of line marker.
XBASIC programs have been written which can be used to write Extended
Basic programs or to convert DV80 listings of extended basic programs
into DV163 (merge format) programs using knowledge of the token
abbreviations.
More information concerning the use of GPL may be obtained by consulting
the "Texas Instruments Graphics Programming Language User's Guide" June
1,1979 (Revised December 3,1979) or "The Graphics Programming Language"
Copyright 1990, R. A. Green. GPL assemblers and disassemblers also exist
but a GRAM device is required to load and change GPL programs.
September 20,1997
Jacques Groslouis
[email protected]
1747 Riverbank Drive
Bathurst New Brunswick E2A 4L1
CANADA
Return to table of contents.
======================================================================
TIFAQ005
TI99: TI tokens
By Jacques Groslouis
<[email protected]>
Tokens which appear in a 205 COS
Basic Program 206 EXP
0 end of line marker 207 INT
129 ELSE 208 LOG
132 IF 209 SGN
133 GO 210 SIN
134 GOTO 211 SQR
135 GOSUB 212 TAN
136 RETURN 213 LEN
137 DEF 214 CHR$
138 DIM 215 RND
139 END 216 SEG$
140 FOR 217 POS
141 LET 218 VAL
142 BREAK 219 STR$
143 UNBREAK 220 ASC
144 TRACE 222 REC
145 UNTRACE 241 BASE
146 INPUT 243 VARIABLE
147 DATA 244 RELATIVE
148 RESTORE 245 INTERNAL
149 RANDOMIZE 246 SEQUENTIAL
150 NEXT 247 OUTPUT
151 READ 248 UPDATE
152 STOP 249 APPEND
153 DELETE 250 FIXED
154 REM 251 PERMANENT
155 ON 252 TAB
156 PRINT 253 # (files)
157 CALL 255 end of file marker
158 OPTION Tokens used only in Extended
159 OPEN Basic Programs
160 CLOSE 130 ::
161 SUB 131 !
162 DISPLAY 163 IMAGE
164 ACCEPT 165 ERROR
169 RUN 166 WARNING
176 THEN 167 SUBEXIT
177 TO 168 SUBEND
178 STEP 170 LINPUT
179 , (comma) 186 OR
180 ; (semi) 187 AND
181 : (colon) 188 XOR
182 ) 189 NOT
183 ( 221 PI
184 & 223 MAX
190 = 224 MIN
191 < 225 RPT$
192 > 232 NUMERIC
193 + 233 DIGIT
194 - 234 UALPHA
195 * 235 SIZE
196 / 236 ALL
197 ^ 237 USING
199 "string" 238 BEEP
200 string 239 ERASE
201 Stmt # 240 AT
202 EOF 254 VALIDATE
203 ABS
204 ATN
My favorite article on tokens is by Jerry Stern and appeared in
the April 1991 issue of MICROpendium. This article also included
a program which displayed both tokens and a program listing so that
you could compare the two formats on a line by line basis. I
understand that Bob Carmany gave a talk on using tokens to write
a program at the recent Lima conference. Iintend to order the video
tapes.
Jacques Groslouis
[email protected]
1747 Riverbank Drive
Bathurst New Brunswick E2A 4L1
CANADA
This addition came later, here is how you can enter them from the keyboard!
The tokens which can be entered from the keyboard are tokens 129 to 159 ,
176 to 183 and 187. These 40 tokens can be entered into a program by
pressing CTRL and the applicable key after a line number. Whether entered
as upper or lower case does not matter. Initially nothing appears but the
statement or command appears when the line is listed. This is not the full
range of tokens but the others cannot be accessed from the keyboard. They
would require using a combination of shift and/or FCTN keys which seem to
override the CTRL key. There is a token associated to each key on the TI
keyboard except for the ENTER key, the space, CTRL and FCTN keys and one
other being CTRL , (comma) which produces character 128. This key seems to
produce a token but not one which I recognize or can use. FCTN V will also
produce a token which is blank being character 127 or DEL.
A listing of these tokens is as follows:
# Token Ctrl
129 ELSE A
130 :: B
131 ! C
132 IF D
133 GO E
134 GOTO F
135 GOSUB G
136 RETURN H
137 DEF I
138 DIM J
139 END K
140 FOR L
141 LET M
142 BREAK N
143 UNBREAK O
144 TRACE P
145 UNTRACE Q
146 INPUT R
147 DATA S
148 RESTORE T
149 RANDOMIZE U
150 NEXT V
151 READ W
152 STOP X
153 DELETE Y
154 REM Z
155 ON .
156 PRINT ;
157 CALL =
158 OPTION 8
159 OPEN 9
176 THEN 0
177 TO 1
178 STEP 2
179 , 3
180 ; 4
181 : 5
182 ) 6
183 ( 7
187 AND /
Jacques Groslouis
[email protected]
1747 Riverbank Drive
Bathurst New Brunswick E2A 4L1
CANADA
Return to table of contents.
======================================================================
TIFAQ006
How can I use Graphics for other machine on my TI?
By Deanna Sheridan
<[email protected]>
The following is excerpted from the Cleveland Area User
Groups Newsletter in January, 1995.
A couple of months ago, I gave a demonstration at
TI-CHIPS on converting DOS graphics to the TI. It was
asked at that time if we can also convert TI graphics
for use in the DOS world, and you can. I am sure a lot
of us have favorite Artist Instances we would like to
continue using, and it's not any more difficult than
transferring from the DOS format to the TI.
Briefly, the common DOS formats that the TI can
utilize are RLE, GIF and MACPAINT.
To transfer programs either way, you need a
program on each machine that will convert to or read
these formats.
I have always used the MACPAINT format. I use the
version of MACFLIX which includes MACFLIX TOOLS so that
I can convert Artist pictures to MACPAINT.
Since I have PC TRANSFER I use that method to
transfer the pictures from my TI to my PC. Without
that program, I also have used my RS232 port and since
I have an external modem, I have cables on both
machines and insert a null modem between the two. I
then use a terminal emulator program on each side and
send them over via Xmodem.
(The article was written in Word Perfect and
included several pictures transferred from the TI).
Hope this helps.
Deanna
[email protected]Return to table of contents.
=======================================================================
TIFAQ007
What is a TIFILES header?
By Steven A. Reynolds
<[email protected]>
In order to preserve attributes associated with TI files, such as
file type,protected status, and the 10 character filename allowable
on the TI, files transferred from the TI to another computer have a
128 byte header preprended to every file to keep this information.
This process is built into the TI's Xmodem protocol and occurs
transparently. In fact, if you transfer a file without a TIFILES
header from an IBM to your TI using Xmodem you will have problems
with the file.
Generally, you can ignore the TIFILES header but it's important to
be able to recognize it so you know if you should use Xmodem or a
different file transfer protocol which does not expect a TIFILES
header before transferring the file.
If you look at the beginning of a TIFILES header you will see the
string TIFILES appear in it. That's usually the easiest way of
telling, not to mention the file will be 128 bytes larger than it
is on the TI.
The format is:
Byte Meaning
------- --------------------------------------------
0 string length 07
1-7 "TIFILES" string
8-9 # of sectors allocated to file
10 status flags
11 # of records per sector
12 EOF offset (# of bytes used in last sector)
13 logical record size
14-15 # of level 3 records allocated
16-17 MS bytes of total # of sector and # of level 3 records
Does someone want to explain what all these fields mean?
TIFILES...
[by Jeff Brown ]
>This process is built into the TI's Xmodem protocol and occurs
>transparently. In fact, if you transfer a file without a TIFILES
>header from an IBM to your TI using Xmodem you will have problems
>with the file.
Not really... an unknown file will generally be imported as IF128
format if I recall correctly. (Geez, I wrote an X/YModem protocol,
I should know this!
argh... I'll have to pull out some old sources)
>The format is:
>
> Byte Meaning
>------- --------------------------------------------
> 0 string length 07
> 1-7 "TIFILES" string
> 8-9 # of sectors allocated to file
> 10 status flags
> 11 # of records per sector
> 12 EOF offset (# of bytes used in last sector)
> 13 logical record size
> 14-15 # of level 3 records allocated
> 16-17 MS bytes of total # of sector and # of level 3 records
>
>Does someone want to explain what all these fields mean?
Sure!! Same fields you'll find in the Low-Level DSR functions "transfer
direct input file" and "transfer direct output file" TDIF/TDOF for short...
and same fields as in the file's FDR. (file descriptor record)
Offset 8 -- # sectors
multiply by 256 to get actual bytes
Offset 10 -- Status flags:
Bit# Description
0 0 = Data file
1 = Program (memory image) file
1 0 = Display
1 = Internal
2 Reserved (0)
3 0 = Unprotected
1 = Protected
4-6 Reserved (0)
7 0 = Variable-length recs
1 = Fixed-length records
Offset 11 -- # recs per sector
Divide 256 by logical record size. Only valid for FIXED LENGTH records.
I'm pretty sure the field is meaningless for VARIABLE LENGTH records. A
DF80 file has 3 records per sector... an IF128 has 2. DV80 will probably
tell you 3, but since its sectors may have more than 3 records, it's
meaningless.
Offset 12 -- EOF offset
You're quite correct... number of bytes used in last sector. In DV80
files, points to an >FF if I recall correctly.
Offset 13 -- Logical record size
Well... maximum number of chars per record... thus 80 in DV80, 163 in
DV163, etc... Note that for variable-length records, the actual record
length can be up to n+1 (1byte for size storage)
Offset 14 -- # of lev 3 records = total # of records allocated
You went and found an obtuse definition. Corresponds to offset 8 in extra
params block of TDIF/TDOF. Simply put, how many records are in this file???
Offset 16 -- no clue! I'll have to check my old sources for this.
Return to table of contents.
======================================================================
TIFAQ008
What is V9T9?
By Steven A. Reynolds
<[email protected]>
V9T9 is a very good TI-99/4A emulator which runs on an IBM 286 or
better and is freeware. The author discontinued support of it and
released the complete source code, which is mostly 808x assembly
language and C for some support utility programs. It is not a
perfect emulator, but it does a very good job on the majority of
TI software and modules. The alternative is to buy PC-99.
V9T9 can run on a 286, but it runs best on a fast 486 or Pentium.
You have to do the fine tuning yourself through the menu system or
by editing the V9T9.CNF file. V9T9 has many configurable options
and is flexible, although it is not user-friendly. An archive called
TIMRADx.ZIP has been uploaded to at least one FTP site and contains
sample configuration files, modules, and ROMs to get you started
with the TI.
The problem is that V9T9 doesn't come with any of the TI ROMs
because they are TI's property. A utility using Forth is provided
to transfer a ROM dump utility to your TI which can be used to
extract your TI's ROMs. Unfortunately very few people have had
success getting this process to work for whatever unknown reason.
Basically, to get V9T9 up and running you really have to first
locate the TI ROM files and an image of the Extended Basic module.
These files, as well as better explanations on what to do, are
found in the TIMRAD archive.
Once you can run Extended Basic on V9T9, have a working serial
connection between your TI and IBM, and are in TI Extended Basic
on your TI, you are ready to go. By the way, remember that the
serial cable between your TI and IBM is a straight through cable
like would go to your modem instead of a real null modem cable.
For some reason, TI decided to make the TI's serial port a DCE
instead of a DTE like most other computers.
Topic: How do I get the TRANS program over to the TI since the
Forth program won't work?
Here is the clever solution by Brian Williams, edited by me:
1. Get V9T9 set up so that you can load a comm program (such
as Procomm) on your IBM and talk to a comm program on your TI
(such as Telco) over your serial cable, with your baud rate,
data bits, stop bits, and parity bits set the same on each end
(such as 4800 baud, 8 data bits, 1 stop bit, no parity).
If you can type characters on each computer and they show up
correctly on the other side, your connection is working.
2. Consult the documentation for V9T9 and type in the RECEIVE
program on the TI in Extended Basic as described. Here it is below:
80 REM Receiver for TRANS object code from PC
90 REM Legal baud rates: 300, 600, 1200, 2400, 4800, 9600
100 INPUT "Enter the baud rate: ":B
110 OPEN #1:"RS232.BA=" & STR$(B) & ".DA=8.PA=N",UPDATE,
VARIABLE 81,INTERNAL
120 OPEN #2:"DSK1.TRANS",OUTPUT,DISPLAY,FIXED 80
130 PRINT "Receiving..."
140 INPUT #1:A$
150 IF A$="" THEN 200
160 PRINT #2:A$
170 PRINT ".";
180 PRINT #1:"O"
190 GOTO 140
200 CLOSE #2
210 CLOSE #1
220 CALL INIT
230 CALL LOAD("DSK1.TRANS")
240 CALL LINK("TRANS")
3. Make sure V9T9 is configured in your .CNF file to use DSK3
as a FIAD (this is the default). After installing V9T9 the file
TRANS should already be located in your DISK subdirectory.
4. Go into Extended Basic on your IBM in V9T9 and type in the following
program:
80 REM Transmitter for TRANS object code to TI
90 REM Legal baud rates: 300, 600, 1200, 2400, 4800, 9600
100 INPUT " Enter the baud rate: ":B
110 OPEN #1:"RS232.BA="&STR$(B)&".DA=8.PA=N",UPDATE,VARIABLE
81,INTERNAL
120 OPEN #2:"DSK3.TRANS",INPUT,DISPLAY,FIXED 80
130 PRINT "Transmitting..."
140 IF EOF(2) THEN 200 ELSE INPUT #2:A$
150 PRINT #1:A$
170 PRINT ".";
180 INPUT #1:B$
190 GOTO 140
200 CLOSE #2
210 PRINT #1
220 CLOSE #1
Save this program in V9T9 as using "SAVE DSK3.TRANSMIT"
(creates a FIAD).
5. Run both programs on the TI and IBM. Enter the baud rate
on both programs as 4800 or 9600. Press ENTER on your TI first.
Due to the poor handshaking of these 2 programs, if you start
the IBM first nothing will happen. If you do it in the wrong order,
FN-BREAK and RUN again.
6. You will see a period for every record that is transferred and
saved on the TI. After a while, the periods will stop printing and
there will be quite a bit of disk activity on the TI. After about a
minute the transfer program will appear. If you wish, you can omit
lines 220-240 on the TI and when the TRANS program has been saved
on your TI disk you will return to BASIC. To load the TRANS program
each time you must execute lines 220-240. For faster loading use
the Editor/Assembler's LOAD AND RUN option. Enter DSK1.TRANS and
then TRANS.
Once TRANS is running on the TI, you need to exit V9T9 on the IBM
and then type RECV to run the RECV utility. Enter the correct
parameters for baud rate, your serial port, and its interrupt.
Do not just hit return! You must type a value.
If you don't know your serial port's interrupt, use a utility
like Norton Sysinfo to find out. V9T9's suggested values seem to
be correct.
Topic: Why don't the DOAD utilities like TIDIR or TICOPY work?
Many people have trouble using the utilities provided to
manipulated DOAD files, depending on which OS you use.
The utilities were written using Dr. DOS 5.0 which may explain
the incompatibilities. It is recommended that you use FIADs to
acess IBM DOS files using V9T9. Using Disk Manager or any other
file manager of your choice under V9T9 you can copy the FIADs
from a FIAD drive to a DOAD on another drive. When V9T9 creates
and manipulates the DOADs, it does it correctly. The utilities
generally do it wrong. Refer to V9T9 and TIMRAD help files for
descriptions of DOADs and FIADs and how to configure
V9T9 to use both.
Topic: How do I use a file I downloaded on my IBM with V9T9?
V9T9 uses its own custom headers which are different for FIADs
and DOADs. You cannot take a raw DOS file or files with a TIFILES
header and have it work properly with V9T9. You must convert the
file(s) to V9T9 format first.
There are several formats you might find a TI file in, but once
a TI file has been transferred to another machine it should be in
TIFILES format unless the transferer was thoughtless. Without a
TIFILES header important TI directory information was thrown away
which makes the file more difficult to use.
The easiest way to find out is to use the TYPE command on the file.
If you see the string TIFILES, it's in TIFILES format. If you see
something that looks very similar to the file's name, it's probably
V9T9 FIAD format. If you see raw data with no apparent header, it's
probably headerless. While there are other formats, you are unlikely
to see any of them because they are not common. You won't find files
in V9T9 FIAD or DOAD format except in archives meant to be used with
V9T9.
Files with the ARK/ARC extension created by Barry Boone's archiver
are made on the TI and usually transferred to the PC via Xmodem.
Therefore, you would expect a TIFILES header on them.
If your file is of the TIFILES type, then run the XMDM2TI utility
in the UTILS subdirectory giving the source filename and destination
path. The utility seems to fail (and kill your original file) if the
source and destination are in the same directory. Therefore, it's
advised that you make a SOURCE subdirectory under V9T9, copy your
files to be converted in there, change to the SOURCE subdirectory,
then run XMDM2TI