TextAloud uses SAPI4 and SAPI5, standard speech interfaces that are part of Windows. In rare occasions, installation of other speech or sound programs can cause problems with these speech interfaces. If you get an error, please send us email to support@nextup.com with the text of the error message you receive, and we'll quickly help you get things corrected. You can also look for quick help in our Advanced FAQ Forum.

The cause of this error is that you are unable to receive UDP data on port 4137. Our direct connection documentation provides assistance to configure your home network and/or firewall to work with BitWise: Direct Connection Information. If you need additional assistance, our users and BitWise administrators will be happy to help you in the forums.

If you are not receiving email from Dallas Linkup, please first check to make sure that the email address you entered in your profile is absolutely correct. If your email address is correct and you're still not receiving email, then in all probability the email is being sent to your bulk mail or "spam" folder of your account with your ISP. Please check there, and if you do find email from us there, contact your ISP to make sure that email from Dallas Linkup is not sent to the bulk mail folder.

This can be caused by a lot of things. Faulty hardware, incorrect drivers for user supplied USB devices, random memory corruptions due to latent network traffic, user code (if you or someone else was writing code on that machine since it was last imaged), humidity, the fact it's Tuesday... Basically, there's often not a lot we or anyone can do to track down these errors.

When executed, you must print an HTTP header followed by a blank line. The header must contain either a Content-type field or a Location field. eg. print "Content-type: text/htmlnn";

First, make sure the image you are attempting to upload is in one of the formats HumSubka accepts (.gif, .jpg). Next, make sure the filename is simple and short, with no spaces or funny characters. "Image.jpg" is a good filename "Looking and hooking up next to some stuff~#~.jpg" is probably not going to work. Next, make sure the filename is less than 600k. We do not allow images over 600k. If none of these things work, it's possible that the image is corrupted.

of the time, the problem is that you are using an old version of Windows Media Player. Downloading the latest version will fix this issue - you can download the latest version here: http://www.microsoft.com/windows/windowsmedia/player/download. Please visit the following link: http://www.microsoft.com/windows/windowsmedia/format/codecdownload.aspx and choose the proper download for your operating system (e.g. Windows XP) to upgrade your codecs.

Why do I get the message WARNING: Process being freed while holding Dataserver semaphore in SQL Server.

This error usually indicates that you did not set the appropriate permissions on the database. The security account used by the web server IIS service should have at least ""Write"" permissions on the database file (Note: You cannot set the permissions from within IIS, see below). To adjust the file permissions, you need to locate the file by using ""My computer"". Right click on the file, click on ""Properties"". Next, click on ""Security"".

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.

explanation of frequent file format problems is available at http://deposit.pdb.org/validate/Validation_FAQ.html.

If you have installed BIND-8 then this is normally due to a conflict between your include files and your libraries. BIND-8 installs its include files and libraries /usr/local/include/ and /usr/local/lib/, while the resolver that comes with your system is probably installed in /usr/include/ and /usr/lib/. If your system uses the header files in /usr/local/include/ before those in /usr/include/ but you do not use the new resolver library, then the two versions will conflict.

The first thing to try with any PayPal error is to clear your browser's cache, cookies, and history. You'll need to refer to your browser's documentation if you don't know how to do this. One possible reason for an error is that PayPal is unable to communicate with your bank. There are other reasons that we are not familiar with. If you are still getting the error, you will need to contact PayPal's customer service to find out the reason for the error.

You're entering your password incorrectly. Remember to enter your password with appropriate capitalization. Your cookies are invalid or corrupted. If you are sure that you have entered your username and password correctly, your next step is to clear your cookies.

We've started work on a Web page explaining some of the common problems which may occur. Hopefully this will help! Otherwise, you can contact ICS Customer Support Help Desk by calling 398-3398, or by sending Email to support.ist@mcgill.ca .