Re[3]: [W] Re: Quickcam problems w/ ANYTHING

marshall katz (
Wed, 21 Feb 96 14:36:04 EST

Well folks,

The Quick Cam mystery is solved. First I want to thank all who
responded to my original post, including the Connectix folks. Their
Responses are copied below in the hope that it may Help others to
debug their Quick Cam problem.

The problem turns out to be that Modem connector doesn't have a 1
to 1 pin correlation, e.g., pin wire 1 in may be connected to pin 3
out so as to connect the cam to my PC's parallel port. Some of the
wires inside the modem connector are crossed. That's what caused the
software not to recognize LPT1. The connector (extension) I was given
fit perfectly as an extension and I had no suspicions otherwise.

The solution is that a ribbon (or other type connector) is needed
for that @#$% oversized parallel port connector on the Quick Cam. I
had a ribbon connector made up and the Quick Cam works perfectly now.

I am told that nothing can be done about the size of the parallel
port connector on the Quick Cam as there is a board inside and that's
the smallest they can get. However, that type connector on the Quick
Cam will only fit 1 in 5 systems here. Some other connector, such as
a mouse connector, gets in the road.

Hope this helps someone avoid the same pitfalls. Have a Nice Day!
Marshall... (see responses I received below)


Hugh "Da Masta" McNally

o Make sure LPT1 is actually LPT1. Attach a printer to it and see if
it prints.
Maybe you have LPT1 mapped out to a network printer; that would
probably make
things not work (just a guess--never happened to me)

o Check out (in your BIOS setup) how LPT1 is configured; you might
need to make it bidirectional (why? I dunno, just something to try)

o Do you have the other QuickCam plug correctly attached to the
keyboard daisy-chain thing? I think that's how the thing gets its

Try the QuickCam SW before ANY CU-SeeMe stuff (eliminate that
variable). Only the White Pine versions of CUSM (v84b7 and later)
work with QuickCam. The latest version from WP is quantum levels
better than previous stuff.


Are you using the parallel port? Was there a printer on the port
before you added QuickCam?

I had the same problem when I first installed QuickCam. Then I
remembered the printer driver was being started in my win.ini file so
it already had control of the port by the time I launched QuickCam
from Program Manager, thus it was unavailable to QC. I was getting the
no device message also as a result.

BTW: Get the QuickCam stuff working first BEFORE you try to integrate
it with CUSM.


Alan Ashton<>
Connectix Corp.

Posted below are a few troubleshooting steps. You also might try the
QuickCam on another computer to make sure its not a hardware problem.

Please look for the MSVIDEO=QUICKCAM.DRV line in the Drivers
section of the System.ini file. Make sure that the QuickCam.drv is
the first video capture driver listed. If necessary, comment out any
other video capture drivers by inserting a semicolon at the beginning
of any lines starting with MSVIDEO.

Please check the Comm.drv= statement in the System.ini. Please make
sure that it says Comm.drv=Comm.drv. This communications driver
controls your ports and brand X drivers sometimes do not operate

The QuickCam does not work well with the ECP type of parallel port.
The EPP type is much better. Changing the type of parallel port is
usually in the BIOS, a jumper on the motherboard or both. Please
check your hardware documentation for further information on your
parallel port setting.

(The QuickCam for Windows polls each parallel port in the computer for
the QuickCam each time you launch the application. If the port is
busy because another application is using it like printing to your
printer or the other application did not properly release the port,
then the QuickCam will not find the camera. You might check the port
to see if it is busy in the Microsoft Diagnostics program (MSD) or
reboot the computer and try again.)