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

Hopefully, this bug has been fixed in the latest version. I changed the memory manager that gcc uses in order to work around a bug in one of the POSIX functions in Cygwin (mmap). Compilation might be slower on machines with lower memory because it now uses a less efficient scheme which may take more memory. This might introduce new bugs, but I have not seen anything yet. See similar questions...

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. See similar questions...

You may need to increase the memory allocation for your application, EPSON monitor, or both. If you have background printing enabled, you may want to try disabling it. These issues are typically memory related errors. Check the available memory and its allocation. You may need to increase the memory allocation for your application, the EPSON monitor, or both. Insure that the needed system resources are available. If you have background printing enabled, you may want to try disabling it. See similar questions...

Move your mouse to an empty area of your desktop and click the right mouse button. Select -Properties- from the menu list. You should now see the Display properties window. Select the -Settings- Tab at the top right. Now change the color quality setting. (e.g. if it says 16bit change it to 32 and if it says 32 bit change it to 16). Restart the game and it should work perfectly. You are probably running Zone Alarm. The game is waiting for you to respond to a request it has made. See similar questions...

The short answer is: lots of errors. If you think of the compiler as a tool for finding your programming mistakes, with the generation of runnable Z-code as a fortuitous by-product, you'll be close to the mark. Just occasionally a compilation is successful, but that's the exception rather than the rule; it's much more likely that it will fail, probably producing a lot of obscure messages. So, you should be neither surprised nor worried by a mass of error reports. See similar questions...

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. See similar questions...

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. See similar questions...

This error is caused by a setting in your FTP client, that limits the amount of time your FTP client will wait for a server to respond. In order to fix this problem, increase the "server timeout" setting; a setting of 180 seconds should be enough time to connect to the archive.org servers. If you use SmartFTP, the "server timeout" setting can be found in Tools > Settings > Connections. See similar questions...

This is because SimEnhancer can't locate or can't access the Directory where your game is. If you are running a user account on Windows 2000 you can either log in as an Administrator or try installing SimEnhancer to the default directory. (C:\Program Files\SimEnhancer) See similar questions...

It is likely that you have run into the USB problems that Windows 98 has brought with it. If you have a USB device plugged into your computer (Gamepads etc) then sometimes, when you shut down into DOS - Windows 98 will give you a blue screen error, that only a reboot can fix. The work around is to unplug the USB device before rebooting. See similar questions...

quot;Could not login. The specified user name does not exist in the system." - This means that your Blackboard account has yet to be created. Often this is because you just enrolled in a class, and the process for creating your Blackboard account hasn't been completed, or you are enrolled in a class that is not using Blackboard. quot;Could not login. See similar questions...

This is because in traditional BSD systems, the sys_errlist[] array was generally known to exist, but it had never officially been defined in any include file. So, many older programs which use this array (which is fairly common since it contains a list of system error strings) had to include their own definitions of it. However, NetBSD did choose to define it in a header file, and it is not defined in quite the same way as most of the older programs do it, so a conflict often arises. See similar questions...

Write a mail to the user's list describing the problem and providing information on the type of hardware, the flavour of operating system. See similar questions...

Office 97 is no longer supported and will not run the macro in Jaws PDF Creator any higher than Jaws PDF Creator v3.6. Higher version of Jaws PDF Creator are no longer compatable with Office 97. See similar questions...

If you get an error when trying to save new or newly edited projects, this may be due to a program installation issue when installing an updated version of the program over an existing installation. Uninstall the ViewletBuilder4 program (this step is essential) and then download the current release and do a fresh installation. This should resolve the issue. See similar questions...

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. See similar questions...

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. See similar questions...