Note that this page contains all kinds of issues we collected during time. Some of them can be outdated and/or solved by newer drivers versions or software. We will not remove them until we are absolutely sure they're history.
Also note that there is no chronological order in the items, as many of them have been updated during time! So always scan the whole item list if you're looking for a solution to a problem.

Terratec Support:

Both In-1 and In-2 should work with a disabled Codec. If you want to use the IN2 load the HD_REC1.MIX from the EWS64\SETTINGS directory via the ControlPanel.
Now you can record the IN2 via the WAVE RECORD ! If this doesn't work, try to reinstall the drivers. If it still doesn't work, there might be a hardware problem.

Terratec Support:

Hands off! This jumper is for internal testing only!

The EWS64 manual tells you how to use two EWS's in your system. But not how to install it in conjunction with another brand. In this item we collect the experiences of users that made a succesful combination of two different soundcards in one system.

EWS64 and AWE32

(Contribution by Ernst)

I have an AWE32 beside my EWS64XL. No Problems. AWE32 is running in DOS and Win95 for Games etc. EWS64XL runs in Win95 only.
First I installed and configuered the AWE32 to be shure, that IRQ 5 and address 220 are reserved for this Card to be DOS and game compatible. Afterwards I installed the EWS64, assigned free IRQs and address 330 for the Midi-1 port.
I am able to use all Midi ports as well as all Sound Devices from both cards in parallel in Win95. I can see and assign them in Cakewalk. The only restriction is the nr of free IRQs available in your system. The Game port of one of the cards needs to be disabled in Win95 because there is an address conflict. The same is for the IDE port on the AWE32 because the motherboard already has 2 IDE ports.

Sometimes your BIOS needs a 'fresh-up': it's not fit anymore to meat the standards of the latest components or OS-update you added to your system. Modern BIOSses are the 'flash' type: you can update them by flashing a new contents into the BIOS-chip. But you should be careful: make sure you have exactly the right version, cause the BIOS is the core of your computer-system. So:

• Find out what brand and type of BIOS you have now. If you are not sure: do not upgrade it! Otherwise your system will not function anymore. Ask your dealer to do it.
• Go to the Website of the BIOS manufacturer and download the upgrade for that particular BIOS only!
• The upgrade process itself is rather easy. It's just a question of running a little program. Follow the manufacturer's instructions carefully!

Most people are not aware of the fact that BIOS manufacturers release BIOS-updates very frequently. So if you did add a new component to your system and that system crashes regularly, it's time to think about this upgrade option. If you don't trust yourself: ask your dealer to do it. It's not much work, so it should be cheap.
Since quite some time we also have a special link with BIOS information in our Useful Links section, Computer System page.

Note that also computer components like modems, video cards etc. can be 'flashed' nowadays. Some piece of advice to conclude: if everything works fine, leave things the way they are!

Mehran Khalili had problems with harddisk recordings. He wrote in the mailing list: "Can I get some tips for avoiding skips when I'm recording to hard disk? Yes, it's an IDE drive and I've tried to increase the buffer size etc, but it still skips in a few places and obviously that's no good for a decent recording. I only have 48 megs of RAM so that's typically not enough to record a track of reasonable length to RAM."

Andrew Morgan answered with a comprehensive contribution, which is worth preserving on this page.

At the risk of sounding like the Monty Python Yorkshiremen (You had gravel? You were lucky!) my system is an iP75 and has only 24 MB of RAM and works fine, certainly on stereo (I've recorded up to 45 minutes with no problems). If youre getting skipping check some other things first:

• When did you last do a Scandisk and Defrag? Do these at least once a week or so if you use your PC heavily (Do a Defrag even if WIN 95 tells you you don't need to).
• Ideally you should be recording onto a seperate physical disk or, failing that, onto a seperate logical partition. If you're only using one partition, does the disk you are recording to have enough space for the recorded data and your WIN95 swap file? (Depending on your software you may need twice the space of the actual recording because a temp file is generated as well).
• How old is your HD? IDE is fine, but if its an older, non AV model it might decide to recalibrate while you're recording or playing, which could cause skips. (I have an old seagate 850MB which is an AV model, and a plain vanilla Fujitsu 2G which is newer and doesn't calibrate).
• Do you have Office 97? If so, kill the automatic indexing (and anything else from office which is in your autostart folder) because its utterly useless and goes off more or less randomly, i.e. in the middle of a recording.
• Check for anti-virus progs and stuff that might be running in the background while youre recording

Adding RAM makes the whole process more comfortable, but may not solve your particular probs. Cleaning up your system and perhaps getting a more modern HD may be more cost effective.

Contribution by Sascha Büdgenbach (TerraTec)

Intel's BX chipset and Windows95 are unable to use IRQ 9 for ISA cards!
For example: if the EWS synthesizer is configured to use IRQ 9, the 'digital-control' in device-manager will indicate an "!" with no conflicts!

The reason is: the IRQ 9 is not available for ISA cards. As soon as you take IRQ 11 or no IRQ, the digital-control and the rest of the EWS card will work fine!

Addition by Guido Jenrich

I had the same problem with VIA-chipset,especially on an FIC-board.

Solution by Computer ConText

The trick here is to make sure that IRQ 9 will not be assigned to an ISA card, but will be available only for PCI. So you have to arrange things in such a way, that in the BIOS you explicitly mark the IRQ'S that should be used for ISA. Note that the solution below is an example from our own BIOS and that the situation can be different for another brand/type.

• Make an inventory of all your ISA cards and the amount of IRQ's they may need (your EWS64 needs two, the XL three if you want to use Midi 2 as well).
• Go to My Computer, Properties, Device Manager, double-click Computer and make an inventory of the IRQ numbers that are still unused (if any; if not: don't bother yet:-))
• Run the EWS Control Panel and press the Setup button. Set up the IRQ's you have choosen for your EWS (so not 9 :-)) Make sure that you know what you're doing here, because not every IRQ is freely assignable. Pretty safe to use are: IRQ 5, 7, 11. IRQ 12 is for the bus-mouse (a mouse with a PS-connector).
• Reset your computer. Go to your BIOS setup by pressing the DEL-key during startup and look for the option 'PNP/PCI Configuration'.
• Look for the line 'Resources controlled by'. If this has been set to AUTO, change it to MANUAL. A long list of IRQ's with options appears.
• Make sure the IRQ's you want to use for your EWS (and other ISA cards) are set to 'Legacy ISA'. You will notice that IRQ 3 and 4 already have been set to Legacy ISA, because those are your COM-ports.  Anyway: don't forget that IRQ 9 should stay on PCI, otherwise all the work is in vain!
  • Freeing up more IRQ's: If you have your mouse connected to a COM-port, look in the manual of your mainboard if you can disable it by setting a jumper on the mainboard (not likely, as the latest mainboards usually don't have that option anymore). You don't use USB (or don't plan to)? Go to the option INTEGRATED PERIPHALS in the BIOS, look for the option USB IRQ RELEASED and set it to YES instead of No. Important: leave the setting USB Legacy Support the way it is!
• Save the BIOS settings and restart the computer. Windows will now re-arrange the IRQ's for PCI and ISA. Don't worry if you get messages like Detecting new hardware etc. That's all part of the process and this should go automatically.
• Now check the Device Manager again and check the new situation. There should be no exclamation marks or conflicts.
• If you don't feel safe in doing all this: ask someone with more expertise in this field.

A very interesting general explanation about the possible conflicts between PCI-video cards and soundcards was written by Greg Hanssen. It can replace our original item about the problems with the Matrox Millennium and Mystique video cards, as this story covers everything. With special thanks to Michael Jantzen for posting this story.

Description of the problem:

A good number of VGA card manufacturers are squeezing out a few extra points on their winbench scores by locking up the PCI bus.  This is fine for graphics and most systems on the PC (hard disks and such) don't even notice the problem. Unfortunately this can hurt the audio system in a big way.
Most audio cards use ISA/DMA to trickle samples over the bus one word at a time.   Even PCI cards such as the AMIII can be hurt by this problem because they trickle the data over the bus in tiny PCI transfers.  When another device illegally locks up the bus for more than 1/88200th of a second, there's a good chance you will lose audio samples resulting an a glitch in the recording or playback.
How do you know if you're having this problem?  Try opening up your favorite wave editing program, loading a wave file and hitting the play button.  While the audio is playing, grab the top of the window (assuming it is not maximized) and repeatedly pick it up and drag it to another location on the desktop.  On a soundblaster compatible card, the audio will glitch and pop while you drag the window.  On a ZA2 card, there is a 50/50 chance the audio will swap L/R channels after such a glitch. On an adb card, not only can the right and left channels swap, but there is also a good chance the audio will be left in a glitchy mode that makes the audio repeatedly jump channels resulting in a high pitch scratchy noise.

At this point in the discussion, I would like to stress that this is NOT (I repeat NOT) the fault of the soundcard!  This is not even the fault of the VGA card... it is in fact the fault of the VGA driver.  If you do not experience any glitching or distortion then you can probably ignore the rest of this post!  I've heard that the VGA drivers supplied by Microsoft (verses the drivers supplied by the VGA manufacturer) do not suffer from this problem.

I think Matrox was the first to play with this, but it doesn't really matter because most high performance VGA accelerator cards for the PCI bus are doing the same thing now.   When a number of graphics acceleration operations need to be performed, these commands are sent from the VGA driver to the VGA card over the PCI bus.  The VGA chipset has a built in queue that is capable of holding several accelerator commands.   Normally the driver checks a status bit on the VGA card to tell if this queue is full or not. If the queue is full, the driver waits for the queue to have a free space before sending the next command.  Matrox discovered (and everyone soon followed) that you could increase VGA performance by NOT CHECKING THIS STATUS BIT!  What happens when you write blindly to a full queue of commands on the VGA card?  The bus hangs... The bus master has started a PCI transaction, but the target (the VGA card) can't accept the data yet because it has no place to put it.  As soon as the VGA card has room for the data, then the transaction can complete... but until that time the PCI bus is completely locked up.  No PCI or ISA transactions can happen.  This can take a long time (40 or more audio cycles) if the current VGA operation is a huge BITBLT on a 24bit screen. A 256 or 512 bit FIFO just ain't gonna cut it.

The only acceptable solution to this problem is to put the queue check BACK into the VGA driver.

Solutions for various video cards:

• Tseng labs
  Tseng labs has released a new version of their ET6000 VGA driver that behaves nicer to the PCI bus. This driver is now trickling down to the STB and Hercules products that use the ET6000 chip.
   
  
• Hercules Dynamite 128
  For the Hercules Dynamite 128 card, there is a new driver on the Hercules BBS (not web
  page... don't ask me) called DV95112  (Version 1.12). 
  Using this driver, you need to add a special switch in your system.ini file. 
  • Under the heading [Hercules] there is a line that reads 'Optimization=0'  you will need to set this to 'Optimization=1'.
    

• Matrox
  It turns out that Matrox has always had a hidden back door switch to enable this check in the VGA driver. 
  If you are using the Matrox Millennium (earlier versions):
  
  • Add the following lines to your system.ini file:
    
    [mga.drv]
    PCIChipset=1
    
    
  • Disable the 'Use PowerGDI acceleration' feature in the Advanced Matrox setup:
    • Control Panel, Display Properties, MGA Settings, Advanced, Performance.

For owners of newer Matrox cards:

• Go to screen properties (right click in main window)
• Go to setting tab, Click on PowerDesk button
• Check 'Use Bus Mastering' (on)
• Uncheck 'Use Automatic PCI Bus retries' (off)
• On Pentium Pro machines, Uncheck 'Use Write-Combining'
• Click on OK

• S3 VGA cards
  I've heard from the good folks at S3 that all S3 drivers for all of their VGA cards (downloaded from www.s3.com) can be fixed:
  
  • Edit sytem.ini as follows:
    • Go to the [display] section:
    • add the line 'busthrottle=1' so (for S3 drivers):
      
        [display]
        busthrottle=1

• #9 Imagine 128 series 2
  For owners of the #9 Imagine 128 series 2 a new driver (version 4.102.36) is now available directly from the folks at #9 upon request.

• Diamond Multimedia
  For the record: I have repeatedly bugged Diamond Multimedia, first off their tech's haven't clue one to what I'm talking about, second their drivers actually have the S3 switch in them, but they don't work!

Unfortunately there are other VGA makers who have not acknowledged this problem (not that Matrox or Tseng has formally done so either).  And we as users, software manufacturers or hardware
manufacturers need to get the word out that this is a VGA problem and not a DMA problem! We need to drill it through the heads of the VGA card makers that they can't get away with this B.S. without at
least having an OPTION to make the driver behave appropriately. Have you ever been told to turn the VGA acceleration off? Or to reduce the size of your VGA screen? Or reduce the color depth? These are not acceptable solutions!
Call your VGA manufacturer and tell them they need to fix the problem! (You will probably need to get beyond Joe Tech Support, because he probably doesn't know anything about this... please inform him!) 

Greg Hanssen (hanssen@zefiro.com) copyright 1996 Zefiro Acoustics.

Note by Computer ConText: we edited the text a bit for readability. Updates on this story were made on July 1997, September 1997, November 1997.

ISA-cards are not as Plug and Play as Windows 95 pretends. For many new users the above mentioned quote was their first frustration with the EWS64. Very likely when you have a lot of other stuff in your computer. And who hasn't nowadays? They want us to 'go multimedia', don't they? So the least you can do is putting in a sound card, a fast video card and a fast internet connection through an ISDN card. But they forgot to supply us with enough available interrupts.

Ok, this is the workaround when your screen confronts you with 'too few PnP recources':

• Make sure you indeed have the two free interrupts available for the EWS64
• Reboot your computer and go into the BIOS setup.
• Find the PCI/PnP options.
• Switch PnP/OS to 'disabled'
• Save the settings and continue booting.

The 'syntax' and approach can vary, depending on the type/brand of BIOS you have, but at least you have an idea where to look for. And it already worked for a lot of users.

Official solution by Terratec as stated in their FAQ of 11/11/97:

(Translated from German by Computer ConText)

Probably you made/overlooked a wrong setting in the BIOS of your system. Because the EWS-initialization has to take place before Windows starts, it's important that the Plug and Play function of the mainboard is not deactivated. Please look in your BIOS for the following entrance: "PNP OS INSTALLED: (YES/NO)". The value in the BIOS has to be set to NO, otherwise the operating system will take over the Plug and Play function.

Additionional comment

In the end it comes to this: let the BIOS do the PnP job, not Windows. Kay Bruns says in so many words: 'Boot To PnP OS' in fact means 'Enable ISA PnP Bios'.
So -as we understand it- the problem only should occur in two situations:

• A first time install with the 1.x drivers. EWSINIT.EXE is activated from your AUTOEXEC.BAT then. After updating with beta 2.0x drivers EWSINIT.EXE is no longer needed (remove the line from your AUTOEXEC.BAT). The problem no longer occurs with beta 2.0x.
• When you have two EWS-cards in your computer. EWSINIT.EXE is still needed.

If you don't have enough free IRQ's left on your system, you can consider one of the following tips other users provide:

• First a remark: the EWS64 doesn't seem to feel happy in a pretty crowded system. Maybe it's better to have a separate computer for your music stuff (if you can afford it, of course).
• If you have a SCSI-controller, it's possible that you don't even need one of the IDE controllers. If you disable that, you free up an IRQ.
• Windows doesn't care if you actually use a bus-mouse or not: if the connection is on your system, Windows detects it. Try to figure out in the manual of your mainboard if there is a jumper present to disable the bus-mouse (we know it can be done on A-Open Pentium 1 mainboards, not on Pentium II). Also check in the Device Manager if the bus-mouse is removed. This should free up IRQ 12.
• If you do use a bus-mouse however, it's possible that you don't use one of your com-ports. Watch out: if you have an internal modem installed, this problably uses the IRQ for the second COM-port. If not, it's a way to find a free IRQ here. But it's not a very elegant solution: we are not in favour of using 'system standard' IRQ's. For the record: COM1 uses IRQ 4, COM2 IRQ 3.
• If present, you can disable the USB, in case you don't need it of course.

Also read the topic about IRQ 9 on this page.

Before you return it to the dealer:

• Try another ISA slot. In some rare cases an ISA slot on your mainboard is not working properly.

You definitely have a IRQ or IO conflict with another device in your system. Go to the Device manager and check every device for conflicts. For less experienced users: a 'conflict' means that another device is already using the same IRQ (interrupt) or IO-address as one of the Terratec devices.

How to check the IRQ-numbers and IO-addresses of the respective devices:

• Right click 'My Computer', choose 'Properties'
• Select Tab 'Device Manager'
• Double-click the entrance 'Computer' at the top of the list. A new list shows up and in the left column you see the IRQ-numbers used by each device in your computer.
• You can 'unfold' every item in the list by clicking the + sign. If there is a conflict, Windows automatically unfolds the item for you.
• Pressing the 'Properties' button reveals (among other things) the IO addresses. Under the tab 'Sources' you will find the IO-address area's each device uses and a report if there are conflicts or not. The IO addresses are stated in Hexadecimal numbers. This looks complicated, but to make it simple we have a trick for you: start your Windows calculator, set the view to 'scientific', select the HEX radiobutton, type in the HEX number (indeed: letters and numbers) and then select the DEC (decimal) radio button. Then you get numbers you are used to. Write down the results in case of suspected conflicts. Above that you will get a basic understanding of which devices are 'living' in which address-area's.

(Contribution by Kay Bruns)

I have a Sennheiser HD580 here and hear no noise except when I set the Out1 volume to approx 20dB. I guess that this is a shielding problem inside your computer. Try to find a better 'routing' for the twisted cable to your front panel.

Also have a look on the Sound Problems page for shielding problems.

Additonal comment: note that the volume of the headphones is controlled by the OUT-1 slider on the Control Panel.

The CoDec must be enabled to record from the MIC In. You must set the Record switch to MIC and use the CoDec Record to get something from the MIC In. You'll hear something from the MIC In when you enable the VU Meter and set the MONITOR to 0dB.

Question:

Can I use a Yamaha DB50XG daughterboard with the EWS synth? I've attached the daughtercard, but can't get any sound from it.

General remarks:

Keep the following in mind:

• The daughterboard has to be WaveBlaster compatible.
• The second MPU-401 midi interface of the EWS64 should be disabled.
• The CD volume slider controls the volume of the daughterboard.
• The daughterboard uses it's own drivers, so they have to be installed.
• It's necessary to assign an I/O address and an IRQ to the daughterboard.
• Within a sequencer progam you can allocate different drivers for each track. So you can allocate the daughterboard's drivers to a midi-track. Try this if you didn't yet.

(Source: the EWS64 hardware manual, page 37).

Answer by Kay Bruns

The Daughterboard is mixed together with the CD Audio In. You must enable the Codec or set the ADM switch to M and set the volume on the CD/Syn2 slider to hear something.

Answer by Stefan Kunkel

I am using the Yamaha DB50-XG Daughterboard on my EWS-64 and it works great! You can use it by enabling MIDI-2 on your EWS (perhaps without IRQ). If you want to use the XG-Table under Windows, simply select the MIDI-2 Driver and under DOS (like Games) use GENERAL-MIDI and then the IO-Port, given by EWSINIT as MIDI-2 IO !

Answer by Grant Haavaldsrud

• Did you remember to switch on MIDI 2 ?
• Another possibility is that your mixer setup is causing this. Load some games.mix-files to test.
• In some cases the In-2 slider is also used to influence the volume of the daughterboard.

In this topic the following items are covered:

• Which types of SIMMs can I use for the EWS?
• Can I use EDO as well as Fast Page mode SIMMs?
• What brands of SIMMS can you recommend?
• Precautions regarding installing SIMMs.
• Additional remarks.

Types of SIMMs

For those who want to expand the EWS64 memory with a memory module (PS/2 SIMMS) we copy the very clear overview from 'Brainis EWS64 FAQ' and add some practical comments.

The SIMM must have less than 32 Chips and 60ns. Else the basic DRAM timing will fail randomly and you'll hear strange sounds from time to time.

In rev1.2 the following SIMMs are supported:

• 4 MB Single sided
• 8 MB Single sided
• 8 MB Double sided
• 16 MB Single sided
• 32 MB Double sided
• 64 MB Single sided

Single sided and double sided has nothing to do how the chips are physically organized on the SIMM... it is something about how they are electrically wired. If you use a wrong SIMM (let's say 16MB double sided) the EWS64 will only be able to use it half. The unsupported SIMMS (4MB DS; 16MB DS; 32MB SS and 64 MB DS) are not common anyway because they are more expensive in production. So if you go to a shop and buy a SIMM it usually meets the requirements of your EWS64 XL.
In the hardware version 1.2 you can use EDO as well as Fast Page memory SIMMs.

SIMM brands

Some users ask us about what brands are best. Impossible to answer, as there are many. The only advice we can give: do not buy very cheap brands of simms. They are less reliable or even faulty, e.g. the brand 'Topless' seems to be rather notorious (if it still excists).

Precautions

SIMMs are very sensitive to static electricity. So work anti-static: first touch a metal object to discharge yourself before handling the SIMM (there is also special gear to work antistatic, but we don't expect you to have that in the house:). Hold the SIMM by it's edges between two fingers, avoid touching the chips on it and the gold-plated contacts.

Additional remarks

(Contribution by Jörg Knitter)

• Hardware versions 1.0 and 1.1 of the EWS are not capable of using double sided SIMMs, so you can not use 32MB SIMMs on these versions. This is only possible with version 1.2.

We are not completely sure about this preliminary answer, because we don't use a daughterboard ourselves. So please correct us if we are wrong. But deducting from other answers, we came to the conclusion that the Midi 2 can not be used anymore if you have a daughterboard installed. We base this conclusion on the following information by the manual and users (see also the Daughterboards item).

• The daughterboard is using the Midi 2 drivers. These are seperate drivers from the Midi 1.
• You should disable the second MPU-401 interface. This means your external Midi 2 can't work anymore. The daughterboard is taking it's place.
• Midi 2 should be enabled though, otherwise your daughterboard doesn't work.

If you are having trouble with connecting external devices via Midi, follow a step by step procedure to eliminate causes:

• We think it's best to remove the daughterboard (only for testing purposes).
• Install the EWS like you have no daughterboard.
• Test the Midi 1 interface with external devices like a synth(-module).
• Enable the Midi 2 and test the Midi 2 interface with external devices.

This way you are sure that your midi-interfaces work. In case you get no sound: read the Control Panel settings under item Daughterboards.

Request: additional information from users that have experience with this Midi 2/Daughterboard issue.

Contribution by Jörg Knitter

• Version 1.0 already had 2MB ram. TerraTec shipped the 1.0 version with 8 MB SIMMs as a bonus for the first users.
• Hardware versions 1.0 and 1.1 are not capable of using double sided SIMMs, so you can not use 32MB SIMMs on these versions. This is only possible with version 1.2.
• Version 1.0 has several hardware bugs (e.g. the SPDIF or was it just the Front Panel? The optical SPDIF is said to work wrong on 1.0 versions) so that Terratec changes this version for free against version 1.1. So only hardware version 1.1 and 1.2 offer the 'clipping' button in the Control Panel.

(Contribution by Holger Fiergolla)

• In the Windows Control Panel open 'System'.
• Switch to 'Device Manager'.
• Select "TerraTec EWS64XL Synthesizer" and click the Properties button.
• In the Properties dialog choose the Information tab.

Contribution by Sven Behncke

This joystick doesn't seem to work in conjunction with the EWS joystick port. Terratec has no solution for this problem. The only thing you can do: call the Microsoft hotline and ask for a an adapter to connect the FF-Pro to a serial port. This has to be a 9-pin serial port. The free adapter has:

• A 9-pin connector to the serial port
• A gameport connector
• A connector to the Force Feedback

After connecting the stuff your Force Feedback should work fine with the EWS, without any additional drivers. The remaining drawback: you need a free 9-pin serial port.

Contribution by Joerg Knitter

Maybe you need the DOS-Prog ICU from Intel (Intel Configuration Utility). My Intel Plato Board also did not show a message like "Initialising PNP cards", but the ICU software comes with an PNP driver that needs to be loaded first in the config.sys.
If your Windows95 does not find the card afterwards, make sure that all drivers are deleted from the registry (c:\windows\regedit; look for "ews" in the registry and delete all entries).

Important: first backup your registry, e.g. with Eru.exe (to be found on your Win95 cd).

Also read the information under 'Too few PnP resources'.

Contribution by Uwe Beck

I have the Sidewinder 3D and had some difficulties with the drivers. DO NOT use the msjstck.drv that comes with the Terratec drivers! Leave the old joystick-port drivers as they are on the system.
Fortunately the Terratec installation asks you if it should replace the drivers. There is also NO problem with the Microsoft drivers if you have the EWS installed.

Contribution by Fabio Zaffora

Your system is looking for the file: EWS64_OS.BIN. The 1.x drivers used to load it from the EWS64 directory, 2.x from c:\windows. Anyway, try locating it with FIND and put it un both the Windows and EWS64 directory.

Several users reported Midi-problems with their EWS and couldn't find the cause. Eventually the problem appeared to find it's origin in a defective Frontpanel. In such cases the only option is to return the card to Terratec. Other users experienced good and fast service.
Note: the 'do-it-yourself' solution mentioned earlier in this item has been removed at Terratec's request as it appeared to be incorrect and dangerous to your system.

The is a new device from Midiman that does exactly that, it's called CO2.
more info on: http://www.midiman.net/new.htm

Contribution by Zak

I recently tried to install my first joystick (a Thrustmaster Rage 3D game pad) after a clean install on Win98 and the latest EWS64XL drivers.  I think I may have found a work around that may help someone else who runs into problems here.
In the past (with a Sound Blaster 64 Gold), when I wanted to install this game pad, all I had to do was put the pad drivers CD in the drive and follow the game pads on screen instructions.  The game pad software installed the proper drivers and software.  When I looked at the joystick set up under Windows, it was there and set up properly ( in the Windows Contol Panel under Game Controller).
After my install of Win98 and the Ews64XL, I tried to install the Thrustmaster Rage 3D game pad.  The install CD for the pad would begin the install but I would get an error message to the effect that the game port was not properly set up and that I needed to exit the install and setup the game port!  The install would halt there and not allow me to continue.  It took awhile to figure out how to set up this pad with the EWS but here how I got it to work.
I clicked to the Game Controller under Windows Control Panel.  There, I selected add and choose the first generic joystick on the list (the 2 axis - 2 button one).  Windows then asked me to insert the Win98 CD in the drive and it installed the drivers necessary ( one of these I saw was msjstick.drv).  After this install, I was able to use the Rage 3D game pad install CD without any problems and the pad works fine on the EWS64XL.

© 1998-1999, Computer ConText, Amsterdam, The Netherlands, except for contributions made by others.

Latest update on page: 21-02-99

© 1998-1999, Computer ConText, Amsterdam, The Netherlands, except for contributions made by others.

Latest update on page: 21-02-99