COM1 unavailable

[N1K]

Hi guys,

I have a big problem...here's the situation:

Company with app 1200 users, PC cloning, domain, group and local policy enforced etc..

All of a sudden we're getting this error.

When you start computer you login and run the mode com1 from command prompt and you get the status for it, but after short period of time (few minutes) you get the error shown in the picture...

[rjz]

Maybe your com port is being hogged. Check for faxes, modems, mice/joysticks. Sometimes more than 1 device might be accidently on the port. What does your device manager say? Also check your bios settings.

[N1K]

Maybe your com port is being hogged. Check for faxes, modems, mice/joysticks. Sometimes more than 1 device might be accidently on the port. What does your device manager say? Also check your bios settings.

<{POST_SNAPBACK}>

Bios settings, and device manager settings are fine. Device manager doesn't report any conflicts..

[rjz]

What com devices do you use?

[egrath]

Hi,

your problem probably has something to do with an application attaching to the COM1 Port. Use "Process Explorer" (www.sysinternals.com) to enumerate which application is using the port:

Find->Find Handle

then Enter: "\Device\Serial0"

and you will see the application which has COM1 opened.

Bye, Egon

[N1K]

Hi,

your problem probably has something to do with an application attaching to the COM1 Port. Use "Process Explorer" (www.sysinternals.com) to enumerate which application is using the port:

Find->Find Handle

then Enter: "\Device\Serial0"

and you will see the application which has COM1 opened.

Bye, Egon

<{POST_SNAPBACK}>

Thx mate, I'll try that!

[N1K]

Hi,

your problem probably has something to do with an application attaching to the COM1 Port. Use "Process Explorer" (www.sysinternals.com) to enumerate which application is using the port:

Find->Find Handle

then Enter: "\Device\Serial0"

and you will see the application which has COM1 opened.

Bye, Egon

<{POST_SNAPBACK}>

Thx mate, it worked, RTVSCAN.exe and DOSCAN.exe were processes that occupied COM port...

Thx mate once again

[rjz]

That's odd symantec AV 10 uses the com1 port. When you stopped them what did Symantec do?

Info:

If your doscan and/orrtvscan is overloaded on startup symantec has a special reg fix.

[N1K]

That's odd symantec AV 10 uses the com1 port. When you stopped them what did Symantec do?

Info:

If your doscan and/orrtvscan is overloaded on startup symantec has a special reg fix.

<{POST_SNAPBACK}>

We find the reg key which solves this problem. In this case those scans aren't run at startup...