JKSimBlast - Help Me!


License file . . . . . . . if you have recently installed JKSimBlast or received a new license file

Test . . . . . . . check that everything is working properly

Files Not Registered . . . . . . . how to register any files that did not install correctly

JKSimBlast License File

The main JKSimBlast programs require both a USB dongle and a license file. The license file is an encrypted file containing the permissions for the software, and the USB dongle contains the encryption code and serial number. Both must be present for the software to operate.

Two types of dongles are available for JKSimBlast – a blue local dongle and a green network dongle. The local dongle must be plugged in to the user’s computer, and the network dongle must be activated on a computer on the network with a server application.

Further documentation is provided on the installation CD about the setup of network dongles.

Each dongle type requires a specific license file. The local dongle requires the file License(.nfo), and the network dongle requires License_NET(.nfo).

With the installation, two license files have been installed in the main JKSimBlast program folder: License(.nfo) and License_NET(.nfo). However, both of these files are dummy files that must be replaced with the correct license file. The dummy files are actually text files that can be opened in Notepad.

You should have a license file supplied to you, either on the CD or by email. If not, contact your JKSimBlast supplier.

The supplied file will have a long name, including the type (License or License_NET) and an ID code. Replace the installed file with the supplied file, and rename the supplied file to the same as the installed file name. Keep a backup copy of the supplied file.

- for a blue, local dongle, replace the file License(.nfo)

- for a green, network dongle, replace the file License_NET(.nfo)

If you have only one dongle type, you can delete the other license file - it is not needed.

However, if you have both a local and a network dongle, you can keep both the local and network license files in the JKSimBlast folder. To enable a fast start for the programs with each dongle, create separate shortcuts with additional command line parameters.

- for local: /LOCAL=cnnn

- for network: /NET=cnnn

      cnnn = ID code
      c = dongle type: local = G, B, R or F; net = N
      nnn = 3 digit number

The ID code is included in the long name of the supplied license file.

The command line parameters apply only to the programs 2DBench, 2DRing, 2DFace and JKBMS.

For example: C:\Programs\JKSimBlast\2DBench\2DBench.exe /LOCAL=G123

For more information about dongles, license files, network installations and command parameters, refer to the documents folder on the CD.

Test Programs

Unfortunately, sometimes, some of the files will not register correctly during installation. The files contain common routines that are used in various parts of the software, and often by other programs as well. These system files need to be recorded in the Windows Registry so that all programs know where to find them. These tests will tell you if any files have not been registered. Once the files are registered, the software will run without any further problems.

The tests below cover the most common files at fault - mscomctl.ocx, comdlg32.ocx, mscomct2.ocx, spin32.ocx, msflxgrd.ocx and threed32.ocx. The same process applies for other files.

Files Not Registered

A batch file is provided in the \install folder on the CD for registering system files. Right-click on the file Register_Files(.bat) and select "Run As Administrator".

For manual registration, use the Command Prompt. It is more secure than using the Run... command. Where you have to enter a command, it is shown below on a separate line in red - type it exactly as shown (or copy and paste, right-click to paste in the command prompt). The file msflxgrd.ocx is used as an example.

If you need to repeat a command, you can use the up and down arrow keys to select previous entries, and the left and right arrow keys to edit.

After registering the file, you should see a success message. Close the error message and try 2DBench again. (If you don't get a success message, try 2DBench anyway, because sometimes it lies.)

If 2DBench will still not run, contact the supplier.