Running the analysis
After running an analysis, there are errors. When
they are viewed, the error message 'out of string space' appears
The main program error file (*.mpe) is too large to be opened up in notepad. Manually open up the file in another text editor and view the errors.
When I run an analysis in Double precision, under
Windows 3.11, I get an error: 'Insufficient memory to load this program'. But th
e single precision works fine.
This is probably due to a lack of conventional memory (ie memory below 640K). Run MEM at the DOS prompt. If this shows less than 500Kb of Free Conventional memory, you are likely to have problems. Run MEMMAKER from DOS so that drivers etc are loaded into HIMEM not conventional.
How do you run the convertor without rerunning the
The Convertor can be re run by running the SCDATAB.EXE program located in the SAGE CRISP directory. The program requires that the complete directory name (including full path) is entered manually. Note:- The file extension is not required.
I get the message "NRS converter program not
found" after running an analysis and cannot look at my results in the Post
This problem is usually an ini file problem. In the ini file the section called programs should look like this:-
The SAGE CRISP Looks to see what the program name is for the NRS file convertor (nrs = scdatab.exe) and then runs the program. The two possible causes for your error message is that either the program is
not correctly referenced in the ini file or scdatab.exe is not in the
When running an analysis with slip elements the
main program crashes on increment 1 in routine DSLIP
This is usually caused by the thickness of the slip element being set to zero. Change this to a small value and rerun the analysis. Check the technical reference guide for future information on slip element thickness
After the analysis has run I get *.LIK file not
This is a common Problem.
It is most likely that you are having problems with DBOS. This is probably stopping the analysis from running properly. You will need to check the following:
1) The DBOS disk has been installed,
2) DBOS is referred to in the path statement in your autoexec.bat file,
3) the file wdbos.386 is present in either the DBOS or Windows directory and
4) the line ‘device=wdbos.386’ is present in the [386enh] section of your windows system.ini file.
In order to rectify this problem you should
First view the autoexec.bat file in a text editor (type ‘edit c:\autoexec.bat’ in Dos. Go to file manager, click on File, then Run and then type ‘notepad c:\autoexec.bat’ in Windows 3.xx. Start, run then type ‘wordpad c:\autoexec.bat’, in Windows 95). The line beginning ‘Path’, should have c:\dbos.dir added to it (note that the different paths in the path statement are separated by semi colons).
If dbos.dir is in the path statement then;
Determine where wdbos.386 is on your hard disk. The first place to check is in the DBOS directory, if it is not there it may be in the windows directory.
Then check the system.ini file in the windows\system directory to make sure wdbos.386 is referenced. The procedure to view this file is the same as described above. In the file, you should find the section headed ‘[386enh]’ and then search for a line saying ‘device=c:\directory name\wdbos.386’ (the quickest way to do this is to search for ‘wdbos.386’ using the search facility in your text editor). If the line does not exist, you will need to add it at the end of the [386enh] section.
If the wdbos.386 line exists in the system.ini file and the autoexec.bat file has dbos.dir in the path;
The problem maybe that the wdbos.386 file is missing or corrupted. It should be 155985 bytes in size and should be in either the dbos or windows directory.
If this does not solve the problem, go to the SAGE CRISP directory and check the date and size of the SCDATAB.EXE file as it sounds like you could be running the old version. If you are running v3.01, the size, date and time should be 31260, 22/8/96 and 3:33:10 respectively. If you have V3.02, the size, date and time should be 34322 bytes, 1/4/97 and 03:02:00 respectively. If this file is okay, then please send me a printout of SAGEINST.LOG from the SAGE CRISP directory and I shall see if there are any other problems with the installation which might account for your difficulties. You could also run the SAGEDIAG.EXE on the SAGE DIAGNOSTICS diskette and send me a copy of the output - c:\sagecrsp.log. Finally, please run an analysis, after choosing ‘Pause between steps’ in the Run Analysis dialogue box and tell me what messages you get in the DBOS window.
If you are still encountering problems, please fax Geoff Watson [(44) 1225 42447443 ] the diagnostics output and the installation log and I shall endeavour to find the problem.
What does the squasher program do?
The squasher program calculates the most efficient way to analyse the mesh and renumbers it (internally) for the frontal solver.