For all of you who are having connectivity problems with your camera,
here is a quick run down of my experience with our customers' systems when
there is no DV device control. Many people call in to our tech support
line every day, and we're always finding a few new problems every week.
Most of these new problems are related to new releases and combinations of
software and/or hardware, but the grunt of our work remains related to the
same type of common misconceptions and problems. Hopefully this brief will
help at least one person. =)

This brief includes our products running on Mac and PC and is organized
likewise...

***************************************
The Most Common Problems

First, the common and most often overlooked situations may lead you to some
heavy frustration. These apply to all platforms and will cause you the
most frustration if you forget about them. They are...

- JVC and other cameras require connection to AC power to enable the
FireWire port. When this type of camera is running off of the battery
(even fully charged), you may never be able to control the camera through
the FireWire.

- Sometimes our products will not initialize properly if your camera is
set to "camera" or "lens" mode instead of "VTR", "VCR", or "Play" mode. If
you want to capture off of the camera's lense, please be sure to launch our
app when the camera is in "VCR", "VTR", or "Play" mode and then later
switch to "camera" or "lens" mode.

- Some AC wiring in buildings may have grouped circuits, which means two
different AC outlets might have two different ground loops. Make sure your
DV device is powered by the same outlet (or power strip, UPS, etc..) as
your computer is. A nasty problem arises if they are not, and could result
in loss of DV control as well as electrical shorts when you attach a device
to the analog composite outputs of your DV device while it is plugged into
our FireWire card.

- Extremely new DV devices just recently released might have a newer
version of DV control codes than older, more widely distributed DV devices.
Please make sure you check our DV compatibilty chart on our website and
also make sure you have the latest version of our drivers / services /
extensions.

***************************************
Mac desktop based products w/ DO/Radius 1394 FireWire card:

- Make sure the FireWire Enabler extension is disabled in Extension
Manager

- Makes sure you have the proper Rad extensions for your product:
RadDVCodec is version 1.7 for EditDV 1.6 and EditDV 1.6.1
RadDVCodec is version 1.6 for EditDV 1.5 and Moto/PhotoDV 1.4.1
RadDVCodec is even earlier and you should upgrade for Moto/PhotoDV 1.1.3 or
earlier

- If using Quicktime 4.0.x, make sure the Quicktime FireWire DV Enabler is
disabled in the extension manager

- Conflict Catcher will allow you to re-sort the load order of extensions.
If you have Conflict Catcher, you must either sort the load order
alphabetically, make sure Quicktime loads before the Rad extensions, or
uninstall Conflict Catcher from the install CD-ROM.

- Early versions of the "ATI Resource Manager" extension will knock out DV
control. Make sure you have the latest or otherwise disable this
extension.

- On another note, having Virtual Memory on will cause our apps to hang
and often not even load. Turn it off.

- MacOS 9.0 and G4 Macs using a "Sawtooth" motherboard (500, 450, and now
even the 400) will run into a lot of issues with our products. First
problem, on the "Sawtooth" motherboards, is that our products do not work
with the new OHCI hardware structure either with our card or the Built-In
FireWire. Apple will be updating some code to correct this issue in the
near future, but it's is still a gray area. Second problem, with MacOS
9.0, is that you may need the "PACE USB Floppy Enabler" extension if you're
running one of apps which require a software keys and you're running all
this on a Mac with USB built-in. This is downloadable from PACE's website
and there is a link to it on our website, under Support, and Downloads.

***************************************
Mac desktop based products w/ Built-In FireWire or Apple PCI FireWire card:

- Make sure the FireWire Enabler and Support extensions are enabled and
version 2.0 or 2.1 in the Extension Manager. MacOS 9.0 installs version
2.2.x of the FireWire Enabler and Support. If this is the case, please
remove these two extensions and install Apple FireWire Update 2.1 from
Apple's website.

- Makes sure you have the proper Rad extensions for your product.
RadDVCodec is version 1.7 for EditDV 1.6 and EditDV 1.6.1, and is the only
version of our extension set which works reliably with the Built-In
FireWire or Apple's PCI FireWire card. Version 1.6 and early should be
upgraded by manually replacing it with the 1.7 set (and I mean the entire
set of our extensions - 8 of them?) which is downloaded from our "EditDV
1.6.1 update" on our website. In that download, there is a folder called
"Extensions" and all the extensions found inside must replace the ones in
your extension folder.

- If using Quicktime 4.0.x, make sure the Quicktime FireWire DV Enabler is
disabled in the extension manager

- Conflict Catcher will allow you to re-sort the load order of extensions.
If you have Conflict Catcher, you must either sort the load order
alphabetically, make sure Quicktime loads before the Rad extensions, or
uninstall Conflict Catcher from the install CD-ROM.

- Early versions of the "ATI Resource Manager" extension will knock out DV
control. Make sure you have the latest or otherwise disable this
extension.

- On another note, having Virtual Memory on will cause our apps to hang
and often not even load. Turn it off.

- MacOS 9.0 and G4 Macs using a "Sawtooth" motherboard (500, 450, and now
even the 400) will run into a lot of issues with our products. First
problem, on the "Sawtooth" motherboards, is that our products do not work
with the new OHCI hardware structure either with our card or the Built-In
FireWire. Apple will be updating some code to correct this issue in the
near future, but it's is still a gray area. Second problem, with MacOS
9.0, is that you may need the "PACE USB Floppy Enabler" extension if you're
running one of apps which require a software keys and you're running all
this on a Mac with USB built-in. This is downloadable from PACE's website
and there is a link to it on our website, under Support, and Downloads.

***************************************
PC desktop based products w/ DO/Radius 1394 FireWire:

- Make sure the driver for our card is listed as "Digital Origin 1394 bus
controller" for EditDV 1.0.x, Moto/PhotoDV 1.4.1, MotoDV Studio 2.0.1, and
IntroDV, or "Radius 1394 bus controller" for Moto/PhotoDV 1.1.x or MotoDV
Studio 2.0 in the Windows device manager. If it is listed as "Texas
Instrument 1394 bus controlled", then you will need to remove it, reboot,
and install the driver from our CD-ROM. Windows 98 second edition (SE)
users will have to choose "One of the other drivers" and then click on
"view" when the "New Hardware Wizard" detects our card and comes to the
screen telling you it found the updated driver.

- Make sure you have only one version of Quicktime installed on your PC.
Versions 3.0.x or 4.0.x will work just fine with all of our current
products. IntroDV on the other hand might expect to see only Quicktime
4.0.x (3.0.x has been untested by me). If you already have Quicktime
4.0.x, and install 3.0.x later, you will have wipe out Quicktime and start
over... IOW, re-install 4.0.x and keep it, or just reinstall it and then
uninstall, then reinstall 3.0.x on the next boot. If you have "Quicktime
32" or "Quicktime 16" listed in your "Add/Remove Programs" utility or in
the "Control Panel", you most likely have a version 2.x Quicktime installed
and this must be removed before installing a later Quicktime version.

- The most common PC problem with our FireWire card is PCI configuration
issues. Be sure to test our card in a configuration in which it is not
sharing an IRQ with any other device and in which it is the first PCI card
on the PCI bus (if you have an AGP video card, it might be best to leave a
blank PCI slot between the FireWire card and the AGP video card). By
first, I mean the PCI slot closest to the power supply (closest to the AGP
connection). Our card will not work well sharing IRQs with any major I/O
device such as a SCSI controller, IDE controller, USB, or network interface
card (NIC), nor will it work well sharing with some types of sound and
video cards. Another resource problem often seen is having our card on an
IRQ lower than 9. Examples of this might be to see our card on IRQ 3, 4,
or 5 and it may be necessary to reserve these IRQs for ISA/ICU resources
(PCI exclusion) in your BIOS setup utility.

- Windows NT will run into the same problems as Windows 9x, but they will
be presented differently since our drivers are activated by our service,
"RadBMSvc" or "Rad Bus Manager Service". If you are running NT and
experiencing problems, please run "WINMSD" and click on "resources". Our
"RadLynx" listing should appear next to a number. If it does not, you have
resource conflicts and you should physically move the FireWire card to
another PCI slot or remove all other non-essential PCI cards and test. If
the "RadLynx" shows up on a number higher than 15, your WINMSD is not
correctly reporting IRQs and to determine a conflict, you may have to go to
Microsoft's website and visit this URL:
http://support.microsoft.com/support/kb/articles/q180/2/87.asp

Happy editing!!!! =)

_________
John Suit
Technical Support Team
Digital Origin