文件列表:

Scientific.Truegrid.v2.1.0_Win9xNT2K-DOD\dod.nfo (8226, 2003-09-13)
Scientific.Truegrid.v2.1.0_Win9xNT2K-DOD\CRACK\.tgauth (33, 2002-10-26)
Scientific.Truegrid.v2.1.0_Win9xNT2K-DOD\CRACK\dodxyz21.exe (17820, 2003-09-13)
Scientific.Truegrid.v2.1.0_Win9xNT2K-DOD\CRACK (0, 2005-04-29)
Scientific.Truegrid.v2.1.0_Win9xNT2K-DOD\tg21\XYZlogo.tg (7490, 2001-10-11)
Scientific.Truegrid.v2.1.0_Win9xNT2K-DOD\tg21\_INST32I.EX_ (300178, 2001-10-11)
Scientific.Truegrid.v2.1.0_Win9xNT2K-DOD\tg21\_ISDEL.EXE (8192, 2001-10-11)
Scientific.Truegrid.v2.1.0_Win9xNT2K-DOD\tg21\_setup.dll (11264, 2001-10-11)
Scientific.Truegrid.v2.1.0_Win9xNT2K-DOD\tg21\_sys1.cab (191165, 2001-10-11)
Scientific.Truegrid.v2.1.0_Win9xNT2K-DOD\tg21\_user1.cab (80576, 2001-10-11)
Scientific.Truegrid.v2.1.0_Win9xNT2K-DOD\tg21\73sbug_h.cor (350060, 2001-10-11)
Scientific.Truegrid.v2.1.0_Win9xNT2K-DOD\tg21\73sbug_h.ele (281020, 2001-10-11)
Scientific.Truegrid.v2.1.0_Win9xNT2K-DOD\tg21\aframe.tg (4248, 2001-10-11)
Scientific.Truegrid.v2.1.0_Win9xNT2K-DOD\tg21\anode.tg (4819, 2001-10-11)
Scientific.Truegrid.v2.1.0_Win9xNT2K-DOD\tg21\ansys.data1 (69570, 2001-10-11)
Scientific.Truegrid.v2.1.0_Win9xNT2K-DOD\tg21\ansys.data3 (34, 2001-10-11)
Scientific.Truegrid.v2.1.0_Win9xNT2K-DOD\tg21\balls.tg (235, 2001-10-11)
Scientific.Truegrid.v2.1.0_Win9xNT2K-DOD\tg21\bowl.tg (547, 2001-10-11)
Scientific.Truegrid.v2.1.0_Win9xNT2K-DOD\tg21\box.data1 (218201, 2001-10-11)
Scientific.Truegrid.v2.1.0_Win9xNT2K-DOD\tg21\box.data2 (135215, 2001-10-11)
Scientific.Truegrid.v2.1.0_Win9xNT2K-DOD\tg21\box.data3 (148103, 2001-10-11)
Scientific.Truegrid.v2.1.0_Win9xNT2K-DOD\tg21\brack1.tg (394, 2001-10-11)
Scientific.Truegrid.v2.1.0_Win9xNT2K-DOD\tg21\brack2.tg (2568, 2001-10-11)
Scientific.Truegrid.v2.1.0_Win9xNT2K-DOD\tg21\bumper.igs (100440, 2001-10-11)
Scientific.Truegrid.v2.1.0_Win9xNT2K-DOD\tg21\canter.tg (4988, 2001-10-11)
Scientific.Truegrid.v2.1.0_Win9xNT2K-DOD\tg21\case.tg (835, 2001-10-11)
Scientific.Truegrid.v2.1.0_Win9xNT2K-DOD\tg21\cask.tg (4518, 2001-10-11)
Scientific.Truegrid.v2.1.0_Win9xNT2K-DOD\tg21\cask1.tg (4520, 2001-10-11)
Scientific.Truegrid.v2.1.0_Win9xNT2K-DOD\tg21\cockpit.tg (230699, 2001-10-11)
Scientific.Truegrid.v2.1.0_Win9xNT2K-DOD\tg21\curd7.tg (827, 2001-10-11)
Scientific.Truegrid.v2.1.0_Win9xNT2K-DOD\tg21\cyl90.tg (504, 2001-10-11)
Scientific.Truegrid.v2.1.0_Win9xNT2K-DOD\tg21\DATA.TAG (123, 2001-10-11)
Scientific.Truegrid.v2.1.0_Win9xNT2K-DOD\tg21\data1.cab (10764, 2001-10-11)
Scientific.Truegrid.v2.1.0_Win9xNT2K-DOD\tg21\dblbtrf.geo (28048, 2001-10-11)
Scientific.Truegrid.v2.1.0_Win9xNT2K-DOD\tg21\dblbtrf.tg (3470, 2001-10-11)
Scientific.Truegrid.v2.1.0_Win9xNT2K-DOD\tg21\dos2unix.exe (34304, 2001-10-11)
Scientific.Truegrid.v2.1.0_Win9xNT2K-DOD\tg21\elbow.tg (3117, 2001-10-11)
Scientific.Truegrid.v2.1.0_Win9xNT2K-DOD\tg21\feed.tg (1382, 2001-10-11)
Scientific.Truegrid.v2.1.0_Win9xNT2K-DOD\tg21\filesplit.exe (31232, 2001-10-11)
Scientific.Truegrid.v2.1.0_Win9xNT2K-DOD\tg21\filter.tg (3278, 2001-10-11)
... ...

TrueGrid by XYZ Scientific Applications, Inc. --------------------------------------------- 1. Installation 2. Sample Input Files 3. Program Removal 4. Authorization 5. Accessing the Network License 6. The TrueGrid Control Program 7. Installing TCP/IP under Windows 95 1. Installation --------------- Run SETUP.EXE to install TrueGrid by XYZ. You can install TrueGrid in any directory which does not have a space in its name. The default is C:\TrueGrid (or the first drive with sufficient space). A full installation is recommended. However, you may omit EXAMPLES, UTILITIES, or DOCUMENTS. Do not omit the LICENSE group *unless* you know that licensing will be maintained on another machine. WARNING:DO NOT INSTALL TRUEGRID IN A DIRECTORY WHICH HAS A SPACE IN ITS NAME!!! TCP/IP is required for TrueGrid. Windows NT installations normally have TCP/IP enabled. However, you may need to enable TCP/IP for Windows 95. If you are not sure whether or not TCP/IP has been installed on your Windows 95 system, then consult item 7 of this file. After you have installed TCP/IP for Windows 95, continue reading from this point. A "hosts" file is usually required for Windows to properly determine the IP address from a host name. Unfortunately, this file is not present by default. For NT, the hosts file is: %windir%\system32\drivers\etc\hosts For Windows 95, the hosts file is: %windir%\hosts To check for this file, issue one of the following commands from a DOS prompt: dir %windir%\system32\drivers\etc\hosts (Windows NT only) dir %windir%\hosts (Windows 95 only) If the file is not present, then create the file using notepad: notepad %windir%\system32\drivers\etc\hosts. (NT) notepad %windir%\hosts. (95) The "." at the end of the name is important because it keeps notepad from appending a ".txt" extension to the file. Add the following line to the hosts file: 127.0.0.1 loopback localhost preinstalledcom You must choose one of these names as the host name during authorization. If this is a permanent installation, then you may also need to install the drivers for the Rainbow Sentinel provided with the program. Generally this is required only if you are installing under NT, and if the machine on which you are installing will host the network license manager. Windows 95 installations do not normally require the Rainbow Sentinel drivers. The Rainbow Sentinel drivers are installed separately. Change to the RAINBOW subdirectory of the TrueGrid release directory and follow the directions in INFO.TXT. Make sure that you reboot immediately after installing the drivers. Do not defer this step in the process. 2. Sample Input Files --------------------- TrueGrid registers the ".tg" extension as a TrueGrid input file. Entries are added so that Notepad and VI can be used with these files. These files appear as green cubes with mesh lines. The default "open" action is to run TrueGrid. The default working directory is the Examples directory, which contains about 50 sample TrueGrid input files. The default working directory is the Examples directory. If this directory is not writeable, then you should copy the Examples directory to a new location which is writeable, and use the TrueGrid Controls program to reset the default working directory. 3. Program Removal ------------------ The installation program creates a "TrueGrid by XYZ" program group. One of the programs in this group is an uninstall program. Run the uninstall program to remove all files created during installation and/or authorization along with any "tsave" files in the installation directory (or the Examples subdirectory). All registry entries that can be deleted at the time removal will be removed. However, each user is allowed a separate set of preferences. The preferences for users not logged on cannot be accessed. Those users may manually delete the following registry key: HKEY_CURRENT_USER\SOFTWARE\XYZ\TrueGrid This key contains two sub-keys (options and version). 4. Authorization ---------------- If this is a new installation, then you will need to run the authorization program (the program icon is a key). Report the following information to XYZ Scientific Applications: Machine ID: Check: Company Name:(you enter this) An authorization key and a check will be returned. Make sure to indicate whether the key is for a permanent or temporary license. XYZ Scientific Applications, Inc. 1324 Concannon Blvd. Livermore, CA 94550 (510) 373-0628 FAX: 373-6326 Email:xyz@netcom.com 5. Accessing the Network License -------------------------------- Once TrueGrid has been authorized on a specific machine, you can run the TrueGrid program on other machines attached to your local network. The machines on your local network must, however, have TCP/IP enabled in order to access the network license manager. TrueGrid uses an authorization file ".tgauth" to store the authorization key and the host name of the machine running the license manager. This authorization file ".tgauth" is located in the TrueGrid installation directory. You can either (1) install TrueGrid on other machines, and copy the ".tgauth" file to the new installation directories, or (2) share the entire installation directory and run the program remotely. 6. Moving the License Manager ----------------------------- You can move the location of the network license manager to another machine. The license manager is tied to the hardware key (dongle) provided with the program. Install TrueGrid on the new machine. Copy the ".tgauth" authorization program to the new installation directory. With a text editor such as notepad, change the host name in the authorization file to that of the new machine. Use the registration program (whose program icon is a key) to install the license manager as a service, and to start the license manager. Either change the host name in ".tgauth" of all machines, or use the TrueGrid Controls program (whose program icon is a steering wheel) to change the name of the license server. It is recommended that you change the host name in ".tgauth" to that of the machine on which the file resides. Use the TrueGrid Controls program to set the name of the machine running the license manager. Then each machine can easily host the license manager. 7. The TrueGrid Control Program ------------------------------- TrueGrid for Windows has no natural "working directory". You use the "TrueGrid Controls" program to specify a working directory. The default is the Examples subdirectory of the TrueGrid installation. Then all file names are assumed to be relative to the working directory. This includes (a) included files (b) mesh output files (c) postscript files (d) session (tsave) files Files specified on the command line are also relative to the "working directory". This can be confusing if you run tg from the command line, and the "working directory" is not the same as your current working directory. A second directory is used for geometry files such as (a) IGES files (b) Viewpoint data files (c) Segment files If you enter a blank line for the Geometry Directory, then the Working Directory is used as the Geometry Directory as well. The control program also allows you to specify the number of mouse buttons being used. Windows reports a default, and that is used. However, this default can be wrong especially if the machine's drivers are improperly configured. The end result is that the mouse may not function correctly for TrueGrid. If this happens to you, try changing the mouse button setting in the control program. If you have a 2-button mouse, then you can access right mouse button functions in TrueGrid by pressing the control key and then the left mouse button. TrueGrid can use a variable amount of memory. However, that amount cannot change dynamically during execution. Specify the number of megabytes to use via the control program. The default is 20 (MB). Few problems will require more than 40 MB (usually only problems with very large mesh sizes or which require complicated IGES data.) The "len=" command-line option is fully functional as well. 7. Installing TCP/IP under Windows 95 -------------------------------------- Warning: Do not proceed unless the Windows 95 Installation media is available. The installation of TCP/IP will require the original Windows 95 Installation disks or CDROM. Incomplete installations of TCP/IP can cause start-up errors. TCP/IP is not installed automatically under Windows 95. If you have no network adapters, then this can be a bit tricky. In effect, Windows 95 must be fooled into thinking that there is a reason for TCP/IP to be enabled. First, check what network components you have installed. To do this, open the "Network" folder in the Control Panel. You can get to the Control Panel via the Desktop Icon labeled "My Computer". Alternatively, access the Control Panel from the Settings submenu of the Start Button. The Network folder has a text area where all installed network components are listed. There are three types of network components which can be installed and configured: 1. Clients Software programs that require connecting to other network programs. 2. Network adapter Hardware attached to the machine such as ethernet cards and modems. 3. Protocols The language used to communicate across the network, such as TCP/IP or IPX. 4. Services Network services such as network printers. ADD TCP/IP PROTOCOL (i) If you do not have TCP/IP showing up, then choose the Add button. (ii) A new screen appears where you have to option to add (a) Clients (b) Adapters (c) Protocols (d) Services Choose to add a protocol. (iii) Another screen appears which prompts you for the protocol Choose TCP/IP from Microsoft. MANUFACTURER NETWORK PROTOCOL Microsoft TCP/IP (iv) After you choose to Add TCP/IP, you may be prompted for the type of network adapter to use with TCP/IP. Choose Microsoft MANUFACTURER TYPE OF ADAPTER Microsoft Dial-up Networking (v) Choose OK for everything except for the main Network window. ADD IPX/SPX PROTOCOL Repeat steps (i) to (iii) to add IPX/SPX. Choose Microsoft IPX/SPX instead of Microsoft TCP/IP. MANUFACTUER NETWORK PROTOCOL Microsoft IPX/SPX-compatible You should not be prompted for a network adapter. Choose OK for everything except for the main Network window. IPX/SPX is not required, but there are potential conflicts which are solved by adding this protocol. IDENTIFY THE COMPUTER (i) From the main Network program screen, choose the Identification tab. Fill in a name for your computer, as well as a name for the workgroup. The computer description is optional. NAME:(required) WORKGROUP:(required) DESCRIPTION:(optional) (ii) Back in the Configuration tab of the Network program, select the TCP/IP entry, and press the Properties button. You will see 7 new tabs. (a) Select DNS Configuration. Select the option to enable DNS. Enter a host name for the machine and leave all the other fields blank. ( ) Disable DNS (*) Enable DNS HOSTNAME:(required) (b) Select the IP Address tab. Enter an IP address for the machine. For example, you could enter 192.0.20.1 and a network submask of 255.255.255.0 These are in the blessed test network and should pose no problem. (c) Select OK for the Properties box to return to the Configuration tab of the network window. SAVE EVERYTHING Press the OK button at the bottom of the main Network program screen. You will need to reboot. TESTING TCP/IP Make sure that you have a hosts file in the windows directory. A hosts file should contain the following 127.0.0.1 loopback localhost 192.0.20.1 hostname where 192.0.20.1 should be replaced by the IP address you entered above, and "hostname" should be replaced by the hostname you entered during DNS configuration. You can edit the hosts file with the command notepad %windir%\hosts. The "." at the end of the name is important. This keeps notepad from appending ".txt" to the name. Now, create a DOS prompt. From the DOS prompt enter the command ping localhost You should see output resembling Pinging hostname [127.0.0.1] with 32 bytes of data: Reply from 127.0.0.1: bytes=32 time<10ms TTL=128 Reply from 127.0.0.1: bytes=32 time<10ms TTL=128 Reply from 127.0.0.1: bytes=32 time<10ms TTL=128 Reply from 127.0.0.1: bytes=32 time<10ms TTL=128 Try pinging the new hostname ping hostname You should see Pinging hostname [192.0.0.20] with 32 bytes of data: Reply from 192.0.0.20: bytes=32 time<10ms TTL=128 Reply from 192.0.0.20: bytes=32 time<10ms TTL=128 Reply from 192.0.0.20: bytes=32 time<10ms TTL=128 Reply from 192.0.0.20: bytes=32 time<10ms TTL=128 If you see any errors, then you will need to contact us for advanced troubleshooting techniques. Errors such as 10043 can occur at this point, and these errors may require that you install additional network components.

近期下载者：

相关文件：

评论：[我要评论] [举报此文件]

收藏者：