Build a great reporting interface using Splunk, one of the leaders in the Security Information and Event Management (SIEM) field, linking the collected Windows events to www.eventid.net. The EventId.Net for Splunk Add-on assumes that Splunk is collecting information from Windows servers and workstation via the Splunk Universal Forwarder.
The control registers for com1 overlaps with the com2 control registers
|English: Request a translation of the event description in plain English.|
This event may occur if you assign an I/O address to a COM port, and that I/O address is already assigned to another COM port. See ME112584 for details.
Variations exist such as ID:3 source: serial "user configuration data for parameter com1 overriding firmware configuration data" and ID: 36, Source: serial "while validating that com1 was really a serial port, the contents of the divisor latch register was identical to the interrupt enable and receive registers. The device is assumed not to be a serial port and will be deleted". Generally, all three errors pertain to misconfigured com ports. They are especially prevalent after creating a new com port. For instance, I added com 2 under nt 4 sp 6a to install my modem (the error is nothing to do with the make of modem by the way) and voila! I got all three errors! The error you get depends on the type of misconfiguration, typically the base I/O or irq is in conflict with another device or you are using the same configuration for both com 1 and com 2 resulting in ID 29.
Sometimes this error is created by winmodems installation (i.e. Lucent ltmodem).
|Private comment: Subscribers only. See example of private comment|
|Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links...|
Send comments or solutions
- Notify me when updated