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: 9/9/03
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 is an "extended DOS" program which is not supported by XP (unlike all previous versions of Windows).
To make TLG get TSP results on XP, 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.
- Click through from My Computer, to Program Files, and the TSP 4.5 folder.
Locate the TSP.EXE file, and either delete it or rename it to something like TSPDW.EXE .- Locate the TSPW.EXE file, and rename it to TSP.EXE .
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. We updated the shipping CD-ROM installers in August 2003 so that TLG runs the Win32 version automatically now.
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 Student TSP 4.5 (prior to August 2003), it does not contain Win32 TSP yet. However, you can download a Student Win32 TSP 4.5. Contact us for download instructions.
We have tested TSP under Windows 98 and to the best of our knowledge, both the TSP and TLG components work exactly the same under Windows 98 as they did under 95. If you have used TSP under Windows 98 and found this not to be the case, please send email to TLG Tech Support.
Right now we do not believe TLG will run under beta versions of Windows NT 5.0. If you do try running TLG under Windows NT 5.0, we would like to hear what happened, so please send email to TLG Tech Support.
In short, TSP/TLG & 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 TLG over a Windows network. Please note that you must purchase or upgrade to a TSP site license in order to install TLG on a network server for shared use.
Currently TLG has been released on Windows 95/98/NT, where it has reached version 1.10, and Windows 3.1, where it is version 1.01. At this time future releases of TLG are not planned for Mac OS or Unix, though we hope to find some way to improve TSP's user experience on the Mac.
You may use a copy of TLG installed on your desktop machine to access a copy of TSP on a network server as long as you map the network drive to your machine.
To do this, double-click on the computer you know TSP is hosted on - for example, Network Server. Once your machine has connected to that computer, select Map Network Drive from the File menu of the folder window. This will assign a drive letter to the machine, for example, "E:". Now TLG can send DOS-compatible commands to TSP. For more information, see "mapping, network drive" in the Windows 95/NT help system.
Please note that you must purchase or upgrade to a TSP site license in order to install TLG on a network server for shared use.
Unfortunately TLG does not run under Windows NT 3.51.
The TSP installer requires that you put something (anything) in the "Company" field. If it's a personal copy you can put whatever you want in the text box.
You may get this error message if your machine doesn't have the MFC42.DLL system file. You can download it from:
ftp://shell7.ba.best.com/pub.f/fozboot/mfc42.dll
Once you save it to your hard drive, put it in your Window System directory which is C:\WINDOWS\SYSTEM under Windows 95/98 and C:\WINNT\SYSTEM32 if you're using Windows NT.
Note: Some users have reported that when this file is downloaded its extension changes from "DLL" to "COM". If this happens, you must change the extension back to DLL in order for it to work.
Very rarely, Windows 95 or NT systems will ship without the MFC42.DLL. This file is required by TLG 1.10. Early versions of the TSP 4.4 installer did not include this system file.
If TLG does not respond when you attempt to make a new file or open an existing file, you will know that you need to get a copy of MFC42.DLL. You can download it from:
ftp://shell7.ba.best.com/pub.f/fozboot/mfc42.dll
Once you save it to your hard drive, put it in your Window System directory which is C:\WINDOWS\SYSTEM under Windows 95/98 and C:\WINNT\SYSTEM32 if you're using Windows NT.
Note: Some users have reported that when this file is downloaded its extension changes from "DLL" to "COM". If this happens, you must change the extension back to DLL in order for it to work.
This problem can result from installing Microsoft Office 97 or Visual Tools 97. In some circumstances, they install a version of the OLEPRO32.DLL that is incompatible with TLG. The problem is described in article Q162518 in the Microsoft Knowledge Base. The fix is to do the following:
Find the following files in your Windows system directory (usually C:\WINDOWS\SYSTEM):
OLEPRO32.DLL
MFC40.DLL
MSVCRT40.DLL
Copy them onto a floppy disk and delete the originals
Restart your machine
Reinstall TSP 4.4
Restart your machine again
Try running TLG
If at this point you still get the "Unexpected error; quitting" error message when you try and run TLG then restore the files you backed up onto floppy disk and get in touch with Microsoft technical support. If TLG runs but then tells you to get the Office-97 compatible version, go to our TLG update page.
When Microsoft released Office 97 and its Visual Tools 97 family of development products (including Visual Basic 5.0, Visual C++ 5.0 and FrontPage 97) the installers for these programs put several files in the Windows system directory which are incompatible with the shipping version of TLG. As a result, we had to make a special version (otherwise identical in functionality) of TLG that is compatible with these changed system files.
Since then, this Office 97-compatible version has been superseded by TLG 1.10, which you can download from our TLG update page.
When Microsoft released Office 97 and its Visual Tools 97 family of development products (including Visual Basic 5.0, Visual C++ 5.0 and FrontPage 97) the installers for these programs put several files in the Windows system directory which are incompatible with the shipping version of TLG. As a result, we had to make a special version (otherwise identical in functionality) of TLG that is compatible with these changed system files.
Since then, this Office 97-compatible version has been superseded by TLG 1.10, which you can download from our TLG update page.
You need to manually register the offending system file. The most likely candidate is the OLEAUT32.DLL file. To register this file with your system, you need to use the REGSVR32.EXE utility. You can find a copy of this utility in the same directory that you installed TSP.
To register OLEAUT32.DLL, select Run from the Windows 95 Start button and use the following DOS command:
C:\TSP44\REGSVR32.EXE C:\WINDOWS\SYSTEM\OLEAUT32.DLL
If that doesn't work, then try this:
C:\TSP44\REGSVR32.EXE C:\WINDOWS\SYSTEM\OLEPRO32.DLL
That command assumes you chose the default install directory for TSP 4.4 and that you are using Windows 95. If you have Windows NT 4.0, the system files will be located in:
C:\WINNT\SYSTEM32
If you chose a different location for TSP while installing, then you will you need to change the first part of the command.
If you get an error message while running REGSVR32.EXE or it doesn't solve the problem please send an email to TLG Tech Support .
Unfortunately when TSP 4.4 and Student TSP 4.4 for Windows 3.1 first shipped, some of the installer disks were corrupted. If you think this happened to you, please get in touch with TSP Sales so you can get a replacement set of disks.
Although it is undocumented by Microsoft, there are actually two versions of the CTL3D32.DLL, one for Windows 95 and one for Windows NT. There is a chance that when you run the TSP 4.4 or the TLG 97 installer, the incorrect version of this file could be installed on your system. If you think this has happened to you, you need to get a new set of installation disks specific to the type of Windows you are running. You can do this by contacting TSP Sales.
Alternatively you could download TLG 1.10, since its downloadable installer contains the CTL3D32.DLL files for both platforms. You can get it from the TLG update page.
In order to run, TLG needs several Windows DLLs and OCXs. The TLG installer automatically places the files you need in the places where they should go. If you downloaded TLG, you may have only gotten the TLG executable (TLG.EXE) and not the full installer (SETUPTLG.EXE). If you purchased TSP 4.4 or downloaded the full installer and installed TLG with no problems, and you still got this message please send a message to TLG Tech Support.
Some versions of TLG 97 and 1.02 do not properly trap an error caused by an improperly registered Windows system file and go into an endless loop. If this happens, you should try manually registering (using the REGSVR32.EXE utility) the following files: OLEAUT32.DLL, OLEPRO32.DLL, TABCTL32.OCX, COMDLG32.OCX or COMCTL32.OCX. If you don't know what REGSVR32.EXE is or don't have it installed on your machine, or if using it doesn't work, please email TLG Tech Support.
Some downloadable versions of TLG 1.10 have the wrong date of TSP 4.4's release programmed into them. As a result, they will say your copy of TSP is not version 4.4 when it is. A version of TLG 1.10 that fixes the problem is available for download from our TLG update page.
Very rarely, Windows 95 or NT systems will ship without the MFC42.DLL. This file is required by TLG 1.10. Early versions of the TSP 4.4 installer did not include this system file.
If TLG does not respond when you attempt to make a new file or open an existing file, you will know that you need to get a copy of MFC42.DLL. You can download it from:
ftp://shell7.ba.best.com/pub.f/fozboot/mfc42.dll
Once you save it to your hard drive, put it in your Window System directory which is C:\WINDOWS\SYSTEM under Windows 95/98 and C:\WINNT\SYSTEM32 if you're using Windows NT.
Note: Some users have reported that when this file is downloaded its extension changes from "DLL" to "COM". If this happens, you must change the extension back to DLL in order for it to work.
Very rarely, Windows 95 or NT systems will ship without the MFC42.DLL. This file is required by TLG 1.10. Early versions of the TSP 4.4 installer did not include this system file.
If TLG does not respond when you attempt to make a new file or open an existing file, you will know that you need to get a copy of MFC42.DLL. You can download it from:
ftp://shell7.ba.best.com/pub.f/fozboot/mfc42.dll
Once you save it to your hard drive, put it in your Window System directory which is C:\WINDOWS\SYSTEM under Windows 95/98 and C:\WINNT\SYSTEM32 if you're using Windows NT.
Note: Some users have reported that when this file is downloaded its extension changes from "DLL" to "COM". If this happens, you must change the extension back to DLL in order for it to work.
This problem is usually caused by the TSP executable's application settings being set wrong under Windows. We have directions available for both Windows 3.1 and Windows 95/98/NT for how to configure your copy of TSP so it can interact properly with TLG.
TLG is taking time to format your batch file, coloring the text according to what type of code it is - for example, coloring comments green and keywords blue. Users who are impatient, color-insensitive or have slower PCs will probably want to turn this feature off.
To do this, select Preferences... from the File menu. A tabbed dialog will appear on the screen. Select the AutoFormat tab. There you have full control over all elements of the AutoFormat feature - you may select which events trigger formatting, what colors to use and which types of code to format.
In order for TLG to find a batch file, it must have the file extension .tsp. If you have a text file with valid tsp commands, but without the .tsp file extension, you can still open it since TLG allows you to open any text file by changing the file type option in the Open Dialog to "All Files (*.*)". You will now be able to see your file. However, in order to send the file to TSP for processing, you will have to do a Save As and change the file type to "TSP input file (*.tsp)".
One thing that is helpful in this situation is to change Windows 95 so that it displays file extensions. 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.
TSP00001.tsp is a temporary file TLG creates when it sends batch files to TSP for processing. Instead of using your actual batch file (which could lead to loss of data in the event of a crash) TLG creates a temporary input file to send to TSP. Once TSP processes the commands, it creates a temporary output file which TLG opens, renames and displays in the output window.
These files are not important and can be deleted at any time. You should only see them if TLG crashed during the middle of a batch fun since TLG automatically deletes its temp files once a batch run is successfully completed. If TLG did crash, the next time you open it, the program will ask you whether you would like to see them. That way, you may be able to save any unsaved work you had when TLG crashed.
Windows 95, Unix and Mac OS all have different ways of creating line breaks. In Preferences under the Opening tab there is an option captioned "Convert Macintosh/Unix files". Check it and TLG will automatically convert Mac or Unix-style line breaks to Windows 95. If you ftp'ed the files you can avoid this problem by using ascii mode instead of binary when downloading.
Yes, if you use the Export/Mac or Export/Unix menu items, found under the File menu. Or you could use ftp them in ascii mode.
TLG's font formatting is contained in RTF (rich text format). By using the Export/RTF menu item, found under the File menu, you can make a .rtf file that preserves the special formatting in your input or output file. You may then open that in the word processor of your choice.
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.
Yes. To do this, select Preferences... from the File menu. A tabbed dialog will appear on the screen. Select the AutoFormat tab. There you have full control over all elements of the AutoFormat feature - you may select which events trigger formatting, what colors to use and which types of code to format. Unfortunately TLG only supports the 16-color Windows system palette in the text editor, so your choices are somewhat limited.
If you like to access menu items via the keyboard (using alt-key combinations), you can show them by opening the Preferences, switching to the Environment tab and clicking the "Show accelerator keys" check box.
This is a problem with Windows 95. There seem to be some TrueType fonts, such as Courier, which can't be sized below 10 points. However, the Windows 95 font dialog makes you think you can.
Yes. To do this, select Preferences... from the File menu. A tabbed dialog will appear on the screen. Select the "Text" tab. There you will find options for the input and output window defaults. You can change the font, font size, style and color, as well as the input and output windows' background color.
The plus signs after the document name mean that the file is "dirty", ie, it is currently unsaved. If you have many files open at once this is a handy way of making sure all are saved in case something goes awry. You can use the Save All menu item (under the File menu) to save all windows at once.
Two situations can cause this problem. First, you may have manually set the working directory for your TSP executable. This problem is usually caused by the TSP executable's application settings being set wrong under Windows. We have directions available for both Windows 3.1 and Windows 95/98/NT for how to configure your copy of TSP so it can interact properly with TLG.
The other problem that could occur is TLG is trying to run a copy of TSP that does not have adjustable memory (most likely a copy of 386 TSP 4.2b). TLG is compatible only with versions of TSP that can run by themselves under Windows 95, i.e., DPMI versions of TSP 4.2b, or TSP 4.3 and higher.
Early versions of TLG (1.00 and 1.02) are unable to process certain ascii characters which are nonstandard in Windows.
Occasionally TSP will generate these characters while processing a TSP input file, so they have to be stripped out before TLG can display the output. This problem has been fixed in TLG 1.10, so if you encounter it, you download it from our TLG update page.
Currently TLG only supports the editing and running of TSP batch files. Interactive mode is something we might add in a later release, along with more data display options and command-making dialog boxes. However, TSP/GiveWin runs in interactive mode with graphics in separate windows, so that is the best way at present to do this.
Yes. Just click the "Cancel" button on the "Sending [your batch file] to TSP" dialog box. This will stop TLG from opening the output file. However, you will notice your computer slowing down slightly since TSP will still be processing your batch file in the background. This is because TLG can not tell TSP to stop executing once it's started. We hope to change this in future versions if TLG and TSP become more tightly integrated.
Yes, though unless you have a very powerful machine with lots of RAM you will probably find your machine slowing down so much it won't be useful. Each time you run a batch file it will open a new copy of the TSP executable, and that rapidly consumes RAM.
By clicking this option, TLG will do a find and replace in every input and output window you have open, not just the active one. This can be very useful for renaming variables. However, take care, since unlike a normal find and replace, a global find and replace is not undoable.
One of two things may have happened. First, you may have not installed the help files when you installed TSP 4.4. Install TSP 4.4 again and this time do a Typical or Custom install, making sure the box next to the Help Files in the list of installation options is checked.
The second possibility is that you inadvertently moved or deleted the help file. The file is named TLG_HELP.HLP and must reside in the same directory as the TLG executable, TLG.EXE. That location is the directory C:\TSP44 unless you chose something else when you installed TSP 4.4.
There is no difference other than the name and a few fixed bugs. For more information on all the different versions of TLG, look at the next question, which lists every version of TLG.
Currently there are seven different versions of TLG:
TLG 1.00 - the original version of TLG that shipped with TSP 4.4 for Windows 95/NT.
TLG 1.01 - the Windows 3.1 version of TLG.
TLG 97 - version of TLG created to fix incompatibility with Microsoft Office 97.
TLG 1.02 - Office 97-compatible version of TLG, renamed to maintain version number consistency and reflect some incremental bug fixes.
TLG 1.10 - upgrade to TLG for TSP 4.4 which encompasses all bugs fixed in TLG 1.02 as well new features and enhancements. Supersedes all previous versions of TLG except 1.01. Available for download.
TLG 1.15 - updated version which ships with TSP 4.5, for TSP without GiveWin.
TLG 1.20 - version which ships with TSP 4.5, for TSP with GiveWin.
Just go to http://www.best.com/~fozboot/cats/fozboot.html and all questions will be answered.
The reason is that there is no support currently in TSP batch files to store header and footer options for TLG. This is something that may be changed in future versions if users request it. If you want more printing options, we recommend opening your batch file in a word processor such as WordPerfect or Microsoft Word and printing it from there. TSP batch files are simple text files and can be opened by any word processor. If you wish to preserve TLG's formatting, you can use the Export RTF feature.
We wanted to include printing as a feature of TLG 3.1 but it turned out the API support for printing in that version of Windows is very different than in Windows 95 and would have required a substantial programming effort. We decided our efforts were better spent improving TLG's interaction with TSP and other, more value-added features. If you need to print your TSP files under Windows 3.1 we suggest you use Microsoft Write or any other word processor to open them. TSP input and output files are ascii in nature and can thus be opened by any word processor, though you will probably have to change the file type selector in the dialog box to "All files (*.*)" in order for them to show up.
You probably installed Microsoft Office 97 or one of the Microsoft Visual Studio 97 family of products (Visual C++ 5.0, Visual Basic 5.0, Front Page 97, etc.). These applications install versions of system files which are incompatible with the original version of TLG. The solution is download TLG 1.10 (which supersedes TLG 97) from our TLG update page.
You probably installed Microsoft Office 97 or one of the Microsoft Visual Studio 97 family of products (Visual C++ 5.0, Visual Basic 5.0, Front Page 97, etc.). These applications install versions of system files which are incompatible with the original version of TLG. The solution is download TLG 1.10 (which supersedes TLG 97) from our TLG update page.
Although TLG will run under Connectix Virtual PC, DOS/Win TSP will not. There appears to be conflict between Virtual PC's memory management for DOS applications and DOS/Win TSP. However, even if you were able to use TSP, you would probably not find it fast enough to be worthwhile. If you have been able to successfully run TSP under Virtual PC, please email TLG Tech Support and tell us how you did it.
Due to the limitations of the development tools we used, and the constraints of time and budget, we were only able to support Windows 3.1, 95 and NT users for this release of TLG. It is unlikely at this time that we will be able to port TLG to Unix. However, we may make an X windows version of TSP for unix at some point, which would do X graphics in the PLOT and GRAPH commands.
If you problem seems to happen when you are using TLG, then please send an email to TLG 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 TLG. Try to be able to answer the following questions:
What version of TLG are you using?
What operating system are you using?
If you are using a PC, who manufactured the machine you are using?
If TLG 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.