Using Wired for Sound Pro Version 2.1 with Windows NT

• Microsoft Windows NT 3.1
• Microsoft Windows NT Advanced Server, version 3.1

WARNING: Using Registry Editor incorrectly can cause serious, system-wide problems that may require you to reinstall Windows NT to correct them. Microsoft cannot guarantee that any problems resulting from the use of Registry Editor can be solved. Use this tool at your own risk.

SYMPTOMS

With Wired For Sound Pro version 2.1 and earlier running in Windows NT, you might not hear all system event sounds, or you might encounter the following error when running 16-bit Windows applications:

[xxxxxxxx] caused an exception in the Win16 Subsystem.

1. Choose the Close button to terminate the application.



2. Choose the Cancel button to debug the application.



3. Choose the Ignore button to continue, you should save your work in a new file.

CAUSE

Wired For Sound Pro version 2.1 is not fully compatible with Windows NT.

RESOLUTION

If Wired for Sound Pro is suspected as the underlying cause for the exception error, closing Wired For Sound Pro should result in being able to start the application (that encountered the error) without getting an exception error.

To stop Wired For Sound Pro from starting automatically, you must manually edit the registry by following the steps below.

CAUTION: Modifying the Registry can harm your system. Query on the following words in the Microsoft Knowledge Base for details:

ntregistry and warning

1. Start Registry Editor, REGEDT32.EXE.



2. Select the window entitled "HKEY_USERS on Local Machine."



3. Locate and select the following Registry subkey:

   Software\Microsoft\Windows NT\CurrentVersion\Windows




4. Double-click the Load entry in the Registry Values window to activate String Editor.



5. Remove C:\WFSOUND\WFSOUND.EXE or the equivalent path and executable.



6. Exit from Registry Editor.

Additional query words: prodnt WFS WFSOUND

Keywords : kb3rdparty
Version : winnt:3.1; :3.1
Platform : winnt
Issue type :