Trouble-Shooting; General Trouble-Shooting; Patchbay Trouble-Shooting; Interface Trouble-Shooting - M-Audio Portman 4x4 Manual

Hide thumbs Also See for Portman 4x4:
Table of Contents

Advertisement

Trouble-Shooting

If you are having problems using your PORTMAN 4x4/S, it is
probably a good idea to re-read this manual and make sure you
have properly installed the interface. If you can't find the source
of your difficulty then check the following typical fixes:

General Trouble-Shooting

Trouble-shooting tip: The unit may not power up properly if a com-
puter is attached and already running. That can be caused by leak-
age current from the computer's parallel port into the PORTMAN
4x4/S. In this case, press and release the PORTMAN RESET button.

Patchbay Trouble-Shooting

If any of the MIDI In or MIDI Out indicators glows brightly and
won't turn off even after pushing RESET, you probably have a
MIDI feedback loop going. In order to track down the source of
the loop, try unplugging the MIDI cables going to the PORTMAN
(one-by-one) or changing the user program.

Interface Trouble-Shooting

SYMPTOM: The computer won't boot with the interface
installed. Everything is fine without the interface connected to the
computer. (This may include strange error messages.)
SOLUTION: Run through the INSTALL procedure given previous-
ly and make sure the interrupt/IRQ you have set the card to is the
same as your parallel port. Also, make sure the interface is recog-
nized at the ADDRESS selected and that all of the diagnostics pass.
SYMPTOM: The diagnostic program's Internal Hardware Test
fails and reports "Interface Not Found."
SOLUTION: The Base Address setting in the diagnostic program
probably does not match the Base Address setting of your parallel
port. Set them to the same value. If this does not alleviate the
problem then you probably have another peripheral set to the
same address (See the Physical Installation and Running the DOS
Diagnostics sections).
SOLUTION: Make sure the PORTMAN is properly connected to
your computer, and to the proper LPT port.
SOLUTION: You may be running the diagnostics under Windows.
Quit Windows and run the diagnostics from the DOS prompt.
40

Hide quick links:

Advertisement

Table of Contents
loading

Table of Contents