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.

Starting with OpenSSH 3.8 you will need to set "ForwardX11Trusted yes" in the client configuration to allow remote clients full access to the xserver.

When I run Tethereal with the "-x" option, why does it crash with an error "** ERROR **: file print.c: line 691 (print_line): should not be reached.

Some versions of the GTK+ library from www.sunfreeware.org appear to be buggy, causing Ethereal to drop core with a Bus Error. Un-install those packages, and try getting the 1.2.10 version from that site, or the version from The Written Word, or the version from Sun's GNOME distribution, or the version from the supplemental software CD that comes with the Solaris media kit, or build it from source from the GTK Web site. Update the GLib library to the 1.2.

You are probably using version 1.0 of the Installer utility. If you give it a larger memory partition, i.e. increase its preferred memory size in its Get Info box to about 1500K, it should run just fine. Unfortunately, this version of the program was compiled with a memory size that is too small. You will probably want to get a copy of version 1.1 or later of the Installer utility, which has slightly greater functionality. It is available at: ftp://ftp.macbsd.

You are probably using a patched demo of the game that is missing some of the resource files from the full game. Download and install missingres.exe from http://www.downloads.hardwar.info/ . The "FixVhID: Error" has also been reported to occur during games played with full installation. It is known to corrupt save games somehow, but there is no known way to recover such save games.

LAS v14 included some enhancements to its backup mechanism which required adjustments to the backup list file. In certain circumstances, this backup list file doesn't get upgraded when you install the new version of LAS. (Starting with LAS v14.10, this file format is corrected during reindex.) To solve this problem, Download the updated version of this file here, and place it in your LAS directory.

From Bill Studenmund (wrstuden@loki.stanford.edu): I bet you have a "minimal" installed MacOS, no? There is a call that was part of an experiment for supporting booting w/ VM on. The project wasn't completed, and this call was left in. It is not implimented on minimal systems, but is on full installs.

This has not been seen since the ver_2_1_0 release of astro_library, and is considered fixed. If you encounter it while using that or newer versions of the library, please e-mail the bee2-mssge list and let us know. This is one of the secret mysteries of Simulink/SysGen, but there is a temporary workaround that seems to be successful. There is presumably a setting somewhere within one of the blocks in the signal processing libraries that Simulink and System Generator can't agree on.

It should not because all possible measures are taken starting from checking every allocation up to the automatic downscaling of the image loaded. Yet, it (very rarely and under very special conditions) happens and everything points to a problem in the Palm OS code. So it is better to escape such situations. See... for the amount of RAM you should have and compare this value with the amount of the free storage memory shown by the RAM Info dialog.

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.

This document tries to answer questions asked frequently on the mailing list or other questions that people might have when starting out with or evaluating Bricolage. Currently only PostgreSQL support is maintained. There is an Oracle driver, but it's old and not known to work. A port to MySQL 4.1 is reportedly underway.

Videodelic doesn't need a lot of memory. The minimum memory partition is 24 megabytes which will be adequate for most projects. If your project uses a lot of pictures or uses QuickTime movies, you will want to increase the partition size.

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.