The kX Mixer and kX Setup are statically linked to certain Windows DLLs, which may or may not be found on every system. You can download the required files from the kX Download page if they are not present on your system.

Windows 2000 and Windows XP provide their own certified drivers for some EMU10kX-based audio cards. Our kX Audio Driver has not been certified by Microsoft (WHQL-ed) and thus a special installation procedure might be required. It is recommended that you first try running kXSetup, and if that fails, follow our Windows XP installation guide.

Basic Windows Mixer functionality is provided, although the audio mixer (kX Mixer) included with the driver package allows access to many more features. The Windows mixer allows Master, Wave and Synth Playback and Record levels to be controlled. A Line-in slider has also been added for compatibilty with TV-card software.

ASIO v2.0 - based hosts are fully supported, however, some ASIO2 features are not implemented due to hardware limitations. 24-bit ASIO support is planned for 10k2-based boards.

Multiple soundcards are indeed supported by the kX driver. In theory, an unlimited number of soundcards could be used at once, but in reality you're likely to be limited by the number of PCI slots in your machine. Any combination of EMU10k1 and/or EMU10k2-based cards can be used with the kX driver (together with soundcards by other manufacturers, running their own drivers), provided the BIOS and the OS recognize the cards and assign the resources correctly.

Yes, the kX Driver is FREE and will remain FREE. However, you can support the development effort by donating to the kX Fund.

Currently, kX-compatible soundcards include all EMU10k1 and EMU10k2-based PC soundcards manufactured by Creative Technology Ltd. and/or E-mu Systems Inc., including: The Live! X-Gamer, Live! MP3+, Live! Player 1024, Live! Platinum cards (CT4760) and value cards (CT4780) The Live! X-Gamer 5.1, Live! MP3+ 5.1, Live! Player 5.1, Live! Platinum 5.1, Live! Digital Entertainment 5.1 cards (SB0060, SB0100, SB0102, SB0220, SB0222, SB0103 and SB0105) and Value 5.

Yes, your soundcard will continue to function as a SoundFont-compatible device under the kX driver. SoundFonts can be loaded and unloaded via SoundFont-aware applications, or via the kX Mixer's SoundFont control page. Currently only SF2 files are supported, however SF1 (SBK) files can be converted to SF2 files using a freely available utility.

The kX Forums have been set up to allow users to ask questions and exchange helpful tips and information with each other. kX developers and collaborators will sometimes drop in to answer questions, but on a limited basis (mainly due to time constraints :-P). Note that the kX Project email address should be used for Bug Reports and suggestions only - support questions will be referred to the kX Forums.

The kX driver will only install on systems running Microsoft Windows 98 Second Edition, Windows Millenium Edition, Windows 2000 or Windows XP. At least one Creative Labs Audigy or EMU10k1-based soundcard, or E-mu Systems APS soundcard, is also required. DirectX 8 or newer should be downloaded and installed prior to installing the kX driver. A minimum of 32 MB of RAM and a video adapter capable of displaying HiColor (16 bit) or TrueColor (24bit) are also highly recommended (actually - required).

The kX driver conforms to the WDM (Windows Driver Model) specification and is therefore compatible with the following Microsoft Windows operating systems: Windows XP, Windows 2000, Windows 98 (Second Edition only), and Windows Me. Windows .NET Server 2003 may also be supported, however, this has not been tested. Windows 98 (First Edition) will not be supported since it has no built-in support for WDM drivers (v1.1 or later).

Yes, the kX driver supports DSP effects, with Reverb and Chorus loaded by default for MIDI Synth compatibility.

Yes, in fact all effects included with the kX driver package are new, custom-programmed DSP effects.

Before you can enjoy the sound quality offered by the kX Audio driver you need to make sure it is configured correctly. For example, Front and Rear outputs are swapped by default -- make sure you have your speakers plugged into the 'Rear' jack, or disable the swap on the 'Master' page of the kX Mixer. If you have more than 2 speakers (4.0/4.1 or 5.0/5.

Answer: The most likely cause of this problem is a missing Microsoft .Net framework (1.1) installation. (Get the .Net Framework)

Network software (e.g., Windows for Workgroups, Netware, Trumpet Winsock) uses a device driver (also called a packet driver) to control a NIC. If you replace the NIC in your PC, you may also need to replace the device driver used by your network software. Most NICs include a diskette with device drivers for the common network software. Note: If you use a transceiver instead of replacing the NIC, you do not need to update the software device driver.

You should try disabling unused kX ASIO inputs and outputs. Logic opens all 16 inputs and 16 outputs by default.

Yes, the kX Mixer includes a SoundFont control panel, which allows loading and unloading of SoundFonts to compatible soundcards running under the kX drivers.

The kX mixer includes a DSP control panel, allowing editing, loading, patching and unloading of custom DSP effects. A command-line utility is also included with the kX driver package, allowing direct access to many functions.

Yes, the kX driver package includes a DSP compiler and loader, allowing skilled users to program their own DSP effects.

If you get an error code 1920 when trying to install the system driver under Windows NT, 2000 or XP, this means that the parallel port service could not be started. Usually this happens if the parallel port is disabled in the BIOS or can't be detected for some reason. You should reboot your computer, enter the BIOS setup program and ensure that the parallel port is enabled. If it already is enabled then see the next question for more information about what to do.

Choose type of hardware. midiLink is to be installed as "Sound, Video and Game controllers". Select the proper serial port for your system ("Advanced"-settings usually not necessary. Additional info in the file: README.TXT)

The Windows98SE driver will be on the CD that came with your player. Follow the instructions in the operating manual as to how to install it.

The short answer is that this problem is often a side-effect of the method used to maintain compatibility across various versions of the DLL libraries. The simplest way to solve this problem is to delete the files with the extension ".dtf" and then completely rebuild the DLLs. This should solve the problem.

You downloaded Bricolage from CVS and didn't run make dist. Do something like this: # make dist [lots of output...] # cd bricolage-1.5.0 # make install Most likely it's because you're installing Bricolage on Red Hat 8 or later and haven't got 'round to reading README.RedHat. In fact, a fair number of Perl modules will fail to install or test properly with Perl 5.8 on Red Hat 8. This is because Red Hat is configured such that it defaults to a Unicode character set.

Insert the midiLink driver disk into drive A. Or type the drive or directory to locate the driver files.

Download the language pack you'd like by right-clicking the link on the Download page, choosing Save As.. and then picking a place to store it on your computer. You will need software installed on your computer which can open a zip file, as that's how the language file (which has the extension DLL) is packaged. Windows XP can open zip files, other versions of Windows will need a tool like WinZip. Once you have the zip file, open it, and extract the file it contains (called language45.

Windows ME, Windows 2000,and Windows XP officially support USB device, Users do not need to install drivers in these OS.

ActiveBarcode needs the following DLLs in the /System (or /System32) folder: mfc42.dll, msvcrt.dll, olepro32.dll and oleaut32.dll. These DLLs are normally found on most Windows PCs, but you should ensure that you have the latest versions of these DLLs - especially if you encounter problems with ActiveBarcode. If you install ActiveBarcode, the required DLLs are installed to your system. You can use regsvr32.exe (this should be on your system) to register the control manually. Launch regsvr32.