This is a bug in Windows 95. Resources are not properly reclaimed when a socket is closed. See the microsoft web site for a patch. (http://www.microsoft.com/)

A : There is a bug in the scaling code in libm.a library released with DJGPP v2.0 which affects several library functions such as ldexp . A work-around is to link without -lm switch; this will cause GCC to use math functions from libc.a. If you need math functions which are only in libm.a, or if you need libm.a for better numerical performance, a patched version of libm is available, courtesy of Tom Demmer. DJGPP v2.

This was a bug which sometimes occurred when BorderMania version 2.0 or 3.0 filters were used with Paint Shop Pro. The bug is fixed in BorderMania 3.1 and above.

Using sockets with Soar is not well-documented, but it has been done numerous times. Socket communication is included in the Eaters and TankSoar applications (which come with a tutorial document) and sockets have also been implemented with C code using a library written at Michigan called SocketIO. Eaters and TankSoar and the Soar 8 Tutorial are available on the Soar "Getting Started" web page, and SocketIO can be found near the bottom of the "Projects/Tools" web page. Soar 8.

Sockets are not currently supported from within a compute node application. Currently the only way to get data from the compute partition to the outside world is through the file system. In the near future, compute node applications will have the ability to communicate with the service partition (and other compute node applications) through an MPI-2 interface.

These questions have more to do with the networking facilities you have available than they do with C.

A11) On UNIX (at least Linux), asynchronous sockets are not generally available, although you can arrange to get a signal when "any fd" is ready (FIOASYNC). If you're on windows, and you're prepared to deal with the significant management overhead, they can lead to good performance.

If you're a new player who's just installed the game, you will need to press the Red diamond button labeled "Update" at the top of your lobby window. this time the DarkSpace installer is for version 1.483, which is our last major version release, since then we've had several smaller patches and as a result the game client version is at 1.483.6. Pressing the Update button in the lobby will re-verify that your installation is up to date.

If you are running TA + UTASP on an AMD K6-2 450/Pentium III 400 or less or are running on a low quantity of RAM (less than 128MB), this is very likely to happen. To solve the problem, you need to reduce the max units. To do this, look for the file named "Totala.ini" in your TA directory (eg C:\Cavedog\totala). Look for the line "UnitLimit = XXX" Change XXX to around 400. This should help to give the processor more breathing space.

The thread libraries shipped with RedHat 9 contain an error causing Posadis not to work. The solution is to upgrade your thread libraries. Instructions on how to do that can be found here. I don’t know whether other distributions also ship this thread library, but if so, check for updates in glibc and check whether that solves your problem.

Often the problem can be attributed to Windows needing a restart to load the newly installed dll's. Try restarting the computer a few times and try again. Also you may try uninstalling the program, restarting the computer, installing the program, restarting the computer. If this doesn't help, contact us

If you have 32 MB RAM, it is possible that not enough memory is available. Make sure that you have at least 100 MB free hard disk space available after installation and that no other programs are running in the background. You can also start the file converter direct from the Windows Explorer without having to start the game first. If you have more than 64 MB RAM, an error has probably occurred while copying the files. Please completely deinstall the game and install it over again.

First, check Question 3.1 for the OS independent answer to that problem. Special Linux case: In some rare cases ( old 3dfx Mesa implementation ), you need to be root to run 3d accelerated programs Try running Armagetron as root; if that works, check out the HOWTOs and FAQs for your graphic card on how to run 3d programs as non-root. Recheck your SDL_image installation; it probably can't load PNG images. The included show-program has to be able to display the PNG images from the textures folder.

This is most likely caused by a bug in a video driver. You should first try upgrading your video drivers to the latest version, which may fix the problem. If it still doesn't work, you can disable OpenGL rendering by removing the file jogl.jar from the Art of Illusion install directory. This will cause it to fall back to the software renderer which should fix the problem, although interactive rendering will be somewhat slower.

This usually means TagLib is crashing while reading that track's tags. Report the bug against TagLib at [1].

The RTT testcases test the system to its limits and may crash RTAI if not properly configured. Especially RTAI 3.0 and older. Also, verify that the RTAI/LXRT (aka 'userspace') test programs work before blaming Orocos. Choosing a different compiler ( GCC 3.3 ) and not using -O3, mostly solves that problem. The RTT is targetted at 32bit or 64bit systems and can run on systems with < 1MB of RAM (for code&data & application code) although with reduced functionality.

Dry socket is a bio-film problem and therefore there is no reason why it should not be treated by ozone.

All of these questions are outside of the scope of this list and have much more to do with the networking facilities which you have available than they do with C. Good books on the subject are Douglas Comer's three-volume Internetworking with TCP/IP and W. R. Stevens's UNIX Network Programming. There is also plenty of information out on the net itself, including the ''Unix Socket FAQ'', and "Beej's Guide to Network Programming".

Secure Sockets Layer (SSL) securely encrypts the information that is being sent over the Internet. Verified by Visa uses SSL to securely transmit data, but also adds another very important layer of protection by confirming the identity of the Visa cardholder during the transaction. This authentication process creates a virtual card present environment.