Table of Contents

1. Message during setup: "Corrupt Installation Detected" or "An I/O error occurred".
2. Message: "OLEAUT32.DLL out of date.  Program requires a newer version".
3. Message: Runtime #429 "Active X cannot create component..."
4. Message: Runtime #336 "Component or one of its dependencies not correctly registered..."
5. Message: Runtime #326 "Resource with identifier VERSION not found."
6. Message: Runtime 440 (or some large negative number) "Automation Error"
7. Message: "Path Not Found" or "File Not Found" error
8. Message: Runtime Error #7 "Out of Memory"
9. WavMan it telling me I have a 16 bit version of AOL and won't start.

1. How much does WavMan cost?
2. Are upgrades free?
3. I just upgraded my version of AOL and WavMan starts the wrong one.
4. My registration number doesn't work.
5. I lost WavMan and my registration number in a computer crash, how do I get them back?
6. I lost my AOL account and got another one, now my registration number for WavMan does not work.
7. Will WavMan work on all of the screen name of my account?

1. I am using WavMan 10.x, and when I play wavs in the chat room, they echo.  Why?
2. I clicked KillWav but the wav did not stop.
3. The Upload Progress Bar gets stuck at 100% while using Upload and Chat.
4. Where is the actual Hug Manager?
5. I don't hear any wavs in the chat room.
6. My sound was working and all of a sudden it stopped.
7. What are the System Requirements for WavMan?
8. My system does not meet the minimum requirements for WavMan, now what?
9. I was logged off while using WavMan, I thought WavMan prevented this from happening?
10. The Fader is not working, I don't see the control panel for it anywhere.
11. Will WavMan's fader fade Instant Messages also?
12. I can't hear wavs in IM's while WavMan is running.

1. I want to create a desktop icon for WavMan. How do I do this?
2. I sent TPA Software an Error Report form and never heard a reply. Why?
3. Is there a Macintosh version of WavMan?
4. Is WavMan compatible with other AOL Add-Ons?

1. If you are running Norton's Antivirus, right click the Norton's icon on your task bar (it will be in the "system tray" near the Windows clock). Then click Disable Auto Protect.  Download the file, then go back to that icon, right click it again, and click Enable Auto Protect.

or

2. If you are running some other antivirus program, press CTRL + ALT + DEL one time, highlight the name of the program, then click End Task. Press CTRL + ALT + DEL again to be sure that the program is no longer showing in the Close Programs window. Then download the file. Turn your antivirus program back on by clicking Start, Programs, then finding the AV program menu, or just reboot your computer.

[ Back to Top ]

[ Back to Top ]

[ Back to Top ]

This is an indication that another programs setup has replaced one of the following files with an older or outdated version: TPABTNX2.OCX, DWSPY36.DLL, or some other file with the .OCX or .DLL extension.  Or, somehow the component was unregistered from the Windows Registry or the file was accidentally deleted from the system, or the file could have even been removed by another programs uninstaller.

This fix is simple.  A *full* reinstall of WavMan must be done so that all of its runtime files are on the system and up to date.  If you need the WavMan installer, you can download it from the WavMan Download Area.

When the installation is complete, do a FULL restart of the computer, whether you are prompted to or not (do not just restart Windows, this will not work). If you do not do a full restart, the newly installed files will not update in the Windows Registry and error will continue.

When the Windows comes back up, restart WavMan. The problem should be resolved.

[ Back to Top ]

Restart the computer and restart WavMan.

If the problem still occurs, do a full uninstall of WavMan, restart the computer again, download a fresh copy of WavMan, reinstall the fresh copy of WavMan, and then restart the computer one more time.  The issue should then be resolved.

[ Back to Top ]

Restart the computer and restart WavMan.

If the problem still occurs, do a full uninstall of WavMan, restart the computer again, download a fresh copy of WavMan, reinstall the fresh copy of WavMan, and then restart the computer one more time.  The issue should then be resolved.

[ Back to Top ]

This is an indication that there are certain data files or data folders for WavMan missing for the root WavMan folder.  The fix is to do a FULL reinstallation of WavMan to restore these files or folders.  If you need the WavMan installer, you can download it from the WavMan Download Area.

[ Back to Top ]

[ Back to Top ]

[ Back to Top ]

[ Back to Top ]

All upgrades WITHIN THE SAME MAJOR VERSION are free for the life of your AOL account.  This means if you have purchased WavMan 10.x, all upgrades within the 10.x versions of WavMan will be free.  Any upgrade to a new MAJOR version, for example WavMan 11.x will carry a modest upgrade fee.

[ Back to Top ]

The easiest way to change the version of AOL WavMan starts is to do the following:

1) Start the copy of AOL you wish to use. DO NOT SIGN ONLINE.
2) Start WavMan.

WavMan will now remember this version of AOL to start from here on in. :)

[ Back to Top ]

Please use the Lost/Invalid Registration Number Form for all registration issues.  Our technical support reps do not have access to registration information and cannot handle registration based requests.

[ Back to Top ]

You can download a copy of WavMan from our website, specifically the WavMan Homepage at any time if you have lost your copy of WavMan due to a system crash, hard drive replacement, new system, etc.

Once you have downloaded the latest version of WavMan, set it up exactly as you did before and use your existing registration number.

If you have lost your registration number, you can request it again by filling out the Request a Lost Registration Number form.

[ Back to Top ]

[ Back to Top ]

[ Back to Top ]

[ Back to Top ]

[ Back to Top ]

WavMan 9.x Solution
I need to start off by making clear that WavMan has *nothing* to do with the way sounds are heard/played in the chat room. WavMan is a wav manager, not a wav player or editor. Its just a tool that organizes them and sends text into the chat room at the click of the button. AOL takes over from there. Hearing wav sounds is a function of where your wav files are physically located on your hard drive, whether or not you have the proper options selected in AOL and in some cases whether or not your system is set up to play wavs compressed with the MPEG-3 format. To prove my point, if WavMan was not running and you were to manually type in a wav name into the chat room...it would still not play. Again, WavMan has zero control over wavs playing in the chat room.

Wav compression is something fairly common these days among wav traders and not every system is properly setup to deal with or handle wav compression. In cases such as this, you will not be able to hear wav sounds in the MPEG-3 compression format is you do not have the proper codecs installed.

If I have completely baffled you, don't worry. I will provide a link to the information you need. But first, lets check out some of the more basic criteria to make doubly sure everything is set properly! :)

As a forenote, the method in which wav sounds are heard in the AOL Chat Rooms is actually discussed at length in the WavMan Help File. I would suggest reading that section carefully.

In order to hear wav sounds in chat rooms, please use the following check list:

1. You must have a sound card on your computer.

2. Make sure your speakers are turned on and the volume is turned up.

3. You must also have chat room sounds enabled (click on Members in the AOL menu (AOL 3.0) or the My AOL icon in the AOL toolbar (AOL 4.0)), Preferences, Chat Icon, Enable Chat Sounds).

4. The wav files must be physically located in your main AOL directory, or in your Windows directory. If they are not in one of those two places on your hard drive, you will not be able to hear them unless the path to the folder in question is in your autoexec.bat. WavMan will be reading the AOL directory of the version of AOL that is running. In example, If you have two copies of AOL on your system...lets call them C:\AOL30 and C:\AOL30A and you have the wavs files stored in the C:\AOL30 folder. If you are running the C:\AOL30A copy of AOL, then all the wavs in the C:\AOL30 folder will *not* be heard. To solve the problem of multiple AOL account, we recommend moving the wav files to the Windows directory so that wavs will play in the chat room regardless the version of AOL running.

Another trick is to create other folders designed especially to store wav files, but this method requires changes to the AUTOEXEC.BAT. WavMan will do this for you when you create a new wav category, but it does not always work on everyone's system. Because of this, TPA Software and it's representatives do not officially support this "trick" of adding SET PATH= lines to the AUTOEXEC.BAT. If you would like more detailed information on this trick, we did include it in the WavMan 32 help file! :)

Finally, make sure your system is designed to handle wav compression. The theory of wav compression and detailed steps to determine if your system is designed to handle wav compression, instructions on setting up your system for wav compression, and instructions on how to compress wavs using the MPEG-3 codec can be viewed on Joy's WAV Compression Help Page. It's a well written precise source of information written in layman's terms :)

WavMan 10/11.x Solution
WavMan 10.x contains a feature called WavDetect which handles that playing of all chat room sounds.  Please make sure this feature is enabled.

1. Access the WavMan main menu and select Options.
2. Click the Chat tab.
3. Check the check box titles Enabled WavDetect by clicking on it once.
4. Close the Options window and try playing your wavs in the chat room again.

Please note that WavMan will only play wav triggered in the chat room that exist in your WavMan Wav Categories.  If there are wavs on your system that are not in any of your Wav Categories, they will not play via the chat room.  Same goes for MID and MP3 files.  :)

[ Back to Top ]

The "sound loss" issue that people are experiencing is actually *not* a WavMan bug or issue.  This problem started with the 46 minute window and its associated sound event.

To explain, there are three AOL sound events that take priority over all other sounds. They are as follows in this order.

1) The 46 minute log-off window (default system sound)
2) The Buddy List notification sound (for buddies joining and leaving)
3) The IM notification (chime)

If you should be playing or listening to a wav played by another in the chat room, these three sound events take priority over all other sounds being played and will cancel them out accordingly. Sometimes, this can cause the sound to stop, or "freeze".

This issue has been researched and tested thoroughly by myself and Will and we have discovered that it happens at random with *and* without WavMan running. Because we were able to duplicate this issue without WavMan running, it then becomes an AOL issue, and not a WavMan issue. The part we have yet to determine is why it only happens sometimes and not others.

Solutions are as follows and work with varying degrees of results depending on the sound that causes the loss and the users system: You can leave the chat room and come back in (this usually works when it happens to me), you can IM yourself, or mail yourself to activate the "You've Got Mail" sound. Again I stress, these may or may not work all the time.

[ Back to Top ]

• A Pentium Class 200 MHz Processor minimum.
• Windows 98ME/2000/XP.
• America Online versions 5.0 through 8.0
• 32 Megs of RAM.
• At least 20 MB Hard Drive space free for files and temporary installation files.

[ Back to Top ]

If your system does not meet the minimum requirements for WavMan, TPA Software can not guarantee full performance of the product, nor will we be able to fully support it.

[ Back to Top ]

Please use the Lost/Invalid Registration Number Form for all registration issues.  Our technical support reps do not have access to registration information and cannot handle registration based requests.

[ Back to Top ]

Although this used to be a feature of WavMan, we were required by AOL to remove this feature from the WavMan program or lose the right to place the WavMan program in their software libraries.  It is very important to keep the WavMan program available on the AOL service to take the strain of the website server.   This is why we made the decision to remove the anti-logoff feature from WavMan.   We do apologize if this in any way inconveniences anyone, but it should be pointed out that WavMan was never advertised an an "anti-logoff" tool.  It was/is advertised as a wav manager.

[ Back to Top ]

First, make sure this feature is turned on.   Open the Fader Control Panel by clicking the Wavs button in the WavMan toolbar and selecting Fade Designer/Control Panel.  To the immediate left of the Fade Control panel are two buttons.  One says Off, the other says On.  Click the button that says On (it will highlighted).  Now type your chat text into the chat room as you normally would and press ENTER, the text should fade automatically.   If it does not, click the small down arrow on the top of the Fade Control Panel and uncheck "Apply Fade to Wavs and Hugs only". 

To automatically have the Fade Control Panel open with the chat room, click the Menu button in the WavMan toolbar and select Options.  Click the Chat tab and click the check box marked "Show Fader Control Panel with Chat Room" so there is a check in that check box.  This is covered in the WavMan Help File.

[ Back to Top ]

Due to an AOL limitation of the IM window, it is not possible to fade anymore than three or four works per instant message. This is because AOL has a 512 character limit on one IM message. One faded letter counts as over 20 characters. AOL counts the HTML used to create the fade as characters. The result of anymore characters then the IM window is error messages.

For this reason, we are not planning on adding IM fade features. The potential for error messages are too high and we are not manned to answer that kind of mail, especially when the messages are coming from AOL due to their own limitations.

If AOL changes this limitation in the future, we will certainly reconsider this feature :)

[ Back to Top ]

For Wavs in IMs to work, there are some criteria that must be met:

1) The feature must be activated: Click IMs in the WavMan toolbar, select IM Manager. Make sure the Enable Wav Support check box has a check mark in it. If it does not, click it once to place a check there. Click Exit when done.

2) All wav text in IM's must be properly formatted, both in sending and receiving (this means the person sending you the wav must be formatting it properly also, if they do not, the feature will not work). Proper formatting of wav text includes the wav trigger "{S" the name of the wav and closed with a bracket "}". An example: {S welcome}. Many times folks forget the end bracket on the wav text and this is why the wav will not play.

[ Back to Top ]

The reason for the "echoing" wavs is because WavMan 10.x's WavDetect feature is fighting with AOL over control over the chat room. The solution is simple. AOL's control over the chat room must be relinquished so that WavMan's WavDetect feature will work properly. Here is how to correct this: (NOTE: You MUST be online before performing these steps)

1. Access the WavMan main menu and select Preferences.

2. Click the Chat item.  Do not click the + next to the chat item, but click the item itself.

3. Uncheck the check box labeled Use WavDetect to recognize chat wavs by clicking on it once.

4. Wait for a few seconds and then place a check back into that same check box by clicking it once.

This will remove AOL's control over the chat room and allow WavMan full control which will eliminate the echoing wavs.

[ Back to Top ]

[ Back to Top ]

[ Back to Top ]

[ Back to Top ]