"); gbWndPopupLinks.document.close(); if (!s_bNS3 && gbWndTemp != null) { gbWndTemp.close(); }else { gbWndPopupLinks.focus(); } return true; } return false; } onload = BSSCOnLoad; document.onclick = BSSCOnClick; onunload = BSSCOnUnload; onerror = BSSCOnError; function reDo() { if (innerWidth != origWidth || innerHeight != origHeight) location.reload(); } if ((parseInt(navigator.appVersion) >= 4) && (navigator.appName == "Netscape")) { origWidth = innerWidth; origHeight = innerHeight; onresize = reDo; } //-->

Common Problems - Novell / NetBIOS

This Appendix details general problems that may be encountered when attempting to execute the NPL Universal Upgrade or a RunTime. Please refer to the documentation provided by your Authorized Niakwa Distributor for further details on problems encountered.


Problem 1:

The RunTime Program ERROR screen appears:

Possible cause: The RunTime Program has encountered an error condition in the application program being run.

Solution: Contact your Authorized Niakwa Distributor on what to do if this occurs.


Problem 2:

The message "DEVICE /DEV/PRN not ready, please check before proceeding" appears.

Possible causes: The printer is not ready to receive output. Either it is turned off, disconnected, not selected, out of paper, or otherwise malfunctioning.

Solution: Correct the problem with the printer and press HOME to proceed.

If the problem with the printer cannot be corrected, it is necessary to execute the "Kill RunTime" option. This exits the RunTime Program entirely.

NOTE: The "printer not ready" message is generated for each character being sent to the printer. Pressing HOME when the printer is still not ready causes the character currently being sent to the printer to be lost. Furthermore, repeatedly pressing HOME when the printer is not ready may eventually cause the system to hang.


Problem 3:

The message "DRIVE (X) not ready, please check before proceeding", where (X) is a DOS drive designation, appears.

Possible causes: This message suggests that the program cannot access the drive specified. Typically, this occurs when the program is attempting to read or write from the diskette drive and either no diskette is in the drive, a diskette is in the drive but is not inserted properly, or a diskette of a different format type than expected by the program is in the drive.

Solution: Insert the proper diskette into the diskette drive and press Home. Should this not work, then contact your Authorized Niakwa Distributor for guidance.


Problem 4:

The message "NPL authorized user limit exceeded. Access denied." appears.

Possible cause: The maximum number of authorized users for that RunTime Package has been exceeded.

Solution: Wait until one of the current users exits the RunTime Program. Access is then allowed. This problem can be avoided by upgrading to a higher user version of the Niakwa RunTime Program (this can often be done remotely). Contact your Authorized Niakwa Distributor for details.


Problem 5:

The message "Interpreter not enabled." appears.

Possible cause: The Interpretive RunTime Package (RTIxxx) has not been enabled on the configuration.

Solution: Use the Non-interpretive version of the RunTime Package (RTPxxx) or contact your Authorized Niakwa Distributor regarding use of the Interpretive RunTime Package.


Problem 6:

The message "'FROM' or 'TO' parameters missing or invalid." appears when installing the Gold Key security.

Possible causes: During the installation of the Gold Key security under the NIAKINST program an improper drive was specified.

Solution: Re-enter the NIAKINST command making sure that the correct diskette drive is specified (where the Gold Key is mounted) and the correct destination hard drive is specified.


Problem 7:

The message "'FROM' or 'TO' parameters missing or invalid. Recall failed." appears when recalling the Gold Key.

Please check that the original RunTime Program diskette was properly mounted and the drives were specified correctly. If still having difficulty, please contact your Authorized Niakwa Distributor for assistance.

Possible causes: During the recall of the Gold Key security under the NIAKRCLL program, an improper drive was specified.

Solution: Re-enter the NIAKRCLL command making sure that the correct diskette drive is specified (where the Gold Key is mounted) and the correct destination hard drive is specified.


Problem 8:

The following message appears when recalling Gold Key security:

"Authorization on the hard drive is not valid for current serial #."

Possible cause: NIAKRCLL has been run when the Gold Key diskette is not installed on the file server.

Solution: Install the Gold Key diskette before running NIAKRCLL.

Possible cause: The drive specifier is not the drive on which the RunTime Program was installed.

Solution: Verify and correct the drive on which the RunTime Program was installed.

Possible cause: The Gold Key that is mounted is not the original diskette that was used for the installation.

Solution: Use the original Gold Key diskette that was used for the installation.


Problem 9:

The message "Please Mount your Gold Key diskette" appears on the screen when executing the RunTime Program.

Possible causes: The RunTime Program was started from a drive other than where the RunTime and/or Gold Key security files were installed and the NIAKWA_RUNTIME environment variable is not properly set.

The Gold Key security may not be properly installed.

Solution: Enter the letter of the drive where the RunTime Program was installed. If the Niakwa software is installed on a different drive or directory, make sure that the directory is in the PATH or the NIAKWA_RUNTIME environment variable is set.

Check to see that the RunTime Program has been installed. This can be done by running the NIAKINST program. If the installation succeeds, retry the RunTime operation. If the Gold Key diskette was previously installed, installation will fail with the message: "No install counts left on floppy." In this case, continue using the Gold Key as a backup and contact your Authorized Niakwa Distributor to arrange for a replacement RunTime Package.


Problem 10:

The message "Please Mount your Gold Key diskette" remains on the screen after inserting the Gold Key diskette and pressing <ENTER>.

Possible causes: The encrypted serial number in the RunTime Package on the file server does not match the encrypted serial number in the Gold Key diskette. This would occur when attempting to use a different diskette from the one installed from the RunTime Program.

Solution: Be sure that the Gold Key that is mounted is the original diskette from which the RunTime was installed.


Problem 11:

The message

"NIAKSER.DAT missing or damaged (Code x)
RunTime Program Canceled
Contact your distributor for assistance"

appears on the screen when executing the RunTime Program.

Possible causes: The NIAKSER.DAT file is not in the \BASIC2C directory on the current hard drive.

Invalid data is contained in the NIAKSER.DAT file.

Solution: Be sure that the NIAKSER.DAT file is in the \BASIC2C directory on the current drive or in the directory specified by the NIAKWA_RUNTIME environment variable. If it is not, copy it from the Gold Key to the proper directory.

If the file is in the proper directory, it may be damaged or may contain invalid data. Delete the current NIAKSER.DAT file and copy again from the Gold Key.

For networks, be sure users have at minimum Read Access privileges (or equivalent).

If the above solutions do not work, make a note of the (Code x) and contact your Authorized Niakwa Distributor.


Problem 12:

The font size is not changing when window sizes are changed.

Possible causes: The Autosize option is not turned on or the BASFONTS.FON file is not selected from Windows.

Solution: Check the option selection to verify that Autosize is selected. If it is, make sure the BASFONTS.FON file is available and selected from the Windows Control Panel font selection options.


Problem 13:

On a network installation, security was installed yesterday and seemed to work fine. Today, all users are getting prompted for the Gold Key.

Possible causes: The users are not set up properly for the Niakwa RunTime security.

Solution: Verify that the users have the PATH properly set (or their NIAKWA_RUNTIME environment variable set) and they have sufficient Read privileges (RF rights on NetWare 3.x or 4.X) or equivalent rights to the RunTime directory.

The reason security was passed the day before is due to the fact that the first user to execute the NPL RunTime passed the network-wide once-a-day security check On NetWare networks, the user must be logged in as SUPERVISOR (or user with equivalent privileges). On NetBIOS networks, any user invokes this. This gives the appearance that the users are passing security from the file server when in fact it is not being checked until the next day.


Problem 14:

On a NetBIOS installation, the message "Could not find NetBIOS drivers. Make sure the NetBIOS driver is installed correctly" appears when trying to execute the NIAKNETB TSR.

Possible causes: The NetBIOS interface for the NetBIOS operating system in use is not loaded on the workstation.

Solution: Some NetBIOS operating systems require this interface to be loaded separately. Load the NetBIOS interface and try executing the NIAKNETB TSR again. Windows installations should check the protocol in use by the network drivers. Consult the NetBIOS operating system manual for details on loading the NetBIOS interface.


Problem 15:

On a NetBIOS installation, #ID is always zero on each workstation.

Possible causes: The NIAKNETB security TSR was not loaded prior to starting the RunTime.

The NIAKNETW.DLL was not loaded during RunTime startup.

Solution: Exit the RunTime, load the NIAKNETB TSR and re-start the RunTime.

Configure the Windows installation to load NIAKNETW.DLL by adding the line "NiaknetwEnabled=1" to the [GENERAL] section of RTIWIN.INI.


Problem 16:

On a Windows for Workgroups installation, the message "Sharing Violation on Drive x:" appears when attempting to access a diskimage on a remote (server) drive.

Possible Causes: Although SHARE is running, the RunTime is not properly configured to operate on a NetBIOS network.

Solution: Configure the Windows installation to load NIAKNETW.DLL by adding the line "NiaknetwEnabled=1" to the [GENERAL] section of RTIWIN.INI.


Problem 17:

Using the NPL Windows SETUP program, the default installation path is not correct.

Possible Causes: The NIAKWA_RUNTIME environment variable is already set to this path.

Solution: Remove the SET NIAKWA_RUNTIME line from AUTOEXEC.BAT or network login script and restart the installation, or click on the Set Location button to change the installation path. Changing the installation path within Setup will update any reference to NIAKWA_RUNTIME in AUTOEXEC.BAT to reflect the new path.