Windows boot, fastdetect and COM port question  
Author Message
jaho





PostPosted: Wed Mar 01 13:58:46 CST 2006 Top

Windows XP >> Windows boot, fastdetect and COM port question We have a system here that will be a call accounting system. It will have
data from a PBX sent to a COM port even when the system is booting up. This
creates a problem under normal circumstances as Windows will try to install a
serial pointing device.
I have /fastdetect in the boot.ini file but the system is still trying to
install pointing devices. I have added the COM1,2,3 etc after fast detect and
still the same problem.
Basically I have done exactly what Microsoft said to do to prevent the
problems I am seeing.
So what is the real solution to this problem?

Windows XP504  
 
 
Yves





PostPosted: Wed Mar 01 13:58:46 CST 2006 Top

Windows XP >> Windows boot, fastdetect and COM port question On 01/03/2006 "Jerry" <EMail@HideDomain.com> wrote:
>We have a system here that will be a call accounting system. It will have
>data from a PBX sent to a COM port even when the system is booting up. This
>creates a problem under normal circumstances as Windows will try to install a
>serial pointing device.
>I have /fastdetect in the boot.ini file but the system is still trying to
>install pointing devices. I have added the COM1,2,3 etc after fast detect and
>still the same problem.
>Basically I have done exactly what Microsoft said to do to prevent the
>problems I am seeing.
>So what is the real solution to this problem?

Use the BOOT.INI /noserialmice

/NOSERIALMICE=[COMx | COMx,y,z...] - Disables serial mouse detection of the
specified COM port(s). Use this switch if you have a component other than a
mouse attached to a serial port during the startup sequence. If you use
/NOSERIALMICE without specifying a COM port, serial mouse detection is
disabled on all COM ports.

--
---

Y.

 
 
Jerry





PostPosted: Wed Mar 01 14:21:33 CST 2006 Top

Windows XP >> Windows boot, fastdetect and COM port question Isn't that switch for NT4.0 and prior OS' only?

"Yves Leclerc" wrote:

> On 01/03/2006 "Jerry" <EMail@HideDomain.com> wrote:
> >We have a system here that will be a call accounting system. It will have
> >data from a PBX sent to a COM port even when the system is booting up. This
> >creates a problem under normal circumstances as Windows will try to install a
> >serial pointing device.
> >I have /fastdetect in the boot.ini file but the system is still trying to
> >install pointing devices. I have added the COM1,2,3 etc after fast detect and
> >still the same problem.
> >Basically I have done exactly what Microsoft said to do to prevent the
> >problems I am seeing.
> >So what is the real solution to this problem?
>
> Use the BOOT.INI /noserialmice
>
> /NOSERIALMICE=[COMx | COMx,y,z...] - Disables serial mouse detection of the
> specified COM port(s). Use this switch if you have a component other than a
> mouse attached to a serial port during the startup sequence. If you use
> /NOSERIALMICE without specifying a COM port, serial mouse detection is
> disabled on all COM ports.
>
> --
> ---
>
> Y.
>
>
 
 
Jerry





PostPosted: Wed Mar 01 14:24:29 CST 2006 Top

Windows XP >> Windows boot, fastdetect and COM port question Here is the key line from my boot.ini file.
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP
Professional" /FASTDETECT /NoExecute=OptIn

Now, fastdetect was in lower case but I just changed it to upper case just
because. I do not think it is case sensitive but you never know.
Any other thoughts on this problem?

"Yves Leclerc" wrote:

> On 01/03/2006 "Jerry" <EMail@HideDomain.com> wrote:
> >We have a system here that will be a call accounting system. It will have
> >data from a PBX sent to a COM port even when the system is booting up. This
> >creates a problem under normal circumstances as Windows will try to install a
> >serial pointing device.
> >I have /fastdetect in the boot.ini file but the system is still trying to
> >install pointing devices. I have added the COM1,2,3 etc after fast detect and
> >still the same problem.
> >Basically I have done exactly what Microsoft said to do to prevent the
> >problems I am seeing.
> >So what is the real solution to this problem?
>
> Use the BOOT.INI /noserialmice
>
> /NOSERIALMICE=[COMx | COMx,y,z...] - Disables serial mouse detection of the
> specified COM port(s). Use this switch if you have a component other than a
> mouse attached to a serial port during the startup sequence. If you use
> /NOSERIALMICE without specifying a COM port, serial mouse detection is
> disabled on all COM ports.
>
> --
> ---
>
> Y.
>
>
 
 
Infosink





PostPosted: Wed Mar 01 14:59:00 CST 2006 Top

Windows XP >> Windows boot, fastdetect and COM port question Jerry wrote:
>> Isn't that switch for NT4.0 and prior OS' only?
>>
>> "Yves Leclerc" wrote:
>>
>>> On 01/03/2006 "Jerry" <EMail@HideDomain.com> wrote:
>>>> We have a system here that will be a call accounting system. It
>>>> will have data from a PBX sent to a COM port even when the system
>>>> is booting up. This creates a problem under normal circumstances
>>>> as Windows will try to install a serial pointing device.
>>>> I have /fastdetect in the boot.ini file but the system is still
>>>> trying to install pointing devices. I have added the COM1,2,3 etc
>>>> after fast detect and still the same problem.
>>>> Basically I have done exactly what Microsoft said to do to prevent
>>>> the problems I am seeing.
>>>> So what is the real solution to this problem?
>>>
>>> Use the BOOT.INI /noserialmice
>>>
>>> /NOSERIALMICE=[COMx | COMx,y,z...] - Disables serial mouse
>>> detection of the specified COM port(s). Use this switch if you have
>>> a component other than a mouse attached to a serial port during the
>>> startup sequence. If you use /NOSERIALMICE without specifying a COM
>>> port, serial mouse detection is disabled on all COM ports.
>>>
>>> --
>>> ---
>>>
>>> Y.

Here's a link if it helps anyone:

[Boot INI Options Reference]
http://www.sysinternals.com/Information/bootini.html


 
 
Jerry





PostPosted: Wed Mar 01 15:30:47 CST 2006 Top

Windows XP >> Windows boot, fastdetect and COM port question The problem with the switches listed are that the /fastdetect one just flat
out does not work.

"Infosink" wrote:

> Jerry wrote:
> >> Isn't that switch for NT4.0 and prior OS' only?
> >>
> >> "Yves Leclerc" wrote:
> >>
> >>> On 01/03/2006 "Jerry" <EMail@HideDomain.com> wrote:
> >>>> We have a system here that will be a call accounting system. It
> >>>> will have data from a PBX sent to a COM port even when the system
> >>>> is booting up. This creates a problem under normal circumstances
> >>>> as Windows will try to install a serial pointing device.
> >>>> I have /fastdetect in the boot.ini file but the system is still
> >>>> trying to install pointing devices. I have added the COM1,2,3 etc
> >>>> after fast detect and still the same problem.
> >>>> Basically I have done exactly what Microsoft said to do to prevent
> >>>> the problems I am seeing.
> >>>> So what is the real solution to this problem?
> >>>
> >>> Use the BOOT.INI /noserialmice
> >>>
> >>> /NOSERIALMICE=[COMx | COMx,y,z...] - Disables serial mouse
> >>> detection of the specified COM port(s). Use this switch if you have
> >>> a component other than a mouse attached to a serial port during the
> >>> startup sequence. If you use /NOSERIALMICE without specifying a COM
> >>> port, serial mouse detection is disabled on all COM ports.
> >>>
> >>> --
> >>> ---
> >>>
> >>> Y.
>
> Here's a link if it helps anyone:
>
> [Boot INI Options Reference]
> http://www.sysinternals.com/Information/bootini.html
>
>
>