Support

Get Support

Direct support is available through the code-selling office or agent that completed your code sale (use the office/agent locator if you are unsure who to contact). Clients of Itasca Consulting Group can use the online Support Request form.

Code Support Policy

Itasca offers full support for the current release version of a code. Itasca also supports the version immediately preceding the current version for 12 months after release of the current version. Code support includes providing email and telephone support, at no charge, to assist the code owner in the installation of the code on the owner's computer system. Additionally, general assistance may be provided in aiding the owner in understanding the capabilities of the various features of the program. However, no-cost assistance is not provided for help in applying Itasca Software to specific user-defined problems.

Technical support covering modeling questions, applications, definitions, interpretation of results, design guidelines, etc., can be purchased on an as-needed basis. For users who envisage the need for substantial amounts of assistance, consulting support is available. In all instances, the user is encouraged to send the problem description to Itasca by fax or electronic mail in order to minimize the amount of time spent trying to define the problem.

Itasca reserves the right to determine what qualifies as no-cost assistance and what requires payment.

Support for versions of codes earlier than the current release versions is limited to bug fixes for existing functionality only for the version immediately preceding the current release version. Development (addition of new features, enhancements to existing features, etc.) is ceased once a version is superceded by a newer release.

Terms and Conditions for Licensing

Please read the following terms and conditions of this agreement carefully before using any Itasca codes.

Installation of the code onto your computer indicates your acceptance of the terms and conditions in this agreement.

If you do not agree with these terms and conditions, please do not install the code.

This program is provided by Itasca Consulting Group, Inc. or one of its authorized suppliers. Title to the media on which the program is recorded and to the documentation in support thereof is transferred to the customer, but title to the program is retained by Itasca. Itasca owns all intellectual property in the program. Itasca permits you to use the program only in accordance with the terms of this agreement. You assume responsibility for the selection of the program to achieve your intended results and for the installation of the program, the use of and the results obtained from the program.

License

1. All Itasca codes (with the exception of Demonstration Versions, see below) are secured software and require a hardware lock to operate the code.
2. A standard single license allows up to two instances of the code to cycle on a single computer. A Network Version (see below) allows one instance of the code, per seat, to cycle on any computer connected to the network.
3. You may make one copy of the program for backup only in support of such use and provided your backup copy is not installed or used on any computer.
4. You may not use, copy, modify, or transfer the program, or any copy, in whole or part, except as expressly provided in this document. You may not reverse engineer, decompile, or disassemble the program to obtain the source code of the program.
5. You may not sell, sub-license, rent, or lease this program.
6. Licenses are not transferable outside the purchasing organization, company, institution, or corporation. Licenses sold to private individuals are not transferable under any terms.
7. The program may not be shared, installed, or used concurrently on different computers (with the exception of Network Versions, see below).

Terms

The license is effective until terminated. You may terminate it any time by destroying the program together with any back-up copies and returning the hardware lock. It will also terminate if you fail to comply with any term or condition of this agreement. You agree upon such termination to destroy the program together with any back-up copies, modifications, and/or merged portions in any form and return the hardware lock to Itasca.

Warranty

Itasca will correct any errors in the code at no charge for twelve (12) months after the purchase date of the code. Notification of a suspected error must be made in writing, with a complete listing of the input and output files and description of the error. If, in the judgment of Itasca, the code does contain an error, Itasca will (at its option) correct or replace the copy at no cost to the user or refund the initial purchase price of the code. This warranty does not apply to demonstration versions (see below).

Limitation of Liablility

Itasca assumes no liability whatsoever with respect to any use of the code or any portion thereof or with respect to any damages or losses that may result from such use, including (without limitation) loss of time, money or goodwill that may arise from the use of the code (including any modifications or updates that may follow). In no event shall Itasca be responsible for any indirect, special, incidental or consequential damages arising from use of the code.

Export

You may not ship, transfer, or export into any country the program or its updates in any manner prohibited by the United States Export Administration Act or any other export laws or restrictions. In addition, you represent and warrant that you are not a citizen or located within an embargoed nation (including without limitation Iran, Syria, Sudan, Cuba, and North Korea) and that you are not otherwise prohibited under United States Export Laws to receive the program. Rights to use the program are forfeited for failure to comply with this agreement.

Hardware Locks

Title to the hardware lock(s) associated with a license belongs to Itasca. You are wholly responsible to maintain and safeguard the hardware lock. Itasca reserves the right to determine the cost of replacing a lost or stolen hardware lock, up to and including the cost of a new license.

Updates and Upgrades

If the software is an update or an upgrade to a previous version, you must possess a valid license to the previous version. Any update or upgrade provided for a previous version is subject to the terms of this agreement. You may continue to use previous versions provided that (a) it is necessary to use the previous version to read or otherwise use outputs from that version of the program, (b) you do not transfer the previous version to another party, and (c) you acknowledge that any obligation that Itasca has to support the previous version of the program may end upon obtaining the update or upgrade.

Network Versions

If and only if the program is a network version, the terms of this agreement apply in all respects with the following exception: the software may be used concurrently on the number of machines for which the program has been licensed and as allowable by the program’s hardware lock.

Demonstration Versions

If and only if the program is a demonstration version, the terms of this agreement apply in all respects with the following exceptions. The program is provided “AS-IS” and Itasca bears no responsibility to provide support for the program. The program shall be operable without a hardware lock. You acknowledge that the program may contain bugs, errors or other problems for which Itasca disclaims any warranty or liability obligations.

Code Support

Itasca will provide email and telephone support, at no charge, to assist the code owner in the installation of the code on the owner’s computer system. Additionally, general assistance may be provided in aiding the owner in understanding the capabilities of the various features of the program. However, no-cost assistance is not provided for help in applying Itasca Software to specific user-defined problems.

Technical support covering modeling questions, applications, definitions, interpretation of results, design guidelines, etc., can be purchased on an as-needed basis. For users who envisage the need for substantial amounts of assistance, consulting support is available. In all instances, the user is encouraged to send the problem description to Itasca by fax or electronic mail in order to minimize the amount of time spent trying to define the problem.

Itasca reserves the right to determine what qualifies as no-cost assistance and what requires payment.

Jump to top

• Whom do I contact for code support?
• What is the best system configuration for my Itasca code?
• Where is the "Knowledge Base?"; Why not more "FAQs?"
• What is the best method for moving my Itasca-code plot to my word processor/presentation/other software program?
• What is the best way to make an animation using output from my Itasca code?

Whom do I contact for code support?

Questions should, in the first instance, be directed to the office or agent where your code was purchased, from where it may be escalated to senior staff if necessary.

All Itasca software is sold through Itasca offices and a network of agents throughout the world. If you do not know which office/agent sold your code, please use the office/agent locator to determine your primary source of technical support.

Clients of Itasca Consulting Group can use the online Support Request form.

What is the best system configuration for my Itasca code?

See the topic "Hardware Configurations FAQ" on this page.

Where is the "Knowledge Base?"; Why not more "FAQs?"

Extensive "Knowledge Bases" and FAQs constitute the "free" portion of a software vendor's support policy; usually, to speak with support personnel is a pay-per-event process. Itasca software is supported in a free, person-to-person manner (see the Support Policy for a complete statement). As a result, there is no need for extensive internet-based support documentation. The information provided in the FAQs available here focuses on two areas: critical code operation issues (startup, keys, installation, etc.) whose resolution should not be delayed by having to wait for communication during normal business hours, and topics of occasional interest that are not immediately proper to the codes themselves (handling plots or making animations, for instance — the subjects of the next two questions).

What is the best method for moving my Itasca-code plot to my word processor/presentation/other software program?

In the last few years, Itasca has added significant new graphical output capacity to each of its codes. Soon all Itasca software will be able to create bitmap (BMP), jpeg (JPG), pcx (PCX), and enhanced metafile (EMF) output, as well as allowing for cut-and-paste operations through the Windows clipboard. As ever, the option to create PostScript (PS) output is available as well. The newer formats provide more user-friendly graphics than PostScript, the original — and once sole — option for graphical output. We recognize the importance of generating intelligible, professional-quality plots from our codes that may be efficiently included in reports and presentations; this is the very reason the new format options were added to the codes.

However, the greater number of choices for output has also increased the number of difficulties users encounter when moving from an Itasca code to the final destination program for that output. Unfortunately, we are unable to propose a "one size fits all" solution to these difficulties. We are not in a position to support or guide all users in the use of all their word processor, presentation, animation, or other software — where, as often as not, the real problems arise. Also, any graphics-based operation is contingent on a number of decisions and potential tradeoffs that are ultimately up to the user (e.g., is the final media going to be print or onscreen? is there a file-size sensitivity for the final media? what is the resolution capability of the output device? and so on ...).

That said, we are happy to share the following general guidelines that we ourselves observe when using our codes for consulting work at Itasca.

1. Avoid using the clipboard (using the SET plot clipboard command), primarily because it creates a situation in which the only "original" copy of the graphic output is that which has been copied-and-pasted into the destination software (for instance, such copied-and-pasted "originals" in Microsoft Word often are intractable to subsequent editing).

2. Don't hesitate to switch formats; if EMF output is not working well, use JPG or PCX files; if PostScript output creates oversized files, use bitmaps, etc.

3. Do not confuse the Itasca code with a graphics-editing package. If annotations, cropping, or other image editing is necessary, create a good-quality plot (PostScript, ideally) and make edits to it using a graphics-editing package. Itasca software is not designed to create image-art. Nor, for that matter, are word processor and presentation programs.

4. Use other tricks. One favorite is to use the "Print Screen" button on your keyboard. This puts a bitmapped copy of your entire screen on the Windows clipboard and can be pasted into another program (using the "Alt" key + "Print Screen" will capture only the active window, if you prefer).

What is the best way to make an animation using output from my Itasca code?

FLAC, UDEC, and 3DEC all contain a command, MOVIE, that allows the user to generate a sequence of PCX plots that are strung together and written to a DCX file that can be viewed using the "MOVIE.EXE" utility that comes with Itasca software. This is probably the fastest approach, but it is not available in FLAC3D, PFC2D, and PFC3D. Also, the MOVIE utility outputs DCX files (the animated version of the PCX format), which is an increasingly rarified file type. Given these shortcomings, it is easy to see why this question comes up. There is no single accepted way to make an animation, considering the plethora of animated file types (AVI, MPEG, MOV, GIF, QT, DCX, SWF, TIF, etc.) and the differences in the final presentation mode of the animation (on the web, in PowerPoint, in a MediaPlayer, embedded in a PDF file, etc.). Here, we share some of the techniques that we have used in the past as options for consideration.

Using a Bitmap Image Editor: Create a set of plots in a bitmap format (JPG, BMP, and PCX files can be output from all the codes). String them together in a bitmap-editor that will produce animated formats (we use Corel Photo-Paint to do this). Apart from the MOVIE command technique, this is probably the fastest method.

Get Around the PostScript Problem: If the initial set of output plots is in PostScript format, we have done the following: Batch-process the entire set into one PDF file using Adobe Acrobat. (Note: you need the full Acrobat program — not just the free Acrobat Reader — to do this.) Crop the resulting PDF file to obtain the desired image size. Choose the graphic selection tool, "Select All," copy the selection, and paste it into an animation building program. Repeat these steps for each page in the PDF file, and save the animation to the desired format.

Using PowerPoint: With slide timings set to zero seconds, a PowerPoint presentation becomes, in effect, an animation. PowerPoint will import all of the code output formats that are available in Itasca software (except PostScript — see the previous point for handling that problem). Since it appears that one predominant use for animations is in making presentations, we recognize the importance of PowerPoint relative to this topic. Consequently, we have built a PowerPoint file that contains a macro that automatically imports the user's entire set of graphic files, thus generating the final animation "all at once." The download available below also contains instructions on how to use the PowerPoint file.

Download the PowerPoint file (ZIP 38k)

The Really Quick "Look No Movie File" Movie: Many image-viewing programs — we use one called "ACDSee" — will automatically, sequentially display a specified collection of images. If the transition time between image views is set to zero seconds, a set of images can be viewed as an "animation" without ever being turned into an animation-format file.

It is worth remembering that (almost) any animation is just a set of rasterized (bitmap) images strung together into a single file with a timing mechanism controlling the rate of movement from one image to the next. Thus the critical questions are: What program will do the stringing? and, What is the final use/destination of the resulting file?

As noted above, the nearly-ubiquitous PowerPoint will create an "animation" but it will not output the slide show to an animation format. If an animation-format file is required, users will need a program that can import the original set of images and then output them to the desired format. Commercially available products from Adobe, Corel, Microsoft, Macromedia, and others will do this. Users are also directed to consider other, less expensive options, such as shareware or freeware, where there is an abundance of options ranging in price from $100 to $0. Entering "animation software" in any web search engine will quickly get you into this large realm of possibilities. Also note that most animation formats are proprietary: their proprietors desire their format to become the "standard" animation type and will offer low- or no-cost tools for building animations in that format.

Jump to top

• How FLAC starts: General Description
• How FLAC starts: Detailed Description of Versions 4.00.222 through 4.00.293 as configured by installations from Itasca CD Versions 7A through 7E
• How FLAC starts: Detailed Description of Versions 4.00.294 through 4.00.313 as configured by installations from Itasca CD Versions 8A through 10A
• How FLAC starts: Detailed Description of Versions 4.00.314 through current as configured by installations from Itasca CD Versions 11A through 12A
• "Can't load file jvm.dll"
• Can't load file jvm.dll: FLAC won't run on Pentium 4 (P4) system [affects FLAC 4.0 installations from CD versions 7A, 7B, and 7C ONLY]
• Can't load file jvm.dll: FLAC won't start on Windows NT, 2000, XP
• Can't load file jvm.dll: FLAC won't start on a network
• "Java/GIIC failed to initialize. GIIC canceled."
• Why does the program appear to start then disappear?
• How do I change the amount of memory utilized by FLAC?
• How do I start FLAC in command-line mode?
• Security key errors on a Toshiba laptop

How FLAC starts: General Description

The Windows executable flacw_sp.exe or flacw_dp.exe (single or double precision) must be started. Immediately, the JAVA runtime environment (JRE) must be located and loaded (this is done by loading "jvm.dll" from a properly formed JRE directory tree). Then, the graphical interface ("GIIC", which is a JAVA application) is started by locating and loading the "giic.jar" file, which contains the classes for the GIIC.

This process must occur in the order described. The critical steps in this process are locating and running the "jvm.dll" and "giic.jar" files; the majority of FLAC startup problems involves errors in one or both of these steps. Since the GIIC is separate from the FLAC executable, a method must be used to start it as well; the method for doing so has changed over time with different installations and is described for each of the respective "Detailed" answers below.

How FLAC starts: Detailed Description of Versions 4.00.222 through 4.00.293 as configured by installations from Itasca CD Versions 7A through 7E

The FLAC executable is started using a shorcut on the Start menu to the file "flacw_sp.bat" (note it is NOT started from flacw_sp.exe — attempting to do so will result in a flashing and disappearing command prompt). A command prompt ("DOS prompt") opens. The first line of the BAT file identifies the location of the JRE using an environment variable. Typically, the first line looks like:

set PATH=%giic%\jre\1.2\bin\classic

Here %giic% is an environment variable that was established during installation that stores the code installation location. Thus, the PATH of the first line evaluates to "c:\itasca\jre\1.2\bin\classic" (assuming the user accepts the default location of "c:\itasca" at installation time). At this location (that is, in the "classic" folder) the file "jvm.dll" should be located. If it is not, an error will result.

The second line of the BAT file is:

%giic%\flac\flacw_sp %1

This line starts the "flacw_sp.exe" file (per above, it evaluates to: "c:\itasca\flac\flacw_sp.exe". The "%1" is a placeholder for a numerical command line argument that may be used to allocate the amount of memory to be used by FLAC.

When the "flacw_sp.exe" is started, the command line argument "GIIC" is immediately passed to it by the file "flac.ini", which is located in the same directory as the executable. This argument starts the GIIC. Removing the word "GIIC" at the start of the "flac.ini" file would prevent the GIIC from automatically loading during FLAC startup — that is, it would allow FLAC to start in command-line mode.

The foregoing description utilizes default installation path ("c:\itasca") in discussing startup. The "%GIIC%" environment variable is formed at installation time and will store whatever location is specified when the code is installed — that is, a user-specified installation location is acceptable since the "%GIIC%" variable will accurately direct FLAC to the necessary files for startup. The description also assumes the user is starting "single precision" FLAC (the procedure is the same in all respects for the double precision version except the file names and BAT file commands use "dp" instead of "sp").

How FLAC starts: Detailed Description of Versions 4.00.294 through 4.00.313 as configured by installations from Itasca CD Versions 8A through 10A

The method is identical to the one above with the following exception: the FLAC EXE files (single, double precision) are located in a folder named "exe" below the main "FLAC" folder in the installation directory ("c:\itasca\flac\exe"). The BAT files are still found in the "FLAC" folder. As a result, the lines of the BAT file appear as follows:

set PATH=%giic%\jre\1.2\bin\classic
%giic%\flac\exe\flacw_sp %1 giic

The first line is the same as before. The second line now points to the location of the EXE file in the "exe" folder; also, the command line argument "giic" appears in the BAT file, which causes the GIIC to be loaded automatically on FLAC startup. Removing this command-line parameter would cause FLAC to start in command-line mode without the GIIC. Also, with the GIIC being started from the BAT file, rather than the "flac.ini" file, it is possible to start FLAC in command-line mode directly from the EXE file without causing an error (as occurred with the earlier startup method).

How FLAC starts: Detailed Description of Versions 4.00.314 through current as configured by installations from Itasca CD Versions 11A through 12A

FLAC is started from a shortcut on the Start menu that has as its target:

"c:\program files\itasca\flac\exe\flacw_sp.exe" giic

The quoted string points to the FLAC EXE; the word "giic" is a command line parameter for starting the GIIC (removing the word from the shortcut would cause FLAC to start in command-line mode).

When the executable starts, it searches, successively, for values in the Windows registry and then for the "GIIC" environment variable (this allows for backward compatibility with the older startup method). Either the registry values or the environment variable, when located, will provide the location of the JRE and the GIIC. An error will result if the information is not located, or if it incorrectly specifies the needed locations.

The location in the registry where the values are stored is "HKCU\Software\Itasca\FLAC". The values are strings the the following name/value pairings:

jrepath c:\program files\itasca\shared\jre\1.2\bin\classic
giicpath c:\program files\itasca\

The "jrepath" string indicates the location of the JRE; the "giicpath" string indicates the location of the "giic.jar" file. The "giic.jar" location is derived by combining the value of the string with the addition "flac\gui\", making a complete path that is "c:\program files\itasca\flac\gui". The "giicpath" stores the location where the code was installed, which may be changed by the user at installation time; the "flac\gui" portion of the path is NOT changeable by the user and thus may be added to whatever is stored in "giicpath" to correctly derive the location of "giic.jar". The preceding description has assumed that the default installation was used when installing; if the user specifies an alternate location at installation time, the registry strings and Start Menu shortcut are formed to reflect the user-specified location. Also, when installing on Windows NT, 2000, and XP, the installation will only work for the user-profile in which the installation was performed (see Q7 below).

"Can't load file jvm.dll"?

This error indicates that the "jvm.dll" file could not be found or loaded, which prevents loading the JRE, which is necessary to run the GIIC. To resolve the problem, the user should check the path specified in the PATH statement in the first line of the "flacw_sp.bat" files (see Q2 above), and/or check the path specified in the string stored in "HKCU\Software\Itasca\FLAC\jrepath" (see Q4 above). Either should indicate a folder in which "jvm.dll" can be found. If the file is properly specified and situated, there may be a problem with the overall structure of the JRE on the user's machine. In such an event, the user should either reinstall FLAC or try reinstalling the JRE alone (see Q6 below for information on doing this). There are other specific causes for this error described in the next three questions.

Can't load file jvm.dll: FLAC won't run on Pentium 4 (P4) system

[this topic is specific to installations of FLAC from CD versions 7A, 7B, and 7C; the problem described is corrected on CD versions 7D and higher]

The Java Runtime Environment (JRE) Version 1.2.2 that installs with FLAC 4.0 does not work on P4 systems. Most commonly the error reported on startup is "Can't load jvm.dll", but other error messages are possible. To resolve this problem, users will need to acquire a new JRE (5.3M file) from Sun. The correct JRE is the Java2 Runtime Environment v 1.2.2_011, available at:

http://java.sun.com/products/archive/j2se/1.2.2_011/jre/index.html
(click the "download" button, accept the license agreement, and choose the US English version for Windows platform)

Important Note: There are newer versions of the JRE, but currently the GIIC should only be run using JRE 1.2.2_011.

After download, when running the installation, YOU WILL NEED TO CHANGE THE INSTALLATION'S SUGGESTED DEFAULT to the location where FLAC and the JRE were originally installed. A standard (default) installation location from Itasca CDs 7A, 7B, and 7C is:

c:\itasca

When installing the JRE 1.2.2_011 update from Sun, the installation program will suggest installing to this location:

c:\program files\Javasoft\JRE\1.2

To properly install the JRE to work with FLAC, this location should be changed to:

c:\itasca\JRE\1.2 [assuming the default location per above]

If the installation of FLAC was put in a user-specified location, then the "c:\itasca" portion of the path above must be changed to the same user-specified location that was entered when installing FLAC.

Can't load file jvm.dll: FLAC won't start on Windows NT, 2000, XP

[in this case specific to FLAC installations from CD version 11A and 12A]

If the user profile when starting FLAC is not the same as the user profile that installed FLAC, an error will occur on startup. (This kind of error is common for users who have system administrators perform their FLAC installation but then try run using their own, differing user profile). To resolve, the user profile will need to have the "jrepath" and the "giicpath" added (see Q4 above. Alternatively, the code could be re-installed under the user's profile, but this does require that the user's profile be given administrator privileges on the machine.

Can't load file jvm.dll: FLAC won't start on a network

[in this case specific to FLAC installations from CD version 11A and 12A]

FLAC cannot be started from a remote machine on a network because the local machine does not have information (registry entries) to locate the "jvm.dll" (JRE) and the "giic.jar" (GIIC). The HKCU of the lcoal machine must have the "jrepath" and "giicpath" strings created in a "HKCU\Software\Itasca\FLAC" section of the registry (this location will also have to be created). The full network path corresponding to the EXE being used must be included. For instance, to start FLAC on a computer with the network name "Zeta", where the EXE is located at "c:\program files\itasca\flac\exe\flacw_sp.exe", the necessary strings/values are:

HKCU\Software\Itasca\FLAC\jrepath =
\\Zeta\c\program files\itasca\shared\jre\1.2\bin\classic
HKCU\Software\Itasca\FLAC\giicpath =
\\Zeta\c\program files\itasca

When started this way, FLAC is run as a process on the local machine, it is not run from the remote processor. The hardware lock necessary to run the code must be on the local machine, not the remote machine from which the code is being pulled.

"Java/GIIC failed to initialize. GIIC canceled."

This error indicates that the "giic.jar" file could not be found or it could not be loaded. To resolve the problem, the user should check the first line of the "flacw_sp.bat" file. Relative to the line "set PATH=%giic%\jre\1.2\bin\classic", the "giic.jar" file will be located in "%GIIC%\flac\gui" (see Q2 above for a fuller description for resolving the %GIIC% variable). Alternately, the user should check the path specified by the string in "HKCU\Software\Itasca\FLAC\giicpath" (see Q4 above). The string should indicate a folder in which "giic.jar" can be found when the additional string "\flac\gui" is added to it. If the "giic.jar" file is properly specified, then the cause of the error may be a corrupted file. In this event, the user should either download and install the latest version of FLAC from this web site or re-install from the CD. This error message is often followed by a line like this: "Execption in thread "main" java.lang.NoClassDefError: flac/gui/main/MainFlac". This is the error reported by JAVA and is part of the same problem; the last part of the message is useful, because it indicates that JAVA is trying to load the main class in the "giic.jar" file from the location "\flac\gui\main\MainFLAC". A correctly formed path would include the full location, that is, "c:\program files\itasca\flac\gui\main\MainFLAC". In other words, the error message is indicating that the correct path to the "giic.jar" file is not being used by FLAC when starting.

Why does FLAC appear to start then disappear?

When the FLAC executable and the GIIC are started together (as in all the startup methods described above), first the EXE is loaded into a command prompt ("DOS box"). Then, if an error occurs while trying to initialize and start the GIIC, it is reported on the command line, and then the command prompt is automatically closed. This behavior is not universally consistent across Windows platforms and under all error conditions. Some of the more common instances of the behavior include: installations of FLAC from CD versions 7A-7E would exhibit this behavior if the user tried to start FLAC directly from the EXE file instead of from the BAT file; startup with a faulty %GIIC% environment variable could cause the behavior; startup on a JRE that is incompatible with the processor (see Q6) could also cause the behavior.

Since the error message that occurs on startup is in fact reported on the command line, it is helpful to get around the "disappearing" problem in order to determine what the error message is. To do so, users should start FLAC "manually": open a command prompt (Start-->Programs-->Accessories-->Command Prompt), type in the location of the FLAC EXE file (for example, "c:\itasca\flac\exe\flacw_sp.exe"; bear in mind that quotes around the entire path may or may not be required). This should start FLAC in command-line mode. At the "flac:" prompt, type "GIIC". This should re-create the error condition that occurs on startup, but the window will not disappear and the error message may be obtained.

How do I change the amount of memory utilized by FLAC?

By default, the amount of memory that FLAC requests from the operating system is 8 Mbytes(single precision) and 24 Mbytes (double precision). For BAT-file based startups (see Q2 above), replace the "%1" in the BAT file with the desired amount of memory, in megabytes. For EXE-file based startups (see Q4 above), modify the shortcut to the EXE on the Start Menu by adding the desired amount of memory, in megabytes, after the word "giic" at the end of the target string. (Right-click on the shorcut in the Start menu and choose "Properties" from the resulting popup menu in order to make this adjustment.)

How do I start FLAC in command-line mode?

A non-GIIC startup for FLAC depends on the installation configuration. Either: 1) remove the command "giic" from the "flac.ini" file (see Q2 above), 2) remove the command line argument "giic" from the BAT file (see Q3 above), or 3) remove the command line argument "giic" from the FLAC shortcut on the Start menu (see Q4) above.

Security key errors on a Toshiba laptop

Toshiba laptops have been particularly error-prone when operated with Sentinel security keys. The following information is obtained directly from the Rainbow Technologies web site — the manufacturer of the Rainbow keys.

Itasca code users who are unable to get their Toshiba laptops working with the Sentinel keys despite trying the above recommendations may wish to contact SafeNet (formerly Rainbow Technologies) directly for further support:

phone: (800) 959-9954
web: www.safenet-inc.com
email: support@safenet-inc.com

Jump to top

• What is the Itasca CD?
• What is the CD-ROM Version?
• What does the version number mean?
• How do I identify the version number of my CD-ROM?
• Are the changes made from version to version of the CD-ROM documented?
• What codes are installed from the current version?
• Is the latest version of my code on the CD-ROM?
• Can I update my CD-ROM?
• Should I update my CD-ROM?
• Known Issues

What is the Itasca CD?

It is the CD-ROM from which all Itasca software is installed. It also includes electronic copies of the code manuals, and code demonstrations. It is freely available to anyone on request. Only licensed users will be able to run Itasca codes that are installed using the CD-ROM. Unlicensed users may install the codes and run them in "non-cycling" mode, which disallows solution cycling. Non-code users may also find the information in the manual and demos useful for code evaluation purposes.

What is the CD-ROM Version?

The CD-ROM is serialized, to provide tracking information and to assist in customer support. The number identifies the version of the Itasca CD-ROM. The number is incremented each time a code is newly added or upgraded on the CD, or if the installation routine for the codes is changed. The current version is 20C.

What does the version number mean?

The two digits at the beginning of the number represent the major version. The major version number only changes when a code is added or receives a major upgrade. The letter indicates the sub-version, which may indicate either minor code updates, bug fixes, or changes to the installation routine.

How do I identify the version number of my CD-ROM?

1) Look at the release window; the version number is written there.
2) Using Windows Explorer (or any file system viewing utility), check thevolume name of the disk; the version number is contained in the name of the volume.

Left: the version is written on the disk itself Above: the version number is contained in the name of the CD volume

Are the changes made from version to version of the CD-ROM documented?

Yes. The "readme.txt" file in the root of the CD-ROM contains basic user instructions for the CD-ROM and, in its last section, has a modifications list. Incidentally, viewing this list would also be a way to determine the version of the CD, since the final entry will indicate the current CD-ROM version.

What codes are installed from the current version?

Itasca23A installs the following codes:

• FLAC 6.0
• FLAC/Slope 6.0
• FLAC3D 3.1, 32-bit and 64-bit
• UDEC 4.01
• 3DEC 4.1, 32-bit and 64-bit
• PFC2D 4.0
• PFC3D 4.0

Is the latest version of my code on the CD-ROM?

The version of the code on the CD-ROM is the latest version that has gone through the full QA procedure. As this procedure is very lengthy it is not performed each time a minor bug is fixed. Because of this it is very likely that a newer version of the code is available from the Download section of this site. This is true even if you have just purchased the code. It is always useful to check this site for code updates.

Can I update my CD-ROM?

Yes. Itasca will freely provide the latest CD-ROM to users on request. If you are a user of any of the codes above, you may obtain a free copy of the latest CD, which contains the current best-practice installation for these codes.

Should I update my CD-ROM?

Since it is impossible to guarantee that today's installation will work on tomorrow's computers, updating your CD-ROM is usually the simplest way to ensure you can correctly install your Itasca code. However, frequent updating of the CD-ROM (from one sub-version to the next, for instance) is probably overkill. Check the list of "known issues" below to help determine whether your CD-ROM should be updated. Consider updating your CD-ROM when the major version number of the CD-ROM changes; seriously consider updating your CD-ROM if it is more than one major version number removed from the current CD-ROM.

Known Issues

Versions up to 4C: contained an error when uninstalling from Windows NT. This problem impacts: all codes. NT users who need to uninstall should do so manually (do not use the uninstall program in the "Add/Remove Programs" applet). Reinstall with a CD Version 4C or later, if possible.

Versions 7A, 7B: did not properly install Unikey drivers for the code security system. This problem impacts: FLAC3D 2.0, PFC2D 2.0, PFC3D 2.0. Users of these codes who have a 7A or 7B CD should update.*

Versions 7A, 7B, 7C: contained a Java Runtime Environment that does not function properly on computers that use a Pentium 4 processor. This problem impacts: FLAC 4.0. Users of FLAC 4.0 who have a Version 7A, 7B, or 7C CD-ROM should update.

Versions up to 10A: may exhibit security key errors when installing to some computers running the Windows XP operating system. This problem originates with Rainbow Technologies. An updated driver installation is available from the About the Keys page. Versions 10A and newer do not require an updated driver.

Jump to top

• Obtain the latest key drivers
• What is my "key" and why is it necessary?
• How many instances of the code can I run with a single key?
• Why does my code report an error locating the hardware lock on my machine?
• Why doesn't Windows XP find my key?
• Security key errors on a Toshiba laptop
• Are there configurations that will interfere with key operation?
• What if my computer does not have a parallel port?

Obtain the latest key drivers

These downloads may be used to install the most up-to-date key drivers that Itasca supplies for use with its codes. In most cases, only the Rainbow key drivers are necessary. Versions earlier than the current version of FLAC3D (versions 2.0 and earlier), PFC2D and PFC3D (versions 2.0 and earlier) may also require the Unikey drivers. Note these downloads may be saved to and run from any location on your computer.

Rainbow Key drivers (for Windows 95, 98, ME, NT, 2000, XP; size: 5.9M)
Unikey Key drivers (for Windows 95, 98, ME, NT, 2000, XP; size: 349k)

What is my "key" and why is it necessary?

The "key" (interchangeably referred to as a hardware lock or dongle) is a security device that prevents the operation of Itasca codes on machines where it is not present. The key is a dongle that is attached to either the LPT1 or USB port at the back of your computer. The key is serialized to your licensed version of the Itasca code you are using. Due to a changeover in 1998, users of newer versions of Itasca software will have Rainbow keys (distinguished by a tan case for parallel keys, or purple for USB keys). Users of older versions will have Unikeys (they have a black case).

How many instances of the code can I run with a single key?

As of June 1, 2008, a licensing policy emendation is being implemented in all subsequent releases of Itasca codes, and is applicable to all users (both new users and those who are upgrading to the new version). The policy, as described in the License Terms is "A standard single license allows up to two instances of the code to cycle on a single computer" and was created for the following reasons.

Under the previous terms of the licensing policy, we did not restrict the number of codes operating on a single computer under a standard license. If multiple instances of the code were being run, then they would execute proportionally slower. As multi-core and multi-processor computers became popular, it became a concern that owning such a computer effectively granted multiple licenses, because multiple instances could be run with no loss of speed. This was counter to the intent of our licensing.

At the time that we decided to change our licensing policy, dual-core computers were already in common use. Therefore, we decided to allow two simultaneous instances per license instead of restricting it to one. We also changed the security implementation so that a license is claimed only while cycling, allowing multiple instances to continue to be used for problem setup and post-processing analysis.

Why does my code report an error locating the hardware lock on my machine?

What: A key-related error is reported on starting the code, which prevents the code from being used.

Why: These errors occur when there is no key present on the user's machine. These errors also result from a faulty installation of the key drivers, or if the driver files have become corrupted/damaged/lost.

Fix: First check to see if your key is properly connected to your computer. If the key is properly connected, download and install the latest key drivers. Please note the drivers for both Unikeys and Rainbow keys must be installed, regardless of the individual type of key you have. Installation instructions are included in the download files. If there is still a problem after installation of the drivers, please contact Itasca.

Why doesn't Windows XP find my key?

Some computers running Windows XP experience difficulty in accessing the key using drivers that are distributed on the Itasca CD (versions up to 9C; see About the CD-ROM for information on CD-ROM versions). This can be solved in most cases by obtaining and installing newer Rainbow key drivers. Note you must have administrator privileges to update the drivers in Windows XP.

Security key errors on a Toshiba laptop

Toshiba laptops have been particularly error-prone when operated with Sentinel security keys. The following information is obtained directly from the Rainbow Technologies web site — the manufacturer of the Rainbow keys.

Itasca code users who are unable to get their Toshiba laptops working with the Sentinel keys despite trying the above recommendations may wish to contact SafeNet (formerly Rainbow Technologies) directly for further support:

phone: (800) 959-9954
web: www.safenet-inc.com
email: support@safenet-inc.com

Are there configurations that will interfere with key operation?

Can I piggy back it with other sofware dongles? The only limitation (known to Itasca) for daisy chaining parallel dongles is a power issue. Technically the power is supplied by the printer. If a printer is not attached, the port does supply some power but may not be able to handle multiple keys.
Lease keys should not be connected with other keys. FLAC3D, PFC2D, and PFC3D versions dated prior to September 2001 should also not be used with multiple keys attached. This will interfere with proper key operation and may result in destruction of one of the keys.

Can I plug the key somewhere into the chain of zip/CD/port connections? Storage devices may damage Unikeys. This has not been reported as a problem for the Rainbow keys.

Can I plug the key into the second port? Our testing with a second parallel port showed no problem or necessary modifications when using a Rainbow key. To get a Unikey to work on a second port, the line SSI_LPT=2 had to be added to SYSTEM.INI. The DDINST32.EXE file (the Unikey driver installation file) would not successfully make this modification, although the instructions claimed it could do so.

What if my computer does not have a parallel port?

For a flat shipping/handling fee, Itasca will trade your parallel key for one that will work through your USB port.

Jump to top

• How do I overlay a DXF image on a FLAC 4.0 grid using the GIIC?
• Why does FLAC3D report the error "Error in system date/time - check your system date and time?"

How do I overlay a DXF image on a FLAC 4.0 grid using the GIIC?

1. Click on the [Draw] menu from the [Model] pane.
2. Click on [Images], and then [DXF].
3. A dialog box will open and allow you to browse your folders and find the desired DXF file.
4. If, for example, you have a DXF file named CIRCLE.DXF, click on this file and open it.
5. The figure should nw appear in the [Model] view.
6. If you do not see it, click on [Reset] (full view) in the [View] menu. You can also zoom in on the view (with [Zoom] box) or translate it (with [Translate]). Also, click on [Fix View] in the [View] pane to fix the oreientation of this view.
7. Now, create the FLAC grid. For example, use the [Simple] tool from the [Build] tab, and adjust the coordinates of the grid to encompass the DXF image. You should now see the "virtual" FLAC grid with the DXF image superimposed. When the [Execute] button is pressed, the commands are sent to FLAC to create the grid.
8. You can make a plot of the grid with the DXF image by using the [Model] tool in the [Plot] tab. Click on [Plot Items/Geometry/dxf] to open a dialog to access the DXF image, then click on [Plot items/Geometry/grid] to add the grid plot. Both items should be added to the plot items list. Then click [OK] and the plot will be created. This is the same as PLOT DXF CIRCLE.DXF GRID.

Why does FLAC3D report the error "Error in system date/time - check your system date and time?"

This problem only effects users that have a leased key. A system variable "timezone" (that is used in FLAC3D) gives two different values in DOS and Windows systems. This system discrepancy was noted and corrected (in version v2.00.092) after FLAC3D version 2.0 was put on the official Release CD (the CD release version is FLAC3D v2.00.071). Users should therefore download the latest version of FLAC3D v2.0 (DOS or Windows) from our website after their installation of the FLAC3D v2.0 from the Release CD.

On versions previous to 2.00.92, if the user runs the DOS version of FLAC3D and then tries to run the Windows version, the System Time/Date error will result from incorrect data being written into the security key.

This error can be rectified:

1. If the user obtains a new password from the sales agent that resets the security key parameters.
2. If the user waits for a day and then starts the latest DOS/Windows version of the code after updating it through our website.

Jump to top

Current versions of Itasca software (see the "Release History" on the Software Overview page for the list of these) are supported on the following Windows operating systems.

• Windows XP, 32- and 64-bit
• Windows Vista, 32- and 64-bit
• Windows 7, 32- and 64-bit

Any other operating system not specifically listed above is NOT supported by Itasca for use with Itasca software. Itasca software may run on these platforms, but as they are not supported Itasca provides no assurance of compatibility with them and will not provide support for them.

Itasca's 32-bit codes are operable on 64-bit computer systems, however, they are not 64-bit programs and do not have 64-bit addresses. Itasca recommends that, whenever possible, users run versions of Itasca codes matched to the 32-bit or 64-bit environment of their computer.

In general, when new Windows operating systems are released it becomes possible, even likely, that there will be errors if users try to use their old installation CD for an Itasca program on the new operating system. In this case it is strongly recommended that the user obtain the latest installation CD available from Itasca for their software.

If you are experiencing problems related to your operating system that are not resolved by the information available here, feel free to contact Itasca for assistance with your issue.

The speed performance of Itasca software is principally affected by two computer hardware elements: processor(s) and RAM. Extremely rareley, hard drive space can also be a concern. Graphics cards can negatively effect rendering and in the worst cases cause crashes.

For each Itasca program (FLAC, UDEC, PFC2D, FLAC3D, 3DEC, PFC3D), a set of suggested minimum system requirements is provided. These are the lowest hardware specification that can be used with no expectation of performance issues. As such, they are recommendations, not guarantees.

Itasca cannot guarantee the performance of any particular system and therefore does not and cannot make recommendations about computers or computer components that users should buy. The number of computer configuration available is, effectively, inifinite. Only direct testing can be used to issue a guarantee of performance and, regrettably, Itasca cannot perform an infinite number of tests to issue such guarantees.

Given the caveats above, the information provided below represents our best effort to guide the user who intends to purchase a computer for use with Itasca software.

Which processor should I buy?

Should I get 2 processors, or 4 (or 6, or n)? What multi-processor configuration is optimal?

How much RAM should I have?

Should I get a 32- or 64-bit processor? a 32- or 64-bit operating system?

What kind of Graphics card should I have?

Which operating system should I use?

Can I virtualize Itasca software?

Can I run Itasca software remotely?

Can I run Itasca software on a network?

Itasca Software on Windows 7
Itasca software is Windows 7 compatible. Testing confirms that the current versions of Itasca codes at the time of the Windows 7 release — FLAC 6.0; FLAC3D 4.0; UDEC 4.0; 3DEC 4.1; PFC2D 4.0; PFC3D 4.0 — are fully operable on 32-bit and 64-bit Windows 7 systems. Until Windows 7 is no longer supported by Itasca these versions and higher of each Itasca code may be expected to be supported on Windows 7. Itasca is committed to supporting its software on the latest commonly available Windows operating systems. If you feel there is an error operating your code that is related to the Windows 7 operating system, please let us know.

 

PFC2D and PFC3D Version 4.0 FishTank-related Startup Error

At startup, if a problem occurs when the FishTank variable is set, an error will be reported in the program, similar to the one shown below.

The code is still FULLY FUNCTIONAL and operable in every respect when this error is reported. The aspect of program operation that this situation affects is the use of the %fist% variable, which is a convenience — and not a necessity — for calling FISH files.

This error occurs if the file "fist_new.dvr" is not in the location specified in the file "fist_load.dat."

Diagnosing and correcting this situation to avoid seeing the error message at startup can be done using the following steps.

1. Find the file "fist_load.dat". This is located as follows:

c:\program files\itasca\pfc2d400\fist_load.dat
  [PFC2D, 32-bit version on a 32-bit machine, or 64-bit version on a 64-bit machine]
c:\program files (x86)\itasca\pfc2d400\fist_load.dat
  [PFC2D, 32-bit version on a 64-bit machine]
c:\program files\itasca\pfc3d400\fist_load.dat
  [PFC3D, 32-bit version on a 32-bit machine, or 64-bit version on a 64-bit machine]
c:\program files (x86)\itasca\pfc3d400\fist_load.dat
  [PFC3D, 32-bit version on a 64-bit machine]

IMPORTANT: the locations shown above correspond to the default installation locations for PFC2D and PFC3D. In the event the user has changed this location at the time of installation, it will be necessary in step 3. to replace the portion of the paths above corresponding to "c:\program files\itasca" with the location the user specified at the time of installation.

2. Read the file "fist_load.dat" and determine if the file "fist_new.dvr" is in the location that it specifies. The contents of the file are the same for PFC2D and PFC3D. They are:

;fname: fist_load.dat  %fist%, PFC2D/3D
;
; ===========================================================================
  def ft_setenv
    if dim = 2 then
      environment('fist') = 'C:\\Program Files\\Itasca\\pfc2d400\\fist'
    else
      environment('fist') = 'C:\\Program Files\\Itasca\\pfc3d400\\fist'
    end_if
  end
  ft_setenv
  call %fist%\fist_new.dvr
; ===========================================================================
return
;EOF: fist_load.dat

Read the file and note that the "fist" variable has been set to:

c:\program files\itasca\pfc2d400\fist    for PFC2D, and
c:\program files\itasca\pfc3d400\fist    for PFC3D

3. If the file "fist_new.dvr" is not in the folder specified by the "fist" variable, then change the appropriate line(s) in the "fist_load.dat" file to specify the location of the "fist_new.dvr" file (hint: if the default installation path was changed, then the file will be located in the user-specified installation path plus the portion "pfc2d400\fist" OR "pfc3d400\fist"). You MUST use double slashes (\\) to separate folder names when specifying the path in the "fist_load.dat" file.

4. Try starting PFC2D or PFC3D again after "fist_load.dat" has been edited. If the error message still appears, contact Itasca for further assistance.

PFC2D and PFC3D 4.0 Startup

The above description of the error occurring at startup may be more fully understood by examining how PFC2D and PFC3D start, which is as follows.

When the program starts, if the working directory is the folder where the executable is located (and this is the case when using the shortcut on the "Start" menu), then the file "pfc3d.ini" that is also in that folder is automatically executed. This file calls "fist_load.dat", which is in the folder one directory level up from the folder that contains the EXE and INI files. The file "fist_load.dat", as seen above, performs a test to determine whether the currently executing code that called it is PFC2D or PFC3D. Based on the result of that test, it sets the "fist" variable to the path it expects to contain the FishTank that is appropriate to use. The last action performed by the "fist_load.dat" file is to call the file "fist_new.dvr", and note that the call is made using the "fist" variable (which is designated with the notation %fist%). The file "fist_new.dvr" first defines the function "ft_PrintVersion" that can be used to provide diagnostic information about the FishTank. Then it calls two FISH files, "fishcall.fis" and "udm_types.fis" (and note, if you examine "fist_new.dvr", that these calls are made using the %fist% variable), and then it executes the "ft_PrintVersion" function. So, this sequence is understood schematically:

Typically, the error that is under examination in this topic occurs inside "fist_load.dat" when a faulty path is designated for locating the "fist_new.dvr" file. It is this path that the user must manually fix by editing the "fist_load.dat" file to point to the proper location of the "fist_new.dvr" file.