H O M E / I N F O / P R O D U C T S
/ O R D E R / S U P P O R T
Contents / Getting
started / TSP FAQ / TLG
FAQ / Updates / Recent
changes
![[TSP International]](../../images/tsplogo.72.gif)
|
H O M E / I N F O / P R O D U C T S
/ O R D E R / S U P P O R T |
|
Last revised: 6/9/04
Here is a compatibility table for TSP and various versions of Windows.
Windows version TSP version 3.x 95,98,NT (prior to 4/2004 Windows Update) 2000,ME (prior to 4/2004 Windows Update) XP, updated NT, updated 2000 TSP/GiveWin (GiveWin 1.30,2.xx) no yes yes yes TSP/GiveWin (GiveWin 1.24) no yes no no Win32 no yes yes yes DOS/Win (TSP 4.5,4.4,4.3) yes yes yes no Newer versions of TSP run on XP, and the older ones apparently do not. For details on how to run the different versions, see Appendix D of the TSP 4.5 User's Guide. One of the reasons we provided several different versions of TSP on the CD was to provide alternatives if "future" Windows upgrades like XP had compatibility problems like this.
These versions run on XP:This version does not run on XP:
- TSP/GiveWin (GiveWin 1.30 or higher)
- Win32 TSP (TSPW.EXE)
This version does not run on XP as installed, but it may run on XP, after two small changes:
- DOS/Win TSP (TSP.EXE)
You will see an error message like:
Abnormal program termination: stack fault
CS:EIP=000Fh:000012A7h
There might be a way around this problem, by changing the Properties of TSP.EXE. But we do not have a solution at present, except to run TSP/GiveWin or TSPW.
- TLG (TSP Through the Looking Glass)
As normally installed, you can start TLG, but when you try to run TSP, you will see an error message like:
There is not enough space on drive C:\ to process your TSP batch file.
Please move your file to a different drive and try again.
The reason this does not work on Windows XP is that TLG normally uses the DOS/Win TSP.EXE to obtain TSP results, but the DOS/Win version does not run on XP.
To make TLG get TSP results on XP (or 2000 or NT 4.0 with the 4/14/2004 Update), have TLG run the Win 32 TSP instead of the DOS/Win version.
To do this, make two small changes: Now, TLG will run the Win32 TSP instead of the DOS/Win version, to get TSP results.
There still may be problems using TLG, though. It may have DLL conflicts with XP or Microsoft Office. (TLG uses some Visual Basic DLLs which are often updated by Microsoft Office to newer versions which are not compatible with TLG).
But the above changes are easy to try and you will find out quickly of TLG is functional if you have XP. For example, the above changes do produce TSP results with TLG on a Windows 98 PC we tested with MS Office 2000.
Note: although this procedure works with TSP 4.5, it does not work with the Win32 version of TSP 4.4. This older version does not handle the command line filename argument properly for TLG. The Win32 TSP 4.4 does work fine from the Command Prompt on Windows XP, though.
Note: If you have a copy of Student TSP 4.5 dated before 8/29/2003, it does not contain Win32 TSP. However, you can download a Student Win32 TSP 4.5. Contact us for download instructions.
Right now we do not believe TLG (and possibly DOS/Win TSP) will run under beta versions of Windows NT 5.0. Win32 TSP and TSP/GiveWin should run fine, though. If you do try running TSP under Windows NT 5.0, we would like to hear what happened, so please send email to TSP through the Looking Glass Tech Support.
In short, TSP & QMS EViews are separate programs made by separate companies that shared a common ancestor long ago. Look at our web page comparing TSP & EViews for more information.
Yes, you can run TSP through the Looking Glass over a Windows network. Please note that you must purchase or upgrade to a TSP site license in order to install TSP through the Looking Glass on a network server for shared use.
Right now the best way for someone to learn econometrics using TSP is to use our TSP supplement to Pindyck & Rubinfeld's authoritative textbook, Econometric Models and Economic Forecasts.
Yes, TSP does run on Linux. Right now it has been successfully run on the Intel Linux Debian 2.x (11/02/98) (aka Red Hat 5.x, clib6/glibc). Also still available for Intel Linux Debian 1.x (aka Red Hat 4.x, clib5). See our unix availability page.
Back in 1998, we were not sure what to call the next version of TSP, and we were considering calling it TSP 5.0. We ended up calling it TSP 4.5. Historically speaking, we have released a new version of TSP about once every 3 years. However, sometimes we will update the current shipping version to include bugfixes and minor new features. TSP 5.0 will be released Summer 2004.
The EMM memory manager's NOEMS switch is not compatible with 4.2a and some 4.2b versions of TSP ("386 TSP"). To run TSP, delete the word NOEMS from your config.sys file and reboot, or upgrade to version 4.3.
You can fix this problem another way if you can run plain DOS on your machine. The above message occurs with 386 TSP (4.2 or earlier), and you are trying to run it directly from Windows (or from the DOS Prompt icon in Windows). 386 TSP uses an old "DOS Extender" standard which was invented before Windows 3.x existed, and is not compatible with Windows. You can run 386 TSP on your PC, if you can exit completely from Windows to the plain DOS prompt. Or, you can upgrade to DOS/Win TSP 4.3, which uses the Windows-compatible "DPMI" standard for DOS Extenders.
These programs are utilities that can help you debug and configure TSP.
PATCH.EXE: This program will set your printer defaults. These defaults can also be set within the program. See graphics.doc for more information.
TELLME.EXE: This program measures the available memory on your computer. Use TELLME | MORE to page its output. Use this program if you get the following message when trying to start the program:
Phar Lap err 10118: Can't load EXP file: C:\TSP43\TSP.EXE
Memory error: insufficient physical memory available . . .
CFIG386.EXE: This program allows you to reconfigure the way TSP uses virtual memory. It is unlikely that you will need to use it. For more information see cfig386.doc.
One thing that will make your life easier using Windows 95/98/NT, and not just in running TSP, is to change the system settings so file types are always shown, as in DOS and Windows 3.1. You can do this by selecting Options... from the View menu of any open folder. Select the "View" tab of the Options dialog box and uncheck the "Hide MS-DOS file extensions for programs that are registered" option. If you do not make the file types visible, you will not be able to distinguish between the .TSP and .OUT files from most of the directory window views.
Actually, TSP can read files from the hard drive just fine, but the problem is that you have to give TSP the *exact* location of the file. Since a hard drive has many nested directories, this can sometimes be difficult.
Unfortunately, Windows 95 hides the directory (folder) names to a certain extent, which makes finding the exact location difficult. Even the Find command from the Start menu will not give the full directory names if they are more than about 15 characters in length. So sometimes it is necessary to use the "My Computer" icon to search through folders, or to run the MS-DOS Prompt.
To give TSP the full pathname, you should use a command like: READ(FILE='\EXCEL\DATA\BOOTER.XLS'); . Finally, if you have a filename with more than 8 characters (not including the file extension), such as ARGENTINA85.XLS you will need to reduce the name to adhere to the DOS 8.3 rule (8 characters for the file name plus three characters for the file extension), because TSP can not currently read longer file names. This also applies to each directory name, although the total pathname can be up to 128 characters in length.
Follow the directions in Configuring TSP under Windows 95/98/NT to access the Properties dialog for the TSP executable. Select the Memory tab. Change DPMI Memory from Auto to 65,535 (or possibly to -1 to obtain all available memory, although this may be a bit too greedy for everyday use).
Use the REGOPT command before the first OLSQ command where you want the extra diagnostics. Every later OLSQ command will compute the additional diagnostics, until the desired set is modified with another REGOPT command.
Use the REGOPT command, with NOCALC or NOPVPRIN options, before the first OLSQ where you want the diagnostics reduced. To reproduce the TSP 4.3 output, use:
REGOPT(NOPVPR) DW FST T;
REGOPT(NOCALC) LMHET RESET JB;
You can do this with the INPUT command, for example, INPUT 'myfunction.tsp'; INPUT commands can be nested. What TSP 4.4 does not have is a "passive" include feature, in which you can call a procedure that has not been input yet. This is something which is supported in TSP 4.5, in batch mode.
GARCH(1,1) can't be done with the regular ML in a FRML, due to the recursive nature of the h(t) equation. You'll need to use the PROC interface to ML (see the ML PROC examples in the TSP examples library).
TSP offers simple line editing, when running interactively. Arrow keys are used to recall and/or edit lines that you've previously typed. This can be used to correct typographical errors, add/drop variables, or to execute a series of commands repeatedly (although the EXEC command might be simpler for this). It is functionally very similar to DOS command line editors like DOSKEY or CED. The following keys are used:
Arrow key up
recall previous line(s)
Arrow key down
recall later line(s)
Arrow key left
move (cursor) left in current line
Arrow key right
move (cursor) right in current line
Ins
toggle typeover/insert mode (default: typeover for each line)
Del
delete character at cursor
Backspace
delete character to left of cursor
Esc
clear current line
Any line which is typed on the keyboard, as well as edited versions of previous lines, are stored. Up to 500 lines (or 15000 bytes -- an average of 30 bytes per line) of text are held in a buffer for retrieval and editing. If the buffer gets full, the first 50 lines are dropped, so that the next 50 lines may be stored. The and keys remember the current line number, and they work in a circular fashion. At most 80 characters in a single line may be typed (you're not allowed to go past the right side of the screen), so the \ to continue long lines may still be useful. Note that if you're editing a multiline command like this, the different lines may no longer be stored together, so this feature is not without its limitations. The old EDIT and RETRY commands are clearly superseded by arrow key editing, but the REVIEW and EXEC commands may still be useful.
For example, say you have just typed 5 lines. You press [up arrow] once, and recall line 5. You make some changes to it, and the new version is stored as line 6. You then type [up arrow] twice, and recall line 4. You press Enter to execute it, without making any changes. You press [up arrow] once and recall line 3. You press [up arrow] twice and recall line 1. You press [up arrow] one more time and recall line 6. You decide none of these lines is close to what you want to do, so you press Esc to clear the line, and type a new one, which is stored as line 7.
It's true that probabilities are between zero and one, but the FIML likelihood function is a density (as opposed to, say, a cdf like in PROBIT). A density can take on any positive value, so its log can be positive (or negative, or zero). For example, the uniform density on the interval [0,.5] has the value 2 at all points. The normal density for a zero residual, with mean=0 and variance=(1/(25*2*pi)), is 5. So a normal density will be largest when the variance and residual are fairly small, i.e. the peak of the "bell curve" can be quite tall when it is narrowed by a small variance. Finally, the FIML likelihood function (in particular) includes the determinant of the Jacobian, which can also be larger than 1.
Look at our Recent changes to TSP page, which lists bugfixes and enhancements.
By default, TSP uses single precision for storing series so only 6-7 digits in the printout have any meaning. If you would like to use double precision for storage of series, issue an OPTIONS DOUBLE; statement at the beginning of your TSP program.
Use OPTIONS DOUBLE; when you have 7-15 significant digits in an ID variable. TSP 4.5 will automatically store an ID variable in double precision, if it has a large number of significant digits, and has been designated as an ID variable by a FREQ(PANEL) command.
TSP is trying to make a higher resolution plot than your monitor can handle. Create a LOGIN.TSP file in your TSP directory (usually C:\TSP44 unless you chose something different during installation) with the command: OPTIONS DISPLAY=VGA; .
This long-standing bug has finally been fixed! It was a bug in the Lahey hardcopy graphics driver, and it was fixed in September 1995.
This appears to happen due to an incompatibility between the compiler we use for DOS/Win TSP and Windows NT 4.0.
To fix this problem, try the following:
In TSP, set options to display=vga; to set my monitor type conservatively.
then run TSP in this manner:
1. I first run the "Cmd" icon (MS-DOS), located on my PC in
\WINNT\system32\cmd.exe .
2. One of the important Properties of Cmd is that Display is "Full Screen"
(not Window).
3. CD \TSP44
4. TSP PLOT
Some early versions of TSP 4.4 shipped without the .bin files, which TSP needs to generate high quality plots. If your copy of TSP does not include these files, you can get them from TSP Tech Support.
It probably means a variance parameter tried to go to the boundary of the parameter space (i.e., 0 or 1), so that it was dropped from the estimation. This message was improved in TSP 4.4.
This is a bug in the WATCOM compiler used to make the old TSP 4.2B Windows and DPMI-N87 versions. You can run DPMI-N87 from DOS (not the Windows DOS prompt). If you have a math coprocessor (or FPU emulation software like Q387), you can run from Windows by upgrading to DOS/Win TSP 4.3 or higher.
We will continue to offer TSP on the PowerPC Mac for the foreseeable future. The 68000 series (Mac II) binary will also still be available, as long as our old Mac IIx keeps working.
Unfortunately, no. Mac TSP requires a math coprocessor. The 68LC040 chip does not have one, and emulation does not work. If you're not sure whether your Mac has the 68LC040 chip, we have a list compiled from official Apple Computer sources.
It is unlikely at this time that we will be ever port TSP through the Looking Glass to Unix. However, we may make an X windows version of TSP for unix ("xtsp") at some point, which would do X graphics in the PLOT and GRAPH commands.
If you problem seems to happen when you are using TSP through the Looking Glass, then please send an email to TSP through the Looking Glass Tech Support. If the problem is related to TSP, then send your email to TSP Tech Support. Please note that you must be a registered user of TSP in order to get tech support for TSP through the Looking Glass. Try to be able to answer the following questions:
What version of TSP through the Looking Glass are you using?
What operating system are you using?
If you are using a PC, who manufactured the machine you are using?
If TSP through the Looking Glass crashed, at what point exactly did it crash and what did the error message say?
Can you reproduce the crash(es) consistently, or do they seem to happen randomly?
If you have any questions or comments about TSP please send an email to info@tspintl.com.
Comments or questions about this website should be sent to the webmaster.
Lost? Please consult the site map.