Close any applications that you currently have running. If you are not sure which programs are running, check the status bar. To close an application, place the pointer on the status bar and right-click the mouse. Select CLOSE from the pop-up menu.

If you get an out-of-memory error (or would like to increase the amount of memory that the server can use), add the "-mx128m" argument when running java/jre. In fact, we recommend increasing the amount of memory available to Java to allow Java and the server to use up to 128 megabytes of virtual memory, if necessary. Alternatively, the config.dct file can be edited to cut down on the amount of memory used by changing the number of threads allocated for each listener.

Click on 'ignore' and let the installation finish. Everything will work, except for the Matroska Splitter. You are probably getting this error because there are one or more crucial Windows components missing on your system. Most likely comctl32.dll or DCOM.

EXTRACT's INSTALL utility does not work with certain recent Windows operating systems. If you get a run time error, simply follow these alternate installation instructions instead.

You probably have run out of virtual memory on your system, or your kernel has a low limit for certain resources. Try this before starting postmaster: ulimit -d 262144 limit datasize 256m Depending on your shell, only one of these may succeed, but it will set your process data segment limit much higher and perhaps allow the query to complete. This command applies to the current process, and all subprocesses created after the command is run.

Wusage contains no arbitrary limitations on the maximum size of a log file to be processed. However, If your log is especially large, and especially when the Summary Reports (summary), Quarterly Reports and Annual Reports options are active, you may receive the following message: This occurs when your computer does not have, or will not allocate, enough memory for Wusage to successfully analyze your log.

You need to upgrade to the newest version of Adobe Acrobat, which is free to download for both PC and Mac. If you still have the problem, you need to completely remove/uninstall Adobe Acrobat from your computer, then restart your computer and go download the new version from the link above.

One of the most common memory problem faced in older PC system during boot-up is "incorrect memory sizing" or the error number 164. Sometimes failures could be caused by incorrect software setting, sometimes it could be caused by hardware ? which could be easily fixed if you know where the faults lies.

You don't have DivX 3.11alpha but some VKI patch or a newer (never use them!) version. Reinstall Divx 3.11alpha and answer yes when asked to overwrite some files. Then reboot and try again. SBC isn't a wonder solution for good rips. It's a tool for advanced rippers which allows you to push the codec to its limits when using the right parameters. My profiles are but a starting point.. you'll end up encoding the same movie many times to get the ideal rip.

Try increasing the -Xmx value to give the JVM more memory. Performance will rapidly disintegrate if you allocate more memory than physical memory on your machine. At this point, the solution is to buy more RAM or go and have a long coffee break. I've got 512 MB and this is OK for good performance with all but the largest dumps from servers that I've seen. Saving the state once parsed is the best thing to do. Also see the section on memory usage in the documentation.

My program ran fine on the orignal PIC, but it behaves erratically or doesn't run when I put it on a different PIC.

If you can access your security features, verify that you have them set the way you want them. If you cannot access the security features, go into Unibase\misc and delete etpasswd file. You will then have to recreate your security features.

You are receiving this error when you are attempting to install the newest build of CAREWare on top of the previous build. You should first attempt to remove the previous business tier build using the Add/Remove Programs located in the Control Panel. You can learn more about how to uninstall CAREWare using that feature at the 'How do I upgrade the business tier?' FAQ link.

This error comes from InstallShield which we use to package our product. This message may appear when other applications are running while you are installing Telnet Magic. You must close all other applications prior to installing Telnet Magic. Close all other applications and try the install again. If closing all other applications fails, the circumvention is to unzip the Telnet Magic self-extracting file using a zip utility.

It is likely that the error is not critical. Press ignore and proceed with the installation. If the program does not install properly, please contact us by email with exact nature of the problem (mention the error code if available). You can always un-install the program by using "Add/Remove Programs" applet in the "Control Panel" <Top>

This error will happen on systems using a software that comes bundled with HP printers, the HP Taskbar Icon, if you have this software running on your Taskbar, close it during Flash Printer installation, and launch it again later.

Almost any installation problem can be resolved by restarting your PC, turning off all memory-resident programs (especially programs like virus-scanners that affect the files being installed), and then running the installation again. However, there is a problem in Windows XP that prevents certain types of files from being written, so you may encounter a message that says, "Error 1931. The Windows Installer service cannot update the system file C:\...\OLE2.