How Do I Configure Serial Port Correctly?

[Marc]

I just installed a new serial device into my Windows XP machine. It is the
first and only serial device that will be placed on this machine.

The device and my motherboard appear to be working fine, as upon initial
installation, it worked correctly. However, the problem arises whenever I
reboot my machine. Then, I get the following exception: Access to the port
'COM1' is denied.

This error makes no sense to me, as it sounds like something else is
blocking the port, but I have never had any other serial devices on this
machine. I have been able to come up with a strange workaround for this, but
it seems ridiculous to me.

In order for it to work on the next reboot, I have to first uninstall COM1
in Device Manager before rebooting. I have to remember to do this every time
I reboot, or it will not work.

I would appreciate any advice you could give me regarding this matter. Is
there a tool that would allow me to see what is blocking COM1 at certain
times? Or, perhaps, is there a way to automate the uninstall with a script
prior to rebooting Windows?

[JS]

Go to the Control Panel/System/Device Manager, expand the Ports option and
then double click on the COM1 entry and check the Resources tab for any
conflicts listed at the bottom.

JS

"Marc" > wrote in message
...
>I just installed a new serial device into my Windows XP machine. It is the
> first and only serial device that will be placed on this machine.
>
> The device and my motherboard appear to be working fine, as upon initial
> installation, it worked correctly. However, the problem arises whenever I
> reboot my machine. Then, I get the following exception: Access to the
> port
> 'COM1' is denied.
>
> This error makes no sense to me, as it sounds like something else is
> blocking the port, but I have never had any other serial devices on this
> machine. I have been able to come up with a strange workaround for this,
> but
> it seems ridiculous to me.
>
> In order for it to work on the next reboot, I have to first uninstall COM1
> in Device Manager before rebooting. I have to remember to do this every
> time
> I reboot, or it will not work.
>
> I would appreciate any advice you could give me regarding this matter. Is
> there a tool that would allow me to see what is blocking COM1 at certain
> times? Or, perhaps, is there a way to automate the uninstall with a
> script
> prior to rebooting Windows?

[Jim Macklin]

What is the "serial device?"



"Marc" > wrote in message
...
|I just installed a new serial device into my Windows XP
machine. It is the
| first and only serial device that will be placed on this
machine.
|
| The device and my motherboard appear to be working fine,
as upon initial
| installation, it worked correctly. However, the problem
arises whenever I
| reboot my machine. Then, I get the following exception:
Access to the port
| 'COM1' is denied.
|
| This error makes no sense to me, as it sounds like
something else is
| blocking the port, but I have never had any other serial
devices on this
| machine. I have been able to come up with a strange
workaround for this, but
| it seems ridiculous to me.
|
| In order for it to work on the next reboot, I have to
first uninstall COM1
| in Device Manager before rebooting. I have to remember to
do this every time
| I reboot, or it will not work.
|
| I would appreciate any advice you could give me regarding
this matter. Is
| there a tool that would allow me to see what is blocking
COM1 at certain
| times? Or, perhaps, is there a way to automate the
uninstall with a script
| prior to rebooting Windows?

[Marc]

No conflicts.

"JS" wrote:

> Go to the Control Panel/System/Device Manager, expand the Ports option and
> then double click on the COM1 entry and check the Resources tab for any
> conflicts listed at the bottom.
>
> JS
>
> "Marc" > wrote in message
> ...
> >I just installed a new serial device into my Windows XP machine. It is the
> > first and only serial device that will be placed on this machine.
> >
> > The device and my motherboard appear to be working fine, as upon initial
> > installation, it worked correctly. However, the problem arises whenever I
> > reboot my machine. Then, I get the following exception: Access to the
> > port
> > 'COM1' is denied.
> >
> > This error makes no sense to me, as it sounds like something else is
> > blocking the port, but I have never had any other serial devices on this
> > machine. I have been able to come up with a strange workaround for this,
> > but
> > it seems ridiculous to me.
> >
> > In order for it to work on the next reboot, I have to first uninstall COM1
> > in Device Manager before rebooting. I have to remember to do this every
> > time
> > I reboot, or it will not work.
> >
> > I would appreciate any advice you could give me regarding this matter. Is
> > there a tool that would allow me to see what is blocking COM1 at certain
> > times? Or, perhaps, is there a way to automate the uninstall with a
> > script
> > prior to rebooting Windows?
>
>
>

[Marc]

It's a SpitFIRE Infrared Remote Control. It uses its internal infrared code
library to support all common TVs, VCRs, DSSs, and DVD Players.

Not exactly a mainstream modem like you're probably expecting...I have a
physical disability and I'm hoping this will help automate my home a little
bit more.

By the way, I'm also a programmer. Neither the software that came with the
device nor a simple little .NET application I quickly scraped together can
establish a connection to COM1 when doing what I described previously.

"Jim Macklin" wrote:

> What is the "serial device?"
>
>
>
> "Marc" > wrote in message
> ...
> |I just installed a new serial device into my Windows XP
> machine. It is the
> | first and only serial device that will be placed on this
> machine.
> |
> | The device and my motherboard appear to be working fine,
> as upon initial
> | installation, it worked correctly. However, the problem
> arises whenever I
> | reboot my machine. Then, I get the following exception:
> Access to the port
> | 'COM1' is denied.
> |
> | This error makes no sense to me, as it sounds like
> something else is
> | blocking the port, but I have never had any other serial
> devices on this
> | machine. I have been able to come up with a strange
> workaround for this, but
> | it seems ridiculous to me.
> |
> | In order for it to work on the next reboot, I have to
> first uninstall COM1
> | in Device Manager before rebooting. I have to remember to
> do this every time
> | I reboot, or it will not work.
> |
> | I would appreciate any advice you could give me regarding
> this matter. Is
> | there a tool that would allow me to see what is blocking
> COM1 at certain
> | times? Or, perhaps, is there a way to automate the
> uninstall with a script
> | prior to rebooting Windows?
>
>
>

[Jim Macklin]

Some hook is being saved since the serial port is being
reserved , even through a re-boot. I'm not a programmer or
even a certified real computer expert. But your suggestion
of writing a script sounds good, maybe some real expert can
point you to the registry entry for the serial port and
change the status from 1 to 0 or whatever is required.
Perhaps a program such as TweakUI or FreshUI has a function
that can do that.
I wonder if http://www.innotechsystems.com/spitfire.htm has
a USB driver or if a USB to serial adapter would work?



"Marc" > wrote in message
...
| It's a SpitFIRE Infrared Remote Control. It uses its
internal infrared code
| library to support all common TVs, VCRs, DSSs, and DVD
Players.
|
| Not exactly a mainstream modem like you're probably
expecting...I have a
| physical disability and I'm hoping this will help automate
my home a little
| bit more.
|
| By the way, I'm also a programmer. Neither the software
that came with the
| device nor a simple little .NET application I quickly
scraped together can
| establish a connection to COM1 when doing what I described
previously.
|
| "Jim Macklin" wrote:
|
| > What is the "serial device?"
| >
| >
| >
| > "Marc" > wrote in message
| >
...
| > |I just installed a new serial device into my Windows XP
| > machine. It is the
| > | first and only serial device that will be placed on
this
| > machine.
| > |
| > | The device and my motherboard appear to be working
fine,
| > as upon initial
| > | installation, it worked correctly. However, the
problem
| > arises whenever I
| > | reboot my machine. Then, I get the following
exception:
| > Access to the port
| > | 'COM1' is denied.
| > |
| > | This error makes no sense to me, as it sounds like
| > something else is
| > | blocking the port, but I have never had any other
serial
| > devices on this
| > | machine. I have been able to come up with a strange
| > workaround for this, but
| > | it seems ridiculous to me.
| > |
| > | In order for it to work on the next reboot, I have to
| > first uninstall COM1
| > | in Device Manager before rebooting. I have to
remember to
| > do this every time
| > | I reboot, or it will not work.
| > |
| > | I would appreciate any advice you could give me
regarding
| > this matter. Is
| > | there a tool that would allow me to see what is
blocking
| > COM1 at certain
| > | times? Or, perhaps, is there a way to automate the
| > uninstall with a script
| > | prior to rebooting Windows?
| >
| >
| >

[JS]

Can you change to use COM2?

JS

"Marc" > wrote in message
...
>I just installed a new serial device into my Windows XP machine. It is the
> first and only serial device that will be placed on this machine.
>
> The device and my motherboard appear to be working fine, as upon initial
> installation, it worked correctly. However, the problem arises whenever I
> reboot my machine. Then, I get the following exception: Access to the
> port
> 'COM1' is denied.
>
> This error makes no sense to me, as it sounds like something else is
> blocking the port, but I have never had any other serial devices on this
> machine. I have been able to come up with a strange workaround for this,
> but
> it seems ridiculous to me.
>
> In order for it to work on the next reboot, I have to first uninstall COM1
> in Device Manager before rebooting. I have to remember to do this every
> time
> I reboot, or it will not work.
>
> I would appreciate any advice you could give me regarding this matter. Is
> there a tool that would allow me to see what is blocking COM1 at certain
> times? Or, perhaps, is there a way to automate the uninstall with a
> script
> prior to rebooting Windows?

[Marc]

I suppose I could try that. That would involve a BIOS change, right? With
my disability, I don't have quick and easy access to regular keyboard use or
plugging and unplugging hardware. I may have to wait for some help to do
this.

I was hoping I could find a way in Windows to correct this. If I'm having
problems with COM1, wouldn't the same issues arise with COM2?

"JS" wrote:

> Can you change to use COM2?
>
> JS
>
> "Marc" > wrote in message
> ...
> >I just installed a new serial device into my Windows XP machine. It is the
> > first and only serial device that will be placed on this machine.
> >
> > The device and my motherboard appear to be working fine, as upon initial
> > installation, it worked correctly. However, the problem arises whenever I
> > reboot my machine. Then, I get the following exception: Access to the
> > port
> > 'COM1' is denied.
> >
> > This error makes no sense to me, as it sounds like something else is
> > blocking the port, but I have never had any other serial devices on this
> > machine. I have been able to come up with a strange workaround for this,
> > but
> > it seems ridiculous to me.
> >
> > In order for it to work on the next reboot, I have to first uninstall COM1
> > in Device Manager before rebooting. I have to remember to do this every
> > time
> > I reboot, or it will not work.
> >
> > I would appreciate any advice you could give me regarding this matter. Is
> > there a tool that would allow me to see what is blocking COM1 at certain
> > times? Or, perhaps, is there a way to automate the uninstall with a
> > script
> > prior to rebooting Windows?
>
>
>

[Marc]

If it is only just a registry setting, that would be easy for me to program.
Do you know of any good registry monitoring software that could compare the
two states (working and not working) of my device?

"Jim Macklin" wrote:

> Some hook is being saved since the serial port is being
> reserved , even through a re-boot. I'm not a programmer or
> even a certified real computer expert. But your suggestion
> of writing a script sounds good, maybe some real expert can
> point you to the registry entry for the serial port and
> change the status from 1 to 0 or whatever is required.
> Perhaps a program such as TweakUI or FreshUI has a function
> that can do that.
> I wonder if http://www.innotechsystems.com/spitfire.htm has
> a USB driver or if a USB to serial adapter would work?
>
>
>
> "Marc" > wrote in message
> ...
> | It's a SpitFIRE Infrared Remote Control. It uses its
> internal infrared code
> | library to support all common TVs, VCRs, DSSs, and DVD
> Players.
> |
> | Not exactly a mainstream modem like you're probably
> expecting...I have a
> | physical disability and I'm hoping this will help automate
> my home a little
> | bit more.
> |
> | By the way, I'm also a programmer. Neither the software
> that came with the
> | device nor a simple little .NET application I quickly
> scraped together can
> | establish a connection to COM1 when doing what I described
> previously.
> |
> | "Jim Macklin" wrote:
> |
> | > What is the "serial device?"
> | >
> | >
> | >
> | > "Marc" > wrote in message
> | >
> ...
> | > |I just installed a new serial device into my Windows XP
> | > machine. It is the
> | > | first and only serial device that will be placed on
> this
> | > machine.
> | > |
> | > | The device and my motherboard appear to be working
> fine,
> | > as upon initial
> | > | installation, it worked correctly. However, the
> problem
> | > arises whenever I
> | > | reboot my machine. Then, I get the following
> exception:
> | > Access to the port
> | > | 'COM1' is denied.
> | > |
> | > | This error makes no sense to me, as it sounds like
> | > something else is
> | > | blocking the port, but I have never had any other
> serial
> | > devices on this
> | > | machine. I have been able to come up with a strange
> | > workaround for this, but
> | > | it seems ridiculous to me.
> | > |
> | > | In order for it to work on the next reboot, I have to
> | > first uninstall COM1
> | > | in Device Manager before rebooting. I have to
> remember to
> | > do this every time
> | > | I reboot, or it will not work.
> | > |
> | > | I would appreciate any advice you could give me
> regarding
> | > this matter. Is
> | > | there a tool that would allow me to see what is
> blocking
> | > COM1 at certain
> | > | times? Or, perhaps, is there a way to automate the
> | > uninstall with a script
> | > | prior to rebooting Windows?
> | >
> | >
> | >
>
>
>

[Jim Macklin]

No, I think you just have to do a backup (save a system
restore point) and then look for the registry line. There
must be somebody with more experience who can help you.



"Marc" > wrote in message
...
| If it is only just a registry setting, that would be easy
for me to program.
| Do you know of any good registry monitoring software that
could compare the
| two states (working and not working) of my device?
|
| "Jim Macklin" wrote:
|
| > Some hook is being saved since the serial port is being
| > reserved , even through a re-boot. I'm not a programmer
or
| > even a certified real computer expert. But your
suggestion
| > of writing a script sounds good, maybe some real expert
can
| > point you to the registry entry for the serial port and
| > change the status from 1 to 0 or whatever is required.
| > Perhaps a program such as TweakUI or FreshUI has a
function
| > that can do that.
| > I wonder if http://www.innotechsystems.com/spitfire.htm
has
| > a USB driver or if a USB to serial adapter would work?
| >
| >
| >
| > "Marc" > wrote in message
| >
...
| > | It's a SpitFIRE Infrared Remote Control. It uses its
| > internal infrared code
| > | library to support all common TVs, VCRs, DSSs, and DVD
| > Players.
| > |
| > | Not exactly a mainstream modem like you're probably
| > expecting...I have a
| > | physical disability and I'm hoping this will help
automate
| > my home a little
| > | bit more.
| > |
| > | By the way, I'm also a programmer. Neither the
software
| > that came with the
| > | device nor a simple little .NET application I quickly
| > scraped together can
| > | establish a connection to COM1 when doing what I
described
| > previously.
| > |
| > | "Jim Macklin" wrote:
| > |
| > | > What is the "serial device?"
| > | >
| > | >
| > | >
| > | > "Marc" > wrote in
message
| > | >
| >
...
| > | > |I just installed a new serial device into my
Windows XP
| > | > machine. It is the
| > | > | first and only serial device that will be placed
on
| > this
| > | > machine.
| > | > |
| > | > | The device and my motherboard appear to be working
| > fine,
| > | > as upon initial
| > | > | installation, it worked correctly. However, the
| > problem
| > | > arises whenever I
| > | > | reboot my machine. Then, I get the following
| > exception:
| > | > Access to the port
| > | > | 'COM1' is denied.
| > | > |
| > | > | This error makes no sense to me, as it sounds like
| > | > something else is
| > | > | blocking the port, but I have never had any other
| > serial
| > | > devices on this
| > | > | machine. I have been able to come up with a
strange
| > | > workaround for this, but
| > | > | it seems ridiculous to me.
| > | > |
| > | > | In order for it to work on the next reboot, I have
to
| > | > first uninstall COM1
| > | > | in Device Manager before rebooting. I have to
| > remember to
| > | > do this every time
| > | > | I reboot, or it will not work.
| > | > |
| > | > | I would appreciate any advice you could give me
| > regarding
| > | > this matter. Is
| > | > | there a tool that would allow me to see what is
| > blocking
| > | > COM1 at certain
| > | > | times? Or, perhaps, is there a way to automate
the
| > | > uninstall with a script
| > | > | prior to rebooting Windows?
| > | >
| > | >
| > | >
| >
| >
| >

[JS]

COM2 uses a different IRQ and I/O resources.
Not sure about a BIOS change, however if the serial device is a card that
uses a PCI slot, then the card itself may have a jumper to select which COM
port it will use.

JS

"Marc" > wrote in message
...
>I suppose I could try that. That would involve a BIOS change, right? With
> my disability, I don't have quick and easy access to regular keyboard use
> or
> plugging and unplugging hardware. I may have to wait for some help to do
> this.
>
> I was hoping I could find a way in Windows to correct this. If I'm having
> problems with COM1, wouldn't the same issues arise with COM2?
>
> "JS" wrote:
>
>> Can you change to use COM2?
>>
>> JS
>>
>> "Marc" > wrote in message
>> ...
>> >I just installed a new serial device into my Windows XP machine. It is
>> >the
>> > first and only serial device that will be placed on this machine.
>> >
>> > The device and my motherboard appear to be working fine, as upon
>> > initial
>> > installation, it worked correctly. However, the problem arises
>> > whenever I
>> > reboot my machine. Then, I get the following exception: Access to the
>> > port
>> > 'COM1' is denied.
>> >
>> > This error makes no sense to me, as it sounds like something else is
>> > blocking the port, but I have never had any other serial devices on
>> > this
>> > machine. I have been able to come up with a strange workaround for
>> > this,
>> > but
>> > it seems ridiculous to me.
>> >
>> > In order for it to work on the next reboot, I have to first uninstall
>> > COM1
>> > in Device Manager before rebooting. I have to remember to do this
>> > every
>> > time
>> > I reboot, or it will not work.
>> >
>> > I would appreciate any advice you could give me regarding this matter.
>> > Is
>> > there a tool that would allow me to see what is blocking COM1 at
>> > certain
>> > times? Or, perhaps, is there a way to automate the uninstall with a
>> > script
>> > prior to rebooting Windows?
>>
>>
>>