• If you have trouble finding Java 1.1.x for your platform, try:
  
  
• Your operating system supplier or manufacturer, they should know.
  
  
• Sun Microsystems Java porting web site - http://java.sun.com/cgi-bin/java-ports.cgi.
  
  
• Java Resources Reference page.
  
  
• If all else fails, try searching the web with a major search engines. If you find the version you are looking for, please let us know so we can put it on our Support page.
  
  
• If you have trouble configuring Java to use the JFC/Swing components, try:
  
  
• Following, again, our instructions to set up the CLASSPATH system variable.
  
  
• Refer to any documentation for your Java port.
  
  
• Make sure you are using Java 1.1.3 and above.
  
  
• If you are using Java 1.2 and above, you will not have to do this.
  
  

• If the message 'class vision not found' is displayed, this is often caused by the following:
  
  
• The NetLoony root directory (directory holding all the java components) has been moved and the .sh and .bat scripts are now incorrect. These can be amended with the new location of NetLoony.
  
  
• You are running Java 1.1.x and the Swing components (swingall.jar) cannot be found. Check the CLASSPATH variable (this is a common problem!).
  
  
• CLASSPATH may also require the location of the NetLoony root directory. This is the directory where all the .class files are held. Check the CLASSPATH variable (this is also a common problem!).
  
  
• Check the CLASSPATH variable has been correctly set after reboot.
  
  
• If the message 'class class-name not found' is displayed, this is often caused by the following:
  
  
• One of the java classes is missing or corrupted. NetLoony will have to be reinstalled or downloaded again.
  
  
• Using Mac OS platform will cause errors as it has a file length limit of 31 characters (at the moment). Some of the class name are over 31 characters long and therefore NetLoony will not run (yet).

These messages could be displayed in a Java window, or text shown on the console which VFA was executed from. Runtime errors are rare, as we try to capture every exception for all circumstances. If you get one of these, please let us know.

• If the message 'OutOfMemoryError' is displayed, this is caused by the following:
  
  
• NetLoony is trying to read in an extremely large configuration file.
  
  
• The Error Log Analyser is trying to cope with an extremely large error_log.
  
  
• SOLUTION:
  
  
  • Trim down very large configuration and log files (this is good practice anyway).
    
    
  • Restart VFA using the following:
    
    java -mx32M vision
    
    This increases the amount of memory Java can use from 16MB (Java standard allocation) to 32MB. You can set it to a higher value if required and place the command in the vision .bat or .sh start-up scripts.
    
    
• If the message 'Java.io.IOException:/dir/dir/file' is displayed, this is often caused by the following:
  
  
• The file you are trying to read is corrupt.
  
  
• You do not have the right privileges to access the selected directory or file.
  
  
• SOLUTION:
  
  
  • Check directory and file permissions.
    
    
  • Check hard disk integrity via anti-virus software or hard disk scanning tools (fsck, scsibadblk, Scandisk etc.).
    
    

• If the support form or enhancements form doesn't seem to work, this might be because of the following reasons:
  
  
• Your web browser is not JavaScript enabled.
  
  
• Your web browser is not configured with an email client application.
  
  
• Your email client/server is not working properly.
  
  
• If all else fails, here are the email addresses:
  
  
• (Please write NetLoony as the subject, together with as much information as possible)
  
  
• If you have sent support requests, but are not receiving any replies, this could be due to:
  
  
• If you are not receiving one of our automated replies to say we have received you email support request, then your email client/server is not sending the messages for some reason.
  
  

• If the update process fails to find the new update file, could be because:
  
  
• The update zip file was not put in the Vision/update directory.
  
  
• If the update process fails because of an 'IO Error', it could be one of the following:
  
  
• The update zip file attachment has become corrupted during its transportation through the Internet. Use the support form to request the another update file.
  
  
• Local hardware or software has caused the zip file to corrupt. Again, use the support form to request another update file.
  
  
• 'Missing update(s)...' is displayed because:
  
  
• There are updates to process but one is missing, stopping the process. Check your email attachments. If you can't find the missing file, use the support form detailing which update you are looking for. We will then send you the missing file.