Conflict on Added COM Port

  • Thread starter Thread starter Thomas M
  • Start date Start date
T

Thomas M

Windows XP

I have a CD duplicating machine that is connected to a computer running
Windows XP. When I try to open the software for the CD duplicator, I
get a message indicating that the software is unable to communicate with
the CD duplicator, and that message is followed by a dialog box that
allows the user to configure the software to use COM1, COM2, COM3, or
COM4 for communications with the duplicator. Whatever I pick gives me
an error message that just indicates that the software still cannot
communicate with the CD duplicator.

So I went into the System Information applet and checked the I/O listing
under Hardware Resources. COM1 is the only COM port that is listed, and
it's in use by another device. So I reasoned that I can add another COM
port, and then configure the duplicator software to use the newly added
COM port.

So I used the Add Hardware Wizard to add a new COM port. The final step
of the Add Hardware Wizard gave me the following message:

Windows cannot determine the settings for this device.
Consult the documentation that came with this device and
use the Resource tab to set the configuration. (Code 34)

I then went in the properties for the COM port and checked the resources
that were assigned to the port. There was a conflict, so I used the
"Settings based on" drop-down box to select a basic configuration that
would not result in a conflict. I then rebooted the computer.

After logging on again, I went back into the Device Manager, and it
still shows a conflict with the device. So I looked at the device
properties again, and the device status reads:

This device cannot start. (Code 10)

However, the Resources tab shows that there are no conflicting devices.

I've gone through this same process on 3 computers now, and I get the
same outcome each time. I've also tried removing and reinstalling the
COM port, and that does not help either. I'm stumped. How can I get
the new COM port working?

--Tom
 
Are there multiple PHYSICAL COM ports on the computer? If not, you're
trying to add a non-existent device which would account for the Code 10
error. You either need to figure out what is using COM1 (internal modem
maybe?) and disable it or add an inexpensive port card. You will also need
a Win XP device driver for the CD duplicating machine.
 
Are there multiple PHYSICAL COM ports on the computer? If not, you're
trying to add a non-existent device which would account for the Code 10
error. You either need to figure out what is using COM1 (internal modem
maybe?) and disable it or add an inexpensive port card. You will also need
a Win XP device driver for the CD duplicating machine.
Click to expand...

Thanks for the reply.

There actually is no such thing as a physical COM port. A COM port is
just a collection of resources--namely, an I/O address and IRQ--that is
assigned to a serial port. Most people, when they hear the term "serial
port," think of a 9-pin connector on the back of a machine, but in fact
the word "serial" just means "one at a time," so any port that sends
data one bit at a time is a serial port, and that includes both USB and
FireWire.

The CD duplicator came with a FireWire card that is installed in the
machine. Windows XP supports the FireWire card with a native driver, so
that driver was installed automatically and the Device Manager shows the
card as working and without conflicts. However, the robotics on the
duplicator apparently require a COM port for communication with the PC.
I believe that if I can clear the conflict from the COM port that I've
added, I will then be able to assign the COM port to the duplicators
robotics, at which point the whole thing will work through the FireWire
connection.

For whatever reason, when I add a COM port, it shows up in Device
Manager with a yellow circle and an exclamation point, indicating an
error of some sort. But when I go into the properties for the COM port
and look at the Resources tab, it shows that there are no conflicting
devices.

I'll try to figure out what is using COM1, as you suggest, and see if I
can maybe use that COM port.

--Tom
 
Thomas M said:
Thanks for the reply.

There actually is no such thing as a physical COM port. A COM port is
just a collection of resources--namely, an I/O address and IRQ--that is
assigned to a serial port. Most people, when they hear the term "serial
port," think of a 9-pin connector on the back of a machine, but in fact
the word "serial" just means "one at a time," so any port that sends
data one bit at a time is a serial port, and that includes both USB and
FireWire.

The CD duplicator came with a FireWire card that is installed in the
machine. Windows XP supports the FireWire card with a native driver, so
that driver was installed automatically and the Device Manager shows the
card as working and without conflicts. However, the robotics on the
duplicator apparently require a COM port for communication with the PC.
I believe that if I can clear the conflict from the COM port that I've
added, I will then be able to assign the COM port to the duplicators
robotics, at which point the whole thing will work through the FireWire
connection.

For whatever reason, when I add a COM port, it shows up in Device
Manager with a yellow circle and an exclamation point, indicating an
error of some sort. But when I go into the properties for the COM port
and look at the Resources tab, it shows that there are no conflicting
devices.

I'll try to figure out what is using COM1, as you suggest, and see if I
can maybe use that COM port.

--Tom
Click to expand...

That's much clearer. I assumed the device connected to a serial port since
you mentioned no hardware. Virtualized COM ports (for devices like internal
or USB modems) are normally created by a device driver, not manually by the
user. If this device is only capable of using COM1 (which would be
surprising) and that is currently assigned to a serial port, you might try
disabling COM1 in the BIOS.
--
 
Back
Top