| 0x40060001 | The kernel debugger is already using %2. |
The kernel debugger is already using %2. |
| 0x40060002 | While validating that %2 was really a serial port, a fifo was detected. The fifo will be used. |
While validating that %2 was really a serial port, a fifo was detected. The fifo will be used. |
| 0x40060003 | User configuration data for parameter %2 overriding firmware configuration data. |
User configuration data for parameter %2 overriding firmware configuration data. |
| 0x40060022 | Disabling %2 as requested by the configuration data. |
Disabling %2 as requested by the configuration data. |
| 0x80060004 | Unable to create the symbolic link for %2. |
Unable to create the symbolic link for %2. |
| 0x80060005 | Unable to create the device map entry for %2. |
Unable to create the device map entry for %2. |
| 0x80060006 | Unable to delete the device map entry for %2. |
Unable to delete the device map entry for %2. |
| 0x8006002A | There is a serial mouse using the same interrupt as %2. Therefore, %2 will not be started. |
There is a serial mouse using the same interrupt as %2. Therefore, %2 will not be started. |
| 0x8006002B | There was a serial mouse found on %2. Therefore, %2 will be assigned to the mouse. |
There was a serial mouse found on %2. Therefore, %2 will be assigned to the mouse. |
| 0xC0060007 | Another driver on the system, which did not report its resources, has already claimed the interrupt used by %2. |
Another driver on the system, which did not report its resources, has already claimed the interrupt used by %2. |
| 0xC0060008 | Not enough resources were available for the driver. |
Not enough resources were available for the driver. |
| 0xC0060009 | The baud clock rate configuration is not supported on device %2. |
The baud clock rate configuration is not supported on device %2. |
| 0xC006000A | The hardware locations for %2 could not be translated to something the memory management system could understand. |
The hardware locations for %2 could not be translated to something the memory management system could understand. |
| 0xC006000B | The hardware resources for %2 are already in use by another device. |
The hardware resources for %2 are already in use by another device. |
| 0xC006000C | No memory could be allocated in which to place new data for %2. |
No memory could be allocated in which to place new data for %2. |
| 0xC006000D | While validating that %2 was really a serial port, the interrupt enable register contained enabled bits in a must be zero bitfield.The device is assumed not to be a serial port and will be deleted. |
While validating that %2 was really a serial port, the interrupt enable register contained enabled bits in a must be zero bitfield.The device is assumed not to be a serial port and will be deleted. |
| 0xC006000E | While validating that %2 was really a serial port, the modem control register contained enabled bits in a must be zero bitfield.The device is assumed not to be a serial port and will be deleted. |
While validating that %2 was really a serial port, the modem control register contained enabled bits in a must be zero bitfield.The device is assumed not to be a serial port and will be deleted. |
| 0xC006000F | While validating that %2 was really a serial port, the interrupt id register contained enabled bits in a must be zero bitfield.The device is assumed not to be a serial port and will be deleted. |
While validating that %2 was really a serial port, the interrupt id register contained enabled bits in a must be zero bitfield.The device is assumed not to be a serial port and will be deleted. |
| 0xC0060010 | While validating that %2 was really a serial port, the baud rate register could not be set consistantly.The device is assumed not to be a serial port and will be deleted. |
While validating that %2 was really a serial port, the baud rate register could not be set consistantly.The device is assumed not to be a serial port and will be deleted. |
| 0xC0060011 | Some firmware configuration information was incomplete. |
Some firmware configuration information was incomplete. |
| 0xC0060012 | No Parameters subkey was found for user defined data. This is odd, and it also means no user configuration can be found. |
No Parameters subkey was found for user defined data. This is odd, and it also means no user configuration can be found. |
| 0xC0060013 | Specific user configuration data is unretrievable. |
Specific user configuration data is unretrievable. |
| 0xC0060014 | On parameter %2 which indicates a multiport card, must have a port index specified greater than 0. |
On parameter %2 which indicates a multiport card, must have a port index specified greater than 0. |
| 0xC0060015 | On parameter %2 which indicates a multiport card, the port index for the multiport card is too large. |
On parameter %2 which indicates a multiport card, the port index for the multiport card is too large. |
| 0xC0060016 | The bus type for %2 is not recognizable. |
The bus type for %2 is not recognizable. |
| 0xC0060017 | The bus type for %2 is not available on this computer. |
The bus type for %2 is not available on this computer. |
| 0xC0060018 | The bus specified for %2 does not support the specified method of interrupt. |
The bus specified for %2 does not support the specified method of interrupt. |
| 0xC0060019 | User configuration for parameter %2 must have %3. |
User configuration for parameter %2 must have %3. |
| 0xC006001A | The user specified port for %2 is way too high in physical memory. |
The user specified port for %2 is way too high in physical memory. |
| 0xC006001B | The status port for %2 is way too high in physical memory. |
The status port for %2 is way too high in physical memory. |
| 0xC006001C | The status port for %2 overlaps the control registers for the device. |
The status port for %2 overlaps the control registers for the device. |
| 0xC006001D | The control registers for %2 overlaps with the %3 control registers. |
The control registers for %2 overlaps with the %3 control registers. |
| 0xC006001E | The status register for %2 overlaps the %3 control registers. |
The status register for %2 overlaps the %3 control registers. |
| 0xC006001F | The status register for %2 overlaps with the %3 status register. |
The status register for %2 overlaps with the %3 status register. |
| 0xC0060020 | The control registers for %2 overlaps the %3 status register. |
The control registers for %2 overlaps the %3 status register. |
| 0xC0060021 | Two ports, %2 and %3, on a single multiport card can't have two different interrupts. |
Two ports, %2 and %3, on a single multiport card can't have two different interrupts. |
| 0xC0060023 | Parameter %2 data is unretrievable from the registry. |
Parameter %2 data is unretrievable from the registry. |
| 0xC0060024 | While validating that %2 was really a serial port, the contents of the divisor latch register was identical to the interrupt enable and the receive registers.The device is assumed not to be a serial port and will be deleted. |
While validating that %2 was really a serial port, the contents of the divisor latch register was identical to the interrupt enable and the receive registers.The device is assumed not to be a serial port and will be deleted. |
| 0xC0060025 | Could not translate the user reported I/O port for %2. |
Could not translate the user reported I/O port for %2. |
| 0xC0060026 | Could not get the user reported interrupt for %2 from the HAL. |
Could not get the user reported interrupt for %2 from the HAL. |
| 0xC0060027 | Could not translate the user reported Interrupt Status Register for %2. |
Could not translate the user reported Interrupt Status Register for %2. |
| 0xC0060028 | Could not report the discovered legacy device %2 to the IO subsystem. |
Could not report the discovered legacy device %2 to the IO subsystem. |
| 0xC0060029 | Error writing to the registry. |
Error writing to the registry. |
| 0xC006002C | Could not report device %2 to IO subsystem due to a resource conflict. |
Could not report device %2 to IO subsystem due to a resource conflict. |
| 0xC006002D | The serial driver detected a hardware failure on device %2 and will disable this device. |
The serial driver detected a hardware failure on device %2 and will disable this device. |